reuse-surface/intakes/REUSE-IN-0001-headless-browser-runnable-answer.md

REUSE-IN-0001 — Answer a headless-browser request with a runnable trial

id: REUSE-IN-0001
kind: intake
title: "Answer a headless-browser request with a runnable trial, or say the gap is availability"
status: closed
outcome: promoted
promoted_to: REUSE-WP-0024
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.


  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"

Registry resolution — 2026-10-13

Implemented under REUSE-WP-0024 and published in commit 50077c9. The original description above is retained as the intake history.

• The same browser capability now includes a pinned, downloadable standalone client, exact preflight/trial commands in the query summary, immutable local container setup and conditional managed instructions. No sibling checkout or consumer browser installation is needed for the provider path.
• A fresh local client-only trial passed all 14 fixture steps; four downloaded PNGs passed independent hash/dimension checks at desktop and narrow sizes. Availability is A5 for the published container, with A2 source reuse retained. The endpoint is ephemeral and managed Railiance admission remains pending.
• Short-name scoring fixes relevance and false-new behavior. Plan-check using the published hosted snapshot ranks the browser first at 0.6667, verdict reuse. Relevance is explicitly separate from runtime readiness; an unavailable provider is an availability gap on this entry.
• Hosted federation readback at 18:49:02 UTC is fresh, warning-free, and includes one browser capability among 66 entries. Public capability/index bytes match the published commit.

Review, trial and publication evidence. This closes the registry-owned intake, not CONTENT-WP-0000-T04, platform admission or consumer application acceptance.