Remove made-up sample files from frontend/public/samples

.github/workflows/qa-pipeline.yml

@@ -43,9 +43,6 @@ jobs:
       # checks use only Node built-ins; keep the existing job/check name for
       # consumers without repeating the dependency install and unit suite.
 
-      - name: FSMA 204 compliance checks
-        run: node qa/fsma-lite-check.js
-
       - name: FSMA 204 CTE count copy check (7, never 6)
         run: node qa/fsma-cte-count-check.js
 
@@ -70,15 +67,9 @@ jobs:
         with:
           node-version-file: .nvmrc
 
-      - name: Full ingestion-to-export flow
-        run: node qa/full-flow.js
-
       - name: Bad data rejection
         run: node qa/bad-data.js
 
-      - name: Export artifact validation
-        run: node qa/export-validate.js
-
   # ── Stage 3: AI Analysis ───────────────────────────────
   # Advisory-only: copy, pricing, and credibility warnings for human
   # follow-up. Its result is intentionally NOT in decision.needs, so a

.gitignore

@@ -85,12 +85,11 @@ secrets.json
 
 # Artifacts that should never be tracked
 *.zip
-# ...except the public proof/sample bundles the frontend serves. These are
+# ...except the public proof bundles the frontend serves. These are
 # intentionally tracked fixtures (the audit-bundle pair backs the public
 # /api/v1/proof/verify demo, including the deliberately tampered one), and
 # the bare *.zip rule above was silently covering them (#2873).
 !frontend/public/proof/*.zip
-!frontend/public/samples/*.zip
 login_resp.json
 frontend/build_log.txt
 frontend/build_output.txt

docs/PRODUCT_DESCRIPTION.md

@@ -14,7 +14,7 @@ Accepted events are stored with tenant boundaries in PostgreSQL. The platform ev
 
 Optional Jev assistance suggests mappings for unfamiliar CSV columns and a file's CTE when none is declared. Upload screens expose suggestions for operator review. Automatic application defaults off, requests use headers without row samples by default, and model suggestions do not replace deterministic validation. Preview and evaluation tools let operators inspect suggestions before enabling automatic application.
 
-Public synthetic artifacts, a browser verifier, a downloadable Python bundle verifier, and a reproducible recall drill let reviewers inspect the evidence format. Successful hash or Merkle verification establishes artifact integrity; it does not establish source-data accuracy or regulatory approval.
+A browser verifier, a downloadable Python bundle verifier, and a reproducible recall drill let reviewers inspect the evidence format. Successful hash or Merkle verification establishes artifact integrity; it does not establish source-data accuracy or regulatory approval.
 
 ## Capability and availability matrix