codex
a042bee363
Completes the migration begun on 2026-08-25, which covered active workplans only. The archived copies kept their historical identifiers, and three repositories shared one number space — so their task identifiers collided, blocking task-level projection reset for those workplans. Numbering continues each repository's active sequence rather than restarting, so no identifier is reused. Projection UUIDs are re-derived from the new canonical ids. Refs CUST-WP-0068, STATE-WP-0083-T06 Assistant: claude-code Assistant-Model: opus Assistant-Process: 2583210@bnt-lap001 Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
3.9 KiB
| id | type | title | domain | repo | status | owner | topic_slug | created | updated | state_hub_workstream_id |
|---|---|---|---|---|---|---|---|---|---|---|
| RCLUSTER-WP-0003 | workplan | activity-core llm-connect live reconcile | financials | railiance-cluster | finished | codex | railiance | 2026-06-18 | 2026-07-01 | 93e33e49-4bc3-57fd-a3f7-da46fcb7793d |
Terminology note: Historical text in this archived workplan may use the legacy term "workstream". The fleet term is workplan (
canon/standards/workplan-terminology-fleet_v0.1.md).
activity-core llm-connect live reconcile
Context
activity-core has updated its Railiance runtime manifest so
actcore-runtime-config points at the verified in-cluster llm-connect URL:
LLM_CONNECT_URL=http://llm-connect.activity-core.svc.cluster.local:8080
LLM_CONNECT_TIMEOUT_SECONDS=300
The remaining live gate belongs at the cluster/operator layer. Provider credentials must stay outside Git and State Hub, and the fixture smoke should record only non-secret evidence.
Add cluster-owned reconcile/check command
id: RCLUSTER-WP-0003-T01
status: done
priority: high
state_hub_task_id: "b752a0cd-b3b7-5ace-ba79-71504e26169f"
Add a repeatable Railiance command that:
- reconciles the non-secret activity-core runtime config keys;
- checks the provider Secret by key count only;
- applies the llm-connect overlay only after the provider Secret exists;
- runs the in-namespace fixture smoke only after deployment readiness;
- posts a non-secret State Hub evidence note.
2026-06-18: Added tools/cmd/railiance-reconcile-activity-core-llm-connect
and Makefile target reconcile-activity-core-llm-connect.
Reconcile live non-secret runtime config
id: RCLUSTER-WP-0003-T02
status: done
priority: high
state_hub_task_id: "90fe9a18-3d05-5faa-862d-8079d9412260"
Patch the live activity-core/actcore-runtime-config ConfigMap so it consumes
the verified llm-connect service URL and timeout. Do not touch Secret values.
2026-06-18: The reconcile command patches only LLM_CONNECT_URL and
LLM_CONNECT_TIMEOUT_SECONDS, then re-reads the live ConfigMap to verify the
values. Live evidence note c72c514a-399e-4c54-8d5b-d36405932360 confirms
LLM_CONNECT_URL=http://llm-connect.activity-core.svc.cluster.local:8080 and
LLM_CONNECT_TIMEOUT_SECONDS=300.
Complete provider Secret, deployment, and smoke gate
id: RCLUSTER-WP-0003-T03
status: done
priority: high
state_hub_task_id: "1764a7e3-b21e-5f71-a68f-c66988e4ccdf"
After an operator stores provider credentials in
activity-core/llm-connect-provider-secrets, rerun:
make reconcile-activity-core-llm-connect
The command will apply the llm-connect overlay, wait for deployment readiness,
run the in-namespace fixture smoke with imagePullPolicy=Never, and post
non-secret evidence: provider Secret key count, deployment readiness,
pass/fail, latency/recommendation summary or sanitized failure.
2026-07-01: Gate closed. Provider Secret activity-core/llm-connect-provider-secrets
present (key count 1, no values inspected), overlay applied (no drift),
deployment llm-connect ready 1/1, in-namespace fixture smoke passed
(health=ok latency_seconds=2.084 recommendations=1). Evidence note
bddbf5d2-6cbe-4d97-9de6-689147d61be1. The first rerun failed with
Connection refused because the llm-connect-activity-core-only
NetworkPolicy (added 2026-06-19) allowlist had not yet propagated the fresh
smoke-pod IP; the reconcile tool now retries the smoke up to 6× with a 5s
warm-up inside the pod.
Historical live gate on 2026-06-18: provider Secret
activity-core/llm-connect-provider-secrets is missing, so deployment and
smoke are intentionally blocked until operator/OpenBao-to-Kubernetes Secret
custody is complete. Evidence note
c72c514a-399e-4c54-8d5b-d36405932360 records provider Secret status
missing, key count 0, deployment status not checked; provider Secret gate not satisfied, and smoke status blocked.