chore: align compact agql auth context

[first-assist]

Summary

• align every workspace and coexistence-fixture agql-auth site to merged 0.17.1 revision b792241b7d9bb46bad81dde4534ae5b39857f614
• patch-bump the co-versioned ORM/macros pair, the AI crate that publicly re-exports auth types, and the router adapter
• keep both lockfile changes minimal to source/package-version alignment only
• update package changelogs, migration notes, examples, implementation status, and generated inventory

Consumer neutrality

This preserves one generic agql-auth Rust type universe for all consumers. The upstream patch compacts default session-context serialization for every issuer; it adds no consumer policy, role/scope name, endpoint, cache behavior, or application identifier. ORM projection, AI authorization/rehydration, and router verification/expansion logic are unchanged.

The complete diff was grepped case-insensitively for gema, First Assist identifiers, and consumer scope strings; the result was empty.

Verification

• scoped cargo check for graphql-orm, graphql-orm-ai, and graphql-orm-router with both auth adapters
• graphql-orm auth library tests: 34 + 2 assurance tests passed before the unchanged local Rust 1.90 trybuild diagnostic wording mismatch
• exact backend coexistence fixture: passed, with one resolved agql-auth 0.17.1 source
• router auth-agql: 65 tests + binary smoke passed
• AI library: 247 tests passed
• warnings-denied Clippy: ORM and router passed; the unchanged AI source hits the existing local Rust 1.90 large_enum_variant diagnostic, while current stable CI owns that lane
• warnings-denied rustdoc: ORM, AI, and router passed
• documentation, generated inventory, package release policy, workspace dependency, formatting, and diff checks passed
• neutrality grep: empty

Documentation impact

• Documentation updated

Updated root and package changelogs/migration guides, dependency examples, AI implementation status, router guidance, and generated workspace inventory. No configuration, schema, persistence, authorization, provider, backup, or restore migration is required.