scenario: support-ticket triage ships ready (record-collection)

[ryandmonk]

What

The fourth ready scenario — replay-first, zero per-scenario code: no agent SCENARIOS entry, no capabilities, no authored surface, no web UI changes. A registry record, owner-authored governance, and two live gpt-oss recordings, shipped atomically (contract + fixtures + registry + break condition + spec + docs), so no intermediate governed-intent-without-scenario state ever exists on main.

Contract (owner-authored governance, astryx.dspack.json)

• Intent record-collection — records of the same kind (tickets, orders, members), scanned and acted on; badge guidance lives in the intent description and worked example, deliberately not a rule (the linter renders a should-severity miss as "Required component does not appear" under a passing gate — a contradiction — and Badge's own docs endorse plain text when no action is needed).
• rule.record-collection-requires-table (component-choice, must) — rationale quoted verbatim from the Astryx Table docs via npx astryx component Table --json; explicitly noted as valid while table is the catalog's only collection structure.
• rule.table-carries-data (required-props, scoped to the intent) — a data-driven table must carry columns and data. Born from observed live failures, see below.
• Worked example ex.support-ticket-triage: badge strip above a compact tickets table (the contract's table is data-driven strings, so badges live beside it, never in cells). Appended last; examples[0] (the A3 build sample) untouched.
• shadcn intent parity: deferred to the standing owner-authored contract-extension item. Generation always lints under the astryx catalog (loadContract() is hardcoded), and shadcn already carries table+badge for restyle rendering — verified, nothing blocks.

The generation bug this work surfaced (and its fix)

Across ~20 live runs on two models (gpt-oss:latest, qwen3-coder:30b), the table's nested data rows were never emitted — every surface shipped an empty table shell, and with the data rule active, runs exhausted repairs instead. Root cause upstream: dspack-gen's generation schema marks every prop optional, and grammar-constrained decoders skip optional heavy branches; a repair round cannot fix what the grammar never demands. Proof: calling Ollama directly with data marked required, the same model fills correct rows first try.

Fix: dspack-gen feat/required-props-grammar (targets 0.1.2) — prop descriptors may declare required: true, which reaches the props schema's required and makes props itself required on the node branch. This contract flags table columns+data accordingly.

Draft until dspack-gen 0.1.2 publishes, then the lockfile bumps here. The deployed static site replays recordings and is unaffected; only local Run It Live for this scenario needs ≥0.1.2.

Fixtures (Spark Ollama, ollama:gpt-oss:latest, recorded under the full final contract)

• fixture-010 "the interface argues back": the model obeys the honest break-it prompt (a stacked prose list) with a lone text node → S3 fails on the table rule → the repaired surface ships badges + a filled 3-row table. --require-repair rejected 3 compliant runs before a genuine violation landed — curation, not distortion; all copy is written from the recorded events.
• fixture-011 "clean first pass": the neutral seed prompt, one attempt, straight through the gates to a five-row triage table with a status badge strip.
• A third emitter-refusal fixture was attempted once honestly; the model built a clean table instead of a dropdown, so nothing ships there.

Fail-first evidence

Pre-contract recording failed with intent 'record-collection' is not registered in the contract (known: destructive-action, scheduling, structured-editing). All four support-triage.spec.ts tests failed on the old registry:

3 failed
  support-triage is a ready, selectable scenario on the shelf
  clean replay: a live run straight through the gates to a filled table
  repair replay: prose list caught by the table rule, repaired surface ships
(permalink test, after adding the reload the permalink effect requires:)
1 failed
  permalink: a support-triage deep link resolves

Upstream, three new grammar-alignment assertions fail on dspack-gen 0.1.1.

Gates

• pnpm -r typecheck / pnpm -r test green; contracts build:catalogs + drift-check clean.
• Playwright: 94 passed, 4 skipped (90 existing + 4 new; zero existing-spec edits needed — studio-shell.spec.ts pins onboarding and permalinks.spec.ts pins hotel-reservations, verified).
• Manual: scenario selected in the browser; clean replay renders the five-row table + badge strip on the canvas; repair replay shows attempt 0: S3✗ → repair → attempt 1: ✓.

Merge note: playwright.production.config.ts will conflict trivially with #16 (project split) — resolution is adding support-triage.spec.ts to the studio project's testMatch.

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR adds a new ready “support-ticket triage” scenario that is replay-first and governed via contract updates (new intent + rules), backed by two new live recordings and a new Playwright spec, plus a dependency bump to pick up required-props grammar support.

Changes:

• Add record-collection intent and table-focused governance rules (including required table.columns + table.data) to the Astryx contract.
• Register the new support-triage scenario as ready, add a new Break-it condition, and ship fixtures fixture-010 / fixture-011.
• Add e2e/support-triage.spec.ts and include it in the production smoke suite; bump @aestheticfunction/dspack-gen to 0.1.2.

Reviewed changes

Copilot reviewed 10 out of 11 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
pnpm-lock.yaml	Bumps @aestheticfunction/dspack-gen to 0.1.2 for required-props grammar support.
playwright.production.config.ts	Includes support-triage.spec.ts in the production “studio” project smoke list.
packages/scenarios/src/registry.ts	Promotes support-triage to ready and wires in fixtures 010/011.
packages/scenarios/src/break-conditions.ts	Adds a support-triage governed-repair break condition (records-as-prose).
packages/replay/fixtures/fixture-010.json	Adds the “argues-back” live recording fixture.
packages/replay/fixtures/fixture-011.json	Adds the “clean first pass” live recording fixture.
packages/contracts/astryx.dspack.json	Adds record-collection intent, table rules, and marks table columns/data as required.
e2e/support-triage.spec.ts	New e2e coverage for shelf readiness, clean replay, repair replay, and permalink resolution.
docs/NAV-REFACTOR.md	Updates scenario lists/matrix to include support-triage as ready and documented.
docs/IMPLEMENTATION_LOG.md	Adds an implementation log entry for the scenario + required-props grammar motivation.
docs/AUDIT.md	Updates audit doc to reflect 4 ready / 2 planned scenarios and support-triage shipping.

Files not reviewed (1)

• pnpm-lock.yaml: Generated file

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.