jb/harness-tools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record runtime verification and benchmark acceptance gaps

Browse Source
This commit is contained in:
jb
2026-09-21 13:15:11 -04:00
parent c0c18a5191
commit 4360f01947
1 changed files with 8 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/plans/fast-browser-performance.md
+8 -6
View File
@@ -3,8 +3,8 @@
## Status
- Status: active
- Current phase: implementation; Slice B verified and committed, A/D running, C ready for dispatch.
- Next safe action: implement C, inspect A/D returns, then run integrated checks and paired measurements.
- Current phase: implementation; B/D verified and committed, C running, A delivered with in-scope verification gaps.
- Next safe action: finish C and correct benchmark accounting/fixture/cleanup gaps before integrated measurements.
## Request and scope
@@ -77,10 +77,10 @@ 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 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 | first delivery within deadline; 15-minute correction assignment | four listed new files | initial owned patch `/tmp/pi-present/performance-slice-a-initial.patch`; c0c18a5 before correction, other dirty Python files owned by C | 4 focused tests and typecheck passed; acceptance gaps returned for correction |
| 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 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 | completed within deadline | runtime.ts + runtime.test.ts | owned patch `/tmp/pi-present/performance-slice-d.patch`; parent reran 12 tests and typecheck | committed c0c18a5 |
| Docs/integration | parent | phase bounded | listed docs/README only | record checkpoints | pending |
## Verification matrix
@@ -112,7 +112,9 @@ After safe integration, make one record-only closure commit, prove reachability,
## Checkpoints and blockers
- Last committed valid checkpoint: approved plan/assignments at 05793fe; Slice B product commit a79418e.
- Last committed valid checkpoint: approved plan/assignments at 05793fe; B product a79418e, D product c0c18a5. Worktree dependency links include workspace-local node_modules; local Git excludes now ignore these symlinks. No dependency installation occurred.
- 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.
- Next safe action: resume browser-hotpath for C. A and D remain assigned exclusively; all returned changes are inspected before acceptance.
- Baseline real Chromium development validation passed (opt-in test exit 0, no skips).
- A corrections: alternate pair order, expose per-density timing/count evidence, independently check saved fixture data, make popup postcondition stable, fail/retain evidence on cleanup or missing counters, and sanitize errors to safe categories. This completes existing acceptance criteria without changing public scope.
- Next safe action: resume A for these bounded corrections; C continues. Final review remains independent.