Conversation
The sunset condition it shipped with — both records that predated #181 having run it — was met about an hour after it was written, so the marker started reporting a removal that was not going to happen. A marker stating a condition it does not mean is the thing it exists to prevent, one level up. Pinned to 1.0.0 instead. More records are coming onto luria before the first stable release and each of them predates #181, so the version is the honest gate; a list of projects is never finished at the moment you read it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YP4P3m8rzVFb8idnTE4FfT
Both existed for #181, which every record that predates it has now run. An upgrade kept past its purpose is dead code that still has to be read, tested and explained — which is what `spent-upgrades` was added to notice, and it noticed about an hour after being written. So the marker goes with the thing it marked. Its job was to raise the question rather than wait to be remembered, and it did; keeping a check whose only finding is answered would be the same mistake in the layer above. The finding for a scheme declaring no `status` vocabulary now names the declaration to write, since the command that used to write it is gone. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YP4P3m8rzVFb8idnTE4FfT
This was referenced Sep 6, 2026
Closed
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
2 participants
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.
Draft, pinned to 1.0.0. More records are coming onto luria before the first stable release and each of them predates #181, so the command has work left even though both current records are done with it.
Two commits, and the first one is wanted now:
1.
b89cc2a— say when it goes, not that it could have gone alreadyThe sunset condition it shipped with was "once luria's own record and the anthology are both on the release that carries this". That was met about an hour after it was written, so
spent-upgradesstarted reporting a removal that was not going to happen — on everyluria lintrun, in both records.A marker stating a condition it does not mean is the failure it exists to prevent, one level up. Repinned to 1.0.0: the version rather than a list of projects, because a list is never finished at the moment you read it.
If you want the false nag to stop before 1.0.0, this commit is the whole fix — say the word and I'll split it into its own non-draft PR.
2.
135439c— the removal itselfDeletes
luria/upgrade.py, its CLI registration, thespent-upgradeslint class andspent_upgrades(), and the three tests that covered them. The finding for a scheme declaring nostatusvocabulary now names the declaration to write rather than a command that no longer exists.The marker goes with the thing it marked. Its job was to raise the question rather than wait to be remembered, and it did — keeping a check whose only finding is answered would be the same mistake in the layer above.
Before this merges
luria— its own record, on 0.10.0dmarx/anthology-of-the-sota— #25, on 0.10.0dmarx/mathematics-of-meaningdmarx/strata-gEach unchecked record predates #181, so each needs
luria upgrade statuses(or the equivalent by hand) while the command still exists. Neither repository is in this session's scope yet; both are reachable and I can pick them up on request.Checks
python -m pytest tests -q: 905 passed (908 → 905, the three removed with the feature).luria lint: clean — including thespent-upgradesrow, which this removes.🤖 Generated with Claude Code
https://claude.ai/code/session_01YP4P3m8rzVFb8idnTE4FfT
Generated by Claude Code