fix(ops): surface pre-record schedule failures

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

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

@@ -347,6 +347,15 @@ Depends on T02–T07 as applicable.
 - 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.
+- Hardened the production status helper so it runs the deterministic
+  multi-source schedule verdict before its SQL detail. Live validation for the
+  window since 2026-08-30 now reports Weekly Forgejo Package Prune as `missed`
+  (`expected=1`, `runs=0`) instead of omitting a failure that occurred before an
+  `activity_runs` row was written. The helper treats a findings exit code as
+  evidence and still prints its remaining bounded diagnostics. The full source
+  suite passes (`494 passed, 1 skipped`), and an activity-filter regression test
+  prevents unrelated evidence-only definitions from leaking into targeted
+  reports.
 - State Hub message `868a2326-cdad-4256-be4c-7cd6c8ec4b5b` asks
   railiance-platform to move the generated protection inventory onto a durable
   checkout-independent path and refresh it through the platform image-rollout