fix(workdays): settle terminal reporting failures

[adrianwebb]

Outcome

Failed reporting can end a settled workday as failed instead of hanging forever.

Work authority

• Work item / Issue: Implement the minimal AgentKernel, profile, and workday architecture platform#520
• Proposal / decision: N/A — operator-requested allocation acceptance repair, not a golden deliverable.
• Assignment / checkpoint: interrupted SDK workday b924a482-351e-4dc2-a84a-57156a6535ca
• Actor: Codex
• Human authority: @adrianwebb
• Agent / capacity provider: operator Codex task; dev2 managed acceptance
• Exact base ref: staging 727d386
• Exact head ref: 31382e0

Contributor mode (select one):

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

Plan

Repair the observed acceptance failure through the existing runtime path. Local verification complete; merge after required Actions, then verify managed local recovery. No tags or releases.

Changes and commits

31382e0: Reuse terminal graph and reservation states; successful reporting remains the only success path; add four negative lifecycle cases.

Verification

Eight focused lifecycle tests, npm run build, and git diff --check passed.

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

Risk and rollback

No database, credential or contract migration. Revert 31382e0 through a PR and rebuild the same managed live target. No purge or bootstrap reinstall.

Completion summary

Bounded repair verified locally. Integrated golden lifecycles remain unproven and are not claimed as complete by this PR.

AGPL committer authorization

Base-owned workflow retains provider-authenticated author authorization.

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.