prompter.json

{
  "instance_label": "boon-zig",
  "port": 4545,
  "command": [
    "co"
  ],
  "store_prompts": true,
  "backend": null,
  "supervisor_prompt": "Read AGENTS.md, PLAN.md, WORKLOG.md, plans/boon_zig_source_physical_ir_plan.md, plans/raybox_zig_implementation_plan.md, and plans/raybox_zig_16ms_runtime_plan.md. The active Boon runtime/transpiler source of truth is plans/boon_zig_source_physical_ir_plan.md on branch source-physical-ir; PLAN.md is supporting baseline context only. Raybox renderer and playground work now lives in this repo under raybox/ and is governed by the copied Raybox plan files. Continue runtime, transpiler, renderer, and playground development in this boon-zig checkout, not in the old sibling raybox-zig repo.\n\nContinue from the current repository state. First inspect git status and current diffs. Preserve user changes. Do not revert, reset, restore, rebase, force-push, or commit unless explicitly instructed in this session.\n\nImplement the branch plan in order, starting at the earliest incomplete item from WORKLOG.md and the active plan files. Keep the core Boon runtime/compiler renderer-neutral: src/ may expose generic host/runtime bridges but must not import SDL or raybox/. Raybox code may import the local Boon runtime host through src/root.zig. Plain zig build commands should work without -Dboon_zig_path.\n\nMake reasonable engineering decisions without asking unless genuinely blocked. Prefer existing repo patterns and keep edits scoped. Use Zig for repo automation/helper work where practical; shell is fine for simple orchestration. After Zig source changes, validate using current-code commands such as zig build run -- ..., zig build run-raybox, or relevant zig build steps, not stale zig-out binaries.\n\nRun the relevant checks for each completed slice, fix breakage, and update WORKLOG.md with phase/subphase, files changed, commands run, pass/fail results, risks, blockers, and the exact next step. For Raybox-related changes, include appropriate commands such as zig build bench-raybox-native, zig build verify-raybox-native-events, zig build verify-raybox-examples-native, zig build verify-raybox-physical-native, zig build verify-raybox-text-native, and zig build test-raybox.\n\nIf flaky automation, tooling, verification scripts, or test harnesses slow progress or make validation unreliable, fix them too when that helps development move faster and more reliably. If the implementation path starts looking too complex, too hacky, circular, or if you seem to be spinning, step back and reconsider the plan. Choose a simpler or more general direction that better matches the active plan files instead of forcing a local workaround.\n\nStop only when the active plan work is complete with evidence, or at a real blocker that cannot be solved locally. If stopping, leave the repo coherent, validated as far as possible, update WORKLOG.md, and state the exact next step.\n",
  "completion_condition": "+completed+",
  "completion_command": null,
  "completion_prompt": "Read AGENTS.md, PLAN.md, WORKLOG.md, plans/boon_zig_source_physical_ir_plan.md, plans/raybox_zig_implementation_plan.md, and plans/raybox_zig_16ms_runtime_plan.md. Do not implement new functionality yet. Audit the current repository state against the active Boon and Raybox plan files.\n\nUse plans/boon_zig_source_physical_ir_plan.md as the runtime/transpiler source of truth and the copied Raybox plan files as renderer/playground source of truth. Treat PLAN.md as supporting baseline context. Treat the old sibling raybox-zig checkout as migrated/archive context unless the user explicitly asks to work there.\n\nInspect git status and diffs first. Account for any uncommitted work separately from committed evidence. Check each required outcome against real code, real fixtures, build.zig steps, manifest/worklog state, benchmark JSON, and actual command results. Do not claim completion from plan text alone.\n\nRun the relevant verification commands needed for the audit. At minimum, verify formatting/diff cleanliness where applicable, corpus verification, existing tests, branch gate commands or documented mappings, and Raybox gates: zig build bench-raybox-native, zig build verify-raybox-native-events, zig build verify-raybox-examples-native, zig build verify-raybox-physical-native, zig build verify-raybox-text-native, and zig build test-raybox. If a named gate is missing, record it as a gap unless WORKLOG.md maps it to an equivalent existing command with coverage.\n\nReport:\n- selected active plans and why they win over nearby docs\n- current git state, including uncommitted files\n- phase-by-phase status: DONE, PARTIAL, NOT DONE, or BLOCKED\n- concrete evidence for every DONE item\n- remaining gaps ordered by importance\n- exact next implementation step\n\nDo not mark the active work complete unless every definition-of-done item has concrete evidence from code, manifests, tests, benchmark/report files, and command output.\n",
  "protected_patterns": [],
  "command_timeout_mins": 10
}