coulomb/rapp-playwright
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Reconcile deployed pilot and published browser discovery progress

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a13590-a16f-7f60-be60-fd71627bc99d
This commit is contained in:
tegwick 2026-10-13 21:43:20 +02:00
parent 70268154c0
commit 3a30ef159a
8 changed files with 661 additions and 28 deletions
Download patch file Download diff file Expand all files Collapse all files

27
workplans/RAPP-PLAYWRIGHT-WP-0004-consumer-verification.md
View file

@ -67,7 +67,7 @@ content-explorer assesses its own completion. A health response alone cannot pas
```task
id: RAPP-PLAYWRIGHT-WP-0004-T03
status: wait
blocked_on: message-from:reuse-surface
blocked_on: message-from:railiance-platform
priority: high
state_hub_task_id: "c8642437-27c5-5e58-b0f8-847c285fb4e6"
```
@ -122,3 +122,28 @@ prepares that decision without inferring approval. Reuse follow-up
T01 and T03 remain wait until their owner outcomes can be verified. Actual
cross-version rollback remains unproven with only one release; same-image
recovery must be labeled accurately.
## Owner progress accepted — 2026-10-13 21:42 Europe/Berlin
Platform reply `8d1de2a9-5209-4f82-a2cd-80d8c2e07001` and RPF-WP-0056
resolve package admission, deployment and the consumer group binding. Fresh
readback confirms 1/1 Ready on the published digest and a Bound 2Gi PVC.
Platform operator-driven evidence passes 14 fixture steps, six negative/health
checks, and same-image restart with all four artifact hashes retained. Evidence:
[readback and reviewed receipts](../docs/evidence/2026-10-13-owner-progress-readback.json).
This supersedes the earlier absent-namespace observations.
T01 remains wait specifically for real human/agent authentication, per-caller
API transport and native consumer receipts under RPF-WP-0056-T03, plus remaining
abrupt-interruption/recovery evidence. Initial eligibility is already decided;
no further membership approval is needed. RPF-WP-0056-T06 tracks Custodian
coordination. Administrator impersonation does not satisfy consumer acceptance.
REUSE-WP-0024 is finished and live federation now has D3/A5/C2/R2, pinned client
instructions, local container guidance and explicit conditional managed access.
The local-provider publication requirement is satisfied. T03's remaining wait
now follows platform consumer acceptance and the final managed-availability
update, rather than an unanswered local-provider registry handoff. The current
published admission-pending wording lags the deployed pilot and should distinguish
pilot runtime from consumer readiness in that update. T03 stays open as requested
by platform until the native consumer receipts are accepted.

2
workplans/README.md
View file

@ -5,7 +5,7 @@
| [WP-0001](RAPP-PLAYWRIGHT-WP-0001-statehub-bootstrap.md) | Demand and State Hub bootstrap | Finished |
| [WP-0002](RAPP-PLAYWRIGHT-WP-0002-consumer-contract.md) | Agent contract and trial | Finished |
| [WP-0003](RAPP-PLAYWRIGHT-WP-0003-service-package.md) | Service, client and Railiance package | Finished: implemented, tested, published and pulled by digest |
| [WP-0004](RAPP-PLAYWRIGHT-WP-0004-consumer-verification.md) | Activate, prove consumption and update discovery | Independent local trial/pilot done; managed activation and registry update blocked |
| [WP-0004](RAPP-PLAYWRIGHT-WP-0004-consumer-verification.md) | Activate, prove consumption and update discovery | Pilot deployed and A5 discovery published; real consumer access and managed acceptance pending |
The founder authorized implementation after the original bootstrap. Platform
lifecycle ownership is railiance-platform. Open tasks retain concrete external