feat(cli): publish workday profile operator commands

[adrianwebb]

Outcome

Adopt exact published SDK116, regenerate canonical command docs/tree/completions, and prepare CLI82. No duplicated source policy or credential implementation. npm lock metadata normalized; version comparison confirms onlyCLI/SDK versions changed.

Work authority

• Work item / Issue: Closes Publish SDK116 workday profile operator commands and acceptance diagnostics #197; Capacity execution: isolated cached source workspaces and research-capable agents platform#501
• Proposal / decision: User-authorized source isolation migration and bounded work/review acceptance.
• Assignment / checkpoint: N/A — local operator integration under the parent issue.
• Actor: Codex through adrianwebb
• Human authority: adrianwebb
• Agent / capacity provider: Codex desktop
• Exact base ref: staging 5672e9f
• Exact head ref: codex/workday-profile-cli ec7d5b6
• Agent-authored under human authority

Plan

Implement explicit source-policy reconciliation, verify identity/ref/check boundaries and replay, publish exact protected artifacts, then managed acceptance. Workday execution remains separately admitted.

Changes and commits

ec7d5b6: Adopt exact published SDK116, regenerate canonical command docs/tree/completions, and prepare CLI82. No duplicated source policy or credential implementation. npm lock metadata normalized; version comparison confirms onlyCLI/SDK versions changed.

Verification

• I ran the narrowest relevant package verification and documented any checks that could not be run.
  npm run release:verify passed:168tests, strict build/architecture and packed-install bin smoke. Candidate CLI successfully listed and reconciled/replayed local SDK source profiles through authorized API; no workday launched.

Risk and rollback

No schema migration, credential reentry, content deletion or automatic workday start. Keep team and software source authority explicit; reject library substitution and unknown/moved refs. Revert application/dependency commit via PR if needed; retain accepted policy generations and receipts. Released acceptance remains pending.

Completion summary

Implementation and local verification complete. Required Actions and exact coordinated release remain.

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.