From ada122edbeced3f1615e06b23b79d891a875f249 Mon Sep 17 00:00:00 2001 From: tegwick Date: Tue, 13 Oct 2026 14:14:53 +0200 Subject: [PATCH] Record the content-explorer request for a runnable headless-browser answer. 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 --- ...N-0001-headless-browser-runnable-answer.md | 66 +++++++++++++++++++ 1 file changed, 66 insertions(+) create mode 100644 intakes/REUSE-IN-0001-headless-browser-runnable-answer.md diff --git a/intakes/REUSE-IN-0001-headless-browser-runnable-answer.md b/intakes/REUSE-IN-0001-headless-browser-runnable-answer.md new file mode 100644 index 0000000..2a50017 --- /dev/null +++ b/intakes/REUSE-IN-0001-headless-browser-runnable-answer.md @@ -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. +```