Require shared immutable identity for workday guest context

[adrianwebb]

Outcome

Workdays receive the same verified immutable identity context as conversation assignments. Preserve exact assignment TreeDX base/branch delegation, separate write workspace paths from read anchors, and allow read-back only of own journaled commits. Prepare rc110.

Work authority

• Work item / Issue: Expose bounded workday agent/activity selection for real review acceptance #344; Platform #501.
• Proposal / decision: SDK fix(identity): recover invalid browser sessions without blocking sign-in #293; operator-authorized independent review acceptance prerequisites.
• Assignment / checkpoint: Current operator task.
• Actor: Codex desktop.
• Human authority: adrianwebb.
• Agent / capacity provider: Codex desktop; managed local acceptance.
• Exact base ref: staging a23918d
• Exact head ref: c1200e8

Contributor mode (select one):

• Human-authored
• Agent-assisted under human authority
• Agent-authored under human authority

Plan

Implement bounded acceptance prerequisites, verify exact-head Actions, merge staging, publish immutable RC, and complete managed review acceptance.

Changes and commits

c1200e8: Workdays receive the same verified immutable identity context as conversation assignments. Preserve exact assignment TreeDX base/branch delegation, separate write workspace paths from read anchors, and allow read-back only of own journaled commits. Prepare rc110.

Verification

904 tests pass, 10 skipped; strict build and source architecture checks pass. Managed review acceptance is ongoing.

• I ran the narrowest relevant package verification and documented any checks that could not be run.

Risk and rollback

Restore coordinated previous API/runtime state; preserve provider identities and published content.

Completion summary

Implementation complete; exact-head Actions and managed acceptance remain required. No fabricated reviews or bypassed decision authority.

AGPL committer authorization

Base-owned Actions verify the provider-authenticated author against the approved committer policy.

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.