Enforce bounded operation guardrails
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Build and Publish Container Image / build-and-push (push) Successful in 21s

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a028de-e2c8-7732-8521-46a7fc5db82f
This commit is contained in:
tegwick 2026-08-23 12:31:13 +02:00
parent c384f60530
commit 26934e25b9
51 changed files with 1843 additions and 472 deletions

View file

@ -427,11 +427,13 @@ Default: **`ISSUE_SINK_TYPE=state-hub`** (ACTIVITY-WP-0022). See
| `null` | Dry-run |
| `rest` | Intentional issue-core / external tracker only |
`TaskExecutorWorkflow` is **disabled** unless
`ACTIVITY_CORE_ENABLE_TASK_EXECUTOR_STUB=true` (legacy tests only).
The legacy `TaskExecutorWorkflow`, its feature flag, and `task_instances` table
were removed by ACTIVITY-WP-0035 after production inventory proved zero use.
`review_required` on instructions is **metadata only** until a downstream
review queue exists (issue-core / work-record lane) — see ACTIVITY-WP-0023-T09.
`review_advisory` on instructions is **advisory evidence only** and report
projections state `review_gate_applied=false`. Legacy `review_required` input is
normalized for compatibility; no pending-review queue or hold occurs here. See
ACT-ADR-003 and ACTIVITY-WP-0035.
## Ops run claim queue (ACTIVITY-WP-0026)
@ -736,7 +738,7 @@ the next scheduled fire is the next authoritative run.
### Multiple worker replicas
Temporal workers are stateless and horizontally scalable. Run additional worker
processes to increase throughput on `orchestrator-tq` and `task-execution-tq`.
processes to increase throughput on `orchestrator-tq`.
Each worker registers the same workflows/activities — Temporal distributes tasks
across all pollers automatically.