kixelated · Oct 23, 2026 · Oct 22, 2026 · Oct 22, 2026 · Oct 22, 2026 · Oct 22, 2026
diff --git a/quest/m1/README.md b/quest/m1/README.md
@@ -170,7 +170,6 @@ tracks, so per-group stats stop costing cluster announces.
 - [Caption store bounds](/quest/m1/caption-store-bounds.md) - a hostile caption track cannot grow a viewer's cue and region store or its per-frame work without bound
 - [Auth contract](/quest/m1/auth-contract.md) - the auth server receives the certificate-selecting SNI, documented as client-chosen, and a certificate grants nothing alone
 - [Nightly benchmark regressions](/quest/m1/bench-ci.md) - each nightly compares the Rust Criterion benches against the previous nightly's commit on the same hosted runner, publishes it to the git.moq.dev report, and alerts on a regression
-- [Performance audit](/quest/m1/audit-perf.md) - benchmarks that regressed since the m0 run are explained, fixed, or planned, and unbenched hot paths get coverage
 - [Interop audit](/quest/m1/audit-interop.md) - our interop runner entries match what we ship, and every red interop cell with a moq.dev side is fixed, reported, or noted as down
 
 ## Related

diff --git a/quest/m1/audit-perf.md b/quest/m1/audit-perf.md
diff --git a/quest/m1/bench-ci.md b/quest/m1/bench-ci.md
@@ -20,7 +20,7 @@ merge, and main PRs skip cloud CI since #6038. This drops the per-PR sticky
 comment design and its `workflow_run` follow-up.
 
 Decided 2026-10-22 (maintainer): the paired run stays on the hosted ARM
-runners. Moved from m2 to m1 so the m1 [performance audit](/quest/m1/audit-perf.md)
+runners. Moved from m2 to m1 so the [performance audit](/quest/m2/audit-perf.md)
 reads paired flags instead of raw history. Rejected hosts:
 
 - The merge queue runner (`nixos-moq-ci`) is an nspawn container on a

diff --git a/quest/m1/release-audit/README.md b/quest/m1/release-audit/README.md
@@ -123,7 +123,7 @@ child records whether its behavior is new on main or inherited from release.
 - [Compressed tracks](/quest/m1/compress/README.md) - mid-group widening and application migration have existing owners
 - [Archive consumer](/quest/m1/archive/consumer.md) - current producer and CLI reader still need the new-format roundtrip
 - [Measured release performance](/quest/m1/release-perf/README.md) - existing paired benchmark regressions and their confirmation runs
-- [Transport performance audit](/quest/m1/audit-perf.md) - congestion-control coverage remains outstanding
+- [Transport performance audit](/quest/m2/audit-perf.md) - congestion-control coverage remains outstanding
 - [Binding timestamps](/quest/m1/binding-timestamps.md) - exact timestamps across language APIs
 - [Dependency audit](/quest/m2/audit-deps.md) - existing advisory inventory
 - [Release gates](/quest/m0/ci/release-gates.md) - post-cut ruleset verification

diff --git a/quest/m1/release-perf/README.md b/quest/m1/release-perf/README.md
@@ -10,7 +10,7 @@ and the reason is written here.
 This epic's own work: once every child has landed, run the full main against
 release comparison again with `just bench origin/release`, and confirm nothing
 new regressed. Then add a release-baseline step to the recurring
-[performance audit](/quest/m1/audit-perf.md), so every later cut
+[performance audit](/quest/m2/audit-perf.md), so every later cut
 repeats this comparison.
 
 ## Plan
@@ -104,5 +104,5 @@ outside the worktree to keep the next one.
 
 ## Related
 
-- [Performance audit](/quest/m1/audit-perf.md) - compares nightly to nightly; this epic compares main to release
+- [Performance audit](/quest/m2/audit-perf.md) - compares nightly to nightly; this epic compares main to release
 - [Nightly benchmark regressions](/quest/m1/bench-ci.md) - paired nightly-to-nightly comparison on one runner
diff --git a/quest/m1/release-perf/recheck.md b/quest/m1/release-perf/recheck.md
@@ -9,7 +9,7 @@ epic.
 
 ## Plan
 
-Use the instruction-count method from the [performance audit](/quest/m1/audit-perf.md).
+Use the instruction-count method from the [performance audit](/quest/m2/audit-perf.md).
 Wall time on a shared host can't tell these apart. Build each bench at
 `origin/release` and at main, and compare instructions per iteration. A
 change that needs a maintainer decision, or is too large to review alongside

diff --git a/quest/m2/README.md b/quest/m2/README.md
@@ -227,3 +227,4 @@ ranked just below deterministic TS legs, which it requires.
 
 - [Quest tree audit](/quest/m2/audit-quests.md) - repeat the whole-tree audit after the release ships, against the m1 baseline
 - [CI workflow audit](/quest/m2/audit-ci.md) - repeat the per-workflow and per-job review after the release ships, against the m1 baselines
+- [Performance audit](/quest/m2/audit-perf.md) - benchmarks that regressed since the m1 run are explained, fixed, or planned, and unbenched hot paths get coverage
Original file line number	Diff line number	Diff line change
Expand Up		@@ -227,3 +227,4 @@ ranked just below deterministic TS legs, which it requires.

		- [Quest tree audit](/quest/m2/audit-quests.md) - repeat the whole-tree audit after the release ships, against the m1 baseline
		- [CI workflow audit](/quest/m2/audit-ci.md) - repeat the per-workflow and per-job review after the release ships, against the m1 baselines
		- [Performance audit](/quest/m2/audit-perf.md) - benchmarks that regressed since the m1 run are explained, fixed, or planned, and unbenched hot paths get coverage