Repository navigation
id: F12.15 id world dev: watch, rebuild, hot-swap, fixture replay, fuzz harness #558
Description
What and why
Watch the source, rebuild, hot-swap into a scratch world via F12.9 migration, replay fixtures on each change, and run a deterministic fuzz harness against declared invariants; edit-to-running under 3 s. Authoring today is compile, install, rejoin by hand. A tight loop is what makes the platform pleasant to build on.
Source
Current status
Not started. No Dev variant in WorldCommand (cli.rs:1388); id world compile and new exist (doc/2026-10-16T18-30-00Z_feature_world_authoring_cli/), but there is no watch/hot-swap.
Acceptance criteria
-
id world devwatches the source, rebuilds and hot-swaps into a scratch world through F12.9 migration - Fixtures replay on each change and failures are reported
- A deterministic fuzz harness runs against declared invariants
- Edit-to-running is under 3 s for an example
Size
L
Prerequisites
- id: Phase 12 designs to run through the research workflow #534 (tracking issue) — D1-027 F12.9 Program upgrade with state migration and rollback
- id(world): F11.16 replay self-check (
id world verify) #544 — D1-016 F11.16 Replay self-check (id world verify)
Metadata
Metadata
Assignees
Labels
Package/app: id (pkgs/ or apps/ in this repo)Large: multi-day or open-ended; expect staged check-insNew feature or requestNew feature or capability requestIntake review done: acceptance criteria, links, and normalized labels addedFully doable remotely: design, config, code, cloudOrg Project gate: queued next — orchestrator adds to the boardOrdinary priority (the default)Filed directly by a humanQueue or user escalation stateQueue packet kind: verify, reproduce, and route this item
Activity
dezren39 commentedon Oct 26, 2026
Intake review
Fleet-monitor intake pass (2026-10-26). Body already carries a full
## Acceptance criteriasection, so this pass is label normalization plus a liveness check — no body edit.Verified live on main
e3467560(2026-10-26):WorldCommandinpkgs/id/src/cli.rshas noDevvariant (current variants include Compile, New, Apply, Replay, Measure — no watch/hot-swap path). Still live, exactly as filed.Related: prerequisites #534 (F12.9 program upgrade with state migration — the hot-swap mechanism this rides on) and #544 (F11.16 replay self-check, the fixture-replay base) are both still open and unenriched; #544 is a sibling in this same F-series batch. This is the largest item in the batch (effort/l) and the most prerequisite-heavy.
Risks / notes: the under-3s edit-to-running target is the acceptance bullet most likely to slip; measure it on an example, not on a trivial program. The deterministic fuzz harness is separable and could land as its own follow-up if the loop itself proves out first.
Suggested approach: sequence after #534 and #544; build watch → rebuild → hot-swap into a scratch world first, wire fixture replay second, and treat the fuzz harness as the final layer.
3 remaining items
docs(id): design #558 local dev loop
dezren39 commentedon Nov 1, 2026
Design record:
doc/2026-11-01_design_id558.mddefines the localid world devarchitecture, trade-offs, invariants and implementation acceptance criteria.Recommends an offline, disposable scratch world; edits compile locally and use F12.9 migration, never a hosted-world install.
A candidate is promoted only when fixture replay and migration pass; failures preserve the last-good scratch world.
Adds a
dev-only cross-version regression mode because existing fixtures are module-hash-bound; normalreplay/verifystay strict.Deterministic, bounded fuzzing uses declared invariants and a reproducible seed, outside the default latency-critical loop.
The under-3s target includes compile, fixtures and migration; F12.9 #1066 (after #1064/#1065) gates hot-swap; #544 is complete.
Phases: (1) local scratch runner, (2) watch/rebuild/migrate, (3) fixture gate, (4) seeded fuzz/invariants, (5) end-to-end latency/docs.
PR: #3823
Questions for Drew: none required; the note records reversible defaults for local-only execution, fixture-failure gating and opt-in fuzzing.
dezren39 commentedon Nov 1, 2026
🤖 Agent note · handed off
id world dev: watch, rebuild, hot-swap, fixture replay, fuzz harness #558 claimed this shift, but revalidation shows the design work is already owned and done elsewhere: a full design record (doc/2026-11-01_design_id558.md) was posted on this issue at 2026-11-01T16:53Z with PR design(id): #558 local dev loop #3823 OPEN carrying it, and an earlier triage (task 2148) already recorded the confirmed verdict. No parallel design record from this lane — that would duplicate PR design(id): #558 local dev loop #3823.id world verify) #544 (the other prerequisite) is CLOSED.Merge pull request #3823 from developing-today/design/id-558
dezren39 commentedon Nov 3, 2026
agent-note:v1
state: triaged (coverage pass)
Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 40 (priority/normal). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
Found via: coverage pass 2026-11-03
dezren39 commentedon Nov 3, 2026
🤖 Agent note · triage verdict (task 7581)
id world dev: watch, rebuild, hot-swap, fixture replay, fuzz harness #558 itself.gh apiraw reads this run):Devvariant exists inWorldCommand(pkgs/id/src/cli.rs): variants run Invite/Install/…/Compile/New/…/Replay/Verify/… with no dev/watch/hot-swap entry; a code search forworld devfinds only docs and plans. The issue's "Current status: Not started" is accurate.id world verify) #544 (F11.16id world verify) is CLOSED andVerifyis in the enum above — the issue body's prerequisite list is stale on this point..opencode/plans/phase-12-platform-flexibility.md;planning/roadmaps/id.mdlikewise marks F12.15 planned, waiting on F12.9).queue/queued— the gate is in the queue system, so this triage enqueues nothing new; an implementation task for id: F12.15id world dev: watch, rebuild, hot-swap, fixture replay, fuzz harness #558 filed now could not start and would only churn.doc/2026-11-01_design_id558.md— local offline authoring session, F12.9 probe/migrate/commit as the only hot-swap path, a dev-only cross-version fixture regression mode (normalreplay/verifystay strict), and deterministic fuzzing off the every-edit path. No design decision is outstanding; when id: F12.9 program upgrade with state migration and rollback #1066 lands, implementation follows that design.triaged. Issue id: F12.15id world dev: watch, rebuild, hot-swap, fixture replay, fuzz harness #558 stays open, labelledstatus/blocked(blocked on id: F12.9 program upgrade with state migration and rollback #1066); re-triage/implementation becomes actionable when id: F12.9 program upgrade with state migration and rollback #1066 closes. Removing the stalequeue/queued/status/needs-triagelabels in the same pass.