feat(02-10): third measurement run against archi-dev-box (5 runs/surface)

- Frontend-only deploy to archi-dev-box first (commit 3e3159fa) — last deploy
  was 02-08's fix (8fe6217b), predating the 02-review commits that touch
  Web5/Discover/Server/OpenWrtGateway and 02-09's investigation; deployed
  clean (dirty=false) before any concurrent uncommitted work landed in the tree
- Harness confirmed byte-for-byte frozen: git diff --stat 3ee20430 -- neode-ui/e2e/perf/
  shows only the new keepalive-remount-probe.spec.ts (02-09), zero changes to
  surfaces.ts/measure.ts/surface-perf.spec.ts
- First attempt (ARCHY_PERF_RUNS=5) hit the harness's own hardcoded 20-min
  test.setTimeout under concurrent node load (a botfights podman build +
  other sessions), aborting after 9/15 surfaces with the rest failing
  "browser has been closed" (not a real measurement, not hand-edited into
  the artifact) — re-ran once per the plan's own contingency, completed
  clean in 7.9 min once the concurrent build finished
- 15/15 rows recorded; runs: 5, baseUrl: http://archi-dev-box; Mesh unmeasured
  again (device not reporting connected, same reason as both prior runs);
  Chat measured this time (bonus data point, no baseline-comparable
  counterpart — findings doc will say so plainly)
- Conditions recorded: pre-run 06:01 EDT, df 79% (1.4T/1.8T, down from
  baseline's 85%), load 8.70/7.99/7.94 with a concurrent podman build
  running; post-run 06:42 EDT, df 79%, load 6.88/11.88/9.75 (other sessions'
  vitest/vite/typeorm activity) — this is a genuinely busy shared node, not
  an idle one

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
archipelago 2026-07-31 06:43:35 -04:00
parent 7c063a2062
commit db629f6f0e

File diff suppressed because it is too large Load Diff