Reconcile deployed pilot and published browser discovery progress

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a13590-a16f-7f60-be60-fd71627bc99d

SCOPE.md

@@ -1,10 +1,11 @@
 # Scope — rapp-playwright
 
-As of 2026-10-13, the service, standalone Python client, browser trial and
-Railiance package are implemented and verified locally. **Managed Railiance
-availability is not established.** Release 0.1.0 is published and verified by a
-cluster pull; platform admission has not been confirmed. The founder selected `railiance-platform` as lifecycle
-owner; service implementation remains here.
+As of 2026-10-13 21:42 Europe/Berlin, release 0.1.0 is published and the
+**Railiance pilot is deployed, with 1/1 Ready replica and a Bound 2Gi PVC**.
+Platform recorded operator-driven browser, permission, cancellation and restart
+proof. **Self-service managed availability is not yet established:** real human
+and coding-agent authentication and per-caller connectivity remain pending.
+Lifecycle ownership is railiance-platform; service implementation remains here.
 
 ## Implemented and evidenced
 
@@ -21,6 +22,11 @@ owner; service implementation remains here.
   browser negative passed. Independent initial and final-image trials verified
   screenshots, keyboard results, artifact hashes and failure categories. Final
   image restart preserved completed receipt/artifact retrieval.
+- Platform pilot on railiance01 passed 14 responsive/keyboard steps, six negative/health
+  checks and same-image restart with four preserved screenshots. Fresh readback
+  confirmed Ready, the exact release image, PVC binding and consumer group binding.
+  All four retained PNG hashes match original and post-restart download receipts.
+  Access used administrator impersonation; this does not prove consumer login.
 - Pinned OnCo home-page pilot passed at desktop and narrow widths with skip-link
   keyboard assertions. Evidence was handed to content-explorer; its T04 and
   visual/route acceptance remain consumer-owned.
@@ -42,23 +48,29 @@ artifacts expire; sanitized evidence under `docs/evidence/` is retained.
 | --- | --- |
 | WP-0002 | Finished: consumption contract, lifecycle and trial/pilot design |
 | WP-0003 | Finished: tested image published at its exact digest and pulled on railiance01; ingress upload deadline fixed. |
-| WP-0004 | T02 provider trial/pilot done. T01 waits on platform admission/access; T03 waits on reuse-surface's maintained/published discovery update. |
+| WP-0004 | T02 provider trial/pilot done. T01 awaits actual consumer identity/access and remaining recovery evidence. T03 has published A5 local-provider discovery; final managed availability update awaits T01. |
 
-Fresh resumed readback confirmed the `playwright` namespace is absent. No browser workload was created. Server
-admission, private consumer binding, live target reachability, managed independent
-trial, restart/cancellation and cross-version rollback remain unverified.
-[Release 0.1.0](releases/0.1.0.json) is now published; see the
-[publication fix and pull evidence](docs/evidence/2026-10-13-publication.md). Package validation/rendering
-and Kubernetes client dry-run passed; they do not imply server admission.
+Platform admitted and deployed the reviewed package under RPF-WP-0056. The
+`playwright-consumers` group is bound to the namespace consumer Role. Initial
+eligibility includes all identified platform humans and coding agents; no further
+membership decision is needed. Registration, native JWT authentication,
+per-caller API transport, renewal/revocation and real consumer receipts are still
+open in RPF-WP-0056-T03. Custodian coordination is requested in T06.
 
-Existing capability `capability.infotech.headless-browser` was still D3/A2/C2/R2
-with source-reuse/planned-provider wording at readback. The owner received actual
-local evidence and the usable client path; registry publication is pending.
-The [fresh readback](docs/evidence/2026-10-13-2031-resumed-readback.json) also
-confirmed local preflight availability at the checked time. The
-[admission review packet](docs/platform-admission.md) identifies the exact package
-and remaining platform decisions. Publication updates were sent in both existing
-owner threads. Open workplan tasks retain blocker messages and exact resume steps.
+Existing capability `capability.infotech.headless-browser` is now published at
+D3/A5/C2/R2 with pinned client/contract/release links and runnable local guidance.
+REUSE-WP-0024 completed the local-provider discovery and relevance work. General
+managed availability must remain unclaimed until real consumer acceptance.
+The published summary still says managed admission is pending; its next update
+should distinguish the running operator pilot from incomplete consumer access.
+
+The [owner progress readback](docs/evidence/2026-10-13-owner-progress-readback.json)
+retains current cluster/discovery observations and platform runtime receipts.
+Platform's [consumer access instructions](https://forgejo.coulomb.social/coulomb/railiance-platform/src/commit/d303c99e3be993ffa989bc9ba3d7b471903858ce/docs/playwright-consumer-access.md)
+are prepared but conditional on identity-owner activation. The earlier
+[admission review](docs/platform-admission.md) is retained as history; package
+admission, deployment and the binding are no longer the outstanding decision.
+Abrupt-interruption recovery and actual cross-version rollback remain unverified.
 
 ## Deliberate limits
 
@@ -69,5 +81,5 @@ sandbox is disabled; hostile pages and mutually untrusted tenants are unsupporte
 Target failures identify the category but not detailed DNS/TLS/HTTP causes.
 The OnCo pilot covers the home page, not all consumer routes or accessibility.
 
-See the [timestamped intent assessment](history/2026-10-13-2033-intent-scope-assessment.md)
+See the [timestamped intent assessment](history/2026-10-13-2142-intent-scope-assessment.md)
 for the prioritized gaps and their acceptance evidence.