The claims name the workloads covered by RELREG-WP-0004. Each pin is a digest the live object already shows. Assistant: grok Assistant-Session: 01a16880-25e0-7031-b553-a1e0321ff397 |
||
|---|---|---|
| client | ||
| declarations | ||
| docs | ||
| examples | ||
| fixtures | ||
| history | ||
| manifests | ||
| registry | ||
| releases | ||
| src | ||
| tests | ||
| tools | ||
| workplans | ||
| .custodian-brief.md | ||
| .dockerignore | ||
| .gitignore | ||
| .repo-classification.yaml | ||
| AGENTS.md | ||
| Dockerfile | ||
| INTENT.md | ||
| Makefile | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| SCOPE.md | ||
| WORK-RECORDS.md | ||
rapp-playwright
A bounded Playwright/Chromium job service for responsive screenshots and keyboard journeys, with a standalone Python client and a private Railiance workload package.
Published and running as a Railiance pilot. Self-service consumer access remains pending. The independent agent trial and pinned OnCo home-page pilot passed. The service uses Playwright 1.64.0 and Chromium 156.0.8078.4; consumers need Python 3.10+ and no browser installation.
For an available provider endpoint:
python3 client/rapp_playwright.py preflight
python3 client/rapp_playwright.py trial --out .local/trial-01
The default endpoint is a loopback tunnel at http://127.0.0.1:18081.
Access and contract explain tunnel setup, target
reachability, receipts, failures and limits. This address alone is not evidence
that a managed deployment exists. See current scope.
For a reproducible local provider (Docker and npm required):
make install test test-integration build
docker run --rm --name rapp-playwright-local --read-only \
--tmpfs /tmp:rw,size=512m --shm-size=256m --memory=1g --cpus=1 \
--cap-drop ALL --security-opt no-new-privileges \
--mount type=volume,src=rapp-playwright-local-data,dst=/data \
-p 127.0.0.1:18081:8080 -e HOST=0.0.0.0 \
-e EXECUTION_LOCATION=workstation-container \
forgejo.coulomb.social/coulomb/rapp-playwright:0.1.0
The local Docker listener is published only on host loopback; the managed pod listens on pod loopback. The fixture works without external target grants. Use an immutable published digest for managed installation.
- Intent and ownership
- Build, deployment and recovery
- Independent consumer evidence
- Content-explorer pilot
- Workplan status
Registered in State Hub under infotech / stack. railiance-platform owns the
platform lifecycle; this repo owns service implementation. Discovery stays with
reuse-surface's existing capability.infotech.headless-browser record.
Release 0.1.0 pins the tested and published image. Publication evidence includes registry manifest verification and a successful pull on railiance01.