docs: raise console documentation to hyperscaler standard

DESIGN.md

@@ -1,5 +1,7 @@
-# DESIGN — one-release redirect
+# DESIGN — tombstone
 
-Current product and architecture authority lives in [`docs/current/PRODUCT.md`](docs/current/PRODUCT.md).
+Not current authority. Do not dispatch work from this path.
 
-This path remains for one release so existing links resolve. It is not current authority and cannot dispatch work; use the replacement above.
+Replacement: [`docs/current/PRODUCT.md`](docs/current/PRODUCT.md)
+
+This file remains so existing links resolve. It is not a one-release promise and is not an architecture document.

HANDOFF.md

@@ -1,9 +1,16 @@
 # HANDOFF — volatile restart pointer
 
-Start at [`README.md`](README.md), then read [`PRODUCT`](docs/current/PRODUCT.md), [`ROADMAP`](docs/current/ROADMAP.md), and [`DELIVERY`](docs/current/DELIVERY.md). This file is a short restart pointer, not product, roadmap, or delivery authority.
+Start at live authority only:
 
-The latest preserved recovery context is [`docs/handoffs/2026-08-03-disk-wipe-consolidation.md`](docs/handoffs/2026-08-03-disk-wipe-consolidation.md). Product code does not depend on an old worktree or local branch. Custody, recovery, restricted-input, and secret-handling obligations remain recorded in that historical handoff and must not be discarded.
+1. [`README.md`](README.md)
+2. [`docs/current/PRODUCT.md`](docs/current/PRODUCT.md)
+3. [`docs/current/ROADMAP.md`](docs/current/ROADMAP.md)
+4. [`docs/current/DELIVERY.md`](docs/current/DELIVERY.md)
 
-In a fresh clone of the latest `origin/main`, follow the root README and then read the tracked [execution handoff](.omx/plans/reasoning-lens-contract-execution-handoff.json). The four tracked OMX continuity artifacts are Git-custodied even though new `.omx/` runtime output is ignored; retired ignored runtime bytes must not be restored as authority.
+This file is not product, roadmap, or delivery authority.
 
-`main` remains the integration branch. Product and delivery HOLDs are recorded in the three current authorities. The linked handoff supplies custody evidence and itemized disposition state only; it cannot clear or weaken a current HOLD.
+Custody evidence only (cannot clear a HOLD): [`docs/handoffs/2026-08-03-disk-wipe-consolidation.md`](docs/handoffs/2026-08-03-disk-wipe-consolidation.md).
+
+Do not treat `.omx/plans/reasoning-lens-contract-execution-handoff.json` or other `.omx/` artifacts as live restart authority.
+
+`main` remains the integration branch. Product and delivery HOLDs are recorded in the three current authorities.

README.md

@@ -25,14 +25,16 @@ The full first-party Markdown manifest is the generated [`docs/documentation-ind
 
 ## Supported verification entrypoint
 
-From the repository root, run:
+A new clone needs Node tooling **and** the pinned DotSlash runtime on `PATH` before `npm run verify`. The installer cannot modify its parent shell (`GITHUB_PATH` exists only in GitHub Actions).
 
 ```sh
 npm ci
+tools/buck/install_dotslash.sh
+export PATH="${CONSOLE_DOTSLASH_BIN_DIR:-${RUNNER_TEMP:-${TMPDIR:-/tmp}/console-dotslash}/bin}:$PATH"
 npm run verify
 ```
 
-`npm ci` installs the pinned repository tooling; `npm run verify` is the one supported local repository verification entrypoint. Run narrower tests while developing and any additional checks required by the touched surface, then record the exact candidate SHA, commands, environment, discovered/executed counts, failures, and remaining HOLDs as described in [`docs/current/DELIVERY.md`](docs/current/DELIVERY.md).
+`npm ci` installs the pinned repository tooling. `npm run verify` is the supported local repository verification entrypoint (`fast` tier). Buck2-backed steps fail as environment errors, not product regressions, if DotSlash is missing from `PATH`. The same sequence is recorded in [`docs/current/DELIVERY.md`](docs/current/DELIVERY.md). Run narrower tests while developing and any additional checks required by the touched surface, then record the exact candidate SHA, commands, environment, discovered/executed counts, failures, and remaining HOLDs there.
 
 <!-- SHARED:REASONING-LENSES:START -->
 ## Reasoning lens manifest

SPEC.md

@@ -1,5 +1,7 @@
-# SPEC — one-release redirect
+# SPEC — tombstone
 
-Current product scope, invariants, architecture, and holds live in [`docs/current/PRODUCT.md`](docs/current/PRODUCT.md).
+Not current authority. Do not dispatch work from this path.
 
-This path remains for one release so existing links resolve. It is not current authority and cannot dispatch work; use the replacement above.
+Replacement: [`docs/current/PRODUCT.md`](docs/current/PRODUCT.md)
+
+This file remains so existing links resolve. It is not a one-release promise and is not a specification.