reuse-surface/workplans/REUSE-WP-0024-browser-discovery-and-provider-evidence.md

---
id: REUSE-WP-0024
type: workplan
title: "Resolve browser discovery relevance and publish verified provider consumption"
domain: infotech
repo: reuse-surface
status: finished
owner: codex
origin: cross-repo
origin_ref: REUSE-IN-0001
created: "2026-10-13"
updated: "2026-10-13"
state_hub_workstream_id: "3d62d0af-5deb-55b5-b570-e62f05a43666"
---

# Browser discovery and provider evidence

Reviewed against the current checkout and rapp-playwright's published 0.1.0
contract, immutable release and independent consumer receipts. All prior
workplans are closed. REUSE-IN-0001 and the October 13 provider inbox handoffs
are the remaining actionable work. User authorized review, implementation,
commit and synchronization.

## Publish the verified provider path

```task
id: REUSE-WP-0024-T01
status: done
priority: high
state_hub_task_id: "dd75f033-02f1-521e-b5c3-cddb5dce80df"
```

Update the existing capability, index and generated views with pinned public
client/contract/release/evidence links and executable preflight/trial guidance.
Assess maturity against the standard; distinguish deployable local container
availability from pending managed platform admission and ephemeral endpoints.
Retain the source-adaptation fallback. No second browser capability or consumer
task closure. Verify published sources and the available local fixture path.

## Fix short-intent relevance

```task
id: REUSE-WP-0024-T02
status: done
priority: high
state_hub_task_id: "a689bc2a-a112-59d4-b00c-f6934665dffb"
```

Keep deterministic token matching, but score capability names separately so
long summaries cannot dilute a direct name match. Test browser versus unrelated
headless services, unrelated queries, long descriptions, and maturity ties.
Make reuse advice distinguish lexical relevance from runtime availability.
Verify the same behavior against the hosted snapshot using the local CLI.

## Validate, publish and synchronize

```task
id: REUSE-WP-0024-T03
status: done
priority: medium
state_hub_task_id: "0be283ba-12da-52a1-b1af-0c2d6dcb58f1"
```

Run the appropriate tests and registry/generated-artifact checks. Commit and
push, refresh hosted federation, retain public readback evidence, reconcile
REUSE-IN-0001 and workplan statuses, and log progress to State Hub. Browser
deployment and CONTENT-WP-0000-T04 acceptance remain their owners' work.

## Implementation evidence

See [review and trial receipts](../docs/evidence/2026-10-13-browser-discovery.md).
The published client passed 14 fixture steps and produced four independently
checked screenshots. Availability is now A5 for the published local container;
A6 managed admission remains pending. Name scoring ranks the browser first at
0.6667 instead of returning false-new. Replaced stale live-registry stats
assumptions with a controlled fixture after the full suite exposed them.

Completed publication: implementation commit `50077c9` pushed to `origin/main`;
public capability and index bytes match. Hosted readback at 18:49:02 UTC is fresh
and warning-free, with 66 capabilities and one browser entry. The updated local
CLI against that snapshot returns browser first, 0.6667, `reuse`; no server code
deployment was required. All **212 tests** pass, registry validation and graph
checks pass. REUSE-IN-0001 is closed for the registry-owned concerns. Managed
admission and consumer acceptance remain with their existing owners.