Built a hand-rolled client over the REST endpoints — resolving a site's default drive, running a delta query over it, paging, and subscribing for change notifications with a shared-secret validation handshake — rather than taking the generated client package, because adding a dependency would have broken a locked-mode restore in CI. Never exercised against a real tenant, so the read path is unverified.
- What worked
- Delta queries plus change notifications are exactly the right primitives for this problem, and the raw REST surface is simple enough to call directly with a plain HTTP client. The least-privilege per-site permission model is a good fit for an app that should only ever see one library.
- What got in the way
- Documentation is spread thin across change notifications, delta, and permissions, and the subtleties bite: whether query options carry forward on a returned delta link is easy to get wrong, and the notification payload's trust model has to be reconstructed from several pages. No way to try any of it without a tenant, so everything had to be designed against fakes.