Record forthcoming rapp-playwright service and clarify delivery ownership
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
ci / validate-registry (push) Failing after 1m58s

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a13502-3de4-7af3-a6ae-3ef26de4adec
This commit is contained in:
tegwick 2026-10-13 16:02:38 +02:00
parent 82a34da494
commit 9042dec5ed
7 changed files with 72 additions and 7 deletions

View file

@ -39,9 +39,10 @@ Generated by `reuse-surface catalog`. Do not edit manually.
- **Vector:** D3 / A2 / C2 / R2
- **Owner:** reuse-surface
- **Path:** `registry/capabilities/capability.infotech.headless-browser.md`
- **Summary:** Headless browser automation with Playwright and Chromium for UI testing, screenshots and page extraction; recommended default based on existing whynot-design, coulomb-social, core-hub and frontend-patterns implementations.
- **Summary:** Headless browser automation with Playwright and Chromium for UI testing, screenshots and page extraction; recommended default based on existing whynot-design, coulomb-social, core-hub and frontend-patterns implementations. A rapp-playwright-provided service will be available shortly (announced 2026-10-13; planned, not yet verified available).
**Known limitations:**
- This is a dated source inspection; run the target-repo trial before claiming adoption success.
- Firefox is evidenced in frontend-patterns; WebKit is supported upstream but unverified in this inspection.
- Selenium is an optional testdrive-jsui dependency, not verified execution; Puppeteer has no verified example here.
- The forthcoming rapp-playwright service has no verified endpoint or launch receipt in this record yet.

View file

@ -33,7 +33,7 @@
<article class="card">
<h3>Headless Browser Automation</h3>
<p class="meta"><code>capability.infotech.headless-browser</code> · D3 / A2 / C2 / R2</p>
<p>Headless browser automation with Playwright and Chromium for UI testing, screenshots and page extraction; recommended default based on existing whynot-design, coulomb-social, core-hub and frontend-patterns implementations.</p>
<p>Headless browser automation with Playwright and Chromium for UI testing, screenshots and page extraction; recommended default based on existing whynot-design, coulomb-social, core-hub and frontend-patterns implementations. A rapp-playwright-provided service will be available shortly (announced 2026-10-13; planned, not yet verified available).</p>
<p class="path">registry/capabilities/capability.infotech.headless-browser.md</p>
</article></section>
</body>

View file

