Record onboarding harness + Stage 1 result; scope Stage 2

Current state: the onboarding doc-harness and its Stage 1 completed-clean
result. ROADMAP: spell out Stage 2 (regtest buyer-pays) under the
agent-payment-connect item. Drop the resolved GET /v1/admin/products 405
debt item.
This commit is contained in:
Keysat
2026-06-16 22:48:17 -05:00
parent 1788c9b082
commit 0813e90510
2 changed files with 28 additions and 2 deletions
+16
View File
@@ -121,6 +121,22 @@ Operator-specific memories at `~/.claude/projects/-Users-macpro-Projects-keysat/
independently confirmed**; verify the StartOS UI shows `0.2.0:57`). `publish.sh` now runs
`make install` as step 5, so future ships auto-deploy (best-effort, non-fatal).
- **Onboarding doc-harness — Stage 1 (Path 1, no payments): `completed-clean` this session.**
New disposable harness at `licensing-service-startos/onboarding-harness/` boots a fresh
fixture, mints a `merchant-onboard` key, serves `keysat-docs/` as the corpus, scaffolds a
pristine Next.js/TS proof-of-work (`sandbox-template/`), then runs the global
`onboarding-tester` agent **docs-only**. Loop converged 5→1→0 stumbles over 3 runs; the
publishable walkthrough is harvested into `keysat-docs/agent.html` (#worked-example). Doc
fixes shipped: `integrate.html` (real v0.3 SDK shape — `verify()` throws + returns
`VerifyOk{payload,…}`, no `valid` bool, `LicensingError`/`.code`), `agent.html`
(merchant-onboard role row, product/policy-create workflows, `buyer_note``note`, license
`/search` endpoint, worked example), `wire-format.html` (issuer-pubkey response shape). Also
`openapi.rs` (licenses `product_id` filter, removed phantom `GET /v1/admin/products`, added
`/v1/admin/licenses/search`, price-field notes) — **served-spec fixes; fixture was rebuilt to
test, but these reach the live spec only on the next daemon release.** keysat-docs static
fixes deploy independently. Full record: `onboarding-harness/STAGE1-RESULT.md`. **Stage 2
(Path 2, regtest buyer-pays) is gated on agent-payment-connect slices 35 below.**
- **In progress — agent-payment-connect (phase 2)**. Approved spec:
`plans/agent-payment-connect-scope.md`. Lets a scoped key connect a BTCPay provider, but
ONLY on a sandbox daemon and ONLY for a non-mainnet network — never folded into a role