release(cli): rc81 with resilient sessions and current source contracts

[adrianwebb]

Outcome

Publish the already-merged Identity session preservation fix with SDK rc115 for the source-candidate host cutover.

Work authority

• Work item / Issue: Preserve authenticated sessions when discovery fails before token refresh #193; Capacity execution: isolated cached source workspaces and research-capable agents platform#501
• Proposal / decision: User-authorized managed source migration without repeated login loss.
• Assignment / checkpoint: Coordinated CLI rc81.
• Actor: adrianwebb
• Human authority: adrianwebb
• Agent / capacity provider: Codex workspace agent
• Exact base ref: badc74f
• Exact head ref: 120c0ea
• Agent-authored under human authority

Plan

Pin current SDK contracts, regenerate operator docs and command schema, pass full release verification, then publish exact staging artifacts for Platform selection.

Changes and commits

120c0ea bumps CLI rc81 and SDK rc115, with generated scope-option documentation. Includes #194 from its current staging base. Separate release worktree preserves unrelated local edits in the existing CLI checkout.

Verification

Full local verify:direct passed: file policy, strict build, CLI tests and package artifact verification. Exact-head Actions required before merge and publication.

Risk and rollback

No new credential storage mechanism or auth authority. Existing safe discovery failure behavior prevents invalidating a session before refresh begins. Previous immutable CLI remains rollback option. No credential values or host paths committed.

Completion summary

Release preparation complete; publish and select only after Actions. Full source send remains a host integration gate.

Submission checklist

• The change is bounded to the stated work item and target repository.
• Exact base and head refs are recorded and the branch is ready for review.
• Verification and compatibility evidence are recorded above.
• No plaintext secrets, credentials, machine state, or unrelated residue are included.
• Plan, status, commits, and completion summary form a complete durable record.
• Rollback or recovery steps are documented and executable.