docs: record profiled consumer deployment blocker

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a02b6f-7db1-7222-918b-e813a6bda38d
This commit is contained in:
tegwick 2026-08-23 00:01:20 +02:00
parent 79a003322a
commit abe1d305f5

View file

@ -4,7 +4,7 @@ type: workplan
title: "Profile-driven ops-run execution through Glas"
domain: infotech
repo: rein-aharness
status: active
status: blocked
owner: codex
topic_slug: rein-aharness
priority: high
@ -90,7 +90,7 @@ redaction-by-allowlist, bounding, and unusable bodies.
```task
id: REIN-A-0004-T04
status: progress
status: wait
priority: high
state_hub_task_id: "b19a4dab-d6d7-537a-8c8f-77217f0d9069"
```
@ -114,3 +114,13 @@ worker's prior error path retried that failure every two seconds; it now uses
the configured 30-second backoff for claim errors and reserves the short pause
for cycles that actually claimed work. Activity Core must apply/verify its
migration before the coordinated pilot can run.
**Live deployment evidence:** railiance01 runs consumer `db58801`,
glas-harness `ae2a706`, and sand-boxer `20258de`; the user service is active,
the packaged profile catalog validates all three profiles, and the remote
unknown-profile probe refused before sandbox creation. Journal timestamps
`21:59:13`, `21:59:43`, and `22:00:13` UTC prove the corrected 30-second error
backoff. Activity Core handoff `413a4041-cfb3-4d02-a41a-1d92b3de06af`
contains the production traceback and requests migration application before a
pilot is scheduled. T04 waits only on that upstream repair and the coordinated
low-risk proof.