`FINDINGS.md`

20 lines
# TK-10663 — DW agentic-commerce surface health (read-only, $0)

**Verdict: HEALTHY (all-clear) + one high-value follow-up that needs a hosted UCP agent profile.**

## Verified (all read-only)
1. **The AI-shopper surface is LIVE + correctly configured.**
   - `/agents.md` → 200 (4,473 B, instructs agents to use the Shop skill + UCP/MCP).
   - `/.well-known/ucp` → 200, valid JSON merchant profile: UCP version 2026-04-08 (+2026-01-23), service `dev.ucp.shopping` over MCP, capabilities checkout+fulfillment.
   - `/api/ucp/mcp` → **POST `tools/list` = 200**, valid JSON-RPC, full 12-tool UCP shopping set (search_catalog, lookup_catalog, get_product, get/create/update/complete/cancel_checkout, get/create/update/cancel_cart, get_order).
2. **No broken-endpoint defect.** The `/api/ucp/mcp` "404 on GET" was a FALSE alarm — it's POST-only; a proper POST returns 200 (VERIFY-BEFORE-ACTING avoided a phantom finding).
3. **Both documented endpoints resolve identically.** agents.md points agents at `www.designerwallcoverings.com/api/ucp/mcp`; the UCP profile declares `designer-laboratory-sandbox.myshopify.com/api/ucp/mcp`. Both return the identical 47,909-byte tools/list — no domain-mismatch breakage.
4. **The agent-identity gate WORKS (healthy).** `search_catalog` requires `meta.ucp-agent.profile` (a fetchable, spec-compliant UCP agent profile with valid cache-control). It correctly rejected a malformed/non-agent profile (`profile_malformed: Invalid cache control`) — i.e. it does NOT serve the catalog to arbitrary unauthenticated callers.

## High-value FOLLOW-UP (could not complete read-only)
- **Does the TK-10661 `$4.25` JSON-LD leak also surface in the AGENT-facing catalog?** If the theme's `variants[0]`=Sample logic feeds the UCP `search_catalog`/`get_product` price, AI shoppers would also see DW premium products at $4.25 — a THIRD leak channel (organic JSON-LD ✓ TK-10661, GMC feed = gmc-agent TK-10635, agentic = here). Reaching this requires hosting a spec-compliant, publicly-fetchable UCP agent profile (with correct cache-control) to pass the identity gate — real infra, beyond a read-only probe. **Recommend as a scoped follow-up**, ideally folded into the TK-10661 variant-reorder verification (after Sample→last, confirm the agent catalog shows real prices too).

## Honesty / limits
- Only read tools were exercised; NO cart/checkout tool was called (those are transactional writes — out of bounds for a read-only audit and gated by design/human-approval).
- The agent-catalog price question is unresolved (identity gate), not negative — flagged as follow-up, not asserted either way.