fix(engine): TAG-ANNOTATED never consulted the register for the newest tag
Reported by catalog (coord, 2026-08-17): register/repos.json has listed ktg-plugin-marketplace v7.7.2 under tags_lightweight_accepted since the 0.11.2 release (2026-08-14), but `accepted` was only ever applied to tags.slice(0, -1) — the newest tag is excluded from that slice by construction, so the entry was dead weight from the day it was written. checkTagIntegrity now checks the newest tag against `accepted` too, emitting a distinct TAG-ANNOTATED-ACCEPTED-NEWEST OK instead of silently doing nothing when the register names it exactly. Acceptance is per-tag-name, not a standing exemption: a new lightweight tag that becomes newest afterwards is still judged (tested). TDD: two new tests written failing first (an existing test's title claimed "cannot be accepted away" but never actually passed a matching `name`, so it was accidentally still green either way — reworded to test what it actually covers). Verified against a fresh clone of ktg-plugin-marketplace: the full finding set now reads OK TAG-ANNOTATED-ACCEPTED-NEWEST + OK TAG-ANNOTATED-ACCEPTED(7 older) instead of ERROR, with no knock-on effect on TAG-SIGNED (all 9 tags predate the signing policy). Register comment updated to record the three-day dead-weight window rather than silently correcting it — a decision that turns out wrong is worse than no record. 247 tests pass (245 + 2 new).
This commit is contained in:
parent
4714f13959
commit
aee0f28539
3 changed files with 72 additions and 12 deletions
|
|
@ -223,6 +223,15 @@
|
|||
"itself enforces that, since a new lightweight newest tag is not on this",
|
||||
"list and fires ERROR.",
|
||||
"",
|
||||
"This entry was DEAD WEIGHT from 2026-08-14 to 2026-08-18: `accepted` was",
|
||||
"only ever consulted for tags OLDER than newest, so v7.7.2 kept firing",
|
||||
"TAG-ANNOTATED ERROR the whole time — the exact 'we decided this' vs.",
|
||||
"'nobody looked' collapse this axis exists to prevent, one level down.",
|
||||
"Caught and reported by the catalog itself (coord, 2026-08-17), fixed in",
|
||||
"`checkTagIntegrity` (repo-standard, 2026-08-18): the accepted set is now",
|
||||
"checked against the newest tag too, emitting a distinct",
|
||||
"`TAG-ANNOTATED-ACCEPTED-NEWEST` OK rather than silently doing nothing.",
|
||||
"",
|
||||
"The two slash-named `config-audit/v*` tags on that forge are OUT OF SCOPE",
|
||||
"by construction, not omitted by a fetch gap: the engine reads",
|
||||
"`refs/tags/v*` — the repo's own version line — and a namespaced",
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue