# Bazaar input-schema recovery

## Result

| Metric | Before | After |
|---|---:|---:|
| `blocked-input-schema-unresolved` routes | 25 | 0 |
| Bazaar metadata candidates | 52 | 77 |

The 24 recovered V2 POST schemas are frozen in
`baseline/schemas/v2/x402-action-input-schema-evidence.json`. Each entry
records the exact canonical V2 route-handler path and its SHA-256 from pinned
V2 commit `a80144d1acbbbbf24b9eca7cd91e61daad0c0ad6`. The builder only accepts
the handler's declared `outputSchema.input.bodySchema`; it does not infer
fields from names, descriptions, or neighboring routes.

The recovered V2 routes are:

```text
accept-bid                       approve-work
attest-belief                    cancel-task
challenge-bond-metrics           create-accountability-bond
create-partnership-bond          create-task
deactivate-agent                 dispute-task
grant-consent                    register-for-partnership
report-mission-violation         report-surveillance-violation
request-bond-distribution        request-validation
revoke-consent                   stake-as-validator
submit-accountability-metrics    submit-feedback
submit-partnership-metrics       submit-validation
submit-work                      unvouch
```

The V3 `POST /api/v3/x402/actions/create-partnership-bond` schema is sourced
from `pr7/sdk/v3/types.ts` (`V3BondTerms`) and
`pr7/sdk/v3/bonds.ts` (`BondsModuleV3.createPartnership`). Its generated
schema carries both paths and SHA-256 values. It is intentionally a V3 terms
plus mutual-signatures contract, not the historical V2 partnership-bond body.

Generated examples are deterministic placeholders only: no private key,
mnemonic, seed, secret, or funded user address is emitted. The static Bazaar
validator checks each generated example against its declared schema, including
the V3 schema's patterns, numeric bounds, `not`, and `anyOf` constraints.

## Remaining evidence gate

There are **no remaining source/input-schema blockers**. The owner-provided
live-readiness gate remains fail-closed for all 77 emitted candidates:

1. read-only x402 validation for each resource;
2. a genuine settled payment bound to each resource; and
3. a non-rejected Bazaar extension response.

No live validation, settlement, deployment, or indexing claim is made by this
recovery.
