docs: close OpenRouter credential recovery
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 2s

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a06bfe-2a55-7ed3-bacd-879977b099bf
This commit is contained in:
tegwick 2026-09-04 19:07:54 +02:00
parent c2c6949cd2
commit 44568a5c70

View file

@ -29,7 +29,7 @@ contracts found during the 2026-08-20 activity-core review.
```task
id: ACTIVITY-WP-0031-T01
status: wait
status: done
priority: high
state_hub_task_id: "d84116ae-8219-569a-8d7b-e4eb83c192c3"
```
@ -115,6 +115,18 @@ an ownership decision. Reconciliation request
newly issued, newline-free key at the canonical path, allow ESO to sync,
restart `llm-connect`, and return value-free fixture evidence.
Resolved 2026-09-04 by operator decision
`914e0e04-fd17-4fba-b2d5-be38f7aca185`. The operator identified the current
`reins/rein-openweights/openrouter` `api_key` as the approved recovery source.
Its OpenBao version 2 value is 73 bytes, has fingerprint `bf082d029c0c`, and
was recognized by OpenRouter with HTTP 200. It was copied without exposure into
the canonical activity-core path as version 2; the source remained unchanged
and target version 1 remains rollback evidence. ESO synchronized the new
fingerprint, `llm-connect` rolled out cleanly, and an in-cluster live smoke
returned health `ok` plus HTTP 200 from `google/gemini-2.5-flash` with non-empty
content and usage metadata. The cross-lane reuse is explicit in the decision;
the two OpenBao delivery paths remain separate.
## Emergency-pause weekly SBOM fan-out
```task