Record completed bootstrap and durable reuse-surface handoff

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a13590-a16f-7f60-be60-fd71627bc99d

docs/demand-and-reuse.md

@@ -61,6 +61,10 @@ is `proposed`/`todo`; bootstrap completion is not implementation completion.
 
 An initial TAMQ update to reuse-surface was queued as
 `m-dccbea4a-ac16-410e-a167-2d2dd8cc27a6`, confirming delivery ownership and planned
-status. The final handoff will carry the registration and workplan references.
+status. TAMQ had no active service/endpoints, so that message remains pending.
+The final handoff was persisted in State Hub as
+`b6a965ed-c02b-49f2-9272-c234e7c8f6a1`, with the registration, published source
+and workplan references; see the [receipt](evidence/2026-10-13-reuse-surface-notification.json).
 Reuse-surface remains the canonical record maintainer; no duplicate registry
-entry is created here.
+entry is created here. Notification persistence does not imply owner
+acknowledgment or a registry edit already performed by that owner.

docs/evidence/2026-10-13-bootstrap.md

@@ -0,0 +1,62 @@
+# Planning and registration evidence — 2026-10-13
+
+## Requested boundary
+
+Reviewed content-explorer demand, recorded the provider intent and sibling-derived
+workplans, registered this repository, and notified reuse-surface. Implementation
+and deployment remain future work. No browser trial was run or represented as run.
+
+## Registration and projection
+
+- Repository: `rapp-playwright`, UUID `23355f26-7ee1-4036-8c63-3ae78e3072bf`.
+- Domain/topic: `infotech/stack`, topic UUID
+  `595afc64-bd28-47bf-aafb-ba230b28371b`.
+- Classification: tooling; secondary domain agents. Validated against the current
+  custodian allowed-values file and read back from State Hub after registration.
+- Forge remote: `forgejo-remote:coulomb/rapp-playwright`.
+- Host observation: `bnt-lap001` → `/home/worsch/rapp-playwright`.
+- Initial published planning revision: `73313606665e9c18b32d3c933b11af5e46ef856d`.
+  `rmgr sync --push` returned `applied`, primary/railiance01, with identical
+  expected and derived commits, four created plans, three resolved dependency
+  edges, no refused records and no unresolved edges. No local-only projection
+  was accepted as a substitute.
+- Independent REST readback matched all four plan IDs, repository bindings and
+  statuses and all 13 task IDs/states against local files. The initial bootstrap
+  was active during this readback; final completion is synchronized separately.
+
+## Checks
+
+- Parsed all frontmatter and fenced task YAML; verified unique IDs and expected
+  repo/domain/topic values. All ten future delivery tasks remain `todo` in three
+  `proposed` plans.
+- Validated classification without errors or warnings, checked local Markdown
+  links including cited sibling evidence, checked template expansion and ran
+  `git diff --check`.
+- A separate `statehub fix-consistency --repo rapp-playwright --json` audit found
+  zero failures and zero automation errors. It regenerated the missing index and
+  refreshed the offline brief. Two standing notices were subsequently read and
+  acknowledged. Its generated-only commit was rejected by the local hook;
+  generated files are included with the substantive bootstrap completion record.
+- No install/build/runtime tests apply to this planning-only checkout.
+
+## Reuse-surface notification
+
+Initial TAMQ message: `m-dccbea4a-ac16-410e-a167-2d2dd8cc27a6`. Inspection showed
+`pending`, no active service or endpoint, and no delivery acknowledgment.
+
+Final State Hub message: `b6a965ed-c02b-49f2-9272-c234e7c8f6a1`, from
+`rapp-playwright` to `reuse-surface`. Its [persisted receipt](2026-10-13-reuse-surface-notification.json)
+contains the provider references, repository UUID, proposed workplan UUIDs,
+published revision and the explicit planned-only availability boundary.
+The message asks reuse-surface to retain the existing capability ID and evidence
+vector, attach the provider plans, and retain ownership of registry relevance
+defects. Delivery to the persistent inbox is verified; owner acknowledgment and
+subsequent registry edits are not claimed.
+
+## Remaining delivery
+
+WP-0002: contract and trial design. WP-0003: service and package implementation.
+WP-0004: managed runtime and independent consumer verification, followed by an
+evidence-backed discovery update. Content-explorer retains acceptance of its own
+screenshot/keyboard task. These are proposed follow-on work, outside the requested
+bootstrap stopping point.

docs/evidence/2026-10-13-reuse-surface-notification.json

@@ -0,0 +1,17 @@
+{
+  "id": "b6a965ed-c02b-49f2-9272-c234e7c8f6a1",
+  "from_agent": "rapp-playwright",
+  "to_agent": "reuse-surface",
+  "subject": "rapp-playwright planning and State Hub bootstrap complete; service remains planned",
+  "body": "Provider planning is established and published at https://forgejo.coulomb.social/coulomb/rapp-playwright (planning source 73313606665e9c18b32d3c933b11af5e46ef856d). INTENT.md defines provider/consumer/platform ownership; docs/demand-and-reuse.md traces REUSE-IN-0001 and CONTENT-WP-0000-T04 and the sibling rapp conventions; SCOPE.md explicitly records planning-only availability.\n\nState Hub repository 23355f26-7ee1-4036-8c63-3ae78e3072bf is registered as tooling, infotech/stack, with Forge remote and bnt-lap001 checkout. Primary railiance01 reconciled the published revision; all 4 workplans and 13 tasks were independently read back. WP-0001 is the bootstrap; proposed WP-0002 (98fb515e-9239-57d5-9ffa-8a5c5a86ed90) defines the agent contract/trial, WP-0003 (8e662d81-cdcb-5d8c-9222-1faaa92fc307) implements the reproducible service/package, and WP-0004 (f9280c40-201e-59b5-a6f0-1aace8e0e2e2) verifies deployment and independent consumer use. See workplans/README.md.\n\nThe intended agent path includes availability/preflight, explicit remote target reachability, version-compatible Playwright/Chromium, desktop and narrow screenshots, keyboard interaction assertions, machine-readable receipts/artifact retrieval, isolation and cleanup. Transport, endpoint and versions remain contract decisions. No browser service, endpoint, client command or launch receipt exists yet. The user requested stopping after this planning/registration handoff; implementation has not begun.\n\nPlease attach these provider intent and workplan references to the existing capability.infotech.headless-browser record and REUSE-IN-0001 while preserving the evidenced D3/A2/C2/R2 source-reuse assessment. Do not create a second capability or upgrade availability from planning evidence. Content-explorer owns its task closure. Registry relevance and false-new behavior remain reuse-surface concerns. Future availability promotion requires WP-0004 runtime and consumer receipts.\n\nAn earlier TAMQ planning message m-dccbea4a-ac16-410e-a167-2d2dd8cc27a6 is still pending because TAMQ has no active service/endpoints; this State Hub message is the durable final handoff. Only bootstrap completion bookkeeping remains in this session.",
+  "thread_id": null,
+  "read_at": null,
+  "archived_at": null,
+  "created_at": "2026-10-13T14:14:41.362488Z",
+  "kind": "message",
+  "expires_at": null,
+  "supersedes_id": null,
+  "reader": null,
+  "delivered_at": null,
+  "acknowledged_at": null
+}