@ -5,7 +5,7 @@
{
"id": "capability.infotech.headless-browser",
"name": "Headless Browser Automation",
"summary": "Headless browser automation with Playwright and Chromium for UI testing, screenshots and page extraction; recommended default based on existing whynot-design, coulomb-social, core-hub and frontend-patterns implementations.",
"summary": "Headless browser automation with Playwright and Chromium for UI testing, screenshots and page extraction; recommended default based on existing whynot-design, coulomb-social, core-hub and frontend-patterns implementations. A rapp-playwright-provided service will be available shortly (announced 2026-10-13; planned, not yet verified available).",
"vector": "D3 / A2 / C2 / R2",
"domain": "infotech",
"status": "reviewed",

View file

@ -63,5 +63,21 @@ description: >
version, plus a query result that names that helper or names the
availability gap. This intake does not ask reuse-surface to mark
CONTENT-WP-0000-T04 done or to import OnCo.
Owner response, 2026-10-13, following founder direction: browser service
implementation, operation and consumer workstation setup are not reuse-surface
responsibilities. A rapp-playwright-provided service will be available shortly.
Record this as announced/planned, not verified availability; no endpoint,
consumption contract or launch receipt has been verified here. Existing A2
source reuse remains available and the current maturity vector is unchanged.
reuse-surface retains responsibility for discovery, accurate availability
guidance, consumption references and the reported false-new/relevance defects.
This intake remains open for those registry concerns; its browser-delivery
request belongs to rapp-playwright. A2 means source/library reuse, not
discovery-only or already installed for a caller. CONTENT-WP-0000-T04 remains
the consumer's task and is not completed by this announcement.
state_hub_intake_id: "01a13530-89a8-77b0-bb95-ef16d74bb29b"
```

View file

@ -5,6 +5,8 @@ summary: >-
Headless browser automation with Playwright and Chromium for UI testing,
screenshots and page extraction; recommended default based on existing
whynot-design, coulomb-social, core-hub and frontend-patterns implementations.
A rapp-playwright-provided service will be available shortly (announced
2026-10-13; planned, not yet verified available).
owner: reuse-surface
status: reviewed
domain: infotech
@ -24,6 +26,8 @@ maturity:
rationale: >
Existing JavaScript and Python source examples can be adapted in a consumer
repo. This entry does not deliver a shared wrapper or hosted browser service.
The founder announced a forthcoming rapp-playwright service on 2026-10-13;
that planned delivery does not change the evidenced current A2 level.
external_evidence:
completeness:
level: C2
@ -36,7 +40,8 @@ external_evidence:
- No shared package, standard configuration or consumer-independent trial receipt.
out_of_scope_expectations:
- Exhaustive estate dependency inventory or comparative browser benchmark.
- Managed browser service or mandatory estate-wide technology policy.
- Browser service implementation or operation by reuse-surface.
- Mandatory estate-wide technology policy.
reliability:
level: R2
confidence: medium
@ -57,7 +62,8 @@ discovery:
- JavaScript UI tests, screenshots and page extraction examples.
- Python visual-check example and Firefox experiment evidence.
excludes:
- Browser hosting, credential provisioning and permission to automate external targets.
- Browser hosting or workstation provisioning by reuse-surface.
- Credential provisioning and permission to automate external targets.
- Claims that a dependency declaration or a workplan proves executed browser usage.
assumptions:
- The consumer chooses a version compatible with its runtime and installs matching browsers.
@ -73,6 +79,11 @@ availability:
- ../coulomb-social/scripts/test-usecase-browser.mjs
- ../core-hub/scripts/check_console_visual.py
- ../frontend-patterns/research/experiments/navigation-history/experiment.mjs
target_artifacts:
- >-
Planned rapp-playwright-provided service, announced by the founder on
2026-10-13 as available shortly; endpoint, consumption contract and readiness
evidence have not yet been verified by reuse-surface.
consumption_modes: [informational, source adaptation, JavaScript library, Python library]
relations:
depends_on: []
@ -84,17 +95,28 @@ evidence:
- ../frontend-patterns/research/experiments/navigation-history/README.md
- ../test-driver/SCOPE.md
- ../testdrive-jsui/pyproject.toml
- ../rapp-playwright/README.md
- intakes/REUSE-IN-0001-headless-browser-runnable-answer.md
tests:
- ../whynot-design/tests/visual/ui-kit.spec.mjs
- ../coulomb-social/scripts/test-usecase-browser.mjs
- ../core-hub/scripts/check_console_visual.py
- ../frontend-patterns/research/experiments/navigation-history/result.json
consumer_feedback: []
consumer_feedback:
- >-
2026-10-13 content-explorer, REUSE-IN-0001: published source examples did not
provide a verified runnable path for screenshots and keyboard interaction.
The false-new plan-check verdict is a registry discovery issue, not evidence
that a new browser stack is needed. Browser delivery belongs to the provider.
consumer_guidance:
recommended_for:
- Use Playwright with headless Chromium for a new repo's general UI automation trial.
- Reuse whynot-design for JavaScript visual tests and core-hub for Python visual checks.
- Reuse coulomb-social for JavaScript browser scripts and frontend-patterns for multi-engine experiments.
- >-
For service consumption, rapp-playwright is the announced provider and its
service will be available shortly. Use its published contract and readiness
evidence when delivered; current availability remains source reuse only.
not_recommended_for:
- Treating this recommendation as an approved mandatory estate standard.
- Selecting test-driver as an implemented JavaScript-capable browser engine.
@ -103,6 +125,7 @@ consumer_guidance:
- This is a dated source inspection; run the target-repo trial before claiming adoption success.
- Firefox is evidenced in frontend-patterns; WebKit is supported upstream but unverified in this inspection.
- Selenium is an optional testdrive-jsui dependency, not verified execution; Puppeteer has no verified example here.
- The forthcoming rapp-playwright service has no verified endpoint or launch receipt in this record yet.
promotion_history: []
---
@ -122,6 +145,27 @@ mandatory estate standard or a benchmark verdict against Selenium/Puppeteer.
reuse-surface maintains this discovery record; the example repos maintain their
implementations and the upstream Playwright project maintains the library.
## Service provider and delivery status
**A `rapp-playwright`-provided service will be available shortly**, as announced by
the founder on 2026-10-13. Its [repository description](../../../rapp-playwright/README.md)
identifies a Railiance wrapper for a Playwright and headless Chromium environment
supporting use-case testing. Service availability is **planned**, not verified:
this record has no confirmed endpoint, consumption contract or launch receipt yet.
The current **D3 / A2 / C2 / R2** vector continues to describe evidenced source reuse.
`rapp-playwright` owns the forthcoming browser service. `reuse-surface` owns
discovery, consumption guidance, maturity assessment and evidence references; it
does not implement or operate the browser service or install browsers on behalf
of consumers. Its `owner` field here denotes the maintainer of this registry record.
The [content-explorer feedback](../../intakes/REUSE-IN-0001-headless-browser-runnable-answer.md)
is retained as consumer evidence. Browser delivery is assigned to the provider;
the reported relevance, false-`new` verdict and availability-clarity issues remain
reuse-surface concerns. A2 means source/library reuse, not proof of a locally
installed browser. The service announcement does not complete the consumer's
screenshot and keyboard-walkthrough task.
## Existing implementations
Paths in frontmatter are relative to the reuse-surface repository root. The links

View file

@ -9,6 +9,8 @@ capabilities:
Headless browser automation with Playwright and Chromium for UI testing,
screenshots and page extraction; recommended default based on existing
whynot-design, coulomb-social, core-hub and frontend-patterns implementations.
A rapp-playwright-provided service will be available shortly (announced
2026-10-13; planned, not yet verified available).
vector: D3 / A2 / C2 / R2
domain: infotech
status: reviewed

View file

@ -945,7 +945,9 @@ capabilities:
name: Headless Browser Automation
summary: Headless browser automation with Playwright and Chromium for UI testing,
screenshots and page extraction; recommended default based on existing whynot-design,
coulomb-social, core-hub and frontend-patterns implementations.
coulomb-social, core-hub and frontend-patterns implementations. A rapp-playwright-provided
service will be available shortly (announced 2026-10-13; planned, not yet verified
available).
vector: D3 / A2 / C2 / R2
domain: infotech
status: reviewed