Files
magicka-vm/.github/workflows/merge-gates.yml
T
linus-dandClaude Opus 4.8 bea076df43 Finding 4: full-trace evidence — reconstructed and re-derived, not summarized
Removes the deferral. Each sampled execution's FULL trace (every graph edge,
count, weight) and delta are persisted as evidence; the independent attestor
reconstructs them, recomputes the canonical trace hash and delta hash, re-derives
the replay-record leaf, and confirms it is among the retained Merkle leaves the
root is built from. The behavior-fingerprint hash is re-derived from features
(not trusted), and f64 divergence is stored bit-exact for an identical hash.

- trace_model: ExecutionTrace::serialize/deserialize (round-trips canonical_hash;
  total on garbage). Test: full_trace_serialize_roundtrips_canonical_hash.
- world_model: WorldDelta::serialize/deserialize (round-trips hash).
- ci_reports: retains TRACE_EVIDENCE_SAMPLE full traces; writes
  evidence/traces.tsv.
- attestation: depends on trace_model/world_model; reconstructs each trace,
  recomputes the leaf, requires it to match the claimed leaf AND be a retained
  leaf. Negative control: tampered_trace_breaks_attestation (corrupting the full
  trace, leaving the claimed leaf, fails attestation).
- merge-gates: requires evidence/traces.tsv; the separate attest step verifies it.

End-to-end (fast profile): 256/256 full traces reconstructed and re-derived to
retained leaves; recomputed root matches the claim over 6600 leaves.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-21 21:22:55 -07:00

93 lines
3.9 KiB
YAML

name: magicka-merge-gates
# The merge-blocking enforcement point for the Phase 0/1 acceptance gates.
# Per the spec's compliance model, acceptance may NOT be satisfied by a locally
# runnable binary, a default (fast) profile, or a documentation claim. This
# workflow is the enforcement: the `merge-gates` job below runs the full merge
# profile (1,000,000 executions, 10 perturbations each, 100% reference/runtime
# comparison, 10,000 persisted replay cases, >=500 mutants) and must be a
# REQUIRED status check on the protected branch / merge queue. If it fails or is
# absent, merge is blocked.
on:
pull_request:
branches: [main]
merge_group: # GitHub merge queue — the merge-blocking entry point
push:
branches: [main]
jobs:
# Advisory PR feedback only. The spec permits a 10% fast slice for PR signal,
# but this job is explicitly NOT acceptance and never substitutes for the
# merge profile.
advisory-fast:
if: github.event_name == 'pull_request'
runs-on: ubuntu-latest
timeout-minutes: 30
steps:
- uses: actions/checkout@v4
- name: Unit tests (incl. negative controls)
run: cargo test --release --workspace
- name: Fast advisory gate run
env:
MAGICKA_PROFILE: fast
run: cargo run --release -p ci_reports --bin ci
# The acceptance gate. Required on merge_group / protected main.
merge-gates:
if: github.event_name == 'merge_group' || github.event_name == 'push'
runs-on: ubuntu-latest
timeout-minutes: 1440
steps:
- uses: actions/checkout@v4
- name: Verify committed replay corpus has >= 10,000 cases
run: |
lines=$(grep -vcE '^(#|master)' crates/replay_corpus/corpus/replay_corpus.tsv)
echo "replay corpus cases: $lines"
test "$lines" -ge 10000
- name: Unit tests (incl. negative controls)
run: cargo test --release --workspace
# plan2.md Phase H: the protocol + socket + replay/visibility gates are
# merge-blocking. These run the full HTTP/WebSocket/protocol/runtime path
# headlessly over real sockets (1k matches, 10k fuzz, 100 e2e, leak +
# resilience). The rendered-browser layer is NOT gated here — see
# web-gates.yml (advisory, blocked on CI infrastructure).
- name: Web protocol + socket gates (merge-blocking)
run: cargo test --release -p protocol -p game_runtime -p server -p web_assets -p web_client -p web_tests
- name: Full merge-blocking acceptance gates
env:
MAGICKA_PROFILE: merge
MAGICKA_OUT: ci_out
run: cargo run --release -p ci_reports --bin ci
- name: Enforce required artifacts exist
run: |
for r in domain_participation_report causal_rank_report \
causal_explanation_report \
compression_resistance_report metamorphic_response_report \
mutation_survivor_report runtime_equivalence_report \
replay_report coverage_report provenance_report \
compliance_report; do
test -s "ci_out/${r}.json" || { echo "MISSING ARTIFACT: ${r}.json"; exit 1; }
done
test -s ci_out/evidence/leaves.tsv || { echo "MISSING EVIDENCE: leaves.tsv"; exit 1; }
test -s ci_out/evidence/traces.tsv || { echo "MISSING EVIDENCE: traces.tsv"; exit 1; }
# Independent attestation (findings 2, 3): a SEPARATE process recomputes
# the Merkle root from the retained leaves and checks it against the
# producer's claim. It never reads compliance_report.json. A producer that
# reported a root inconsistent with its own leaves fails here.
- name: Independent attestation of evidence
run: cargo run --release -p attestation --bin attest -- ci_out
- name: Upload acceptance evidence
if: always()
uses: actions/upload-artifact@v4
with:
name: magicka-acceptance-evidence
path: ci_out/