Participant: codex (AI agent)
Understanding
Todo2code currently has two simultaneously true but incompatible identities.
Release and SDK metadata say 0.5.1, while the runtime constant, CLI and every
new provenance envelope say 0.5.0. doDSL is not inventing the older value;
it reads it from the pinned todo2code CLI and binds it to the exact analysed Git
commit and tree.
Changing one string would make the immediate output look correct but would not
prevent the next partial release. The repair therefore needs a deterministic
version contract plus removal of current-version literals from behavioral
tests. Historical artifacts must not be rewritten.
Execution plan after approval
- Create separate
core-dsl, extractors and runtime tickets with
ticket-058 as their integration coordinator.
- Align the core runtime version and replace only current-behavior literals in
the owning test workstreams.
- Once the active integration reservation permits it, add the no-dependency
version verifier, focused negative fixtures and the root verify hook.
- Run focused tests,
npm run verify, governance, Docker smoke and both E2E
profiles.
- Rebuild the todo2code image consumed by doDSL, compile a fresh candidate and
verify the resulting DevelopmentEvidenceDSL identity and safety fields.
Actual changes
- Audited all release/runtime declarations at exact main HEAD.
- Identified the release commit that introduced the mismatch.
- Confirmed the live CLI emits
todo2code 0.5.0 while package and VERSION are
0.5.1.
- Confirmed doDSL faithfully persists that emitted producer version.
- Created planning evidence only; no implementation file changed.
- Recorded the human approval of this plan and authorization to create the
three owner-workstream tickets.
Blockers
- Ticket-054 currently reserves the
integration workstream. The approved
--force-new exception created this ticket but does not silently
override active-scope enforcement.
- Each non-integration path requires its owning workstream ticket.