Codex daily-state-hub-wsjf-triage paused per operator confirmation;
activity-core is now the only enabled runner for the daily State Hub
WSJF triage at 07:20 Europe/Berlin. Set status: draft → active to
match.
Temporal schedule activity-schedule-6fca51fa-... is unpaused; next
run tomorrow ~07:20 Europe/Berlin will be the first real scheduled
verification.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The daily-triage workflow completed end-to-end with all three evidence
surfaces (working-memory note, State Hub daily_triage event, ActivityRun
row) referencing the same run_id f9b97749. Backend: llm-connect against
OpenRouter anthropic/claude-sonnet-4, 12.85s end-to-end.
Add Implementation Notes - 2026-06-02 capturing the bug chain found and
fixed today (five llm-connect commits, two activity-core commits), the
backend choice and its consequences for the next scheduled run, and an
explicit carve-out: the operational cutover step (pause Codex, flip
enabled: true, sync schedules) is intentionally deferred to operator
action and remains a prerequisite for T08.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
llm-connect's CLI default port (:8080) collides with the dev stack's
temporal-ui container. Hit during the 2026-06-01 cutover attempt with
OSError: Address already in use. Update Steps 3, 5, and 6 to use :8088
and note the conflict reason inline so the next operator does not
rediscover this the slow way.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
T06 remains in_progress — no canary was rerun. Capture the runbook deliverable
(workplans/CUST-WP-0045-cutover-runbook.md @ 8ef5399), the still-unchanged
upstream fixes that should let the patched canary succeed, and the two
operational gotchas the runbook now documents (host-mode env overrides vs.
Docker-network .env; Claude CLI quota collision when triggering from inside
an active Claude Code session). Bump updated: to 2026-06-01.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Exact command sequence to rerun the patched real-LLM canary and, on success,
perform the Codex → activity-core cutover. Captures the heads-up about CLI
session collision, the host-mode env-var overrides for the worker/API, and the
verification queries for all three evidence surfaces. Frontmatter uses
type: runbook so the consistency checker does not treat it as a workstream.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
