coulomb/reuse-surface
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Record the content-explorer request for a runnable headless-browser answer.
Some checks failed
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details
ci / validate-registry (push) Has been cancelled
Details

Browse source 
CONTENT-WP-0000-T04 needed a browser on the workstation. The published capability is a discovery card at availability A2, and plan-check still returns new for "headless browser". REUSE-IN-0001 asks the query to name a verified trial or to report that availability gap.

Assistant: grok
Assistant-Session: 01a1346c-fdff-7741-b1af-b7283661554b
This commit is contained in:
tegwick 2026-10-13 14:14:53 +02:00
parent 80e04c02fe
commit ada122edbe
1 changed files with 66 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

66
intakes/REUSE-IN-0001-headless-browser-runnable-answer.md Normal file
View file

@ -0,0 +1,66 @@
# REUSE-IN-0001 — Answer a headless-browser request with a runnable trial
```yaml
id: REUSE-IN-0001
kind: intake
title: "Answer a headless-browser request with a runnable trial, or say the gap is availability"
status: open
lane: green
flavor: implementation
origin: cross-repo
origin_ref: CONTENT-WP-0000-T04
priority: medium
owner: reuse-surface
repo: reuse-surface
requested_by: content-explorer
created: "2026-10-13"
updated: "2026-10-13"
description: >
content-explorer asked the hosted reuse-surface index for a headless browser
while CONTENT-WP-0000-T04 was open. That task needs responsive screenshots
and a keyboard walkthrough. On 2026-10-12 the workstation had no Chrome,
Chromium, Firefox, or Playwright launcher.
GET https://reuse.coulomb.social/v1/federated (composed_at
2026-10-13T11:56:56Z, stale false) returns
capability.infotech.headless-browser at D3 / A2 / C2 / R2. The card
recommends adapting Playwright plus Chromium from whynot-design,
coulomb-social, core-hub, and frontend-patterns. The entry states that it
does not deliver a shared wrapper or a hosted browser. A keyword filter for
"headless" also returns four unrelated engines (kontextual-engine,
user-engine, email-connect, evidence-source). Hosted plan-check for the
intent "headless browser" includes the entry and still returns verdict
new. The publication note on ADHOC-2026-10-13-T02 already records that
scoring limitation.
What the consumer needed from the service:
1. A response that answers whether a browser can be launched on this
workstation now.
2. When it can, one verified command path in the query response itself:
install the matching Playwright Chromium, open one page, save a screenshot,
and record a short keyboard interaction. Learning that next step should
not require opening a sibling checkout and copying another repo's fixtures.
3. When it cannot, the same response should say the record is
discovery-only, availability is A2, nothing is installed for the caller,
and nothing is hosted. The verdict should be an availability gap on
capability.infotech.headless-browser, so the worker extends that entry
instead of starting a second browser stack.
4. The phrase "headless browser" should rank apart from unrelated headless
services.
A hosted browser farm, credential handling, and permission to automate
arbitrary external sites are outside this request. The current entry is
right to keep those excluded. The useful increment is a
workstation-verified trial helper with a pinned Playwright and Chromium
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.
```