Fix compound work routing and active amendments

[Lucas1479]

Summary

• treat the first role control proposal as the single action-existence gate for compound authority while preserving per-clause operations and Project/WorkItem references
• pass exact current-user clauses to ordinary compound operations so fragmented role tags cannot dispatch only part of one deliverable
• expose an identity-free unique active-goal summary to ControlDecision so in-flight requirement changes resolve as amendments
• make reference-blocked narration operation-scoped instead of falsely claiming that no sibling work started

Regression coverage

• duplicate streamed DELEGATE gates collapse to one turn gate
• a desktop game request retains the complete user instruction instead of only its export/visual fragment
• a multiplayer follow-up is corrected from execute plus Project to amend plus the unique active WorkItem, even with a prior blocked message in history
• confirmed go-ahead turns retain their grounded prior payload

Verification

• 117 control, routing, and amendment tests passed
• 69 multi-turn Session, Project, WorkItem, Provider continuity, history, and routing tests passed
• 106 Attach, External Attach, Launch, Bundle, lifecycle, and Work/AUIP cross-axis tests passed
• 129 AppSession role-branch, control, engagement, managed-core, and Web SDK tests passed

No public authority boundary or lifecycle contract changes; SEMANTIC_SNAPSHOT.md does not require an update.

[Lucas1479]

Maintainer self-review completed; no blocking findings.

Bypass rationale: I am the current product-semantic owner for this routing boundary and no independent reviewer with equivalent context is available. The bypass is used only for the approval requirement, not to skip freshness, CI, conflict, or conversation checks.

Reviewed invariants:

• one role proposal remains only the action-existence gate; canonical compound authority still owns per-clause control
• exact current-user clauses replace fragmented role payloads without changing grounded prior-payload continuity
• the unique active goal is identity-free, bounded, and explicitly untrusted
• Project/WorkItem identity remains Host-grounded; ambiguity still fails closed

Local verification on current public/main base:

• Ruff: passed
• changed control/routing tests: 56 passed
• AUIP, launch, amend, and WorkItem continuity tests: 87 passed
• git diff --check: passed

Required GitHub checks build and cpu-model-less are green. Rollback is the single squash commit revert.