coulomb/activity-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add bounded Glas profile production pilot
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
Build and Publish Container Image / build-and-push (push) Successful in 6s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a028de-e2c8-7732-8521-46a7fc5db82f
This commit is contained in:
tegwick 2026-08-23 00:13:11 +02:00
parent caed3d2ab9
commit 01ee87de12
4 changed files with 100 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

20
workplans/ACTIVITY-WP-0032-glas-profile-execution-contract.md
View file

@ -230,7 +230,7 @@ deselected because it requires the local integration stack.
```task
id: ACTIVITY-WP-0032-T05
status: wait
status: progress
priority: low
state_hub_task_id: "e71423f9-8baf-566b-8a70-eec195e2f65f"
```
@ -241,16 +241,14 @@ definition is proven end to end. Note that FI and Binky are unsuitable as the
pilot while ACTIVITY-WP-0031-T01 is unresolved — their failures are currently
provider-credential failures and would mask the result.
Wait confirmed 2026-08-22 after T03/T04 source completion. The current
rein-aharness claim consumer does not yet carry `harness_profile_ref` or
`execution_refs` in `OpsRun.from_api`; its claim loop still calls the legacy
`select_approach` matcher. Launching a profiled pilot now could silently ignore
the authoritative selector, so Activity Core will not do that. Consumer handoff
message `4ed3422a-b42c-4408-843c-f63c3e86cf3e` asks rein-aharness to invoke
Glas for profiled rows with no legacy fallback and return the full
`GatewayResult`. Glas was notified in thread message
`6ac93cc9-6d5b-4039-aa89-81a025efef82`. Resume T05 only after that consumer
slice is tested and deployed and a low-risk pilot is available.
Resumed 2026-08-23. Rein-aharness source `0f01c3e` is deployed on railiance01:
profiled rows now preserve `harness_profile_ref` / `execution_refs`, route
through Glas before legacy selection, refuse without fallback, and return the
full `GatewayResult`. Handoff confirmation
`413a4041-cfb3-4d02-a41a-1d92b3de06af` also identified production schema
drift: the live image expects migration `0008`, while PostgreSQL was still at
`0007`, making `/ops-runs/claim` fail with `UndefinedColumnError`. Apply and
verify the additive migration before scheduling the pilot.
## Acceptance