Close WB-6: baseline records stay dated snapshots (P5-09, P5-12)

CHANGELOG.md

@@ -116,6 +116,9 @@ this project uses [semantic versioning](https://semver.org/).
 
 ### Changed
 
+- The implementation plan carries the same point-in-time banner as the other baseline records. P5-09 and P5-12 are
+  closed in the roadmap: the records stay as dated snapshots, and no pull request or Dependabot item is open.
+
 - Blocker B4 is resolved by retiring the claim. The two tests that compared a published Basalt estimate of TUM VI
   room1 with a subsampled ground truth always skipped, because neither file could be fetched. They are removed. The
   claim of a reproduction of the published 0.069 m is dropped. `tests/test_recorded_orientation.py` takes over the

ROADMAP.md

@@ -306,8 +306,10 @@ Where each item stands:
   P5-13 (a TUM VI fetch path).
 - **Spike done, opt-in:** P5-03 (the stochastic clone, [ADR-0017](docs/adr/0017-stochastic-clone-for-the-visual-update.md)).
   Calibrated for independent visual errors, not for correlated ones. The shipped configuration is unchanged.
-- **Partly done:** P5-09 (the stale figures in docstrings are fixed; the baseline records are excluded from the site
-  and not rewritten), P5-12 (the pull requests it names are closed; `uv.lock` was removed).
+- **Done as decided:** P5-09 (the stale figures in docstrings are fixed; every baseline record is a dated
+  point-in-time snapshot with a banner saying so, excluded from the site and deliberately not rewritten, because their
+  old figures are what the remediation was measured against) and P5-12 (no pull request or Dependabot item is open,
+  `uv.lock` was removed).
 - **Not started:** P5-11 (a comparison with an established consistent
   estimator, which strains constraint S1).
 

docs/IMPLEMENTATION_PLAN.md

@@ -1,5 +1,10 @@
 # Implementation plan
 
+> **Point-in-time snapshot (2026-09-29).** This plan was written from the audit, before the remediation in
+> `CHANGELOG.md` was applied. The baseline figures below are deliberately not updated: they are what the work was
+> measured against. For the current state see `ROADMAP.md` and `CHANGELOG.md`.
+
+
 Derived from `docs/ENGINEERING_BASELINE.md` and `docs/PUBLICATION_READINESS.md`
 (audit 2026-09-29). Prioritised by impact on correctness, reproducibility,
 research credibility, and publication safety. Not a wish list: every item cites

docs/product_management/05_work_breakdown.md

@@ -27,7 +27,7 @@ TUM VI data path was M. No hours are quoted, because none were recorded.
 | WB-6 | Remaining P5-09 and P5-12 | Baseline records and the pull-request clean-up | None | S | Stated in the roadmap item. |
 | WB-7 | UrbanNav | A licence answer, then a third dataset | Issue 94 | M | The licence permits the use, or the dataset is dropped. |
 
-WB-1 is done: the [vision-ramp study](../vision_ramp.md) puts the floor at about 2 m/s for independent visual errors. WB-2 has a feasibility result: the [fault classification study](../fault_classification.md) separates multipath, calls spoofing in about three quarters of runs and has a control false-alarm rate of 35% on unseen runs, so the exit test is not met and the package stays open. WB-4 is done: option 3 was taken and B4 is resolved (R5 in `CONSTRAINTS.md`). WB-7 is on hold.
+WB-1 is done: the [vision-ramp study](../vision_ramp.md) puts the floor at about 2 m/s for independent visual errors. WB-2 has a feasibility result: the [fault classification study](../fault_classification.md) separates multipath, calls spoofing in about three quarters of runs and has a control false-alarm rate of 35% on unseen runs, so the exit test is not met and the package stays open. WB-6 is done: the baseline records are dated snapshots by decision, and no housekeeping item is open. WB-4 is done: option 3 was taken and B4 is resolved (R5 in `CONSTRAINTS.md`). WB-7 is on hold.
 
 ## 3. B4: the published TUM VI estimate