todo2code

Participant: codex (AI agent)

Understanding

todo2code is pinned to new-project 0.10.0 at 9706e63d5f121323e9087d0db47a16acdbd276bb. The published 0.11.0 package adds the canonical classification DSL, its schema and the current approval evidence contract. The adoption generator intentionally refuses the current target manifest until its declared standard version is reviewed and changed to 0.11.0.

Execution plan

1. After approval, transition ticket-044 to IN_PROGRESS / EDIT.
2. Change only the target manifest’s standard version, preserving customization.
3. Run local Goal’s immutable adoption adapter with --check, review the plan, then apply it with --upgrade.
4. Verify lock provenance and managed DSL hashes.
5. Run governance, focused/full Node checks and Docker smoke validation.
6. Publish a ticket-scoped PR for independent exact-head validation.

Actual changes

• User approval received; ticket transitioned to IN_PROGRESS / EDIT.
• Advanced only the standard version in the customized target manifest.
• Goal adopted the immutable 0.11.0 package and added the canonical package manifest, work-classification DSL and its schema to the managed lock.
• Repeated adoption check, governance, full Node verification and Docker smoke all pass.
• Koru and Validator approved exact head 80f860c; protected PR #58 merged as main@aae9ec5 and removed the implementation branch.

Blockers

• None.

Preflight evidence

• Docker client/server: 29.1.3 / 29.1.3.
• Global Goal lacks the governance command.
• Local .venv/bin/goal exposes governance adopt.
• Read-only adoption preflight stops on the expected 0.10.0 -> 0.11.0 manifest compatibility boundary before writing.
• Applied adoption is idempotent at exact release SHA cc9b04673bbd85cb4e35fb683d288ef34be1485f.
• Host verification required npm ci in the clean worktree; after dependency restoration all 391 tests completed without failures.

This site is open source. Improve this page.