Skip to content

Clean up runtime boundary naming#1223

Open
chubes4 wants to merge 1 commit into
mainfrom
cleanup/runtime-boundary-names-20260619
Open

Clean up runtime boundary naming#1223
chubes4 wants to merge 1 commit into
mainfrom
cleanup/runtime-boundary-names-20260619

Conversation

@chubes4

@chubes4 chubes4 commented Jun 19, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Replace WPSG/Data Machine-specific fixtures and public examples with neutral sample runtime names.
  • Remove the --data-machine and --data-machine-code public CLI aliases; document --component <slug>=<path> as the neutral replacement.
  • Tighten production boundary enforcement to catch hyphenated Data Machine names in package sources.

Tests

  • npm run test:production-boundary-enforcement
  • npx tsx scripts/component-plugin-entrypoint-contract-smoke.ts
  • npx tsx scripts/agent-runtime-diagnostics-summary-smoke.ts
  • npm run test:runtime-recipe-resolver
  • npx tsx scripts/task-input-contract-smoke.ts
  • npm run test:materialize-replay-package-command
  • npm run build

AI assistance

  • AI assistance: Yes
  • Tool(s): OpenCode (gpt-5.5)
  • Used for: Drafted and applied the runtime boundary naming cleanup, fixture updates, and focused verification steps. Chris remains responsible for review and merge.

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