TAS-182: Article demo and benchmark equivalence gate

[AtlantisPleb]

Summary

• combine Hungarian and Sudoku closure into one gate

Roadmap Position

• Phase: Phase 6. Close demos and benchmark claims
• Sequence: article-gap closure after TAS-156A
• Owned-route boundary: any canonical article route referenced here means the psionic-transformer-based route established by TAS-156A / TAS-160, not a reintroduced mixed implementation spread across model or runtime crates.
• Claim posture: necessary for article-equivalent closure, but not sufficient by itself to widen public capability claims

Description

• publish one checker that turns green only when:
  • Hungarian demo parity is green
  • Arto parity is green
  • benchmark-wide Sudoku parity is green

Why This Matters

• the final article audit needs one unified demo/benchmark surface

Primary Surfaces

• psionic-transformer (canonical owned article-route base for this issue)
• psionic-eval
• psionic-provider

Validation

• checker tests
• negative tests on any missing demo or benchmark row

Claim Discipline

• Keep machine-legible boundaries explicit; partial progress must not be presented as full article equivalence.
• Preserve typed refusal, fallback, blocked, and suppressed posture where closure is still incomplete.
• Keep public language bounded to the declared article envelope rather than implying generic arbitrary-program closure from a partial green result.

Done When

• one article demo/benchmark gate exists and is green

[AtlantisPleb]

Implemented in 868b0f9.

Summary:

• added the unified TAS-182 article demo-and-benchmark gate in psionic-eval, binding TAS-180 Hungarian parity and TAS-181 hard-Sudoku closure into one machine-readable report that stays green only when the Hungarian demo row, named Arto row, and declared benchmark-suite row are green together
• added the matching operator summary in psionic-research and provider receipt projection in psionic-provider
• advanced the blocker/acceptance frontier by closing BEQ-005, marking TAS-182 green, and shifting the next blocking tranche to TAS-183
• updated the article transformer boundary doc, TAS sync doc, dedicated TAS-182 audit note, checker script, and regenerated the dependent report/summary fixtures tied to the new frontier

Validation:

• cargo test -p psionic-eval article_demo_benchmark_equivalence_gate -- --nocapture
• cargo test -p psionic-research article_demo_benchmark_equivalence_gate -- --nocapture
• cargo test -p psionic-provider article_demo_benchmark_equivalence_gate -- --nocapture
• cargo test -p psionic-eval article_equivalence_acceptance_gate -- --nocapture
• cargo test -p psionic-eval article_equivalence_blocker_matrix -- --nocapture
• cargo test -p psionic-eval article_fast_route_architecture_selection -- --nocapture
• cargo test -p psionic-eval article_frontend_compiler_envelope -- --nocapture
• cargo test -p psionic-eval article_frontend_corpus_compile_matrix -- --nocapture
• cargo test -p psionic-eval article_demo_frontend_parity -- --nocapture
• cargo test -p psionic-eval article_hungarian_demo_parity -- --nocapture
• cargo test -p psionic-eval article_hard_sudoku_benchmark_closure -- --nocapture
• cargo test -p psionic-eval article_interpreter_breadth_envelope -- --nocapture
• cargo test -p psionic-eval article_interpreter_breadth_suite_gate -- --nocapture
• cargo test -p psionic-research article_hungarian_demo_parity -- --nocapture
• cargo test -p psionic-research article_hard_sudoku_benchmark_closure -- --nocapture
• cargo test -p psionic-research article_interpreter_breadth_suite_gate -- --nocapture
• bash scripts/check-tassadar-article-demo-benchmark-equivalence-gate.sh