@riddledc/riddle-proof-packs 0.2.2 → 0.3.0

package/packs/neon-step-sequencer/case-study/reusable-lessons.md

@@ -0,0 +1,27 @@
+# Reusable Lessons
+
+## Atomic proof first
+
+Start with the smallest claim that can produce useful evidence. For Neon, that is not "the mix sounds good"; it is route, contract, source readiness, render metrics, no silence, and no clipping.
+
+## Failure is product input
+
+A failing run should become a clearer classification, not a vague "Riddle caught a bug" headline. Use `product_regression`, `proof_insufficient`, `profile_calibration`, `app_contract_gap`, `runtime_environment_blocked`, and `needs_human_review`.
+
+## App contracts beat scraping
+
+Complex audio state is easier to prove when the app exposes a small redacted proof contract. Scraping visible controls is still useful, but rendered metric agreement needs intentional app state.
+
+## Keep metrics compact
+
+Large metrics belong in artifacts. The summary should answer:
+
+- did the render complete?
+- did the mix clip?
+- was it silent?
+- did the intended metric move?
+- what should a human review next?
+
+## Core changes are last
+
+Most ratchet steps should change profile JSON, pack docs, app proof contracts, or app fixtures. Riddle Proof core changes are justified only when the missing primitive applies beyond Neon.

package/packs/neon-step-sequencer/examples/README.md

@@ -0,0 +1,20 @@
+# Neon Step Sequencer example runs
+
+These examples are local Playwright runner outputs captured against LilArcade Neon Step Sequencer on May 24, 2026. They are included to show how this pack records atomic proof claims with explicit evidence-role patterns.
+
+The raw `profile-result.json` files are real runner outputs. They intentionally keep enough evidence to audit the verdict, but the summaries are the preferred place to start.
+
+## Runs
+
+| Run | Evidence-role pattern | Status | Claim |
+| --- | --- | --- | --- |
+| `run-001-fast-mix-health` | `current_target` | passed | The current Neon target exposes a proof contract, source receipts, and a bounded offline mix-health render. |
+| `run-002-mix-change` | `interaction_snapshots` | passed | A bass-level edit changes rendered bass and mix metrics without clipping. |
+| `run-003-full-matrix` | `current_target` | passed | The mix-health proof holds across desktop, phone, iPad Mini, and iPad viewports. |
+
+## What these examples do not prove
+
+- They do not prove subjective mix taste.
+- They do not prove every song, section, or mix preset.
+- They do not prove production CDN asset availability; these were local dev-server runs.
+- They do not prove a reference/candidate release delta. The mix-change run uses pre-action/post-action snapshots inside one proof run, not a separate baseline deployment.