docs: drop the pinned version from the port's preamble - #929
Merged
Conversation
`claude/action.yaml` moved to 2.1.226 while #904 was in flight, so the sentence naming 2.1.220 as the version it pins shipped already false. The skill no longer names a version at all — it had no reason to, and a version sitting in a file nothing re-checks is a claim waiting to rot. `TODO.md` keeps the provenance, where the drift is the point rather than an aside: the port came from 2.1.220, CI now runs 2.1.226, and the restructuring between them is exactly what decides whether the port should survive. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
tend-agent
approved these changes
Aug 9, 2026
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.
claude/action.yamlmoved to 2.1.226 while #904 was in flight, so the sentence naming 2.1.220 as the version it pins was already false when it landed. The skill's preamble no longer names a version at all — it had no reason to, and a version sitting in a file nothing re-checks is a claim waiting to rot.TODO.mdkeeps the provenance, where the drift is the point rather than an aside: the port was taken from 2.1.220, CI now runs 2.1.226, and what changed between them is exactly what decides whether the port should survive. That entry already listed a version bump as a revisit trigger; this records that the trigger has fired.