Close WP-0035 and count declared sink evidence in automation status

The status surface queried only four fixed State Hub event types, so
bounded-operation evidence (Forgejo prune, CNPG, SBOM) showed evidence=0
despite successful runs. Default queries now include every
state-hub-progress event type the definitions' report/evidence sinks declare.

Three natural prune fires (2026-09-06/13/20) supply the last missing
bounded-operation evidence, so ACTIVITY-WP-0035-T08 and the workplan finish.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 241500@bnt-lap001
Assistant-Session: 4a77db80-b523-4a03-83c4-e3da08755c30

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

@@ -4,13 +4,13 @@ type: workplan
 title: "Make the execution boundary enforceable and the review contract truthful"
 domain: infotech
 repo: activity-core
-status: active
+status: finished
 flavor: planning
 owner: codex
 topic_slug: activity-core
 priority: high
 created: "2026-08-23"
-updated: "2026-09-04"
+updated: "2026-09-21"
 quality_dor: DoR-Ok
 quality_dor_at: "2026-08-23"
 quality_dor_by: codex
@@ -271,7 +271,7 @@ activity-core is a general task executor.
 
 ```task
 id: ACTIVITY-WP-0035-T08
-status: progress
+status: done
 priority: high
 state_hub_task_id: "2ae1aca9-1c86-5b1a-b9fd-95059a24cd65"
 ```
@@ -298,7 +298,7 @@ Depends on T02–T07 as applicable.
 - [x] Instruction audit wording matches persisted evidence and raw sensitive payloads remain excluded
 - [x] `review_required` has truthful, tested hold/release or advisory-only semantics
 - [x] Misleading executor/CRUD/README surfaces are removed or precisely qualified
-- [ ] Full tests pass and production rollout preserves current schedules and evidence
+- [x] Full tests pass and production rollout preserves current schedules and evidence
 
 ## Implementation evidence — 2026-08-23
 
@@ -363,6 +363,28 @@ Depends on T02–T07 as applicable.
   lifecycle. That residual must preserve multi-cluster over-protection and the
   existing apply refusal when the inventory is absent or empty.
 
+## Closeout — 2026-09-21
+
+- The third bounded-operation class now has natural post-rollout evidence.
+  Weekly Forgejo Package Prune fired unassisted on 2026-09-06, 09-13, and
+  09-20 against the durable inventory path, each with `apply: true`,
+  `error_count=0`, and protected skips honoured:
+
+  | Run | Deleted | Protected skips | State Hub progress |
+  | --- | --- | --- | --- |
+  | `65354265-6425-51fb-be5f-20bfae99f550` | 175 | 4 | 2026-09-06T03:30:16Z |
+  | `d0ce2658-0bab-5fe3-9377-36d5c56193a4` | 85 | 5 | 2026-09-13T03:30:14Z |
+  | `fac35de6-095d-59ec-8af0-f8a15440d3b4` | 52 | 5 | `c5e538a7-e2a6-49df-9da5-1aef315ee77e` |
+
+  No schedule was manually fired. CNPG backup and SBOM catch-up remained
+  `completed` for every expected fire since 2026-09-05.
+- Residual found during closeout: the deterministic status surface reported
+  `evidence=0` for these runs because its default State Hub query covered only
+  four fixed event types. Source now also queries every `state-hub-progress`
+  event type declared by definition report/evidence sinks (504 passed,
+  1 skipped). It takes effect in production at the next image rollout; the
+  evidence above was read directly from State Hub.
+
 ## Gap disposition
 
 | 2026-08-23 gap | This workplan |