fix(ci): track the paper count the published version actually declares - #1584
Merged
Conversation
check_catalog_count.py printed, on every invocation, that the SSOT's 83 disagreed with a paper count of 84 and that an erratum to arXiv:2606.09686 was required. The erratum in question is ERRATA_2026-06-14.md, and the v2 replacement carried it out. Fetching the current entry shows both the title and the abstract were corrected: TITLE : An 83-Format Numeric Catalog with Bit-Exact Conformance Vectors: ... ID : http://arxiv.org/abs/2606.09686v2 UPDATED : 2026-06-22T12:28:45Z abstract: "a catalog of 83 numeric formats spanning 13 families" The constant tracked the withdrawn v1. The existing comment warns against silently editing this to match the SSOT, and that warning is right -- but this is not that edit. The constant tracks what the PAPER declares, and the paper changed. Matching it to the SSOT would defeat the gate; matching it to the current published title and abstract is what keeps the gate doing its job. The comment now carries the fetch command, the version and the date, so the next reader can re-check in one line rather than trusting this one. The alarm is intact, verified by mutation in the spirit of wp18_selftest_gate.py: with a divergent constant the gate still warns and still exits 3 under --strict-paper. With the corrected value it reports SSOT == fresh regen == paper == 83 and exits 0. A gate that cries wolf every run is one nobody reads on the day the divergence is real. This silences the false alarm without touching the alarm. Closes #1583
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
This was referenced Aug 1, 2026
now-sync-gate requires every PR to master to update docs/NOW.md. This PR predates my knowing that; the entry describes what it lands and states its honesty limits, in the file's existing shape.
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
PR DashboardGenerated at: 2026-08-01 07:44:37 UTC
Summary
Seal Status
|
gHashTag
enabled auto-merge (squash)
August 1, 2026 07:46
Five branches each added an entry at the top of docs/NOW.md, so the first merge conflicted with the other four. Resolved losslessly: this branch's entry sits on top of master's file as it now stands.
Contributor
PR DashboardGenerated at: 2026-08-01 07:48:08 UTC
Summary
Seal Status
|
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Every PR here must touch docs/NOW.md and every entry goes at the top, so each merge conflicts whatever is still open. Resolved losslessly: this branch's entry sits on top of master's file as it now stands.
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
PR DashboardGenerated at: 2026-08-01 08:00:50 UTC
Summary
Seal Status
|
Every PR here must touch docs/NOW.md and every entry goes at the top, so each merge conflicts whatever is still open. Resolved losslessly.
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
PR DashboardGenerated at: 2026-08-01 08:02:05 UTC
Summary
Seal Status
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
tools/check_catalog_count.pyprints a warning on every invocation:The constant behind it tracks the paper's declared count:
That was accurate for v1. It is not accurate now. Fetching the current entry:
The v2 replacement corrected both the title and the abstract. The erratum the gate demands is the one
ERRATA_2026-06-14.mdrecorded and the v2 replacement carried out. The gate has been asking for it ever since.Why this is not the edit the comment forbids
The comment says:
Agreed, and that is not what this does. The constant tracks what the paper declares, and the paper changed. Editing it to match the SSOT would defeat the gate; editing it to match the current published title and abstract is what keeps the gate doing its job. Nothing is silent about it — the evidence, the fetch command and the date are in the comment now, so the next reader can re-check in one line.
The alarm still works
Verified by mutation, in the spirit of
wp18_selftest_gate.py. With the constant set to a divergent value:And with the corrected value:
A gate that cries wolf on every run is one nobody reads on the day the divergence is real. This silences the false alarm without touching the alarm.
Closes #1583