docs: record Forgejo prune recovery evidence

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a06bfe-2a55-7ed3-bacd-879977b099bf

workplans/ACTIVITY-WP-0035-intent-boundary-guardrails.md

@@ -9,7 +9,7 @@ owner: codex
 topic_slug: activity-core
 priority: high
 created: "2026-08-23"
-updated: "2026-08-23"
+updated: "2026-09-04"
 quality_dor: DoR-Ok
 quality_dor_at: "2026-08-23"
 quality_dor_by: codex
@@ -325,6 +325,29 @@ Depends on T02–T07 as applicable.
   Natural post-rollout operation evidence remains open: CNPG and SBOM next run
   2026-08-24; Forgejo prune next run 2026-08-30. No schedule was manually fired.
 
+## Production evidence follow-up — 2026-09-04
+
+- The read-only and two of three bounded-operation classes have natural
+  post-rollout evidence. Daily CNPG backup is healthy through 2026-09-04
+  (`run_id=da76a381-af99-5c91-ab7f-6df9ed89e710`, four dumped/uploaded,
+  zero failed). Daily SBOM catch-up completed its controlled 2026-08-24 fire
+  (`run_id=4c4594ad-366b-5720-b3f9-44fb300fda70`, three frozen references,
+  State Hub progress `f62eaadd-d10c-4a21-8547-293569ed5637`).
+- The 2026-08-30 Forgejo prune schedule did fire naturally, but failed closed
+  before mutation because its required hostPath inventory
+  `docs/evidence/live-images-all.txt` was absent after the platform checkout
+  changed. No packages were deleted and no progress evidence was emitted for
+  the rejected run.
+- Rebuilt the railiance01 inventory on 2026-09-04 and merged the preserved
+  coulombcore export. The worker now sees 51 non-empty lines with SHA-256
+  `ceb53015d130e205314892262d331925fb3fa6c88d9429da65189b432566296a`.
+  A read-only prune dry-run returned zero errors and zero deletions, admitted
+  22 protected package versions, and explicitly skipped both protected
+  State Hub tags (`f2e042a`, `main-1cf949b`).
+- Temporal reports the schedule enabled and unpaused. T08 remains `progress`
+  until the next natural apply fire (2026-09-06 03:30 UTC) produces successful
+  State Hub evidence; the schedule was not manually fired.
+
 ## Gap disposition
 
 | 2026-08-23 gap | This workplan |