Skip to content

Register Debian source set 19 (v1.4.0) - #180

Merged
luisleo526 merged 1 commit into
mainfrom
register-source-set-19
Nov 10, 2026
Merged

luisleo526 merged 1 commit into
mainfrom
register-source-set-19

Conversation

@luisleo526

Copy link
Copy Markdown
Contributor

Registers Debian source set 19: 72 source/version pairs, with the source list and Linux archive already published on v1.4.0. The only source change from set-18 is linux 6.12.115-2 to 6.12.116-1.

Updates the source-set registry, its existing test data and the README. No workflow or runtime code changes.

Validation on the exact commit: source registry 43 tests, docs runtime 6 tests and workflows 151 tests passed. HPO image tests reported 38 tests with 2 wheel-dependent skips; guard policy reported 17 tests and an image-class skip. Those skips do not establish wheel resolution or image-layer coverage. Hosted CI remains required.

🤖 Generated with Claude Code

Register the 72-pair source set and published list held by v1.4.0. Update
the registry test data and document the Linux 6.12.116-1 source update.

@graphify-labs graphify-labs Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Graphify reviewed this change.

Worth a look — the grounded gate found no coupling regressions or blocking issues, but 1 advisory finding(s) below merit a look before merge.

Not checked: tests were not run; no formal proof of the changed code.


Graphify review — findings

Adds set-19 to the source-set registry: 72 source/version pairs at v1.4.0, identified by the set-id 25857d47…e9c8. It updates linux to 6.12.116-1 and keeps set-18's other 71 sources, and the README now documents this. Raises the registry test's expected row count and unique set-id count from 18 to 19, with the extra v1.4.0 tag and 72 count, so the new row has to match the registered set-19.SOURCES.list asset, which is not in the diff.

Worth a look

  • Registered set-19 list asset is missing — docker/SOURCE-SETS.tsv:21 · Escalate · medium
    • unverified hypothesis — survived the adversarial refute pass; needs human review
Analysis details — impact, health, verification

Impact & health

Graphify review

Impact — 80 functions depend on the 80 functions this change touches.

Health — grade A; no new coupling hotspots.

Verification — 80 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.

Advisory (not blocking):

  • verification_scope: 80 function(s) in the blast radius were not formally verified this run

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, uncovered-code) — the selection is not trustworthy on its own (see below). CI should run the whole suite.

  • tests/test_facts_cards.py — full-run-safety
  • tests/test_facts_descriptions.py — full-run-safety
  • tests/test_facts_fanout.py — full-run-safety
  • tests/test_facts_validate.py — full-run-safety
  • tests/test_fingerprint_canonical.py — full-run-safety
  • tests/test_parity_bundle.py — full-run-safety
  • tests/test_parity_source_proof.py — full-run-safety
  • tests/test_release_action_pins.py — full-run-safety
  • tests/test_release_asset_fetch.py — full-run-safety
  • tests/test_release_binding.py — full-run-safety
  • tests/test_release_binding_workflows.py — full-run-safety
  • tests/test_release_coordinator_receipts.py — full-run-safety
  • tests/test_release_docs_runtime.py — full-run-safety
  • tests/test_release_fanout_check.py — full-run-safety
  • tests/test_release_guard_policy.py — full-run-safety
  • tests/test_release_hosted_postmerge_receipts.py — full-run-safety
  • tests/test_release_hpo_image.py — full-run-safety
  • tests/test_release_main_push_inventory.py — full-run-safety
  • tests/test_release_pair.py — full-run-safety
  • tests/test_release_parity.py — full-run-safety
  • tests/test_release_parity_image.py — full-run-safety
  • tests/test_release_parity_runtime.py — full-run-safety
  • tests/test_release_parity_wire.py — full-run-safety
  • tests/test_release_receipt_collect_sweep.py — full-run-safety
  • tests/test_release_receipt_legacy_previous.py — full-run-safety
  • tests/test_release_receipt_shards.py — full-run-safety
  • tests/test_release_receipts.py — full-run-safety
  • tests/test_release_redeliver.py — full-run-safety
  • tests/test_release_runtime_smoke.py — full-run-safety
  • tests/test_release_sink_image.py — full-run-safety
  • tests/test_release_sources.py — impact, changed-test, full-run-safety
  • tests/test_release_workflows.py — full-run-safety
  • tests/test_repo_descriptions.py — full-run-safety
  • tools/release-dry-run/test_wfrun.py — full-run-safety

non-code file(s) changed (README.md, docker/SOURCE-SETS.tsv) → running the full suite for safety (a code graph can't see config/fixture/data deps)

changed code file(s) with no mapped test (README.md) — a coverage gap or a missing link — running the full suite rather than only the selected tests

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.

@luisleo526
luisleo526 merged commit ae29ae9 into main Nov 10, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant