Log in

mrmrs-b26e28

mrmrs-b26e28

Open into main
1 commit · 4 files +3 added ~1 modified · 6 behind main ·Seen by zach 9 hours ago
M docs/benchmark-coverage.md
@@ -38,6 +38,7 @@
3838 | Shaped network operations and first-payload timing | Implemented for netshape lane where Linux netns/tc is available | `scripts/netshape_bench.py` `netshape_clone_cold`, `netshape_log_follow_cold`, byteproxy `ttfd_ms` fields | Cross-subject latency claims require the same `netshape_profile` and server host. `netshape_log_follow_cold` measures cold network acquire plus file-history query (`git.log.follow`/`oak.log.follow`) with TTFD fields. Non-Linux or missing Oak local server paths emit skip rows. |
3939 | Mount lifecycle (desc, finish, space clean, task loop) | Implemented handlers; needs remote to run | `mount_probe.py` `oak.desc`/`oak.finish --desc-file`/`space.clean`/`loop.push_desc*`, `task_lifecycle_loop` scenario | `oak finish` capability-gated per binary; skip rows until OAK_BENCH_MOUNT_REPO set. |
4040 | Compact-output follow-up cost | Implemented for streams exposing per-call outcomes | `tool_call_metrics.vcs_info_followup_calls_total` via `oakbench/stream_adapters.py` | Each follow-up means the first output was insufficient; null when commands are not adapter-visible. |
41+| Stale-branch landing (`stale_branch_land_v1`) | Implemented; baseline before a server-side land primitive | `scripts/stale_land.py` (arms `oak_safe`, `oak_naive`, `git_competent`, `git_fifo`), `scripts/oakbench/ci_stub.py` (loopback CI executor speaking oakspace's signed dispatch/callback protocol), `tests/test_stale_land.py` | Oak rows need an owned local oakspace server (not `oak serve`: no hosted merge/CI gate) and are labeled `loopback` / `hosted-equivalent-local`; Git rows are `local-file`. CI duration is a fixed labeled delay (`ci_added_seconds`) plus a real check script. `combined_tree_tested_before_land` and `red_main_events` come from independent tree oracles (server token-scoped export / `git archive`), never agent reports. Oak `tool_call_count` includes one explicit `oak ci trigger` per CI cycle that hosted auto-triggering would not need (`tool_call_count_hosted_equivalent` subtracts it). Not a transport-matched Oak-vs-Git latency claim. |
4142 | Contention commit-latency tail + retry depth | Implemented | `parallel_contention.py` `commit_latency_tail`, `retry_depth_histogram`, per-worker samples | Cite p95 only when `tail_supported` includes it. |
4243
4344 Known unmeasured-by-design (null in v2 rows until instrumented): hydration