Repair production automation truth and schedule cleanup

workplans/ACTIVITY-WP-0030-daily-sbom-catchup.md

@@ -8,7 +8,7 @@ status: active
 owner: grok
 topic_slug: infotech
 created: "2026-08-18"
-updated: "2026-08-18"
+updated: "2026-08-20"
 parent_workplan: CUST-WP-0062
 related:
   - CUST-WP-0062
@@ -92,16 +92,17 @@ oldest never-scanned repo.
 
 ```task
 id: ACTIVITY-WP-0030-T03
-status: wait
+status: progress
 priority: high
 state_hub_task_id: "18bcfc21-616a-48a2-aac3-cdcef7579913"
 ```
 
-After the daily job is proven on railiance01: set
-`weekly-sbom-staleness` `enabled: false` (or remove `flag-stale-sbom`), keep
-or drop the weekly summary report only if it no longer emits one task per
-repo. Update runbook / playbook. Prove one Monday window with zero SBOM task
-spawns and a successful daily catch-up the same week.
+Emergency containment began 2026-08-20 under ACTIVITY-WP-0031: set
+`weekly-sbom-staleness` `enabled: false` in source and production before the
+bounded replacement is available. Keep or drop the weekly summary report only
+if it no longer emits one task per repo. After the daily job is proven on
+railiance01, update the runbook / playbook and prove one Monday window with zero
+SBOM task spawns and a successful daily catch-up the same week.
 
 ### Prod enable and evidence