Repository navigation
5.15.0 post-release: eval records and two stale checkout paths - #882
Merged
Merged
Conversation
The three eval documents are part of the release, not optional write-ups. Each
answers a different question, and a clean run is evidence where silence is not:
CREATOR_VALIDATION.md Gate 10, pre-publish, against the built wheel
POSTPUBLISH_EVAL.md Stage 5, against the published package
STAGE6_DOWNSTREAM_SWEEP.md companions, ranges, drift, consumers
Gate 10a went red twice before it passed, and neither was a nodus-lang
regression -- which is the case for running it that the record now carries:
1. exit 2, a registered checkout that no longer resolved. nodus-a2a-wire had
moved from C:\codev to C:\dev. A missing checkout is not a pass; an unrun
suite covers nothing.
2. one NEW failure in nodus-mcp -- its own two version sources disagreeing,
__init__.py at 0.1.3 against pyproject.toml at 0.1.4. Published 0.1.4
therefore reports 0.1.3 from `--version` and both serve banners. Fixed in
that repo (51cb91d); PyPI keeps 0.1.4's wrong banner.
Third run clean: all 8 dependent suites, 953 tests. Gate 10b 136/136 against the
wheel from site-packages under --require-installed. Stage 5 8/8 through the
published package, no index lag.
TWO STALE PATHS FIXED, and the second is the interesting one. The a2a-wire move
broke tools/nodus_lang_dependents.json AND tools/check_publish_drift.py, which
carries its own hardcoded path table -- so fixing the first left the drift sweep
still skipping, and a skip is not a pass. #810 unified the membership lists and
left the paths duplicated. The comment at the second site now says so rather
than leaving the next reader to rediscover it.
The eval-record claim moves here and only here: `points_at` requires the
directory to hold the document, so it cannot be bumped at the cut. --versions
reported exactly the one predicted failure on this commit and 13/13 after.
Still owed, and deliberately not taken unilaterally: a nodus-mcp 0.1.5 for the
banner, and the two consumer republishes (nodus-run-action, nodus-wiki). Their
flags stay set until the work is done -- a flag cleared early is worse than no
flag.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
nodus-run-action v1.0.16 and nodus-wiki b9550c2. The flags move here and only here -- after the republishes, in the same commit as the work, because a flag cleared early is worse than no flag. `--consumers --strict` is 3/3 in step. Two things the version fingerprint caught only indirectly, both on the wiki: _Sidebar said "Nodus v5.12", stale by three releases and invisible to a grep for the current version; and Security's supported-versions table named v5.13.x as latest, stale by two, which on a security page actively misinforms. The wiki's two "Since v5.14.0 ..." sentences were deliberately left alone. They say when something arrived, not what is current, and bumping them would make the page lie about which release introduced the serve budget -- the same distinction tools/version_claims.json encodes upstream. Embedding-API was checked against the real constructor rather than trusted: 27 documented, 27 in the signature, all three capability flags present. nodus-run-action also surfaced something no fingerprint tracks: the floating `v1` tag had not moved since the 5.9.0 cycle, six releases, while the README tells everyone to use @v1. Verified before moving it -- `git diff v1 HEAD` touches README.md only, action.yml byte-identical -- so nothing a consumer runs changes. Every wiki claim and its code example were run against the PUBLISHED 5.15.0 before pushing. That wiki has no PR and no CI, so nothing else would have. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
The three eval documents for 5.15.0, plus two tooling path fixes the sweep surfaced.
Gate 10a went red twice before it passed, and neither was a nodus-lang regression — which is the argument for running it that the record now carries:
nodus-a2a-wirehad moved fromC:\codevtoC:\dev. A missing checkout is not a pass.__init__.py0.1.3 vspyproject.toml0.1.4). So published 0.1.4 reports 0.1.3 from--versionand both serve banners. Fixed in that repo (51cb91d); PyPI keeps 0.1.4's wrong banner.Third run clean: 8 suites, 953 tests. Gate 10b 136/136 against the wheel from
site-packagesunder--require-installed. Stage 5 8/8 through the published package, no index lag.Two stale paths fixed, and the second is the interesting one. The a2a-wire move broke
nodus_lang_dependents.jsonandcheck_publish_drift.py, which carries its own hardcoded path table — so fixing the first left the drift sweep still skipping, and a skip is not a pass. #810 unified the membership lists and left the paths duplicated. The comment at the second site says so now.The eval-record claim moves here and only here.
points_atrequires the directory to hold the document, so it cannot be bumped at the cut:--versionsreported exactly the one predicted failure on this commit, 13/13 after.Still owed, deliberately not taken unilaterally
nodus_version, so they go stale at every bump by construction)Their consumer flags stay set until the work is done — a flag cleared early is worse than no flag.
🤖 Generated with Claude Code