open/repo-standard
1
0
Fork 0
Code Issues Releases 7 Activity

fix: three more measured false positives, all reported the same day v0.1.2 shipped

Browse source 
- extractChangelogTop truncated PEP 440 pre-release versions (0.5.0a2 -> 0.5.0),
  so VERSION-CHANGELOG disagreed with VERSION-TAG over a version everything
  already agreed on. Reported by llm-ingestion-okf with a repro.
- BADGE-STATIC-CLAIM treated a bare `status` badge as a run claim, same as
  tests/build/CI. A self-declared maturity label asserts no run, same class
  as version/licence/platform. Reported by llm-ingestion-pipeline-security.
- BOILERPLATE flagged FIXME when a scanner's own docs named the TODO/FIXME
  convention rather than an instance of it. Reported by config-audit.

92 tests green, up from 86.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Uwwfdmrfnp7FuGQ4z25RKH
This commit is contained in:
Kjell Tore Guttormsen 2026-08-03 22:10:17 +02:00
commit 5eba10acdd
7 changed files with 110 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

29
CHANGELOG.md
View file

@ -4,6 +4,34 @@ All notable changes to this project are documented here.
Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/);
versioning is [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [0.1.3] — 2026-08-03
### Fixed
Three more measured false positives, all reported via coord the same day
0.1.2 shipped, from repos running the gate for the first time.
- `extractChangelogTop` truncated a PEP 440 pre-release (`0.5.0a2`) to `0.5.0`,
so `VERSION-CHANGELOG` disagreed with `VERSION-TAG` — which compares the
untruncated tag and does not have this problem — over a version the manifest
and the tag already agreed on. Reported by `llm-ingestion-okf` with a
repro. An affected repo could reach 0 ERROR only by lying about its version;
now the pre-release suffix is kept.
- `BADGE-STATIC-CLAIM` treated a bare `status` badge (`status-alpha`,
`status-experimental`) as a run claim, the same as `tests-34-passing`.
A self-declared maturity label asserts no run — the same class as version,
licence and platform, already exempt. Reported by
`llm-ingestion-pipeline-security`. `build`/`ci`/`passing` still catch the
run-asserting compounds ("build status", "CI status"); only the bare word
is dropped.
- `BOILERPLATE` flagged a bare `FIXME` even when it named the *convention*
rather than an instance of it — a scanner's own docs describing what it
detects ("Flag TODO/FIXME markers…", a table row listing "TODO/FIXME
comments" as a finding type) read the same as a forgotten marker. Reported
by `config-audit`, whose product literally is a marker scanner. "TODO/FIXME"
named together is now read as the convention; a lone `FIXME` is still
caught.
## [0.1.2] — 2026-08-03
### Fixed
@ -133,6 +161,7 @@ First release. Covers the checks that a single repository can answer on its own.
- No hook ships in this release. A blocking gate has to be precise enough not to
fail a correct repository first.
[0.1.3]: https://git.fromaitochitta.com/open/repo-standard/src/tag/v0.1.3
[0.1.2]: https://git.fromaitochitta.com/open/repo-standard/src/tag/v0.1.2
[0.1.1]: https://git.fromaitochitta.com/open/repo-standard/src/tag/v0.1.1
[0.1.0]: https://git.fromaitochitta.com/open/repo-standard/src/tag/v0.1.0