experiments in a post-browser web

docs(window-manager): the migration status reflects the finished cutover master

The step-status block still reported the write-debt gate at 23 allowlisted entries / 37 calls; `scripts/check-r2-window-ops.mjs` reads 15 entries / 23 calls. Section 6 carried the same stale pair and also described the kernel, the Escape interpreter and the executor as built but constructed nowhere in production, which is the opposite of what the app does: the provider install in `window-state-singleton.ts initWindowStateMachine` makes the kernel perform every window operation, and four responsibilities remain on the old machine. The per-step statuses in that block track the older 11-step migration, not the kernel cutover, and were not re-verified. The block now says so, so a reader does not take them for current fact.


+16 -9
1 changed file