Repository navigation
facts: export the 1.12.0 release_tag baseline - #187
Conversation
Exports the 1.12.0 release_tag baseline (full re-measurement of the pinned population at the producer tags engine v1.12.0 6e27d0f2 and codegen v1.12.0 126e055f): 7,989 probes, 7,983 excellent, 6 strong, 0 engine errors. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
Graphify reviewed this change.
No issues found by static checks — no coupling regressions or blocking issues in the code graph. That is not the same as safe to merge: see what was not checked.
Not checked: tests were not run; no formal proof of the changed code.
No blocking issues. I didn't find anything I'd hold the merge for.
Analysis details — impact, health, verification
Impact & health
Graphify review
Impact — 0 functions depend on the 0 functions this change touches.
Health — grade A; no new coupling hotspots.
Verification — 0 functions in the blast radius were not formally verified this run (proofs are advisory here).
Gate & verification
graphify gate
PASS — objectively clean (no health regressions, tests not run — proofs not run this pass (advisory)). Grounded, not self-assessed.
Test selection
Test selection
34 of 34 test file(s) selected (100%) via static blast radius.
Escalated to a full run for safety (
noncode-change) — the selection is not trustworthy on its own (see below). CI should run the whole suite.
tests/test_facts_cards.py— full-run-safetytests/test_facts_descriptions.py— full-run-safetytests/test_facts_fanout.py— full-run-safetytests/test_facts_validate.py— full-run-safetytests/test_fingerprint_canonical.py— full-run-safetytests/test_parity_bundle.py— full-run-safetytests/test_parity_source_proof.py— full-run-safetytests/test_release_action_pins.py— full-run-safetytests/test_release_asset_fetch.py— full-run-safetytests/test_release_binding.py— full-run-safetytests/test_release_binding_workflows.py— full-run-safetytests/test_release_coordinator_receipts.py— full-run-safetytests/test_release_docs_runtime.py— full-run-safetytests/test_release_fanout_check.py— full-run-safetytests/test_release_guard_policy.py— full-run-safetytests/test_release_hosted_postmerge_receipts.py— full-run-safetytests/test_release_hpo_image.py— full-run-safetytests/test_release_main_push_inventory.py— full-run-safetytests/test_release_pair.py— full-run-safetytests/test_release_parity.py— full-run-safetytests/test_release_parity_image.py— full-run-safetytests/test_release_parity_runtime.py— full-run-safetytests/test_release_parity_wire.py— full-run-safetytests/test_release_receipt_collect_sweep.py— full-run-safetytests/test_release_receipt_legacy_previous.py— full-run-safetytests/test_release_receipt_shards.py— full-run-safetytests/test_release_receipts.py— full-run-safetytests/test_release_redeliver.py— full-run-safetytests/test_release_runtime_smoke.py— full-run-safetytests/test_release_sink_image.py— full-run-safetytests/test_release_sources.py— full-run-safetytests/test_release_workflows.py— full-run-safetytests/test_repo_descriptions.py— full-run-safetytools/release-dry-run/test_wfrun.py— full-run-safety
non-code file(s) changed (
facts/facts.json) → running the full suite for safety (a code graph can't see config/fixture/data deps)
Selection is safe under the controlled-regression assumption; always-run tests + a periodic full run are the backstops. Advisory — it never changes the check verdict.
Exports the 1.12.0 release_tag baseline
pineforge-parity-baseline-20261112-release-tag-cd9c85a6tofacts/facts.json.6e27d0f2and codegen v1.12.0126e055f.cd9c85a6(digest-verified); populationcf857209.1.12.0; every earlier release entry is kept.lab facts checkon this tree: PASS (0 files drifted).Depends on the workflow PR that maps 1.12.0 in
campaign/facts/releases.json(pineforge-4pass/pineforge-workflow#414). Merge that one first.🤖 Generated with Claude Code