Skip to content

Extract the Codex plugin into mainsequence-codex-plugin (0.3.0) - #12

Merged
MainSequenceDev merged 1 commit into
mainfrom
codex/extract-codex-plugin
Oct 21, 2026
Merged

MainSequenceDev merged 1 commit into
mainfrom
codex/extract-codex-plugin

Conversation

@MainSequenceDev

Copy link
Copy Markdown
Contributor

Summary

Devtools becomes a pure library plus the ms-devtools terminal CLI, and each host owns its releases, as Claude Desktop already does. The Codex adapter, its presentation layer, the --codex-hook runner branch, manifests/codex, the plugin build, pack and host-verification scripts, the Codex tests and the Codex assertions in check-release and verify-package move to mainsequence-sdk/mainsequence-codex-plugin (mainsequence-sdk/mainsequence-codex-plugin#1), which pins and vendors this package.

  • parseArguments, tokenizeCommand and HELP are exported from the package entry; tests/arguments.test.cjs covers them and the terminal runner.
  • Package files are dist, README.md, LICENSE and NOTICE; .codex-plugin, hooks, skills, assets, build-info.json and docs leave files and .gitignore.
  • .agents/plugins/marketplace.json stays here, because people added the marketplace by this repository's URL. It still points at devtools 0.2.8, the last package that carries the plugin; check-release refuses any newer devtools pin and accepts the new package once the marketplace change (Point the Codex marketplace at mainsequence 0.3.0 (merge after publishing) #13, stacked on this branch) lands after publication.
  • verify-package asserts the npm archive carries no plugin files and that the packaged runner refuses --codex-hook.
  • ADR 0003 records the decision, the plugin rename to mainsequence (owner's decision; a new plugin in Codex, with the migration note in the plugin repository), the publish order and the verification. ADR 0001, the roadmap, the README and the phase-2 documents point to the new repository; the moved ADR 0002 and MCP guide leave stubs.

Verification

npm run release:check under Node 22.22.0 / npm 11.6.2: type-check, 111 tests, release metadata and marketplace checks, npm pack (58 files) and the isolated-consumer check of the archive. The packed 0.3.0 archive (integrity sha512-0aLOykrjmMgpB0IP5awhqCGiQH0wsNDpblqK7qi3nNPeeYWAW0nyHDL1zANfTlfXhC2EUArEJeCuyIsqANCZQw==) built the Codex plugin 0.3.0 and passed its installed-host checks.

Publish order

  1. Merge this and tag v0.3.0 here (the release workflow publishes with provenance).
  2. Confirm the Codex repository's lockfile integrity matches the registry archive, then tag v0.3.0 there.
  3. Merge the marketplace pull request.

VS Code and Claude Desktop keep their 0.2.8 pins until 0.3.0 is on npm.

🤖 Generated with Claude Code

Devtools is now the shared library plus the ms-devtools terminal CLI. The
Codex adapter, its presentation layer, the --codex-hook runner branch, the
manifests, skills and icons, the plugin build, pack and host-verification
scripts and the Codex tests move to mainsequence-sdk/mainsequence-codex-plugin,
which pins and vendors this package like Claude Desktop does.

- Export parseArguments, tokenizeCommand and HELP from the package entry so a
  host runner parses the same command line; tests/arguments.test.cjs covers
  them and the terminal runner
- Package files are dist, README, LICENSE and NOTICE; the plugin-only paths
  leave package.json and .gitignore
- check-release validates the Codex marketplace file, which stays here
  because people added it by this repository's URL, against the published
  packages; verify-package asserts the archive carries no plugin files and
  that the packaged runner refuses --codex-hook
- ADR 0003 records the decision, the plugin rename to `mainsequence`, the
  publish order and the verification; ADR 0001, the roadmap, the README and
  the phase-2 documents point to the new repository, and the moved ADR 0002
  and MCP guide leave stubs behind

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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