{
  "skill_name": "create-journeys",
  "evals": [
    {
      "id": "uj005",
      "prompt": "In /home/user/Projects/trance-shop-israel, recreate only the venue/promoter application journey from repository evidence. Write one journey artifact to the requested output path. Do not edit repository files or write tests. If evidence is incomplete or contradictory, mark the journey blocked instead of inventing behavior.",
      "expected_output": "One evidence-backed journey using structured H/A/P branches, exact request and response contracts, deterministic setup, fresh-read and forbidden-effect oracles, complete risk mapping, per-claim source:line evidence, and honest readiness state.",
      "assertions": [
        "Uses the real /{locale}/onboarding/apply UI route; never invents apply-venue or apply-promoter pages.",
        "Includes a complete Reachability proof connecting actor state, UI entry, initial data, trigger, request construction, endpoint boundary, domain operation, authoritative writes, response handling, and terminal render.",
        "Every H/A/P branch contains Setup, Action, Request, Response, Visible, Durable, Fresh read, Forbidden, Risks, and Evidence fields.",
        "Maps source:line evidence separately for Setup, Action, Request, Response, Visible, Durable, Fresh read, and Forbidden.",
        "Every Request contains one exact HTTP method and path; every Response contains one exact numeric HTTP status and body/literal contract.",
        "Splits anonymous versus authenticated behavior and does not combine 400/409/429 or 401/403 alternatives in one branch.",
        "Names deterministic fixtures or records missing fixture/fault seams as blockers.",
        "Uses readiness blocked and canonical false if any required evidence or observation seam is unresolved.",
        "Risk coverage contains all canonical risk IDs with exact branch mapping or one-clause N/A reasons.",
        "Every evidence claim uses an existing repository source path with a line number.",
        "Trace ranges cover complete UI, endpoint, and domain/external functions; every decision line maps through Guard coverage.",
        "A different native reviewer writes a hash-matched review sidecar with all checks passed; changed-file and catalog certification validators exit zero."
      ],
      "files": []
    },
    {
      "id": "guest-checkout-order",
      "prompt": "In /home/user/Projects/trance-shop-israel, recreate only the journey where an anonymous guest creates a checkout order and reaches the card-payment form. Use repository evidence, write one journey artifact to the requested output path, do not edit application files, and mark unresolved fixtures or seams as blockers without inventing behavior.",
      "expected_output": "One connected, evidence-backed guest checkout-order journey using the actual guest UI entry, exact inline-item request, endpoint and imported domain-write evidence, boundary-relevant blockers, atomic branches, and honest readiness.",
      "assertions": [
        "Uses CheckoutModal as the guest UI path and does not claim an anonymous guest can load a cart through GET /api/cart on /{locale}/checkout.",
        "Reachability proof connects anonymous state, modal entry, inline items, POST /api/checkout/orders, endpoint guest handling, imported createOrder writes, response handling, and payment-form render.",
        "Guard coverage maps every relevant CheckoutModal validation, endpoint rejection, imported domain error, reservation failure, partial-write seam, and response-loss retry to an atomic branch, sibling journey, or evidence-backed N/A reason.",
        "POST /api/checkout/orders request includes one exact inline items payload plus guest identity fields.",
        "Durable evidence traces into packages/core/src/checkout/create-order.ts instead of stopping at the API wrapper or schema declaration.",
        "Covers or blocks partial-write behavior across orders and order_items because writes are not wrapped in one proven transaction.",
        "Does not use missing /api/checkout/capture as a blocker when terminal outcome is reaching the payment form.",
        "Splits invalid payload, empty cart/items, missing guest details, shipping requirement, missing item, and relevant downstream failures into atomic branches or explicit boundary-relevant blockers.",
        "Maps field-scoped evidence and contains no response-code unions, generic messages, or risk-table contradictions.",
        "Does not manufacture a permission branch by probing order-status or another post-terminal API outside the payment-form journey boundary.",
        "Uses readiness blocked and canonical false when deterministic fixtures or fault seams remain unavailable.",
        "Trace ranges cover complete UI, endpoint, and imported checkout-domain functions; every decision line maps through Guard coverage.",
        "A different native reviewer writes a hash-matched review sidecar with all checks passed; changed-file and catalog certification validators exit zero."
      ],
      "files": []
    },
    {
      "id": "add-track-to-cart",
      "prompt": "In /home/user/Projects/trance-shop-israel, recreate only the authenticated customer journey for adding one track from its detail page to the cart. Use repository evidence, write one journey artifact plus required catalog files, do not edit application code, and record real implementation defects or missing seams without inventing behavior.",
      "expected_output": "One validator-clean, semantically reviewed cart journey that traces the complete TrackCTA handler and cart POST handler, pins exact sequential and concurrent behavior, and distinguishes known client recovery from genuine missing feedback.",
      "assertions": [
        "Trace ranges cover the complete TrackCTA cart handler and POST /api/cart handler, with every if, else, catch, and throw mapped through Guard coverage.",
        "Records that non-2xx responses roll back inCart, 401 opens login, other errors show the exact toast, and rejected fetch rolls back without visible feedback.",
        "Pins existing-track response to default 200 and new-track response to 201.",
        "Pins the catch response literal to Failed to add item to cart.",
        "Does not manufacture a schema-invalid branch from the hard-coded valid UI payload; maps direct-API invalid input outside this UI journey boundary.",
        "Pins anonymous denial to 401 Unauthorized and traces the login-modal event instead of marking it unknown.",
        "Marks concurrency applicable because check-then-insert lacks a user/item uniqueness constraint or lock.",
        "Uses an actor-visible state oracle or records missing accessible state; a CSS class identifier alone is insufficient.",
        "Every branch pins committed, no-write, partial, or uncertain state with field-scoped evidence.",
        "Splits database failure before insert from enrichment failure after insert; separate missing seams or branches cover each phase.",
        "Splits transport rejection before dispatch from response loss after commit; transport failure alone never proves no write.",
        "A different native reviewer writes a hash-matched review sidecar with all checks passed and zero findings.",
        "Failed review triggers repair, failed-report deletion, and fresh review; repairable findings are never reported as certification blockers.",
        "Changed-file and full-catalog validator commands both exit zero; invalid output remains draft and is never reported complete."
      ],
      "files": []
    }
  ]
}