docs: record browser hot-path verification and batching handoff

This commit is contained in:
jb
2026-09-21 13:05:42 -04:00
parent a79418efcb
commit 3c321b3033
+6 -6
View File
@@ -3,8 +3,8 @@
## Status ## Status
- Status: active - Status: active
- Current phase: approved plan; isolated worktree established, before product edits. - Current phase: implementation; Slice B verified and committed, A/D running, C ready for dispatch.
- Next safe action: commit the approved record and dispatch A/B/D with exclusive ownership. - Next safe action: implement C, inspect A/D returns, then run integrated checks and paired measurements.
## Request and scope ## Request and scope
@@ -78,8 +78,8 @@ Each mutating assignment has a 15-minute deadline. B and C are separate assignme
| Research browser | browser-performance-research / scout | complete | none; read-only | source unchanged | delivered | | Research browser | browser-performance-research / scout | complete | none; read-only | source unchanged | delivered |
| Research runtime | runtime-performance-research / scout | complete | none; read-only | source unchanged | delivered | | Research runtime | runtime-performance-research / scout | complete | none; read-only | source unchanged | delivered |
| A benchmark | performance-benchmark / worker | 15 minutes from dispatch | four listed new files | feature/fast-browser-performance, 6fba62800ac9ad613466234292cba7b84ce52606, clean; empty before patch `/tmp/pi-present/performance-before.patch` | dispatch authorized | | A benchmark | performance-benchmark / worker | 15 minutes from dispatch | four listed new files | feature/fast-browser-performance, 6fba62800ac9ad613466234292cba7b84ce52606, clean; empty before patch `/tmp/pi-present/performance-before.patch` | dispatch authorized |
| B browser duplication | browser-hotpath / worker | 15 minutes from dispatch | worker Python + Python tests | same clean 6fba628 checkpoint and before patch as A | dispatch authorized | | B browser duplication | browser-hotpath / worker | completed within deadline | worker Python + Python tests | delivered only owned paths; `/tmp/pi-present/performance-slice-b.patch`; parent reran 47 Python tests (pass) and diff check | committed a79418e |
| C observation batching | browser-hotpath / worker | 15 minutes after B | same Python files | capture before dispatch | pending | | C observation batching | browser-hotpath / worker | 15 minutes from resumed dispatch | same Python files | a79418e; Python paths clean; A/D files and parent performance doc dirty under their owners; `/tmp/pi-present/performance-before-c.patch` | dispatch authorized |
| D origin context | runtime-hotpath / worker | 15 minutes from dispatch | runtime.ts + runtime.test.ts | same clean 6fba628 checkpoint and before patch as A | dispatch authorized | | D origin context | runtime-hotpath / worker | 15 minutes from dispatch | runtime.ts + runtime.test.ts | same clean 6fba628 checkpoint and before patch as A | dispatch authorized |
| Docs/integration | parent | phase bounded | listed docs/README only | record checkpoints | pending | | Docs/integration | parent | phase bounded | listed docs/README only | record checkpoints | pending |
@@ -112,7 +112,7 @@ After safe integration, make one record-only closure commit, prove reachability,
## Checkpoints and blockers ## Checkpoints and blockers
- Last committed valid checkpoint: initial approved record is being committed before product mutation. - Last committed valid checkpoint: approved plan/assignments at 05793fe; Slice B product commit a79418e.
- Blockers: none for implementation. Source still has only the approved unrelated untracked file. - Blockers: none for implementation. Source still has only the approved unrelated untracked file.
- Worktree creation verified at the specified base and path. `/.worktrees/` was already in local Git excludes; no exclude change was needed. - Worktree creation verified at the specified base and path. `/.worktrees/` was already in local Git excludes; no exclude change was needed.
- Next safe action: dispatch A/B/D concurrently after the record commit. - Next safe action: resume browser-hotpath for C. A and D remain assigned exclusively; all returned changes are inspected before acceptance.