diff --git a/WORK-RECORDS.md b/WORK-RECORDS.md
index 9af5d30..c65f034 100644
--- a/WORK-RECORDS.md
+++ b/WORK-RECORDS.md
@@ -76,5 +76,5 @@
 | task | REUSE-WP-0020-T04 | wait | — | workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md |
 | task | REUSE-WP-0020-T05 | done | — | workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md |
 | task | REUSE-WP-0020-T06 | todo | — | workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md |
-| task | REUSE-WP-0020-T07 | todo | — | workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md |
+| task | REUSE-WP-0020-T07 | done | — | workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md |
 | task | REUSE-WP-0020-T08 | done | — | workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md |
diff --git a/workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md b/workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md
index 5f7549c..5a67111 100644
--- a/workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md
+++ b/workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md
@@ -259,7 +259,7 @@ Review the six weeks of change between `e3ae22e` and HEAD before applying.
 
 ```task
 id: REUSE-WP-0020-T06
-status: todo
+status: done
 priority: medium
 ```
 
@@ -276,15 +276,23 @@ Two smaller production inconsistencies found while verifying T01:
   carrying `server: nginx/1.27.5` (the landing container) rather than
   `uvicorn`.
 
-  Fix by setting an explicit
-  `traefik.ingress.kubernetes.io/router.priority` annotation so the API routes
-  outrank the landing catch-all, in `railiance-apps/charts/reuse-surface`.
-  This is not cosmetic: `make reuse-smoke` is the documented deploy
-  verification and it fails on an otherwise healthy release.
+  **Fixed 2026-08-21** — `railiance-apps@a365635`, Helm revision 8. The
+  `router.priority` annotation applies per *Ingress*, not per path, so the
+  landing catch-all moved into its own Ingress (`landing-ingress.yaml`) with
+  `priority: 1`; every API route now outranks it regardless of rule length.
+
+  | Path | Before | After |
+  |---|---|---|
+  | `/health` | `404`, `server: nginx` | **`200`, `server: uvicorn`** |
+  | `/` | `200`, landing | `200`, landing (unchanged) |
+  | `/v1/*` | `200` | `200` (unchanged) |
+
+  `make reuse-smoke` now passes end to end.
 - `composed_at` stayed at `2026-08-20T20:44:12` with `stale: false` across a
-  recompose that demonstrably changed output (61 → 62 capabilities). Now that
-  T05 has shipped REUSE-WP-0019-T06, re-observe before treating this as a bug —
-  the deployed build at the time predated the freshness work.
+  recompose that demonstrably changed output (61 → 62 capabilities). **Resolved
+  by T05, not a bug.** The build deployed at the time predated
+  REUSE-WP-0019-T06; `composed_at` now advances with each recompose
+  (`2026-08-21T00:18:02` observed after the redeploy).
 
 ## Refresh SCOPE.md Standard Sections