docs: repair links left dangling by the operations-doc removal

Untracking the ops docs broke every reference to them. Repoints or removes
those references across README, architecture, ROADMAP, the archive index,
lifecycle TESTING, the hardening plan, and the security docs — pointing at
the issue tracker where a live task list was meant, and dropping the entry
entirely where it only existed to link an internal file.

Also fixes two pre-existing broken links found by validating every relative
link in the tracked docs:
- README linked docs/OPEN_SOURCE_READINESS.md, which never existed
  (underscores vs hyphens).
- reticulum-daemon/README.md linked a local Claude session plan at
  ../../.claude/plans/enchanted-strolling-rocket.md — outside the repo, and
  a path that would have shipped publicly pointing at nothing.

All relative links in tracked markdown now resolve: 0 broken.
audit-secrets.sh still 5/5.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

docs/1.8.0-RELEASE-HARDENING-PLAN.md

@@ -3,7 +3,6 @@
 > **The one living checklist for shipping 1.8.0.** Derived from a full-system deep
 > audit (2026-07-02): backend security, backend code-quality, frontend, mesh,
 > tests/release pipeline, and the ISO build. Supersedes nothing — it *sits above*
-> `docs/UNIFIED-TASK-TRACKER.md` (day-to-day) as the release exit-criteria list.
 > **Keep it updated: tick a box the moment an item lands, with the commit sha.**
 
 **Definition of done for 1.8.0:** the supply chain is authenticated end-to-end
@@ -375,7 +374,7 @@ media (latest artifact only one minor behind).
 
 ---
 
-## §I — Carried-over open items (from `UNIFIED-TASK-TRACKER.md`, still valid)
+## §I — Carried-over open items (still valid)
 
 - [~] 🟠 **Multinode gate pass** — 5× destructive gate was launched on node `.5`; bring the
       rest of the fleet to precondition, then run the existing (undocumented-but-present)

docs/ROADMAP.md

@@ -1,8 +1,7 @@
 # Archipelago Roadmap
 
 _Last updated: 2026-07-08. This is the public-facing summary. The live,
-priority-ordered engineering list is [`UNIFIED-TASK-TRACKER.md`](UNIFIED-TASK-TRACKER.md);
-the narrative plan behind it is [`PRODUCTION-MASTER-PLAN.md`](PRODUCTION-MASTER-PLAN.md)._
+open engineering work is tracked in the public issue tracker._
 
 ## North star
 

docs/architecture.md

@@ -225,9 +225,6 @@ mesh, steganography, store-and-forward outbox.
 | [`app-manifest-spec.md`](app-manifest-spec.md) | The `manifest.yml` schema |
 | [`user-walkthrough.md`](user-walkthrough.md) | End-user installation and usage guide |
 | [`troubleshooting.md`](troubleshooting.md) | Diagnostic scenarios and solutions |
-| [`operations-runbook.md`](operations-runbook.md) | Ops commands and emergency recovery |
 | [`multi-node-architecture.md`](multi-node-architecture.md) | Federation protocol design |
 | [`marketplace-protocol.md`](marketplace-protocol.md) | Decentralized app discovery via Nostr |
-| [`PRODUCTION-MASTER-PLAN.md`](PRODUCTION-MASTER-PLAN.md) | North star and workstream narrative |
-| [`UNIFIED-TASK-TRACKER.md`](UNIFIED-TASK-TRACKER.md) | Live, priority-ordered open items |
 | [`archive/`](archive/) | Historical audits, session logs, shipped designs |

docs/archive/README.md

@@ -7,15 +7,11 @@ docs whose feature has since shipped. They are kept for provenance and are
 
 For current state, start at:
 
-- `docs/UNIFIED-TASK-TRACKER.md` — what's open, priority-ordered
-- `docs/PRODUCTION-MASTER-PLAN.md` — north star and workstream narrative
 - `docs/architecture.md` — as-built system architecture
 - `docs/ROADMAP.md` — public-facing roadmap
 
 | File | What it was | Why archived |
 |------|-------------|--------------|
-| `SESSION-1.8.0-OTA-PROGRESS.md` | Session narrative of the 1.8.0 OTA work | Superseded by the unified task tracker |
-| `HANDOVER-2026-07-02-iso-feedback.md` | One-shot handover for the ISO feedback bug-bash | All fixes merged |
 | `rust-orchestrator-migration.md` | Design for migrating container lifecycle from bash to Rust | Migration complete — `prod_orchestrator.rs` + `boot_reconciler.rs` are the live system |
 | `demo-deployment-design.md` | Design for the public demo sandbox | Demo shipped; `docs/demo-build-info.md` is the live ops doc |
 | `app-registry-status-2026-06-21.md` | Per-app migration snapshot from node .228 @ v1.7.99-alpha | Point-in-time snapshot; headline findings (immich legacy, meshtastic present) no longer true |

