39 lines
4.4 KiB
Markdown
39 lines
4.4 KiB
Markdown
# XZBT implementation status
|
|
|
|
**Updated:** September 4, 2026\
|
|
**State:** Stopped in Phase 0 at GC1; no later phase started\
|
|
**Baseline commit:** `05fe2b4e021ba86e4a290d05b63c7cae0e386128`
|
|
|
|
The user requested sequential implementation with a stop on problems. The [manual version 3 evidence](evidence/phase0/2026-09-04-user-run-v3.md) verifies embedded data-URL worklet loading in direct-file Chrome. The subsequent [user-performed restart test](evidence/phase0/2026-09-04-user-restart.md) restored Blue Study activity 0.37 and master volume 0.19 immediately on reopening. Native tone output and AudioContext suspend/resume are also observed. GC1 still awaits the directory-permission/unavailability fallback check. Ordinary file import, selection of both exhibits, and regular Chrome mode have been confirmed. The agent's direct-file browser-navigation restriction remains in effect.
|
|
|
|
| Phase | Status | Evidence or next prerequisite |
|
|
| --- | --- | --- |
|
|
| 0 — Contracts and feasibility | Awaiting remaining manual evidence; incomplete | [Restart/settings pass and outstanding checks](evidence/phase0/2026-09-04-user-restart.md) |
|
|
| 1 — Runtime skeleton | Not started | Complete Phase 0 |
|
|
| 2 — Common grammar | Not started | Complete Phase 1 and shared contracts |
|
|
| 3 — Audio engine | Not started | Earlier phases and audio contracts |
|
|
| 4 — Visual engine | Not started | Earlier phases and visual contracts |
|
|
| 5 — Events and cadence | Not started | Earlier phases and event/cadence contracts |
|
|
| 6 — Scenario director | Not started | Earlier phases and scenario contracts |
|
|
| 7 — Dynamic UI | Not started | Earlier phases and UI contracts |
|
|
| 8 — Library and persistence hardening | Not started | Earlier phases and library contracts |
|
|
| 9 — Reference suite completion/audit | Not started | Earlier phases, challenge coverage, benchmark and soak evidence |
|
|
|
|
## Work saved
|
|
|
|
- A self-contained [Phase 0 probe](../prototypes/phase0/XZBT-phase0-probe.html) for import, isolated probe caching, settings restoration, user-initiated audio, embedded engine worklet loading, suspend/resume, and injected storage failure.
|
|
- Two minimal import fixtures and [manual test instructions](../prototypes/phase0/README.md).
|
|
- Syntax checks passed for the probe's JavaScript and both JSON fixtures. These checks do not establish browser behavior or complete GC1.
|
|
- Preserved the user's version 1 and version 2 evidence, including the failed Blob-module attempts. Version 2 separated tone/worklet tests and added failure diagnostics.
|
|
- Version 3 changes the fixed processor module from a Blob URL to an embedded data URL and adjusts the page script-source allowlist while continuing to block network connections. Three stubbed regression tests passed; the user's subsequent version 3 run now verifies real loading and connection in direct-file Chrome.
|
|
|
|
## Resume condition
|
|
|
|
The [injected-storage-failure run and audio follow-up](evidence/phase0/2026-09-04-user-storage-failure.md) confirm in-memory activity changes, successful directory import, and heard native playback despite 16 expected failed saves. The user subsequently confirmed the visible session-only warning. The injected-storage-failure check passed; this does not establish real browser permission-denial behavior.
|
|
|
|
Worklet loading and the user-performed restart/settings test have passed and need not be repeated without a relevant code change. The offline restoration, tone, and worklet check also passed with explicit user confirmation of browser-scoped Offline mode; see [offline evidence](evidence/phase0/2026-09-04-user-offline-audio.md). The [user confirmed regular Chrome mode and ordinary import/activation](evidence/phase0/2026-09-04-user-import-environment.md). Directory-permission/unavailability fallback remains unverified. The earlier reload results remain distinct from the subsequent manual restart procedure.
|
|
|
|
The browser rejection explicitly forbids agent workarounds through alternate browser surfaces, raw commands, or indirect execution. No workaround was attempted. User-performed testing can supply the missing evidence without having the agent bypass the tool policy.
|
|
|
|
Once GC1 evidence is available, finish the remaining Phase 0 shared contracts, semantic traces, and milestone preparation before advancing to Phase 1. A manual GC1 pass alone does not mark all of Phase 0 complete. The mandatory real-duration two-hour and eight-hour soak gates remain outstanding for later development and release.
|