Pin .agents to origin/main - #11
Merged
Merged
Conversation
The submodule pointer referenced 624a6b4, which exists only on the branch of an unmerged pull request. A squash-merge of that PR followed by deleting the branch would leave this repository pinned to an unreachable SHA, and a clone with --recurse-submodules would fail. I caused it and did not catch it. The session-close check verified the submodule was clean and that the pointer matched its working tree — both true — without asking the question that mattered: whether that commit is reachable from a permanent branch. Pinning to origin/main adopts five commits and loses one. The five touch no hook, script, rule or workflow — a release seal, the repository rename, vendored skill provenance, README identity and a social card. The one lost is the secret scanner fix, which is pending review as PR #27 and which this repository never depended on: it is a framework improvement, not a requirement of this app. It also puts this host on the same lineage as the other two, which pin 4029c65 — an ancestor of this commit rather than a divergent one. Co-Authored-By: Claude Opus 5 <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.
What this changes
The
.agentssubmodule pointer moves from624a6b4todfa68ed(origin/main).Why it was broken
624a6b4exists only on the branch of an unmerged pull request. Squash-merging that PR and deleting the branch would leave this repository pinned to an unreachable SHA, andgit clone --recurse-submoduleswould fail for anyone.I caused it and did not catch it. The session-close check verified the submodule was clean and that the pointer matched its working tree — both true — without asking the question that mattered: is that commit reachable from a permanent branch?
What the move adopts and loses
None of the five touches a hook, script, rule or workflow — checked with
git diff --name-only, not assumed. The one lost is a framework improvement this repository never depended on.It also puts this host on the same lineage as the other two, which pin
4029c65— an ancestor of this commit rather than a divergent one.How it was verified
A real recursive clone of this branch, which is the only thing that proves a pointer resolves:
🤖 Generated with Claude Code