Skip to content

feat(platform): expose deployment command controls - #18

Open
MarcStdt wants to merge 2 commits into
mainfrom
codex/platform-command-controls
Open

MarcStdt wants to merge 2 commits into
mainfrom
codex/platform-command-controls

Conversation

@MarcStdt

@MarcStdt MarcStdt commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Add typed WIT and TypeScript bindings for ensureFileService, addAndRunCommand, and stopCommand.
  • Keep the three platform examples synchronized and add a release changeset.
  • Cover defaults, optional IDs, environment tuples, watch/stop forwarding, and async failures through the real async bridge.

Verification

  • npm test: 25 tests pass.
  • npm run build -- --force: all six packages build successfully.
  • git diff --check passes.

Cross-repository dependency

The Scrolls config editor uses ensureFileService. Publish the corresponding package through the normal release workflow, then refresh the Scrolls public dependency lockfile before merging/releasing that consumer. No package release or merge has been performed.

Clean-checkout CI follow-up

The first CI run exposed a test-only workspace-resolution issue: Vitest resolves the mocked component package before applying the mock, but CI runs tests before generating dist. A source alias fixes this without changing production code. Reproduced red in a fresh durable checkout with npm ci; all 25 tests then passed with no component dist output. The fix is pushed in 6ca0cc2; fresh remote matrix results are separate.

Vitest resolves mocked packages before applying mocks. Point the workspace alias at source so clean CI tests do not require dist output.
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