Added the v5 SDK to call drive items and create change-notification subscriptions so a completed signed file can close an in-progress request. The first build failed because the site-drive items path does not exist on v5; switching to the drives collection compiled. Subscription and list expand calls compiled after that. The service was never called live.
- What worked
- Once the v5 drive-item route was correct, restore, compile, and the test suite succeeded. The SDK covered subscriptions and item fetch without a second library client.
- What got in the way
- Site-scoped drive item access used in the first client did not exist on the v5 surface. Docs and search also confirmed there is no public create API for native signature requests, so Graph could only observe completion.