Ty
2d12cbcfbd
The file repeated requirement IDs on nearly every line, carried defensive negations, mixed 'description' with 'long description', and left a cross reference and the payload shape incomplete. - Cite requirement IDs once in the Requirements impact table. - Name the seven leaves as the synced WooCommerce wood-category leaves. - Keep the length ft/in split with the short-description pattern it serves. - Use 'description' only, matching the Woo field. - Complete the cross references with section pointers. - Follow the Woo v3 product shape and add an example submission whose taxonomy values are placeholders, since the synced cache supplies them.
Contract docs
Cross-cutting interface detail shared by capabilities.
Rules (docs/STRUCTURE.md): a contract doc cites requirement IDs from docs/REQUIREMENTS.md; it never defines or restates them.
Contract docs (migrated):
WOO-API.md— external WooCommerce REST API v3 surface (new; the dependency contract)API.md— FastAPI HTTP contract (from tagOPENAPI.md)DATA-MODEL.md— SQLite schema and status machine (from tagDATA-MODEL.md)UX.md— screens, field recovery, outcomes (from tagUX.md)PROMPTS.md— Call 1 / Call 2 prompt text and inputs (from tagPROMPTS.md)CONTENT-WOO.md— listing copy and Woo payload intent (fromdocs/CONTENT-WOO.md)TEST-SPEC.md— test pyramid, vectors, dishonest proxies (from tagTEST-SPEC.md) — pending
Template: docs/_templates/contract.md.