Skip to content

Release v2.0.0 — README and add-command corrections - #51

Merged
r-bart merged 2 commits into
mainfrom
develop
Aug 20, 2026
Merged

Release v2.0.0 — README and add-command corrections#51
r-bart merged 2 commits into
mainfrom
develop

Conversation

@r-bart

@r-bart r-bart commented Aug 20, 2026

Copy link
Copy Markdown
Owner

Follow-up to #50, before v2.0.0 reaches npm. The tag was pulled and the gated publish
cancelled, so nothing has been released — this lands on top and the tag moves here.

Two things #50 shipped wrong

devtronic add codex answered "Unknown IDE." add kept a private copy of the IDE list
and never received codex, so the release's own new target was reachable from init and from
nowhere else. Both commands now read one exported IDE_OPTIONS.

The npm README contradicted the package it ships with. It promised Node.js >= 18.0.0
against an engines of 20 — the exact requirement this release breaks — omitted Codex and the
portable skill export, and listed recap as an orchestration addon skill.
docs/customization.md, docs/plugins.md and docs/skills.md carried the same stale listing,
and the skill counts still counted the folded recap (9 addon → 8).

The root README was already correct; only the npm-facing one had been left behind.

The guard

documented-surface.test.ts (22 tests) joins the promise to the fact:

  • the README's stated Node requirement must equal engines.node
  • both READMEs must name every IDE in IDE_OPTIONS and every skill in ADDONS — and no skill
    an addon does not ship
  • IDE_OPTIONS must cover the IDE union, which is the drift that hid codex

Mutation-checked: restoring Node.js >= 18.0.0 and deleting the codex entry makes three
tests fail.

Verification

typecheck, lint, build clean. 1073 tests, 50 files.

r-bart added 2 commits August 20, 2026 06:27
`devtronic add codex` answered "Unknown IDE" for the whole release that
introduced Codex as a target. `add` kept a private copy of the IDE list and
never received the new entry, so `codex` was reachable from `init` and from
nowhere else. Both now read one exported `IDE_OPTIONS`.

The npm README — the package page — still promised `Node.js >= 18.0.0`
against an `engines` of 20, omitted Codex and the portable skill export, and
listed `recap` as an orchestration addon skill. Three docs carried the same
stale addon listing, and the skill counts still counted the folded `recap`.

`documented-surface.test.ts` joins the promise to the fact: the README's Node
requirement is checked against `engines`, both READMEs must name every IDE and
every addon skill, and the prompt list must cover the `IDE` union. All three
failures were present before the fix.
Same drift, third copy: `docs/cli-reference.md` listed the five IDEs `add`
used to accept. The guard now checks that list against `IDE_OPTIONS` too, so
the doc and the command cannot disagree about what `add <ide>` takes.
@r-bart
r-bart merged commit 572f800 into main Aug 20, 2026
6 checks passed
r-bart added a commit that referenced this pull request Aug 20, 2026
Renumbers the release from 2.0.0. `REMOVED_FILES` now names 1.5.0 as the
version that renamed `/loop`, `/recap` and `/design-system-sync`, so
`devtronic update` tells the user the right release, and the sample manifest
versions in the docs are refreshed to match.

The changelog leads the upgrade section with what the number does not say:
the release moves three skill names, two runtime paths and the Node floor.

Note: the merge commits on main from #50 and #51 carry "Release v2.0.0" in
their subjects. They are published history and are left as they are.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant