Move optional workload systems out of the mandatory runtime core
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- build-system, cli, tooling
Research direction
Start by mapping the optional systems currently owned by runtime-core, runtime-playground, and the CLI, separating generic runtime primitives from workload policy. Review the existing public contracts, commands, capabilities, exports, and tests before defining extension package boundaries. Done means optional packages build and test independently, existing workflows migrate, and the acceptance criteria are met without loading workload policy in the default core/runtime/CLI.
Written by the indexing model from the issue text.
Description
Parent: #2429
Problem
runtime-core now owns substantial fuzz-suite execution and builders, adversarial campaigns, benchmark contracts/substrates, WordPress discovery plans, browser exploration contracts, and specialized quality artifacts. runtime-playground and the CLI contain their corresponding runners and commands.
These systems are valuable, but they are optional workloads built on Codebox. Making all of them part of the mandatory core contract and CLI expands dependencies, commands, schemas, tests, documentation, and release risk for every consumer.
The architecture already says Codebox is not an evaluation harness. Core should provide composable runtime primitives; workload packages should provide evaluation policy and orchestration.
Desired shape
Keep generic primitives in core:
- bounded command execution;
- observations and evidence references;
- transport-fault and service-control interfaces where backend-neutral;
- snapshots/checkpoints;
- artifact integrity and provenance;
- runtime capability negotiation.
Move optional systems into independently built extension packages inside the monorepo, beginning with:
- fuzzing and WordPress fuzz-suite builders;
- adversarial campaign orchestration;
- benchmark orchestration and scoring-oriented contracts;
- specialized visual-comparison and adaptive-exploration policy above generic browser capture.
Acceptance criteria
- The default core/runtime/CLI can execute a contained WordPress command without loading optional workload packages.
- Optional workload packages depend on public Codebox contracts and register commands/capabilities through an extension mechanism.
- Generic browser capture and runtime observations remain available without importing quality-suite policy.
- Fuzz, adversarial, benchmark, and specialized visual systems have independent builds and tests.
- Existing public workflows migrate before old core commands and exports are removed.
runtime-corehas a documented size/responsibility budget preventing workload policy from returning to the mandatory package.
AI assistance
- Model: OpenAI gpt-5.6-sol
- Tool: OpenCode
- Used for: Classified mandatory runtime primitives versus optional workload systems and drafted the extension extraction tracker under Chris Huber's direction.
- Dominant language
- TypeScript
- Stars
- 18
- Forks
- 4
- Avg merge
- 1h 39m
- Merged PRs (30d)
- 45
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Automattic/wp-codebox
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Automattic/wp-codebox#2531 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Automattic/wp-codebox#2467 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Automattic/wp-codebox#2466 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Automattic/wp-codebox#2105 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Automattic/wp-codebox#2061 ·
Maintainers usually reply within 1 day
All issues in Automattic/wp-codebox
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
[Bug] remember() with special characters in namespace hangs until timeout instead of returning 400Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MystenLabs/MemWal#1133 · 1 comment ·
Maintainers usually reply within 1 day
-
bug user-priority/P2
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Effect-TS/effect#8881 · 1 comment ·
Maintainers usually reply within 1 day