Plan declarations; isolate test fixtures from Git hook variables - #28
Merged
Merged
Conversation
A plan anchor on a field or signature line, as in a walkthrough on an external repository, previously found no supported block.
Run from a pre-push hook in a linked worktree, repository-packet fixtures inherited GIT_DIR and wrote to the pushed repository: a fixture commit on the branch, core.bare=true and a fixture identity in the shared config.
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.
Planner. A tool-level walkthrough of the 0.4.0 tarballs on an external repository (sindresorhus/ky at 0d59458) anchored a plan on a class field (
HTTPError.ts:20) and gotno supported syntax block. Named classes, interfaces, type aliases and enums are now planner blocks. The smallest enclosing block still wins, so a line inside a method selects the method; imports are still not planned.Test isolation (found while pushing this branch). Run by a pre-push hook in a linked worktree, git exports
GIT_DIR,GIT_INDEX_FILEand similar. The repository-packet MCP fixtures and the ecosystem snapshot fixtures then rangit init/config/commitagainst the pushed repository: a fixture commit on the branch,core.bare = trueand a fixture identity in the shared.git/config. Both suites now dropGIT_*variables (a vitest setup file for context-tools; module-level cleanup in the Python test). Verified by runningnpm run checkwithGIT_DIRpointed at a decoy repository: all suites pass and the decoy is unchanged; without the setup file the MCP fixtures write the fixture identity into the decoy.Checks:
npm run check(183 context-tools tests, 31 worker-packet tests), navigation smoke, both benchmark gates with recall 1.0.🤖 Generated with Claude Code
https://claude.ai/code/session_01KzXbuBSq88i3Re82qt6c4L