activity-core

Files

tegwick c79d0980a9 Make Temporal activity timeout env-configurable (ADHOC-2026-06-01-T03)

The CUST-WP-0045 daily triage canary on 2026-06-01 hit a BrokenPipeError
on the llm-connect side. Two 5-minute timeouts were racing:

- _ACTIVITY_TIMEOUT = timedelta(minutes=5) in workflows.py
- LLM_CONNECT_TIMEOUT_SECONDS default 300 in llm_client.py

The 10KB curated digest + max_depth:2 + JSON schema enforcement pushed
Claude past 5 minutes. Whichever timer fired first killed the httpx call;
the model's late response arrived to a closed socket.

Read _ACTIVITY_TIMEOUT from ACTIVITY_TIMEOUT_SECONDS env (default 900 —
15 minutes) so judgement-call activities have headroom for slow LLM runs.
Operators should also widen httpx via LLM_CONNECT_TIMEOUT_SECONDS=840 so
httpx still times out slightly before Temporal, preserving the
clean-error contract.

Tests: 120 passed, 1 skipped.

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

2026-06-02 08:10:24 +02:00

ACTIVITY-WP-0005-railiance01-production-service.md

Record state hub IDs for railiance deployment

2026-05-22 13:51:51 +02:00

ADHOC-2026-06-01.md

Make Temporal activity timeout env-configurable (ADHOC-2026-06-01-T03)

2026-06-02 08:10:24 +02:00

custodian-WP-0001-temporal-backbone.md

chore(workplan): close WP-0001 Foundation — all 21 tasks done

2026-05-14 15:03:26 +02:00

custodian-WP-0002-triggers-ops.md

feat(WP-0002): complete Triggers & Ops workstream