docs/bitcoin-multi-version-design.md

@@ -94,7 +94,7 @@ changes.
 
 See also: [`docs/registry-manifest-design.md`](registry-manifest-design.md)
 (catalog distribution + signing this builds on),
-[`docs/PRODUCTION-MASTER-PLAN.md`](PRODUCTION-MASTER-PLAN.md) (gate that must be
+the production test gate (which must be
 green first), `MEMORY → project_decoupled_app_updates`,
 `MEMORY → project_manifest_driven_north_star`.
 

docs/manifest-hooks-design.md

@@ -3,7 +3,7 @@
 **Status:** implemented through Phase 4 (see §6; updated 2026-07-08) — only declarative `pre_start` remains · originally Task #20
 (indeedhub, netbird) off legacy Rust installers.
 
-See `docs/PRODUCTION-MASTER-PLAN.md`, `docs/APP-PACKAGING-MIGRATION-PLAN.md`
+See `docs/APP-PACKAGING-MIGRATION-PLAN.md`
 ("controlled hooks").
 
 ---

docs/multinode-testing-plan.md

@@ -1,6 +1,6 @@
 # Multinode / Fleet Testing Plan (separate from the single-node gate)
 
-> **Scope split (2026-06-22):** the production test gate (`docs/PRODUCTION-MASTER-PLAN.md` §5,
+> **Scope split (2026-06-22):** the production test gate (
 > `tests/lifecycle/TESTING.md`) is now a **single-node criterion on .228**. Verifying the same
 > lifecycle matrix across the rest of the fleet (.198 and the other testers) lives HERE and is run
 > **after** the .228 single-node gate is green. This is intentionally NOT a blocker on the .228 gate.

docs/qr-scanner-snappiness-handover.md

@@ -1,7 +1,7 @@
 # QR scanner snappiness — research + companion-dev handover
 
 *2026-07-29. Owner: web side = node repo (this doc's "web" items); native side =
-companion app dev (Mac). Backlog origin: UNIFIED-TASK-TRACKER "optimise
+companion app dev (Mac). Backlog origin: "optimise
 companion QR scan (quicker start/decode, low-light)".*
 
 ## Where scanning happens today

docs/security/ENTROPY-SEED-AUDIT-2026-07-31.md

@@ -955,7 +955,7 @@ Everything else in this document is queued in §8, not implemented.
 
 Prioritised by severity × effort, most valuable per unit of work first. **Only R-00 was
 implemented by this audit.** Everything else is queued here and mirrored into
-`docs/UNIFIED-TASK-TRACKER.md` so it is not stranded in a document nobody re-reads.
+the issue tracker so it is not stranded in a document nobody re-reads.
 
 **Effort scale:** S = under an hour; M = half a day; L = a day or more; **PHASE** = needs its
 own `/gsd-plan-phase`, not an opportunistic edit.

docs/security/PHASE-10-VERIFICATION-GUIDE.md

@@ -57,7 +57,7 @@ State these plainly so an auditor is not left inferring them:
   mitigation targets *future silent rebinding* of the entropy source.
 - **Findings F-04 through F-12 are out of scope** for this phase and remain open. See
   `ENTROPY-SEED-AUDIT-2026-07-31.md` remediation register (R-05..R-15) and
-  `docs/UNIFIED-TASK-TRACKER.md`.
+  the issue tracker.
 
 ---
 

docs/security/PSBT-SIGNING-ARCHITECTURE.md

@@ -23,7 +23,7 @@
 > - **§5 (LND) is unaffected and remains accurate**, including **§5.4's honesty table**, which is
 >   correct as written and unchanged.
 >
-> **For the current state, read `docs/security/KEY-03-SIGNING-POSTURE.md`** — it records the
+> **Note:** the current signing-posture record is maintained internally. It records the
 > deletion with its evidence, an honest per-step coverage map of the LND PSBT round trip, and the
 > verdict on whether an external signer can sign a default node's PSBT today (it cannot: no fleet
 > node is provisioned watch-only). Phases 2-7 below are unaffected as design targets.