Record settled usage in agent terminal performance

[adrianwebb]

Outcome

Terminal assignment performance now reflects settled capacity usage rather than zero-filled completion input.

Work authority

• Work item / Issue: Implement the minimal AgentKernel, profile, and workday architecture platform#520
• Proposal / decision: SDK golden proposal golden-sdk-decision-governed-workday-intent; no accepted decision yet.
• Assignment / checkpoint: diagnostic assignment assignment_K_PAAJusvGNcLMiA2aihTan-HXeNuwoj; formal acceptance pending.
• Actor: Codex
• Human authority: adrianwebb
• Agent / capacity provider: SDK Architect / provider_-rcKRK8gG2NGnOU3yGu_CV3Wz7ACppTP
• Exact base ref: staging a9814b2
• Exact head ref: codex/agent-terminal-settlement-usage 8b61fb4

Contributor mode (select one):

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

Plan

Use the committed aggregate usage for terminal performance; test the projection, then verify a live SDK planning turn. Refreeze before formal golden acceptance.

Changes and commits

• 0dfc289: terminal ledger projection and regression test.
• 8b61fb4: comply with file-length policy.

Verification

• I ran the narrowest relevant package verification and documented any checks that could not be run.
• Focused Vitest: 1 passed; npm run build:dist, check:file-lengths, and check:file-architecture passed.
• Live development SDK Architect assignment: 61 active seconds, 459044 input tokens, 2141 output tokens in terminal performance, agreeing with result usage. Diagnostic workday stopped; full golden not passed.

Risk and rollback

No schema migration. Revert this commit to restore prior projection; capacity ledger remains intact.

Completion summary

Narrow repair verified. Platform #520 tracks unfinished formal golden acceptance.

AGPL committer authorization

The base workflow checks approved committer identity.

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.