Open RAILIANCE-WP-0015: platform rapp consistency
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s

Survey of the four-axis repo family model against the live cluster and all six
family repos found the concepts sound but unenforced: rapp.yaml has no schema
and has drifted three ways across the three existing rapps, the reef binding
registry lists 1 of 3 live rapps, the rapp population diverged from the
first-wave plan of record, and the model is not in custodian canon so
fix-consistency cannot check it.

Operator decisions recorded in the workplan: grouped-by-bounded-context rapp
granularity, S3 owns only its own rapps and routes schema/canon changes to the
repos that own them, canonize the model now, and build the missing wave-1
user-facing exemplar.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
codex 2026-08-11 11:08:44 +02:00
parent b7aef386d5
commit b876a9b5ba
3 changed files with 194 additions and 0 deletions

View file

@ -12,6 +12,7 @@ updated: "2026-08-11"
related_repos:
- rapp-postgres
- ops-warden
state_hub_workstream_id: "4dea40b7-43f5-499a-8919-79221623aa79"
---
# RAILIANCE-WP-0014 - Credential-change test suite stabilization
@ -62,6 +63,7 @@ It must not:
id: RAILIANCE-WP-0014-T01
status: done
priority: high
state_hub_task_id: "18d3358b-2cd6-4fe0-aab6-602f85d8cccd"
```
Repair `CCR-2026-0009` (qonto-assistant workload KV read lane) so it validates:
@ -79,6 +81,7 @@ missing source artifact, it does not advance the lane.
id: RAILIANCE-WP-0014-T02
status: done
priority: high
state_hub_task_id: "4705a142-4168-41a8-aba0-691d8fc3c6bd"
```
Stop the refusal tests depending on live CCR lifecycle state. Add a
@ -99,6 +102,7 @@ already correct and was left untouched.
id: RAILIANCE-WP-0014-T03
status: done
priority: medium
state_hub_task_id: "dd34d578-97e5-4c26-aef8-faafc994c387"
```
Fix `test_approve_records_comment_but_unconfirmed_claim_still_blocks_apply`,
@ -112,6 +116,7 @@ test actually wants. The validation rule is correct and unchanged.
id: RAILIANCE-WP-0014-T04
status: done
priority: high
state_hub_task_id: "457053f2-261f-4c80-92d4-c084e6236e88"
```
Confirm acceptance against the requested criteria: