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

docs: refresh OpenRouter credential evidence
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a06bfe-2a55-7ed3-bacd-879977b099bf
This commit is contained in:
tegwick 2026-09-04 17:49:08 +02:00
parent 3e94cfd43a
commit c2c6949cd2
1 changed files with 11 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

11
workplans/ACTIVITY-WP-0031-production-execution-reliability-cleanup.md
View file

@ -104,6 +104,17 @@ value outright). It is currently harmless only because
does not strip would fail on a perfectly valid key. Worth fixing in the
OpenBao→ESO lane while the key is being replaced.
Rechecked 2026-09-04 without reading or printing the value. The canonical
OpenBao record is still KV version 1 created 2026-07-02. Its ESO-managed
Kubernetes Secret and the running `llm-connect` process have the same 74-byte
fingerprint `ab938241a2ec`; production continues to return sanitized upstream
401. Thus no replacement is waiting for a pod restart. The only other cataloged
OpenRouter lane is scoped to `rein-openweights` and is not transferable without
an ownership decision. Reconciliation request
`c32901ff-2072-4b93-81cd-db93dddfa5f3` asks railiance-platform to install a
newly issued, newline-free key at the canonical path, allow ESO to sync,
restart `llm-connect`, and return value-free fixture evidence.
## Emergency-pause weekly SBOM fan-out
```task