Repository navigation
Graph Climbing v0.3: standalone public core - #1
Merged
Merged
Conversation
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
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 changes
This makes Graph Climbing v0.3 a portability and clarity release candidate with one obvious standalone path:
v0.2.0tag and a conciseEVIDENCE.mdboundary;advanced/;adapters/;skills/graph-climbingentrypoint as a zero-copy compatibility symlink to the adapter;Why
The previous tree truthfully described a runtime-neutral protocol, but its default inventory mixed the small serial kernel with the private origin project's case studies, tool-specific bindings, and advanced worker machinery. An outside adopter should not need to understand that system before running one climb.
The removed reports were useful origin evidence, but neither was independent replication. Keeping them in the current tree made the public surface look more mature and more system-dependent than the evidence supports.
Compatibility
The checker and multi-worker logic are relocated without logic changes. In Git checkouts that preserve repository symlinks, existing installations targeting
skills/graph-climbingcontinue to resolve the exact adapter content through a relative symlink; there is no duplicated skill tree. All 79 pre-curation tests remain present; five new public-surface tests bring the total to 84. The frozen durable-worker contract retains its existing SHA-256 assertion.The default path requires no private system, named model vendor, task tracker, skill loader, hook, or durable runtime. Bun remains optional for the reference checker; the README includes a manual frontier rule when Bun is unavailable.
Verification
bun test— 84 passed, 0 failedbun run graph-check starter/SPEC.md— valid claim frontierbun run graph-check examples/notes-cli/SPEC.md— valid vertical frontierC-2; missing-probe spec failed nonzerogit diff --checkEvidence boundary
This PR does not claim independent replication, general productivity improvement, release publication, or maturity beyond an experimental reference implementation. The PR itself does not create a v0.3 tag or update the separate Gist. If merged, the planned release step is to tag the exact merge as
v0.3.0and synchronize the Gist to the taggedGRAPH-CLIMBING.md; the repository remains authoritative.Reviewer focus
Please check that the serial path is genuinely sufficient for a cold adopter, that the legacy skill alias resolves without duplication, and that relocating advanced material has not weakened the preserved multi-worker contract or made any public links unreachable.