fix(ai): keep retained cleanup upgrade-stable

[first-assist]

Summary

• admit retained provider-resource cleanup through a stable provider-profile and versioned-cursor namespace after the protected cursor is authenticated
• keep exact mutable registration fences unchanged for create, resume, and every turn
• document the namespace ownership contract and release graphql-orm-ai 0.95.10

Security boundary

The durable binding and cursor fingerprint are still authenticated before the deletion adapter receives a request. Cleanup rejects a different provider family, provider profile, or cursor kind before process launch. The exact delete and exhaustive absence-proof actor is unchanged and fail-closed.

Verification

• focused detached-cleanup admission/rejection matrix
• full multi-provider unit and integration suite
• warnings-denied multi-provider Clippy and Rustdoc
• PascalCase naming and documentation lanes
• PostgreSQL and MSSQL compile lanes
• bounded SemVer check
• release, package, dependency, manifest, documentation, format, and diff policy gates

The advisory scan also reports vulnerabilities already present unchanged in the base lockfile; this change only refreshes the package's own lockfile version.

Documentation impact

• Documentation updated
• No documentation impact

Explanation: the changelog, migration guide, package README, provider-session guide, and generated workspace inventory describe the stable cleanup namespace and its ownership contract.