chore(sagasmith): lock modern MCP component set

[dajiaohuang]

Summary

• replace the old v2 component manifest with an unpublished sagasmith.release-lock/v3 compatibility lock pinned to the merged Core, D&D, CoC, and Narrative modern commits
• require MCP 2026-07-28, auth-context v2, and sagasmith.authoritative-mcp/v2; reject unknown, archived, missing, or mis-profiled release inputs before cloning
• make owned Local Kit definitions use exact target-service audiences and modern protocol mode, and update the external AuthBridge plus local Agent wrapper to sign target-specific v2 delegations while preserving the explicit legacy v1 adapter
• keep requester, resource owner, and acting Host as distinct v2 identity fields; a player is the requester while workload:sagasmith-agent is the acting Host, and legacy actor_principal remains only a requester compatibility alias
• force both release-lock and latest-main real-domain CI lanes through all 42 Host/domain/transport combinations on MCP 2026-07-28; keep the separate dual-era contract test for legacy compatibility
• update English and Chinese configuration, deployment, upgrade, rollback, stable-catalog, and component-lock documentation and templates

Locked dependencies

• Core: 0ac316655687757203a9df1b2eb81669ec1d2d78 (feat(auth): add audience-bound host delegations Sagasmith-core#11)
• D&D: dd31d809cf406d9af99eb6c3fea176c33e16fee2 (feat(mcp): add MCP 2026-07-28 dual-era boundary Sagasmith-dnd#15)
• CoC: 492be2073a2b9bb3191111c470514e63c088d59f (feat(mcp): add request-scoped 2026 protocol support Sagasmith-coc#10)
• Narrative: c15fb2400407986b457d5406b76f9c3dae5b5358 (feat(mcp): add request-scoped 2026 protocol support sagasmith-narrative#7)

All four commits were verified as the current default-branch tips before this PR was created. None of the repositories is archived or a fork.

Validation

• focused Agent/Hosted/MCP/local-stack regression before the identity correction: 184 passed
• focused v2 identity, AuthBridge, Host-contract and channel regression after the correction: 36 passed
• Hosted worker regression: 12 passed
• real locked stack materialize/install/start/doctor: passed with exact component revisions and all owned MCP definitions on 2026-07-28
• required real-domain release-lock matrix: 42 passed (7 Hosts x 3 domains x stdio/Streamable HTTP); the matrix now also requires distinct requester/resource-owner/Agent-acting-Host values in every modern receipt
• additional lock/Host contract collection: 53 passed, 35 skipped
• Ruff: passed
• wheel build with NANOBOT_SKIP_WEBUI_BUILD=1 plus scripts/verify_wheel.py: passed
• git diff --check: passed

Cross-repository semantic boundary

This Agent change signs and transmits the three identities correctly. It does not claim to change domain authority attribution by itself: the locked Core revision currently derives its compatibility AuthContext.actor_principal from requester_principal, and the three domains bind their authoritative actor check to that compatibility field. A follow-up Core change is required to define the v2 compatibility actor as acting_host_principal while retaining requester and resource owner for authorization and audit. The real-domain receipt assertions in this PR preserve explicit evidence of all three original fields so that follow-up can be verified without conflating them.

Rollout and rollback

This PR does not publish a package, image, tag, GitHub Release, or deployment. The manifest explicitly records release_status: compatibility-lock-not-published. For an emergency protocol rollback, retain the same pinned repositories and signed authorization while setting an affected server to explicit legacy mode; archived split repositories and Mcp-Session-Id are not authority fallbacks.