feat: add Open GameStudio Codex port

This commit is contained in:
MerlinH
2026-05-27 22:58:48 +00:00
parent 38fd33394a
commit f8530077d9
12 changed files with 113 additions and 33 deletions
+1 -1
View File
@@ -15,4 +15,4 @@ npm run validate
Keep generated projects under `projects/<slug>/`.
The first build intentionally excludes planner commands, direct Codex execution, telemetry, parallel orchestration, changed-file tracking, and ownership enforcement.
The first build includes direct Codex execution through `run --exec`. It still intentionally excludes planner commands, telemetry, parallel orchestration, changed-file tracking, and ownership enforcement.
+4 -4
View File
@@ -8,16 +8,16 @@ npm exec open-gamestudio -- status --project projects/my-game
npm exec open-gamestudio -- validate --project projects/my-game
```
Prepare a bounded prompt packet:
Run a role agent directly through Codex:
```bash
npm exec open-gamestudio -- run market_analyst --project projects/my-game --task "Create the initial market overview."
npm exec open-gamestudio -- run market_analyst --project projects/my-game --task "Create the initial market overview." --exec
```
Manual external Codex command; `open-gamestudio` does not spawn Codex in the first build:
Inspect the bounded Codex prompt packet first:
```bash
codex exec --cd projects/my-game "Read .gamestudio/runs/<run-id>/prompt.md and perform the requested task."
npm exec open-gamestudio -- run market_analyst --project projects/my-game --task "Create the initial market overview." --dry-run
```
Discover templates:
+3 -1
View File
@@ -12,4 +12,6 @@ Legacy validation depended on Python and shell assumptions. This port is TypeScr
Intentional omissions for the first build: no interactive `menu`, no `startover`, no generated `project_orchestrator.md`, no exact `template_info.md`, no eager competitor reports during init, and no upstream license/authorship/citation parity documents.
Future-only features are not implemented in this build: planner/`next`, telemetry, direct Codex execution, parallel orchestration, changed-file tracking, prompt-size metrics, and hard output-ownership enforcement.
Codex-native difference: `run --exec` invokes `codex exec` directly against the generated bounded prompt packet instead of requiring a separate manual command.
Future-only features are not implemented in this build: planner/`next`, telemetry, parallel orchestration, changed-file tracking, prompt-size metrics, and hard output-ownership enforcement.
+4 -8
View File
@@ -1,18 +1,14 @@
# Migration From Claude-Oriented Game Studio
Use the canonical TypeScript CLI:
Use the canonical TypeScript CLI with direct Codex execution:
```bash
npm exec open-gamestudio -- init --name "My Game" --engine godot --mode prototype --non-interactive --competitor "Mini Metro"
npm exec open-gamestudio -- run market_analyst --project projects/my-game --task "Create the initial market overview."
npm exec open-gamestudio -- run market_analyst --project projects/my-game --task "Create the initial market overview." --exec
```
Manual external Codex command; `open-gamestudio` does not spawn Codex in the first build:
```bash
codex exec --cd projects/my-game "Read .gamestudio/runs/<run-id>/prompt.md and perform the requested task."
```
For inspection-only runs, omit `--exec` or add `--dry-run` to view the generated Codex prompt packet and metadata path before execution.
Intentional differences: no interactive menu, no `startover`, no exact `template_info.md`, no eager competitor reports during init, and no generated `project_orchestrator.md`.
Future-only features are not implemented: `open-gamestudio next`, `run --exec`, telemetry, parallel orchestration, changed-file tracking, and ownership enforcement.
Future-only features are not implemented: `open-gamestudio next`, telemetry, parallel orchestration, changed-file tracking, and ownership enforcement.
+3 -3
View File
@@ -2,15 +2,15 @@
Validation exits nonzero when any check fails.
Repo validation checks package scripts, build output, NodeNext import specifiers, package assets, engine configs, base agents, templates, package packing, and installed-bin asset loading.
Repo validation checks package scripts, build output, NodeNext import specifiers, package assets, engine configs, base agents, templates, package packing, installed-bin asset loading, and direct Codex execution exposure.
Project validation checks schema-valid config, active agents, engine source root, engine project file, materialized agents, project `AGENTS.md` provenance and config hash, market seed, starter GDD, timeline sections, and read-only `status`/`resume` behavior.
Absence checks:
CLI surface checks:
```bash
npm exec open-gamestudio -- run --help | grep -- "--exec"
! npm exec open-gamestudio -- --help | grep -E " next|telemetry"
! npm exec open-gamestudio -- run --help | grep -- "--exec"
```
No generated `project_orchestrator.md` is required or produced.