Recorded upstream in polyengine's consumer findings (POLYVISOR-1, from the A19 audit 2026-08-22): docs/spike-todomvc/app.js is a checked-in minified bundle containing an entire deltic-era engine copy — RUNTIME_VERSION "0.1.0", deltic.*/1 brand keys, DELTIC_SCHED_SEED. It is the one raw deltic.witError/1 spelling left anywhere in the consumer family.
Inert as archived documentation, but it is exactly the undiagnosed multi-copy scenario A18/A19 describe: its brand namespace is disjoint from every current line, so revived next to a current engine, values go unrecognized with no error naming the mismatch.
Options when this gets its turn: delete the committed bundle (the spike archive keeps its source, loses its live Pages demo), or regenerate against current pins (cuts against spikes/ being a frozen archive — the bundle would no longer be the executed artifact the spike record describes). Leaning delete-with-a-note; either way the decision should be deliberate, which is what this issue holds open.
Recorded upstream in polyengine's consumer findings (POLYVISOR-1, from the A19 audit 2026-08-22):
docs/spike-todomvc/app.jsis a checked-in minified bundle containing an entire deltic-era engine copy —RUNTIME_VERSION"0.1.0",deltic.*/1brand keys,DELTIC_SCHED_SEED. It is the one rawdeltic.witError/1spelling left anywhere in the consumer family.Inert as archived documentation, but it is exactly the undiagnosed multi-copy scenario A18/A19 describe: its brand namespace is disjoint from every current line, so revived next to a current engine, values go unrecognized with no error naming the mismatch.
Options when this gets its turn: delete the committed bundle (the spike archive keeps its source, loses its live Pages demo), or regenerate against current pins (cuts against spikes/ being a frozen archive — the bundle would no longer be the executed artifact the spike record describes). Leaning delete-with-a-note; either way the decision should be deliberate, which is what this issue holds open.