feat(workdays): high-level allocation inputs

[adrianwebb]

Outcome

Expose high-level workday allocation inputs without manual assignment durations.

Work authority

• Work item / Issue: Implement the minimal AgentKernel, profile, and workday architecture platform#520
• Proposal / decision: User-approved Integrated Workday Allocation and Capability Accounting plan.
• Assignment / checkpoint: N/A — direct implementation before golden acceptance.
• Actor: Codex
• Human authority: Adrian Webb, workspace user; explicitly authorized implementation
• Agent / capacity provider: N/A — desktop implementation.
• Exact base ref: staging 9d3a7d7
• Exact head ref: codex/workday-allocation-inputs 85bd290

Contributor mode (select one):

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

Plan

Bind planning percentage, allocation weight, turn ceiling, and project/class targets. Reuse canonical SDK policy validation. Integrated admission and provider enforcement remain pending in the owning packages.

Changes and commits

85bd290 adds finite numeric/JSON input transforms and pre-request policy validation. Requires SDK PR #309 contracts; no package version or release tag changed.

Verification

Local current SDK development overlay: node --import tsx --test tests/unit/command-boundary/workdays/selection.test.ts — 13/13 pass. Valid nested inputs reach the API; malformed JSON and invalid shares never invoke it. Actions and published dependency alignment pending. Existing generated documentation changes were preserved, not included.

Risk and rollback

Do not promote before coordinated allocation acceptance. Revert this commit with its SDK command-binding changes if abandoning the contract. No database mutation or secret material is introduced.

Completion summary

CLI input tranche implemented and locally tested; complete allocation migration and golden acceptance remain pending. No RC or tags.

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.