Multiplayer agent harness for work.
Always review Historylessness in the Wall of shame (#2337)
Regan Bell3ce173a3ae08
diff --git a/docs/SPEC.md b/docs/SPEC.mdindex 815f2a2d6..33363ab9d 100644--- a/docs/SPEC.md+++ b/docs/SPEC.md@@ -168,10 +168,11 @@ Replacing or swallowing a failure so the evidence needed to diagnose it disappea- **Rejected session titles:** `sanitizeTitle` returned `undefined` for rejected model output. The fallback title made the request look successful, while neither the rejected text nor the rule that rejected it reached the error log. _Status:_ [qm#1303](https://github.com/yc-software/qm/pull/1303) records the rejection rule and a bounded sample in the durable error log.- **Failed transaction rollback:** `withPgTransaction` and copied transaction handlers awaited `ROLLBACK` before rethrowing the original error. If rollback also failed, its exception replaced the actual transaction failure. _Status:_ still present on main; [qm#1834](https://github.com/yc-software/qm/pull/1834) proposes preserving the original error and discarding the broken connection.-### Legacy preservation (4 examples)+### Historylessness (always reviewed, 5 examples)-Keeping old endpoints, data shapes, and code paths alive next to their replacement. Our priority is future users, not seamless continuity for past ones. Do the bare minimum for history: a DB migration or a one-off migration script, then make the breaking change and let people adapt; agents can usually smooth over the breakage for existing users. Only preserve the old way when removing it would leave the system in an unrecoverable state. In general the codebase should be historyless: it represents the system at its current best, without sedimentary layers of how it got there.+Growing the codebase to keep every path it ever took alive. The canonical case: a conditional that string-matches IDs or prefixes because older rows lack a typed field. Trust the typed field; rows without it get no special handling, and if they matter, migrate them once. The same goes for compatibility shims, dual reads and writes, and old endpoints or data shapes kept beside their replacement. Make the breaking change and let people adapt; agents can usually smooth over the breakage for existing users. If keeping an old shape truly seems necessary, ask the user rather than building it. The codebase represents the system at its current best, without sedimentary layers of how it got there.+- **Sidebar surface** (2026-10-14): The web sidebar's `surfaceOf` (`plugins/web-ui/src/sessions.ts`) is a conditional that string-matched `threadRef` prefixes (`web:`, `dm:`, `ch:`) because older sessions lacked a typed `surface`, and trusted the stored field only for subagents. When automation sessions landed in the wrong group, the proposed fix added more prefixes. Every session now stores its surface; read that field alone. _Status:_ still present on main.- **Credential capture redesign** (2026-10-08): The login-as-a-skill handoff planned that "a stale skill calling /v1/keychain/use gets a clear refusal" and that "logins saved under the old capture system still load." Both keep the old system on life support. Remove the endpoint and the old capture system outright; stale skills fail and get fixed. _Status:_ [qm#2146](https://github.com/yc-software/qm/pull/2146) deletes `/v1/keychain/use` (open).- **Sandbox routing retirement** (2026-10-02): Retiring `sandbox_routing` came with a locked, marker-guarded one-time upgrade import that preserved legacy IDs, explicit nulls, and machine IDs, kept the old table as rollback input, and told operators to keep credentials for legacy-mapped providers. A plain migration would have done. _Status:_ merged in [qm#2019](https://github.com/yc-software/qm/pull/2019).- **Session tape beside session entries** (2026-09-16): The tape was meant to replace `session_entries`, but caution kept both. `SESSION_TAPE_MODE` shadow/serve chose between them, exact-transcript annotations were added so the tape could reproduce every historical field, and a verifying, lease-aware operator backfill with dry runs and partial-scan statuses guarded the cutover. We got stuck here for weeks; one migration and a hard cutover would have left one system instead of two. _Status:_ code reads and writes only `session_entries` since [qm#2273](https://github.com/yc-software/qm/pull/2273); `session_tape` is dropped by a gated migration once its step metadata has been copied out ([qm#2280](https://github.com/yc-software/qm/pull/2280)).diff --git a/test/wall-of-shame-check.test.ts b/test/wall-of-shame-check.test.tsindex c83c97ec3..21cc0a723 100644--- a/test/wall-of-shame-check.test.ts+++ b/test/wall-of-shame-check.test.ts@@ -1,4 +1,5 @@import assert from "node:assert/strict";+import { readFileSync } from "node:fs";import test from "node:test";import { wallOfShameLenses, wallOfShameProblems } from "../scripts/wall-of-shame-check.ts";@@ -68,3 +69,13 @@ test("always-reviewed lenses cannot be triaged as not relevant", () => {["Overengineering: always reviewed; triage cannot mark it Not relevant."],);});++test("the spec always reviews Historylessness", () => {+ const real = readFileSync("docs/SPEC.md", "utf8");+ const rows = wallOfShameLenses(real).map((lens) =>+ lens === "Historylessness" ? `| ${lens} | Haiku triage | Not relevant | | No schema change. |` : row(lens),+ );+ assert.deepEqual(wallOfShameProblems(real, body(head, rows), head), [+ "Historylessness: always reviewed; triage cannot mark it Not relevant.",+ ]);+});