fix(supervise): preserve cloud director continuity and scoped access

[drewstone]

Change

Keep a retained provider director's environment and conversation across deliberate re-prompts.
Mint a new execution and turn for new work, and replay the same identities after interruption.
Use the existing scope settlement policy for final cleanup, including explicit unconfirmed releases.

Bind default coordination credentials to the live scope and its original deadline.
Keep explicit finite TTLs, scope and audience checks, and revocation.
Reject alternate signature encodings that could bypass listener-local revocation.

Adopt published Knowledge 17.0.2, which rejects malformed write proposals before modifying memory.
The shared dependency catalog also requires a patch version for agent-bench.
No Discovery runner, provider-specific continuation loop, or Sandbox change is added.

Evidence

• Three deliberate director turns: one environment, one session, three executions, one final submission.
• Controller loss after the second environment admission: exact turn recovered, two total dispatches, one environment.
• Release, keep, failed cleanup, and overlapping environment IDs across owners/providers.
• Real authenticated HTTP after three simulated hours, explicit expiry, restart, and revocation denial.
• Existing-environment intent replay refuses changed material and preserves the workspace after a rejected dispatch.
• Independent source reviews approved auth and continuity/cleanup after their findings were fixed.
• Integrated focused run: 147/147 passed across five files, including upstream native transcript capture.
• Broader prior affected run: 305/305 passed across nine files.
• Typecheck, lint, build and generated API records checked locally.
• Full serialized local suite and packed-package verification are in progress; final results will be appended before merge.

Knowledge release proof: tangle-network/agent-knowledge#213 (comment)

Refs #1246 and #1245.
These issues remain open pending live cloud acceptance; simulated time is not a multi-hour production result.
Related system issue: SYS-011 — outcome: mitigates — proof: retained owner recovery tests and this PR.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.