datlechin · Oct 18, 2026 · Oct 18, 2026
diff --git a/linux/README.md b/linux/README.md
@@ -261,7 +261,7 @@ says where the realm, the KDC and the tickets come from there.
 | Testing conventions, suites and CI jobs | [docs/testing.md](docs/testing.md) |
 | Saved passwords, SSH, Kerberos, logs and crash reports, for users | [docs/troubleshooting.md](docs/troubleshooting.md) |
 | Release setup, releases and packaging fixes | [docs/releasing.md](docs/releasing.md) |
-| Every guide, driver page and dated audit | [docs/README.md](docs/README.md) |
+| Every guide and driver page | [docs/README.md](docs/README.md) |
 | Architecture decision records | [docs/decisions/](docs/decisions/) |
 
 ## License

diff --git a/linux/ROADMAP.md b/linux/ROADMAP.md
@@ -174,7 +174,7 @@ Not committed: server monitoring (sessions, locks, slow queries), maintenance co
 
 ## Release criteria
 
-From the [production-readiness audit](docs/production-audit.md#what-production-ready-means-here), for GNOME 50. A user on Ubuntu 26.04 or Fedora 44, with where each stands on 2026-10-18:
+What has to hold before the first release, for a user on GNOME 50 with Ubuntu 26.04 or Fedora 44, and where each stands on 2026-10-18:
 
 | # | The user | Holds today | Still needed |
 |---|---|---|---|

diff --git a/linux/crates/session/src/session/mod.rs b/linux/crates/session/src/session/mod.rs
@@ -6,7 +6,7 @@ mod object_list_snapshot;
 mod schema_catalog;
 #[expect(
     clippy::module_inception,
-    reason = "the Session type is the module's subject, as the plan names its file"
+    reason = "the Session type is the module's subject"
 )]
 mod session;
 mod session_deps;

diff --git a/linux/docs/README.md b/linux/docs/README.md
@@ -29,13 +29,3 @@ The reference for working on the Linux app. Start with [ARCHITECTURE.md](../ARCH
 ## Decisions
 
 The architecture decision records, with a summary of each, are indexed in [decisions/README.md](decisions/README.md).
-
-## Dated audits and plans
-
-Snapshots, kept as they were written. The code has moved on since each date.
-
-| Date | Document |
-|---|---|
-| 2026-04-26 | [production-audit.md](production-audit.md): the production-readiness audit the roadmap's release criteria come from |
-| 2026-09-14 | [plan-2026-09-14-audit-remediation.md](plan-2026-09-14-audit-remediation.md): the plan that fixed the 2026-09-13 audit's findings, with its [details](plan-2026-09-14-audit-remediation-details.md) |
-| 2026-09-14 | [dependency-review-2026-09-14.md](dependency-review-2026-09-14.md): the dependency review whose amendments override that plan |
diff --git a/linux/docs/decisions/README.md b/linux/docs/decisions/README.md
@@ -61,7 +61,7 @@ ADRs are short on purpose. If yours is more than a page, you are probably arguin
 | [0017](0017-distribution-channels.md) | Distribution channels | Superseded by 0018 | Flathub, a .deb for Ubuntu 26.04 on GitHub Releases built with rustup, and an .rpm for Fedora 44 on COPR, all from `meson install` and one vendor tarball; no AppImage. |
 | [0018](0018-ppa-copr-and-flathub-later.md) | A PPA and COPR first, Flathub later | Accepted | A Launchpad PPA built with `rustc-1.97` and a COPR project built on each release are the primary channels; Flathub follows as a submission a maintainer writes; Rust 1.97 is the MSRV. |
 
-0011 is not used. The 2026-09-14 remediation plan reserved it for the DDL decision, which was recorded as 0010, and docs cite ADRs by number, so the later ones keep theirs.
+0011 is not used. It was reserved for the DDL decision, which was recorded as 0010, and docs cite ADRs by number, so the later ones keep theirs.
 
 ## Adding an ADR
 

diff --git a/linux/docs/dependency-review-2026-09-14.md b/linux/docs/dependency-review-2026-09-14.md
diff --git a/linux/docs/plan-2026-09-14-audit-remediation-details.md b/linux/docs/plan-2026-09-14-audit-remediation-details.md
diff --git a/linux/docs/plan-2026-09-14-audit-remediation.md b/linux/docs/plan-2026-09-14-audit-remediation.md
diff --git a/linux/docs/production-audit.md b/linux/docs/production-audit.md
diff --git a/linux/docs/regression-tests.md b/linux/docs/regression-tests.md
@@ -1,6 +1,6 @@
 # Regression tests
 
-The 2026-09-13 audit rated seven findings critical. Each one has tests that fail if it comes back, and every such test carries the finding in its name: a guard for F-001 starts with `f001_`. The audit itself is not in the tree; the [remediation plan](plan-2026-09-14-audit-remediation.md#finding-to-task-index) lists the tasks that fixed each finding.
+The 2026-09-13 audit rated seven findings critical. Each one has tests that fail if it comes back, and every such test carries the finding in its name: a guard for F-001 starts with `f001_`. The audit itself is not in the tree; the table below is the record of each finding.
 
 ```bash
 finding=f002_