RAIL-BS-WP-0008/0009 finished: live deploy, top-7 proof, admin-sync smoke

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

workplans/RAIL-BS-WP-0008-activity-core-wp0016-triage-output-deploy.md

@@ -4,7 +4,7 @@ type: workplan
 title: "activity-core WP-0016 triage-output robustness deploy"
 domain: financials
 repo: railiance-cluster
-status: active
+status: finished
 owner: railiance-cluster
 topic_slug: railiance
 created: "2026-07-01"
@@ -32,7 +32,7 @@ whole-doc validator. It MUST ship together with the new `executor.py`
 
 ```task
 id: RAIL-BS-WP-0008-T01
-status: progress
+status: done
 priority: high
 state_hub_task_id: "079e39a9-f938-4d03-a5bc-4d3d2f7b1d83"
 ```
@@ -64,7 +64,7 @@ image save/scp/import from the deploy README, sync the repo with `.git`, then
 
 ```task
 id: RAIL-BS-WP-0008-T02
-status: progress
+status: done
 priority: high
 state_hub_task_id: "129fb472-41e8-4e5c-bcbb-0995a96e223b"
 ```
@@ -89,7 +89,7 @@ or one-object-per-line framing, and `max_tokens` headroom of at least 1800.
 
 ```task
 id: RAIL-BS-WP-0008-T03
-status: todo
+status: cancel
 priority: medium
 state_hub_task_id: "59559f1d-821f-4660-8a7d-c623c6631864"
 ```
@@ -104,7 +104,7 @@ secrets.
 
 ```task
 id: RAIL-BS-WP-0008-T04
-status: todo
+status: done
 priority: high
 state_hub_task_id: "8096621a-54ee-4be5-943e-5dc2da19ed28"
 ```
@@ -120,4 +120,32 @@ WP-0006-T03.
 2026-07-02: The deploy command now triggers the daily-triage definition after
 reconcile and polls State Hub for a post-trigger `daily_triage` event with
 `output_validated=true`. If the run is partial, it also requires
-`quarantined_count>0` before posting pass evidence.
+`quarantined_count>0` before posting pass evidence.
+
+## Completion 2026-07-02
+
+Deployed live with operator authorization. Image `activity-core:railiance01-prod`
+rebuilt from main `7612112`, imported into railiance01 k3s
+(`sha256:550c5592...`), repo synced with git metadata, and
+`make deploy-activity-core-triage-robustness` applied the coupled
+schema/executor bundle with all rollouts and migrate/sync jobs green.
+
+- T01/T02 done: revision gate and runtime contract gate both passed
+  (`bounded_top_7`, `ndjson_or_line_framing`, `fewer_well_formed`,
+  `max_tokens_headroom` >= 1800 all true).
+- T04 done: manually triggered daily-triage run produced a clean schema-valid
+  report — State Hub event `24d2d321-c761-47f7-bf9e-7950a6253c21`
+  (2026-07-02T09:50:44Z) with `output_validated=true`, exactly 7 ranked
+  recommendations, `working_memory_status=written`, no validation error. The
+  bounded top-7 contract is proven live; the three-clean-run streak for
+  ACTIVITY-WP-0010-T04 / WP-0006-T03 restarts from this run.
+- T03 cancelled: the raw 2026-06-26 llm-connect response is unrecoverable —
+  the llm-connect pod is stateless (no volumes, no response store) and its
+  log stream contains only 2 startup lines from 2026-06-19. Root cause stands
+  on existing evidence (output truncation at ~char 5268 under the old
+  ~1200-token budget) and the deployed fix is live-proven.
+- Trigger note: the deployed API exposes definitions by `name`/`id` only (no
+  slug field), so the trigger step needs
+  `DAILY_TRIAGE_DEFINITION_SLUG=6fca51fa-387a-4fd0-bc4e-d62c29eb859a`; the
+  State Hub evidence poll can also exceed the default 240s window on slow LLM
+  runs.

workplans/RAIL-BS-WP-0009-activity-core-admin-sync-smoke.md

@@ -4,7 +4,7 @@ type: workplan
 title: "activity-core no-restart admin-sync smoke (ACTIVITY-WP-0012-T05)"
 domain: financials
 repo: railiance-cluster
-status: active
+status: finished
 owner: railiance-cluster
 topic_slug: railiance
 created: "2026-07-01"
@@ -30,7 +30,7 @@ The deploy precondition is covered by RAIL-BS-WP-0008-T01 (main at
 
 ```task
 id: RAIL-BS-WP-0009-T01
-status: wait
+status: done
 priority: medium
 state_hub_task_id: "60f3387d-3d14-42a9-b8a3-725a86468510"
 ```
@@ -54,4 +54,17 @@ optionally runs an operator-supplied enabled-flip/rename fixture via
 `POST /admin/sync?definitions=true&schedules=true`, verifies the expected
 response counters and empty `errors[]`, rechecks that the same worker pod did
 not restart, and posts non-secret State Hub evidence. T01 stays `wait` until
-RAIL-BS-WP-0008-T01 is deployed and the smoke is run on railiance01.
+RAIL-BS-WP-0008-T01 is deployed and the smoke is run on railiance01.
+
+## Completion 2026-07-02
+
+`make admin-sync-smoke` passed against the freshly deployed
+RAIL-BS-WP-0008 runtime: `POST /admin/sync?definitions=true&schedules=true`
+returned `ok=true` with `definitions.synced=6`, `schedules.upserted=4`,
+`schedules.paused=2`, `deleted_orphans=0`, empty `errors[]`, and the worker
+pod identity (`actcore-worker-5b78f85b76-ng54t`, restart_count 0) was
+unchanged before and after — proving no-restart admin sync. Non-secret
+evidence: State Hub event `4caa288d-830b-4348-9cff-b2d5855cd42d`. The
+optional enabled-flip fixture was skipped (no operator fixture supplied);
+schedule pause/upsert semantics were exercised by the sync counters. Closes
+ACTIVITY-WP-0012-T05.