chore(consistency): sync task status from DB [auto]

Updated by fix-consistency on 2026-10-13:
  - update .custodian-brief.md for rapp-playwright

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a13590-a16f-7f60-be60-fd71627bc99d
This commit is contained in:
custodian-sync 2026-10-13 20:24:20 +02:00
parent e2705891ac
commit e9b63c307b
15 changed files with 409 additions and 20 deletions

View file

@ -2,7 +2,7 @@
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.** Image publication failed and platform admission
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.
@ -41,13 +41,14 @@ artifacts expire; sanitized evidence under `docs/evidence/` is retained.
| Workplan | State and remaining evidence |
| --- | --- |
| WP-0002 | Finished: consumption contract, lifecycle and trial/pilot design |
| WP-0003 | Local implementation complete; T01 waits on OCI publication. Forgejo blob PUT returned HTTP 499/500 and remote manifest inspection returned `manifest unknown`. |
| WP-0004 | T02 provider trial/pilot done. T01 waits on publication and platform admission/access; T03 waits on reuse-surface's maintained/published discovery update. |
| 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. |
The `playwright` namespace is absent. No cluster workload was created. Server
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.
A local build digest is not a published release. Package validation/rendering
[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.
Existing capability `capability.infotech.headless-browser` was still D3/A2/C2/R2