Implement bounded browser service, consumer evidence and managed package

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a13590-a16f-7f60-be60-fd71627bc99d
This commit is contained in:
tegwick 2026-10-13 19:23:29 +02:00
parent 386b0c0f04
commit ccf46d8c59
81 changed files with 3455 additions and 73 deletions

View file

@ -68,9 +68,8 @@ credentials and browser storage state must not enter ordinary result logs.
## Initial scope and later decisions
Start with Chromium, one consumer-independent trial, and the content-explorer
pilot. Native Playwright compatibility is the starting point. The contract
workplan will decide whether remote sessions, submitted jobs, or a combination
best satisfies agent use and artifact retrieval. Transport, endpoint, deployment
pilot. Native Playwright compatibility is the starting point. The consumption contract decides whether remote sessions, submitted jobs, or a
combination best satisfies agent use and artifact retrieval. Transport, endpoint, deployment
binding, package versions, and access mechanism are not selected by this intent.
Multi-browser coverage, a general browser farm, unrestricted script execution,
@ -87,8 +86,9 @@ Isolation, timeouts and cleanup must have executed negative-case evidence.
Planning, registration, image publication and a successful health check alone do
not prove this outcome. Availability advances only with runtime and consumer
receipts. Until then the service is **planned**, with no verified endpoint;
reuse-surface's existing source-reuse evidence remains unchanged.
receipts. Claims must distinguish a verified local runtime from an admitted managed
endpoint; neither image publication nor local proof establishes Railiance
availability.
See [SCOPE.md](SCOPE.md) for current facts and [workplans](workplans/README.md)
for the staged implementation and verification gates.