@ruverd/julius 0.0.0-stage → 0.24.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +31 -0
- package/CREDITS.md +25 -0
- package/LICENSE +21 -0
- package/PROVENANCE.md +9 -0
- package/README.md +225 -2
- package/dist/ai/crux.d.ts +60 -0
- package/dist/ai/crux.d.ts.map +1 -0
- package/dist/ai/crux.js +141 -0
- package/dist/ai/crux.js.map +1 -0
- package/dist/ai/failure.d.ts +60 -0
- package/dist/ai/failure.d.ts.map +1 -0
- package/dist/ai/failure.js +86 -0
- package/dist/ai/failure.js.map +1 -0
- package/dist/ai/llm/anthropic.d.ts +37 -0
- package/dist/ai/llm/anthropic.d.ts.map +1 -0
- package/dist/ai/llm/anthropic.js +144 -0
- package/dist/ai/llm/anthropic.js.map +1 -0
- package/dist/ai/llm/factory.d.ts +28 -0
- package/dist/ai/llm/factory.d.ts.map +1 -0
- package/dist/ai/llm/factory.js +36 -0
- package/dist/ai/llm/factory.js.map +1 -0
- package/dist/ai/llm/litellm.d.ts +34 -0
- package/dist/ai/llm/litellm.d.ts.map +1 -0
- package/dist/ai/llm/litellm.js +45 -0
- package/dist/ai/llm/litellm.js.map +1 -0
- package/dist/ai/llm/openai.d.ts +44 -0
- package/dist/ai/llm/openai.d.ts.map +1 -0
- package/dist/ai/llm/openai.js +239 -0
- package/dist/ai/llm/openai.js.map +1 -0
- package/dist/ai/llm/orcarouter.d.ts +34 -0
- package/dist/ai/llm/orcarouter.d.ts.map +1 -0
- package/dist/ai/llm/orcarouter.js +45 -0
- package/dist/ai/llm/orcarouter.js.map +1 -0
- package/dist/ai/llm/recover-tool.d.ts +19 -0
- package/dist/ai/llm/recover-tool.d.ts.map +1 -0
- package/dist/ai/llm/recover-tool.js +109 -0
- package/dist/ai/llm/recover-tool.js.map +1 -0
- package/dist/ai/llm/types.d.ts +122 -0
- package/dist/ai/llm/types.d.ts.map +1 -0
- package/dist/ai/llm/types.js +33 -0
- package/dist/ai/llm/types.js.map +1 -0
- package/dist/ai/providers.d.ts +59 -0
- package/dist/ai/providers.d.ts.map +1 -0
- package/dist/ai/providers.js +54 -0
- package/dist/ai/providers.js.map +1 -0
- package/dist/ai/summarize.d.ts +25 -0
- package/dist/ai/summarize.d.ts.map +1 -0
- package/dist/ai/summarize.js +34 -0
- package/dist/ai/summarize.js.map +1 -0
- package/dist/ai/synthesize.d.ts +40 -0
- package/dist/ai/synthesize.d.ts.map +1 -0
- package/dist/ai/synthesize.js +131 -0
- package/dist/ai/synthesize.js.map +1 -0
- package/dist/app/checkout.d.ts +46 -0
- package/dist/app/checkout.d.ts.map +1 -0
- package/dist/app/checkout.js +223 -0
- package/dist/app/checkout.js.map +1 -0
- package/dist/app/events.d.ts +44 -0
- package/dist/app/events.d.ts.map +1 -0
- package/dist/app/events.js +64 -0
- package/dist/app/events.js.map +1 -0
- package/dist/app/identity.d.ts +54 -0
- package/dist/app/identity.d.ts.map +1 -0
- package/dist/app/identity.js +96 -0
- package/dist/app/identity.js.map +1 -0
- package/dist/app/main.d.ts +2 -0
- package/dist/app/main.d.ts.map +1 -0
- package/dist/app/main.js +62 -0
- package/dist/app/main.js.map +1 -0
- package/dist/app/pages.d.ts +56 -0
- package/dist/app/pages.d.ts.map +1 -0
- package/dist/app/pages.js +193 -0
- package/dist/app/pages.js.map +1 -0
- package/dist/app/queue.d.ts +40 -0
- package/dist/app/queue.d.ts.map +1 -0
- package/dist/app/queue.js +68 -0
- package/dist/app/queue.js.map +1 -0
- package/dist/app/review-process.d.ts +66 -0
- package/dist/app/review-process.d.ts.map +1 -0
- package/dist/app/review-process.js +200 -0
- package/dist/app/review-process.js.map +1 -0
- package/dist/app/review-worker.d.ts +2 -0
- package/dist/app/review-worker.d.ts.map +1 -0
- package/dist/app/review-worker.js +108 -0
- package/dist/app/review-worker.js.map +1 -0
- package/dist/app/review.d.ts +23 -0
- package/dist/app/review.d.ts.map +1 -0
- package/dist/app/review.js +142 -0
- package/dist/app/review.js.map +1 -0
- package/dist/app/server.d.ts +49 -0
- package/dist/app/server.d.ts.map +1 -0
- package/dist/app/server.js +123 -0
- package/dist/app/server.js.map +1 -0
- package/dist/ask/ask.d.ts +195 -0
- package/dist/ask/ask.d.ts.map +1 -0
- package/dist/ask/ask.js +1252 -0
- package/dist/ask/ask.js.map +1 -0
- package/dist/ask/file-rank.d.ts +72 -0
- package/dist/ask/file-rank.d.ts.map +1 -0
- package/dist/ask/file-rank.js +160 -0
- package/dist/ask/file-rank.js.map +1 -0
- package/dist/ask/file-selection.d.ts +22 -0
- package/dist/ask/file-selection.d.ts.map +1 -0
- package/dist/ask/file-selection.js +66 -0
- package/dist/ask/file-selection.js.map +1 -0
- package/dist/ask/fuse.d.ts +195 -0
- package/dist/ask/fuse.d.ts.map +1 -0
- package/dist/ask/fuse.js +344 -0
- package/dist/ask/fuse.js.map +1 -0
- package/dist/ask/graphrank.d.ts +61 -0
- package/dist/ask/graphrank.d.ts.map +1 -0
- package/dist/ask/graphrank.js +130 -0
- package/dist/ask/graphrank.js.map +1 -0
- package/dist/ask/index-file.d.ts +44 -0
- package/dist/ask/index-file.d.ts.map +1 -0
- package/dist/ask/index-file.js +128 -0
- package/dist/ask/index-file.js.map +1 -0
- package/dist/bin/julius.d.ts +3 -0
- package/dist/bin/julius.d.ts.map +1 -0
- package/dist/bin/julius.js +4 -0
- package/dist/bin/julius.js.map +1 -0
- package/dist/blast/blast-cli.d.ts +35 -0
- package/dist/blast/blast-cli.d.ts.map +1 -0
- package/dist/blast/blast-cli.js +155 -0
- package/dist/blast/blast-cli.js.map +1 -0
- package/dist/blast/blast.d.ts +128 -0
- package/dist/blast/blast.d.ts.map +1 -0
- package/dist/blast/blast.js +383 -0
- package/dist/blast/blast.js.map +1 -0
- package/dist/blast/diff.d.ts +53 -0
- package/dist/blast/diff.d.ts.map +1 -0
- package/dist/blast/diff.js +193 -0
- package/dist/blast/diff.js.map +1 -0
- package/dist/blast/evidence.d.ts +51 -0
- package/dist/blast/evidence.d.ts.map +1 -0
- package/dist/blast/evidence.js +162 -0
- package/dist/blast/evidence.js.map +1 -0
- package/dist/blast/modules.d.ts +33 -0
- package/dist/blast/modules.d.ts.map +1 -0
- package/dist/blast/modules.js +83 -0
- package/dist/blast/modules.js.map +1 -0
- package/dist/blast/name.d.ts +74 -0
- package/dist/blast/name.d.ts.map +1 -0
- package/dist/blast/name.js +269 -0
- package/dist/blast/name.js.map +1 -0
- package/dist/blast/owners.d.ts +85 -0
- package/dist/blast/owners.d.ts.map +1 -0
- package/dist/blast/owners.js +272 -0
- package/dist/blast/owners.js.map +1 -0
- package/dist/blast/render.d.ts +46 -0
- package/dist/blast/render.d.ts.map +1 -0
- package/dist/blast/render.js +422 -0
- package/dist/blast/render.js.map +1 -0
- package/dist/blast/viz.d.ts +37 -0
- package/dist/blast/viz.d.ts.map +1 -0
- package/dist/blast/viz.js +180 -0
- package/dist/blast/viz.js.map +1 -0
- package/dist/brand.d.ts +13 -0
- package/dist/brand.d.ts.map +1 -0
- package/dist/brand.js +43 -0
- package/dist/brand.js.map +1 -0
- package/dist/check/learning-edits.d.ts +9 -0
- package/dist/check/learning-edits.d.ts.map +1 -0
- package/dist/check/learning-edits.js +62 -0
- package/dist/check/learning-edits.js.map +1 -0
- package/dist/check/local-check.d.ts +104 -0
- package/dist/check/local-check.d.ts.map +1 -0
- package/dist/check/local-check.js +830 -0
- package/dist/check/local-check.js.map +1 -0
- package/dist/check/types.d.ts +31 -0
- package/dist/check/types.d.ts.map +1 -0
- package/dist/check/types.js +2 -0
- package/dist/check/types.js.map +1 -0
- package/dist/claude/build-progress.d.ts +29 -0
- package/dist/claude/build-progress.d.ts.map +1 -0
- package/dist/claude/build-progress.js +76 -0
- package/dist/claude/build-progress.js.map +1 -0
- package/dist/claude/format.d.ts +131 -0
- package/dist/claude/format.d.ts.map +1 -0
- package/dist/claude/format.js +328 -0
- package/dist/claude/format.js.map +1 -0
- package/dist/claude/hook-layers.d.ts +8 -0
- package/dist/claude/hook-layers.d.ts.map +1 -0
- package/dist/claude/hook-layers.js +74 -0
- package/dist/claude/hook-layers.js.map +1 -0
- package/dist/claude/hooks.d.ts +101 -0
- package/dist/claude/hooks.d.ts.map +1 -0
- package/dist/claude/hooks.js +849 -0
- package/dist/claude/hooks.js.map +1 -0
- package/dist/claude/init.d.ts +70 -0
- package/dist/claude/init.d.ts.map +1 -0
- package/dist/claude/init.js +207 -0
- package/dist/claude/init.js.map +1 -0
- package/dist/claude/note-signals.d.ts +28 -0
- package/dist/claude/note-signals.d.ts.map +1 -0
- package/dist/claude/note-signals.js +325 -0
- package/dist/claude/note-signals.js.map +1 -0
- package/dist/claude/paths.d.ts +9 -0
- package/dist/claude/paths.d.ts.map +1 -0
- package/dist/claude/paths.js +22 -0
- package/dist/claude/paths.js.map +1 -0
- package/dist/claude/session-metrics.d.ts +73 -0
- package/dist/claude/session-metrics.d.ts.map +1 -0
- package/dist/claude/session-metrics.js +209 -0
- package/dist/claude/session-metrics.js.map +1 -0
- package/dist/claude/settings-merge.d.ts +66 -0
- package/dist/claude/settings-merge.d.ts.map +1 -0
- package/dist/claude/settings-merge.js +249 -0
- package/dist/claude/settings-merge.js.map +1 -0
- package/dist/claude/shim-template.d.ts +18 -0
- package/dist/claude/shim-template.d.ts.map +1 -0
- package/dist/claude/shim-template.js +226 -0
- package/dist/claude/shim-template.js.map +1 -0
- package/dist/claude/skill-template.d.ts +12 -0
- package/dist/claude/skill-template.d.ts.map +1 -0
- package/dist/claude/skill-template.js +294 -0
- package/dist/claude/skill-template.js.map +1 -0
- package/dist/claude/state.d.ts +73 -0
- package/dist/claude/state.d.ts.map +1 -0
- package/dist/claude/state.js +33 -0
- package/dist/claude/state.js.map +1 -0
- package/dist/claude/stats.d.ts +5 -0
- package/dist/claude/stats.d.ts.map +1 -0
- package/dist/claude/stats.js +24 -0
- package/dist/claude/stats.js.map +1 -0
- package/dist/claude/statusline.d.ts +14 -0
- package/dist/claude/statusline.d.ts.map +1 -0
- package/dist/claude/statusline.js +45 -0
- package/dist/claude/statusline.js.map +1 -0
- package/dist/claude/sync-run.d.ts +3 -0
- package/dist/claude/sync-run.d.ts.map +1 -0
- package/dist/claude/sync-run.js +46 -0
- package/dist/claude/sync-run.js.map +1 -0
- package/dist/claude/tally.d.ts +50 -0
- package/dist/claude/tally.d.ts.map +1 -0
- package/dist/claude/tally.js +211 -0
- package/dist/claude/tally.js.map +1 -0
- package/dist/cli-epilogue.d.ts +12 -0
- package/dist/cli-epilogue.d.ts.map +1 -0
- package/dist/cli-epilogue.js +55 -0
- package/dist/cli-epilogue.js.map +1 -0
- package/dist/cli-meta.d.ts +45 -0
- package/dist/cli-meta.d.ts.map +1 -0
- package/dist/cli-meta.js +145 -0
- package/dist/cli-meta.js.map +1 -0
- package/dist/cli-picker.d.ts +129 -0
- package/dist/cli-picker.d.ts.map +1 -0
- package/dist/cli-picker.js +432 -0
- package/dist/cli-picker.js.map +1 -0
- package/dist/cli.d.ts +3 -0
- package/dist/cli.d.ts.map +1 -0
- package/dist/cli.js +2213 -0
- package/dist/cli.js.map +1 -0
- package/dist/cloud/diff.d.ts +20 -0
- package/dist/cloud/diff.d.ts.map +1 -0
- package/dist/cloud/diff.js +59 -0
- package/dist/cloud/diff.js.map +1 -0
- package/dist/cloud/nudge.d.ts +66 -0
- package/dist/cloud/nudge.d.ts.map +1 -0
- package/dist/cloud/nudge.js +268 -0
- package/dist/cloud/nudge.js.map +1 -0
- package/dist/cloud/workspace-sync.d.ts +58 -0
- package/dist/cloud/workspace-sync.d.ts.map +1 -0
- package/dist/cloud/workspace-sync.js +268 -0
- package/dist/cloud/workspace-sync.js.map +1 -0
- package/dist/cloud/workspace.d.ts +159 -0
- package/dist/cloud/workspace.d.ts.map +1 -0
- package/dist/cloud/workspace.js +134 -0
- package/dist/cloud/workspace.js.map +1 -0
- package/dist/context/build.d.ts +52 -0
- package/dist/context/build.d.ts.map +1 -0
- package/dist/context/build.js +362 -0
- package/dist/context/build.js.map +1 -0
- package/dist/context/check.d.ts +42 -0
- package/dist/context/check.d.ts.map +1 -0
- package/dist/context/check.js +162 -0
- package/dist/context/check.js.map +1 -0
- package/dist/context/map-dir.d.ts +4 -0
- package/dist/context/map-dir.d.ts.map +1 -0
- package/dist/context/map-dir.js +6 -0
- package/dist/context/map-dir.js.map +1 -0
- package/dist/context/node-file.d.ts +109 -0
- package/dist/context/node-file.d.ts.map +1 -0
- package/dist/context/node-file.js +362 -0
- package/dist/context/node-file.js.map +1 -0
- package/dist/context/price.d.ts +49 -0
- package/dist/context/price.d.ts.map +1 -0
- package/dist/context/price.js +83 -0
- package/dist/context/price.js.map +1 -0
- package/dist/context/savings.d.ts +26 -0
- package/dist/context/savings.d.ts.map +1 -0
- package/dist/context/savings.js +59 -0
- package/dist/context/savings.js.map +1 -0
- package/dist/economy/cli.d.ts +3 -0
- package/dist/economy/cli.d.ts.map +1 -0
- package/dist/economy/cli.js +52 -0
- package/dist/economy/cli.js.map +1 -0
- package/dist/economy/delivery.d.ts +49 -0
- package/dist/economy/delivery.d.ts.map +1 -0
- package/dist/economy/delivery.js +176 -0
- package/dist/economy/delivery.js.map +1 -0
- package/dist/economy/index.d.ts +67 -0
- package/dist/economy/index.d.ts.map +1 -0
- package/dist/economy/index.js +519 -0
- package/dist/economy/index.js.map +1 -0
- package/dist/engine.d.ts +83 -0
- package/dist/engine.d.ts.map +1 -0
- package/dist/engine.js +122 -0
- package/dist/engine.js.map +1 -0
- package/dist/evaluation/index.d.ts +41 -0
- package/dist/evaluation/index.d.ts.map +1 -0
- package/dist/evaluation/index.js +61 -0
- package/dist/evaluation/index.js.map +1 -0
- package/dist/graph/bindings.d.ts +64 -0
- package/dist/graph/bindings.d.ts.map +1 -0
- package/dist/graph/bindings.js +713 -0
- package/dist/graph/bindings.js.map +1 -0
- package/dist/graph/build.d.ts +88 -0
- package/dist/graph/build.d.ts.map +1 -0
- package/dist/graph/build.js +375 -0
- package/dist/graph/build.js.map +1 -0
- package/dist/graph/cards.d.ts +46 -0
- package/dist/graph/cards.d.ts.map +1 -0
- package/dist/graph/cards.js +280 -0
- package/dist/graph/cards.js.map +1 -0
- package/dist/graph/check.d.ts +25 -0
- package/dist/graph/check.d.ts.map +1 -0
- package/dist/graph/check.js +192 -0
- package/dist/graph/check.js.map +1 -0
- package/dist/graph/container.d.ts +63 -0
- package/dist/graph/container.d.ts.map +1 -0
- package/dist/graph/container.js +190 -0
- package/dist/graph/container.js.map +1 -0
- package/dist/graph/enrich.d.ts +62 -0
- package/dist/graph/enrich.d.ts.map +1 -0
- package/dist/graph/enrich.js +253 -0
- package/dist/graph/enrich.js.map +1 -0
- package/dist/graph/extract-cache.d.ts +101 -0
- package/dist/graph/extract-cache.d.ts.map +1 -0
- package/dist/graph/extract-cache.js +199 -0
- package/dist/graph/extract-cache.js.map +1 -0
- package/dist/graph/extract.d.ts +85 -0
- package/dist/graph/extract.d.ts.map +1 -0
- package/dist/graph/extract.js +2376 -0
- package/dist/graph/extract.js.map +1 -0
- package/dist/graph/fingerprint.d.ts +76 -0
- package/dist/graph/fingerprint.d.ts.map +1 -0
- package/dist/graph/fingerprint.js +160 -0
- package/dist/graph/fingerprint.js.map +1 -0
- package/dist/graph/generic.d.ts +74 -0
- package/dist/graph/generic.d.ts.map +1 -0
- package/dist/graph/generic.js +580 -0
- package/dist/graph/generic.js.map +1 -0
- package/dist/graph/invariants.d.ts +33 -0
- package/dist/graph/invariants.d.ts.map +1 -0
- package/dist/graph/invariants.js +52 -0
- package/dist/graph/invariants.js.map +1 -0
- package/dist/graph/load.d.ts +29 -0
- package/dist/graph/load.d.ts.map +1 -0
- package/dist/graph/load.js +97 -0
- package/dist/graph/load.js.map +1 -0
- package/dist/graph/lsp/client.d.ts +43 -0
- package/dist/graph/lsp/client.d.ts.map +1 -0
- package/dist/graph/lsp/client.js +179 -0
- package/dist/graph/lsp/client.js.map +1 -0
- package/dist/graph/lsp/enrich.d.ts +11 -0
- package/dist/graph/lsp/enrich.d.ts.map +1 -0
- package/dist/graph/lsp/enrich.js +155 -0
- package/dist/graph/lsp/enrich.js.map +1 -0
- package/dist/graph/lsp/registry.d.ts +15 -0
- package/dist/graph/lsp/registry.d.ts.map +1 -0
- package/dist/graph/lsp/registry.js +46 -0
- package/dist/graph/lsp/registry.js.map +1 -0
- package/dist/graph/map.d.ts +107 -0
- package/dist/graph/map.d.ts.map +1 -0
- package/dist/graph/map.js +239 -0
- package/dist/graph/map.js.map +1 -0
- package/dist/graph/native.d.ts +38 -0
- package/dist/graph/native.d.ts.map +1 -0
- package/dist/graph/native.js +169 -0
- package/dist/graph/native.js.map +1 -0
- package/dist/graph/queries/c.scm +13 -0
- package/dist/graph/queries/c_sharp.scm +19 -0
- package/dist/graph/queries/clojure.scm +58 -0
- package/dist/graph/queries/cpp.scm +23 -0
- package/dist/graph/queries/dart.scm +42 -0
- package/dist/graph/queries/elixir.scm +54 -0
- package/dist/graph/queries/java.scm +20 -0
- package/dist/graph/queries/kotlin.scm +43 -0
- package/dist/graph/queries/lua.scm +36 -0
- package/dist/graph/queries/nix.scm +32 -0
- package/dist/graph/queries/php.scm +40 -0
- package/dist/graph/queries/ruby.scm +65 -0
- package/dist/graph/queries/rust.scm +41 -0
- package/dist/graph/queries/scala.scm +66 -0
- package/dist/graph/queries/solidity.scm +43 -0
- package/dist/graph/queries/swift.scm +51 -0
- package/dist/graph/refresh.d.ts +49 -0
- package/dist/graph/refresh.d.ts.map +1 -0
- package/dist/graph/refresh.js +255 -0
- package/dist/graph/refresh.js.map +1 -0
- package/dist/graph/relations.d.ts +14 -0
- package/dist/graph/relations.d.ts.map +1 -0
- package/dist/graph/relations.js +8 -0
- package/dist/graph/relations.js.map +1 -0
- package/dist/graph/resolve.d.ts +17 -0
- package/dist/graph/resolve.d.ts.map +1 -0
- package/dist/graph/resolve.js +654 -0
- package/dist/graph/resolve.js.map +1 -0
- package/dist/graph/root.d.ts +11 -0
- package/dist/graph/root.d.ts.map +1 -0
- package/dist/graph/root.js +40 -0
- package/dist/graph/root.js.map +1 -0
- package/dist/graph/scopes.d.ts +42 -0
- package/dist/graph/scopes.d.ts.map +1 -0
- package/dist/graph/scopes.js +342 -0
- package/dist/graph/scopes.js.map +1 -0
- package/dist/graph/seed.d.ts +38 -0
- package/dist/graph/seed.d.ts.map +1 -0
- package/dist/graph/seed.js +226 -0
- package/dist/graph/seed.js.map +1 -0
- package/dist/graph/source-files.d.ts +40 -0
- package/dist/graph/source-files.d.ts.map +1 -0
- package/dist/graph/source-files.js +85 -0
- package/dist/graph/source-files.js.map +1 -0
- package/dist/graph/traverse-cli.d.ts +55 -0
- package/dist/graph/traverse-cli.d.ts.map +1 -0
- package/dist/graph/traverse-cli.js +189 -0
- package/dist/graph/traverse-cli.js.map +1 -0
- package/dist/graph/traverse.d.ts +112 -0
- package/dist/graph/traverse.d.ts.map +1 -0
- package/dist/graph/traverse.js +192 -0
- package/dist/graph/traverse.js.map +1 -0
- package/dist/graph/types.d.ts +78 -0
- package/dist/graph/types.d.ts.map +1 -0
- package/dist/graph/types.js +14 -0
- package/dist/graph/types.js.map +1 -0
- package/dist/graph/workspace-cli.d.ts +48 -0
- package/dist/graph/workspace-cli.d.ts.map +1 -0
- package/dist/graph/workspace-cli.js +102 -0
- package/dist/graph/workspace-cli.js.map +1 -0
- package/dist/graph/workspace.d.ts +135 -0
- package/dist/graph/workspace.d.ts.map +1 -0
- package/dist/graph/workspace.js +598 -0
- package/dist/graph/workspace.js.map +1 -0
- package/dist/graph/write.d.ts +13 -0
- package/dist/graph/write.d.ts.map +1 -0
- package/dist/graph/write.js +86 -0
- package/dist/graph/write.js.map +1 -0
- package/dist/hosts/antigravity.d.ts +8 -0
- package/dist/hosts/antigravity.d.ts.map +1 -0
- package/dist/hosts/antigravity.js +42 -0
- package/dist/hosts/antigravity.js.map +1 -0
- package/dist/hosts/claude-global.d.ts +36 -0
- package/dist/hosts/claude-global.d.ts.map +1 -0
- package/dist/hosts/claude-global.js +153 -0
- package/dist/hosts/claude-global.js.map +1 -0
- package/dist/hosts/codex-hooks.d.ts +11 -0
- package/dist/hosts/codex-hooks.d.ts.map +1 -0
- package/dist/hosts/codex-hooks.js +80 -0
- package/dist/hosts/codex-hooks.js.map +1 -0
- package/dist/hosts/config-write.d.ts +36 -0
- package/dist/hosts/config-write.d.ts.map +1 -0
- package/dist/hosts/config-write.js +64 -0
- package/dist/hosts/config-write.js.map +1 -0
- package/dist/hosts/cursor-hooks.d.ts +21 -0
- package/dist/hosts/cursor-hooks.d.ts.map +1 -0
- package/dist/hosts/cursor-hooks.js +103 -0
- package/dist/hosts/cursor-hooks.js.map +1 -0
- package/dist/hosts/init.d.ts +26 -0
- package/dist/hosts/init.d.ts.map +1 -0
- package/dist/hosts/init.js +82 -0
- package/dist/hosts/init.js.map +1 -0
- package/dist/hosts/install.d.ts +12 -0
- package/dist/hosts/install.d.ts.map +1 -0
- package/dist/hosts/install.js +347 -0
- package/dist/hosts/install.js.map +1 -0
- package/dist/hosts/instructions.d.ts +7 -0
- package/dist/hosts/instructions.d.ts.map +1 -0
- package/dist/hosts/instructions.js +71 -0
- package/dist/hosts/instructions.js.map +1 -0
- package/dist/hosts/investigation-instructions.d.ts +2 -0
- package/dist/hosts/investigation-instructions.d.ts.map +1 -0
- package/dist/hosts/investigation-instructions.js +2 -0
- package/dist/hosts/investigation-instructions.js.map +1 -0
- package/dist/hosts/mcp-config.d.ts +59 -0
- package/dist/hosts/mcp-config.d.ts.map +1 -0
- package/dist/hosts/mcp-config.js +229 -0
- package/dist/hosts/mcp-config.js.map +1 -0
- package/dist/hosts/plan.d.ts +32 -0
- package/dist/hosts/plan.d.ts.map +1 -0
- package/dist/hosts/plan.js +77 -0
- package/dist/hosts/plan.js.map +1 -0
- package/dist/hosts/registry.d.ts +35 -0
- package/dist/hosts/registry.d.ts.map +1 -0
- package/dist/hosts/registry.js +157 -0
- package/dist/hosts/registry.js.map +1 -0
- package/dist/hosts/retract.d.ts +47 -0
- package/dist/hosts/retract.d.ts.map +1 -0
- package/dist/hosts/retract.js +541 -0
- package/dist/hosts/retract.js.map +1 -0
- package/dist/hosts/sections.d.ts +46 -0
- package/dist/hosts/sections.d.ts.map +1 -0
- package/dist/hosts/sections.js +126 -0
- package/dist/hosts/sections.js.map +1 -0
- package/dist/index.d.ts +43 -0
- package/dist/index.d.ts.map +1 -0
- package/dist/index.js +33 -0
- package/dist/index.js.map +1 -0
- package/dist/ingest/fs.d.ts +79 -0
- package/dist/ingest/fs.d.ts.map +1 -0
- package/dist/ingest/fs.js +307 -0
- package/dist/ingest/fs.js.map +1 -0
- package/dist/init-guard.d.ts +11 -0
- package/dist/init-guard.d.ts.map +1 -0
- package/dist/init-guard.js +21 -0
- package/dist/init-guard.js.map +1 -0
- package/dist/investigation/index.d.ts +57 -0
- package/dist/investigation/index.d.ts.map +1 -0
- package/dist/investigation/index.js +315 -0
- package/dist/investigation/index.js.map +1 -0
- package/dist/mcp/compact.d.ts +9 -0
- package/dist/mcp/compact.d.ts.map +1 -0
- package/dist/mcp/compact.js +133 -0
- package/dist/mcp/compact.js.map +1 -0
- package/dist/mcp/instructions.d.ts +5 -0
- package/dist/mcp/instructions.d.ts.map +1 -0
- package/dist/mcp/instructions.js +57 -0
- package/dist/mcp/instructions.js.map +1 -0
- package/dist/mcp/server.d.ts +7 -0
- package/dist/mcp/server.d.ts.map +1 -0
- package/dist/mcp/server.js +128 -0
- package/dist/mcp/server.js.map +1 -0
- package/dist/mcp/tool-names.d.ts +20 -0
- package/dist/mcp/tool-names.d.ts.map +1 -0
- package/dist/mcp/tool-names.js +36 -0
- package/dist/mcp/tool-names.js.map +1 -0
- package/dist/mcp/tools.d.ts +22 -0
- package/dist/mcp/tools.d.ts.map +1 -0
- package/dist/mcp/tools.js +300 -0
- package/dist/mcp/tools.js.map +1 -0
- package/dist/notes/ask-notes.d.ts +8 -0
- package/dist/notes/ask-notes.d.ts.map +1 -0
- package/dist/notes/ask-notes.js +19 -0
- package/dist/notes/ask-notes.js.map +1 -0
- package/dist/notes/branches.d.ts +102 -0
- package/dist/notes/branches.d.ts.map +1 -0
- package/dist/notes/branches.js +304 -0
- package/dist/notes/branches.js.map +1 -0
- package/dist/notes/cold-start.d.ts +177 -0
- package/dist/notes/cold-start.d.ts.map +1 -0
- package/dist/notes/cold-start.js +537 -0
- package/dist/notes/cold-start.js.map +1 -0
- package/dist/notes/edit-overlap.d.ts +62 -0
- package/dist/notes/edit-overlap.d.ts.map +1 -0
- package/dist/notes/edit-overlap.js +202 -0
- package/dist/notes/edit-overlap.js.map +1 -0
- package/dist/notes/git-facts.d.ts +21 -0
- package/dist/notes/git-facts.d.ts.map +1 -0
- package/dist/notes/git-facts.js +121 -0
- package/dist/notes/git-facts.js.map +1 -0
- package/dist/notes/home.d.ts +87 -0
- package/dist/notes/home.d.ts.map +1 -0
- package/dist/notes/home.js +430 -0
- package/dist/notes/home.js.map +1 -0
- package/dist/notes/learning-fields.d.ts +102 -0
- package/dist/notes/learning-fields.d.ts.map +1 -0
- package/dist/notes/learning-fields.js +217 -0
- package/dist/notes/learning-fields.js.map +1 -0
- package/dist/notes/note-gate.d.ts +42 -0
- package/dist/notes/note-gate.d.ts.map +1 -0
- package/dist/notes/note-gate.js +181 -0
- package/dist/notes/note-gate.js.map +1 -0
- package/dist/notes/notes.d.ts +214 -0
- package/dist/notes/notes.d.ts.map +1 -0
- package/dist/notes/notes.js +591 -0
- package/dist/notes/notes.js.map +1 -0
- package/dist/notes/pr-reviews.d.ts +108 -0
- package/dist/notes/pr-reviews.d.ts.map +1 -0
- package/dist/notes/pr-reviews.js +325 -0
- package/dist/notes/pr-reviews.js.map +1 -0
- package/dist/notes/repo-julius.d.ts +18 -0
- package/dist/notes/repo-julius.d.ts.map +1 -0
- package/dist/notes/repo-julius.js +111 -0
- package/dist/notes/repo-julius.js.map +1 -0
- package/dist/notes/session-cost.d.ts +35 -0
- package/dist/notes/session-cost.d.ts.map +1 -0
- package/dist/notes/session-cost.js +276 -0
- package/dist/notes/session-cost.js.map +1 -0
- package/dist/search/grep-cli.d.ts +35 -0
- package/dist/search/grep-cli.d.ts.map +1 -0
- package/dist/search/grep-cli.js +115 -0
- package/dist/search/grep-cli.js.map +1 -0
- package/dist/search/grep.d.ts +60 -0
- package/dist/search/grep.d.ts.map +1 -0
- package/dist/search/grep.js +176 -0
- package/dist/search/grep.js.map +1 -0
- package/dist/search/ignored-code.d.ts +9 -0
- package/dist/search/ignored-code.d.ts.map +1 -0
- package/dist/search/ignored-code.js +73 -0
- package/dist/search/ignored-code.js.map +1 -0
- package/dist/skills/skills.d.ts +118 -0
- package/dist/skills/skills.d.ts.map +1 -0
- package/dist/skills/skills.js +370 -0
- package/dist/skills/skills.js.map +1 -0
- package/dist/telemetry/contract.d.ts +103 -0
- package/dist/telemetry/contract.d.ts.map +1 -0
- package/dist/telemetry/contract.js +270 -0
- package/dist/telemetry/contract.js.map +1 -0
- package/dist/telemetry/flush.d.ts +21 -0
- package/dist/telemetry/flush.d.ts.map +1 -0
- package/dist/telemetry/flush.js +85 -0
- package/dist/telemetry/flush.js.map +1 -0
- package/dist/telemetry/gate.d.ts +30 -0
- package/dist/telemetry/gate.d.ts.map +1 -0
- package/dist/telemetry/gate.js +81 -0
- package/dist/telemetry/gate.js.map +1 -0
- package/dist/telemetry/identity.d.ts +40 -0
- package/dist/telemetry/identity.d.ts.map +1 -0
- package/dist/telemetry/identity.js +80 -0
- package/dist/telemetry/identity.js.map +1 -0
- package/dist/telemetry/index.d.ts +18 -0
- package/dist/telemetry/index.d.ts.map +1 -0
- package/dist/telemetry/index.js +16 -0
- package/dist/telemetry/index.js.map +1 -0
- package/dist/telemetry/key.d.ts +4 -0
- package/dist/telemetry/key.d.ts.map +1 -0
- package/dist/telemetry/key.js +4 -0
- package/dist/telemetry/key.js.map +1 -0
- package/dist/telemetry/notice.d.ts +19 -0
- package/dist/telemetry/notice.d.ts.map +1 -0
- package/dist/telemetry/notice.js +93 -0
- package/dist/telemetry/notice.js.map +1 -0
- package/dist/telemetry/queue.d.ts +35 -0
- package/dist/telemetry/queue.d.ts.map +1 -0
- package/dist/telemetry/queue.js +162 -0
- package/dist/telemetry/queue.js.map +1 -0
- package/dist/telemetry/send.d.ts +19 -0
- package/dist/telemetry/send.d.ts.map +1 -0
- package/dist/telemetry/send.js +84 -0
- package/dist/telemetry/send.js.map +1 -0
- package/dist/telemetry/sessions.d.ts +25 -0
- package/dist/telemetry/sessions.d.ts.map +1 -0
- package/dist/telemetry/sessions.js +104 -0
- package/dist/telemetry/sessions.js.map +1 -0
- package/dist/telemetry/track.d.ts +62 -0
- package/dist/telemetry/track.d.ts.map +1 -0
- package/dist/telemetry/track.js +142 -0
- package/dist/telemetry/track.js.map +1 -0
- package/dist/upkeep-run.d.ts +15 -0
- package/dist/upkeep-run.d.ts.map +1 -0
- package/dist/upkeep-run.js +71 -0
- package/dist/upkeep-run.js.map +1 -0
- package/dist/upkeep.d.ts +125 -0
- package/dist/upkeep.d.ts.map +1 -0
- package/dist/upkeep.js +255 -0
- package/dist/upkeep.js.map +1 -0
- package/dist/util/browser.d.ts +3 -0
- package/dist/util/browser.d.ts.map +1 -0
- package/dist/util/browser.js +14 -0
- package/dist/util/browser.js.map +1 -0
- package/dist/util/front-matter.d.ts +19 -0
- package/dist/util/front-matter.d.ts.map +1 -0
- package/dist/util/front-matter.js +21 -0
- package/dist/util/front-matter.js.map +1 -0
- package/dist/util/id.d.ts +7 -0
- package/dist/util/id.d.ts.map +1 -0
- package/dist/util/id.js +14 -0
- package/dist/util/id.js.map +1 -0
- package/dist/util/paths.d.ts +29 -0
- package/dist/util/paths.d.ts.map +1 -0
- package/dist/util/paths.js +71 -0
- package/dist/util/paths.js.map +1 -0
- package/dist/util/source.d.ts +4 -0
- package/dist/util/source.d.ts.map +1 -0
- package/dist/util/source.js +12 -0
- package/dist/util/source.js.map +1 -0
- package/dist/util/spinner.d.ts +15 -0
- package/dist/util/spinner.d.ts.map +1 -0
- package/dist/util/spinner.js +52 -0
- package/dist/util/spinner.js.map +1 -0
- package/dist/util/state.d.ts +100 -0
- package/dist/util/state.d.ts.map +1 -0
- package/dist/util/state.js +186 -0
- package/dist/util/state.js.map +1 -0
- package/dist/viewer/app.js +2 -0
- package/dist/viewer/index.html +49 -0
- package/dist/viewer/style.css +154 -0
- package/dist/viz/assemble.d.ts +83 -0
- package/dist/viz/assemble.d.ts.map +1 -0
- package/dist/viz/assemble.js +101 -0
- package/dist/viz/assemble.js.map +1 -0
- package/dist/viz/export.d.ts +39 -0
- package/dist/viz/export.d.ts.map +1 -0
- package/dist/viz/export.js +98 -0
- package/dist/viz/export.js.map +1 -0
- package/dist/viz/serve.d.ts +12 -0
- package/dist/viz/serve.d.ts.map +1 -0
- package/dist/viz/serve.js +129 -0
- package/dist/viz/serve.js.map +1 -0
- package/docs/assets/context-benchmark.svg +31 -0
- package/docs/assets/julius-hero.png +0 -0
- package/docs/upstream-changelog.md +785 -0
- package/package.json +138 -4
|
@@ -0,0 +1,785 @@
|
|
|
1
|
+
# Changelog
|
|
2
|
+
|
|
3
|
+
## 0.23.1
|
|
4
|
+
|
|
5
|
+
### Fixed
|
|
6
|
+
|
|
7
|
+
- **Learnings reach Claude when it opens the file they're about** (#642). When
|
|
8
|
+
Claude reads or edits a file, it gets the learnings whose `touches` name that
|
|
9
|
+
file, at most two, once a session, without calling trail first.
|
|
10
|
+
- **A learning's `touches` come from what the session did**: files edited, then
|
|
11
|
+
files named in the learning, then files read. They no longer list whatever
|
|
12
|
+
untracked files sat in the repo.
|
|
13
|
+
- **An empty `trail grep` names the git-ignored code it didn't search.**
|
|
14
|
+
- **Exploratory turns are asked for a learning too**, when trail's answers
|
|
15
|
+
saved 30k+ tokens of reading.
|
|
16
|
+
- **`trail init` refuses your home folder**, and outside git it says the
|
|
17
|
+
learnings stay on this machine.
|
|
18
|
+
- **The shared hook reads single-quoted learning titles** (#626), as Prettier
|
|
19
|
+
writes them, so teammates without trail see clean titles. `.trail/hook.cjs`
|
|
20
|
+
is updated at the next session; commit it once.
|
|
21
|
+
|
|
22
|
+
## 0.23.0
|
|
23
|
+
|
|
24
|
+
### Changed
|
|
25
|
+
|
|
26
|
+
- **One shared folder** (#619): `trail init` now shares `.trail/hook.cjs` and
|
|
27
|
+
one SessionStart line in `.claude/settings.json`. Everything else is
|
|
28
|
+
personal: `.claude/settings.local.json`, and the skill in `~/.claude`. Repos
|
|
29
|
+
set up the old way move over by themselves at the next session; commit
|
|
30
|
+
`.trail/` and `.claude/settings.json` once after that.
|
|
31
|
+
- **The code map lives in `.trail/cache/`** in a repo on trail, kept out of git
|
|
32
|
+
by `.trail/.gitignore`. An existing `graft/` map is moved there, not rebuilt.
|
|
33
|
+
- **No MCP server for Claude Code.** init stops adding it and removes the one
|
|
34
|
+
an older init added. Cursor keeps its server.
|
|
35
|
+
- **Overlap shows up after an edit, per function** (#617): a teammate's open
|
|
36
|
+
branch is mentioned only when you both change the same function, and merged
|
|
37
|
+
or closed branches no longer count.
|
|
38
|
+
- **A learning's cost counts from where its work began** (#620), not from the
|
|
39
|
+
start of a long session.
|
|
40
|
+
|
|
41
|
+
### Fixed
|
|
42
|
+
|
|
43
|
+
- A fresh `trail init` no longer leaves an untracked `graft/` folder behind.
|
|
44
|
+
|
|
45
|
+
## 0.22.1
|
|
46
|
+
|
|
47
|
+
### Added
|
|
48
|
+
|
|
49
|
+
- **Teammates without trail still get the learnings** (#611): in a repo with
|
|
50
|
+
committed `.trail/`, Claude reads the newest learnings, credits the one it
|
|
51
|
+
used, and then offers once to install trail.
|
|
52
|
+
- **`trail init` lets you tick which learnings to keep**, and says how many
|
|
53
|
+
sessions each one came from.
|
|
54
|
+
- **`trail init` learns from PR review comments**: things reviewers flagged on
|
|
55
|
+
2 or more of the last 50 merged PRs become team learnings.
|
|
56
|
+
- **`trail check` flags edits to a teammate's learning.**
|
|
57
|
+
|
|
58
|
+
### Fixed
|
|
59
|
+
|
|
60
|
+
- **`trail init` finds Claude Code installed only as a VS Code or Cursor
|
|
61
|
+
extension**, so it no longer skips past sessions without a word. Run
|
|
62
|
+
`trail init` again to get the learnings it missed.
|
|
63
|
+
|
|
64
|
+
### Removed
|
|
65
|
+
|
|
66
|
+
- The GitHub App's brain build (#613).
|
|
67
|
+
|
|
68
|
+
## 0.22.0
|
|
69
|
+
|
|
70
|
+
graft is now **Trail-code**. The same build ships as two packages:
|
|
71
|
+
`@trailhq/trail-code` (the `trail` command) and `@nanonets/graft` (the `graft`
|
|
72
|
+
command, unchanged). Both keep getting every release.
|
|
73
|
+
|
|
74
|
+
### Added
|
|
75
|
+
|
|
76
|
+
- **`npm install -g @trailhq/trail-code`** gives you the `trail` command: the
|
|
77
|
+
code map plus learnings your team shares in `.trail/`.
|
|
78
|
+
- **`graft upgrade` adds `trail` alongside graft**, and the next Claude Code
|
|
79
|
+
session in a graft-wired repo moves it to trail by itself.
|
|
80
|
+
- **The agent passes the news on**: on a machine with graft and no trail,
|
|
81
|
+
Claude Code is told once a week to mention that `graft upgrade` adds trail.
|
|
82
|
+
|
|
83
|
+
### Fixed
|
|
84
|
+
|
|
85
|
+
- **Each Claude Code hook answers once**, not from both the repo's and
|
|
86
|
+
`~/.claude`'s copies, so learnings no longer arrive twice per prompt.
|
|
87
|
+
- **Hook shims find `@trailhq/trail-code`**, and `trail` warns in a repo whose
|
|
88
|
+
older graft hooks can't reach it.
|
|
89
|
+
- **No crash on npm 12**, which skips the grammars' install scripts: grammars
|
|
90
|
+
load per language and fall back to WASM.
|
|
91
|
+
- The package points at `github.com/trailhq/Trail-Code`.
|
|
92
|
+
|
|
93
|
+
## 0.19.0
|
|
94
|
+
|
|
95
|
+
### Added
|
|
96
|
+
|
|
97
|
+
- **Push a repo's brain from the terminal** (#422): a loopback handoff hands the
|
|
98
|
+
browser a finished brain instead of a half-built one — the push waits for the
|
|
99
|
+
build, then lands the browser on the result.
|
|
100
|
+
- **A public repo can be read without installing the App** (#349): access is
|
|
101
|
+
answered on its own, without first reading the repo.
|
|
102
|
+
|
|
103
|
+
### Fixed
|
|
104
|
+
|
|
105
|
+
- **The finished push lands in Trail** (#417), not on a local page, and signup
|
|
106
|
+
goes to Trail's own front end rather than the shared agents host.
|
|
107
|
+
- **A repo read runs in a child process** so the app keeps answering while it
|
|
108
|
+
works, and the digest finishes sending before the child disconnects.
|
|
109
|
+
- **Public reads borrow an installation token** instead of falling back to the
|
|
110
|
+
anonymous rate limit.
|
|
111
|
+
|
|
112
|
+
## 0.18.0
|
|
113
|
+
|
|
114
|
+
### Added
|
|
115
|
+
|
|
116
|
+
- **Trail Brain integration** (#322): graft can build a *brain* from a repo and
|
|
117
|
+
carry its rules into every `ask` — a two-way link, so retrieval is shaped by
|
|
118
|
+
the team context a brain accumulates, not the code graph alone.
|
|
119
|
+
- **A brain verifies the checkout before it mines** (#344): graft checks the
|
|
120
|
+
working copy against the repo a brain expects, so rules are never mined from
|
|
121
|
+
the wrong tree.
|
|
122
|
+
|
|
123
|
+
### Fixed
|
|
124
|
+
|
|
125
|
+
- **A brain refreshes its rules from upkeep** (#343), so a single empty pull no
|
|
126
|
+
longer leaves it stuck without rules.
|
|
127
|
+
|
|
128
|
+
## 0.17.0
|
|
129
|
+
|
|
130
|
+
### Added
|
|
131
|
+
|
|
132
|
+
- **Claude Code sessions now report the dollar value of what graft saved** (#282),
|
|
133
|
+
not just the token count — the running total on the statusline is priced, so
|
|
134
|
+
the payoff of routing a lookup through the graph instead of reading files whole
|
|
135
|
+
is visible in the terminal.
|
|
136
|
+
- **`graft init` also writes the Claude Code wiring into `~`** (#276), so
|
|
137
|
+
worktrees and fresh shells created off the same home keep graft available
|
|
138
|
+
instead of losing the hooks and statusline the moment you leave the repo root.
|
|
139
|
+
|
|
140
|
+
### Fixed
|
|
141
|
+
|
|
142
|
+
- The **PR-review GitHub App** keeps its review pages on disk (#278) so posted
|
|
143
|
+
links survive a restart, reviews **merged and closed PRs** via the head ref
|
|
144
|
+
diffed against the merge base (#279, #280) so a merged PR keeps a working graph
|
|
145
|
+
link, and **runs each review in its own process** (#281) so one slow review no
|
|
146
|
+
longer blocks the server.
|
|
147
|
+
- **Green main** (#277): the telemetry test clears every CI environment variable
|
|
148
|
+
before asserting, and the CodeQL action pins are realigned.
|
|
149
|
+
|
|
150
|
+
## 0.16.0
|
|
151
|
+
|
|
152
|
+
### Added
|
|
153
|
+
|
|
154
|
+
- **`graft init --no-statusline`** (and `GRAFT_NO_STATUSLINE=1`) skips writing
|
|
155
|
+
Claude Code's `statusLine` / `subagentStatusLine`. A custom bar — in the
|
|
156
|
+
project's `.claude/settings.json` or in `~/.claude/settings.json` — stays in
|
|
157
|
+
front: a project-level field would otherwise hide the user-level one. The
|
|
158
|
+
choice is recorded in the wiring stamp, so a later session refresh cannot
|
|
159
|
+
put Graft's bar back. Graft still recognises its own helper
|
|
160
|
+
(`graft-statusline.cjs`) and will update that command on re-init.
|
|
161
|
+
|
|
162
|
+
## 0.15.0
|
|
163
|
+
|
|
164
|
+
### Added
|
|
165
|
+
|
|
166
|
+
- **Swift gets full-fidelity (depth-tier) extraction**, promoted from the
|
|
167
|
+
breadth tier the same way Kotlin was (#130) — whose swift tags query had no
|
|
168
|
+
call captures at all, so Swift repos indexed symbols with zero wiring.
|
|
169
|
+
`tree-sitter-swift` (native, `^0.7.1` — the first release whose install
|
|
170
|
+
compiles the shipped parser instead of regenerating it, which broke under
|
|
171
|
+
npm's hoisting; a root `overrides` entry pins its `tree-sitter` peer for dev
|
|
172
|
+
installs) parses `.swift`. One `class_declaration` node covers `class` /
|
|
173
|
+
`struct` / `enum` / `actor` / `extension`, told apart by their own keyword:
|
|
174
|
+
class and actor → `class`, struct → `struct`, enum → `enum`, `protocol` →
|
|
175
|
+
`interface`, `typealias` → `type`, top-level `let`/`var` → `variable`. An
|
|
176
|
+
`extension Point` node takes the extended type's own name, so its members
|
|
177
|
+
mint as Point methods and member calls on a Point receiver resolve to them.
|
|
178
|
+
The extension node itself is kind `module`, not a second same-named class —
|
|
179
|
+
otherwise every `Point()` call and `: Point` heritage target would go
|
|
180
|
+
ambiguous and drop. `init` becomes a method named after its type (like a
|
|
181
|
+
Java constructor); `func` is a method inside any type and a function
|
|
182
|
+
elsewhere. Calls resolve via `call_expression` with `navigation_expression`
|
|
183
|
+
/ `self` / `super` receivers. A bare lowercase call inside a type body is
|
|
184
|
+
ONE edge carrying both of its readings in Swift's own inner-scope-first
|
|
185
|
+
order: the member reading first (owner-qualified index + the in-repo
|
|
186
|
+
ancestor chain — a stdlib call like `contains` inside `extension Set`
|
|
187
|
+
drops instead of binding to an unrelated type's only same-named method, a
|
|
188
|
+
false positive dogfooding on swift-composable-architecture caught), then
|
|
189
|
+
the free-function reading only when no member exists on the chain — so a
|
|
190
|
+
name defined as both yields the member edge alone, as Swift dispatches it.
|
|
191
|
+
`super.method()` resolves against the declaration's own superclass (the
|
|
192
|
+
first `:` entry, which Swift's grammar puts before any protocol), climbing
|
|
193
|
+
past the current class's override. Overloads disambiguate by declared
|
|
194
|
+
arity vs call-site argument count (Java's exact mechanism — defaults and
|
|
195
|
+
variadics make the arity a minimum); an overload set arity can't split
|
|
196
|
+
(`save(Int)` vs `save(String)`) DROPS rather than taking the same-file
|
|
197
|
+
tiebreak, which would stamp whichever overload appears first `extracted`.
|
|
198
|
+
An initializer call (`Animal(legs: 4)` — an ordinary call node, no `new`)
|
|
199
|
+
falls back to class/struct/enum targets once functions find nothing,
|
|
200
|
+
Python's constructor-fallback shape. The `:` inheritance clause yields `extends`
|
|
201
|
+
edges (bare names — Swift can't say syntactically which specifier is the
|
|
202
|
+
superclass), `import` declarations yield module-path import edges, and
|
|
203
|
+
visibility maps to `exported` as only `private`/`fileprivate` hidden —
|
|
204
|
+
Swift's default `internal` is module-wide, which for a one-module repo is
|
|
205
|
+
the API surface. A Swift bindings collector types receivers from the
|
|
206
|
+
confident, syntax-local clues: typed parameters (`func feed(animal:
|
|
207
|
+
Animal)`, argument labels handled), typed properties, initializer-call
|
|
208
|
+
assignments (`let vet = Vet()` — UpperCamelCase callee, the same convention
|
|
209
|
+
trust as Go's `NewX`), and fields bound both bare and `self.`-prefixed —
|
|
210
|
+
so `vet.check()`, `keeper.wave()`, `self.repo.save()`, and type-member
|
|
211
|
+
calls (`Animal.census()`) all resolve through the owner-qualified method
|
|
212
|
+
index. A receiver with no local clue (a chained call's result) stays
|
|
213
|
+
unresolved rather than guessed.
|
|
214
|
+
### Fixed
|
|
215
|
+
|
|
216
|
+
- **`allowScripts` now names R by the identity npm actually matches on.** The
|
|
217
|
+
entry was `tree-sitter-r@1.3.0`, the alias in `dependencies`, but npm derives
|
|
218
|
+
the identity from the resolved package in the lockfile —
|
|
219
|
+
`@davisvaughan/tree-sitter-r@1.3.0`. The old key matched nothing, so the
|
|
220
|
+
grammar's install script counted as unreviewed and was blocked;
|
|
221
|
+
`npm ci --strict-allow-scripts` failed on it. Harmless in practice only
|
|
222
|
+
because the package ships prebuilds for every supported platform. Note the
|
|
223
|
+
`overrides` key must stay the alias — the two fields key differently.
|
|
224
|
+
- **`graft check` no longer reports every container-tier node as `removed`.**
|
|
225
|
+
`checkGraph` branched on the depth and breadth tiers but never on the container
|
|
226
|
+
tier the build uses for `.vue`, so `genericLangOf` returned null, a `generic!`
|
|
227
|
+
assertion threw, and the catch swallowed it as a parse failure — every `.vue`
|
|
228
|
+
node fell through to `removed` on a clean build, and the `graft build` the
|
|
229
|
+
check told you to run had already written them. The check now mirrors the
|
|
230
|
+
build's three-way branch, warms the container grammars alongside the generic
|
|
231
|
+
ones, and treats "no tier claims this file" as an explicit case rather than a
|
|
232
|
+
non-null assertion, so the next tier added fails in the type checker instead of
|
|
233
|
+
silently reporting drift. ([#236](https://github.com/trailhq/Graft/issues/236))
|
|
234
|
+
|
|
235
|
+
### Added
|
|
236
|
+
|
|
237
|
+
- **Telemetry can now tell "graft saved tokens" apart from "the user was told".**
|
|
238
|
+
`saved_tokens_bucket` counted what graft *computed* — every
|
|
239
|
+
`[graft] tokens saved ≈ N` footer the PostToolUse accumulator swept up — so a
|
|
240
|
+
turn that saved 20,000 tokens in silence and a turn that saved nothing were the
|
|
241
|
+
same number. `session_summary` now also carries `graft_turns_bucket` and
|
|
242
|
+
`reported_turns_bucket`: of the turns that used graft, how many closed with the
|
|
243
|
+
one-line tally `SKILL.md` and `SAVINGS_TURN_NUDGE` both ask for.
|
|
244
|
+
|
|
245
|
+
The agent's own prose lives in one place a hook can reach, so at the end of a
|
|
246
|
+
turn that used graft the Stop hook reads the tail of the host transcript named
|
|
247
|
+
on its stdin and checks the reply for a "graft saved ~N tokens" line. Only a
|
|
248
|
+
count of turns is kept, and only as a bucket — no reply, no fragment, not even a
|
|
249
|
+
length. `TELEMETRY.md` documents the local read in full.
|
|
250
|
+
|
|
251
|
+
A turn that can't be checked — a host whose Stop hook names no transcript, an
|
|
252
|
+
unreadable file, a Stop racing the transcript write — is counted in *neither*
|
|
253
|
+
total, so the ratio means "of the turns we could read" rather than deflating to
|
|
254
|
+
zero on every editor but Claude Code. One reply is one turn however often Stop
|
|
255
|
+
fires, guarded by the id of the last reply examined.
|
|
256
|
+
|
|
257
|
+
- **`scripts/tally-audit.mjs`**, the same ratio offline and at full resolution:
|
|
258
|
+
which turns were silent, whether the number the agent reported matched graft's
|
|
259
|
+
own footers, and whether it named the call count. Run it when the aggregate says
|
|
260
|
+
something surprising. It also flags per-turn savings estimates large enough to be
|
|
261
|
+
artifacts rather than savings.
|
|
262
|
+
|
|
263
|
+
|
|
264
|
+
- **`graft init` converges instead of accumulating, and `graft uninstall` removes
|
|
265
|
+
graft entirely.** `init` wrote the files the selected agents needed and never
|
|
266
|
+
looked at the rest, so a repo wired by an older version — or by the same version
|
|
267
|
+
with different `--agents` — kept that run's files forever, and the session-start
|
|
268
|
+
refresh then kept them *up to date*. `init` now retracts every agent it isn't
|
|
269
|
+
about to write, and `graft uninstall` retracts the lot.
|
|
270
|
+
|
|
271
|
+
Only graft's own contribution is touched: inside a shared file just the
|
|
272
|
+
marker-fenced block, inside a config just the `graft` key — foreign MCP servers,
|
|
273
|
+
hooks, statuslines and ignore entries survive byte for byte. A file left holding
|
|
274
|
+
nothing is deleted rather than truncated to an empty shell, and the directories
|
|
275
|
+
that empties are pruned. An unparseable config is reported and left alone.
|
|
276
|
+
`uninstall` is dry-run until `-y`.
|
|
277
|
+
|
|
278
|
+
The target list is derived from the same registries `init` writes through, so a
|
|
279
|
+
host added later is retractable for free; only a host *removed* from the registry
|
|
280
|
+
needs a hand-written entry, and `LEGACY_TARGETS` says so. Exclusion is by path as
|
|
281
|
+
well as by host id: three hosts write `AGENTS.md`, and keeping any one of them has
|
|
282
|
+
to spare that block.
|
|
283
|
+
|
|
284
|
+
### Fixed
|
|
285
|
+
|
|
286
|
+
- **A stale `[mcp_servers.graft]` is now replaced instead of skipped.** The TOML
|
|
287
|
+
writer returned early the moment the header existed, which froze the launch
|
|
288
|
+
command at whatever the first `init` wrote — a repo wired when graft wasn't on
|
|
289
|
+
`PATH` kept the slow `npx` form forever, and no upgrade could correct it. Codex
|
|
290
|
+
and Grok both went through that path. Foreign tables are untouched either way.
|
|
291
|
+
|
|
292
|
+
- **`.claude/settings.json` no longer accumulates graft's own entries.** The
|
|
293
|
+
allowlist and `footerLinksRegexes` were append-only, so a renamed invocation form
|
|
294
|
+
stayed in the user's settings beside its replacement with nothing able to remove
|
|
295
|
+
it. Both now drop graft's prior entries before adding the current set, the same
|
|
296
|
+
way the hooks merge already did. Scoped to the forms graft is actually invoked as,
|
|
297
|
+
so a hand-written `Bash(graft-mytool:*)` survives.
|
|
298
|
+
|
|
299
|
+
- **`graft blast` suggests who to tag.** The comment already named the areas a
|
|
300
|
+
diff changes and the areas it can affect; it now names the people behind them,
|
|
301
|
+
read from git history with no API call and no config file. One `git log` per
|
|
302
|
+
area over that area's own files, weighted towards recent work (120-day
|
|
303
|
+
half-life), with areas the diff only *reaches* counted at 0.6 against a changed
|
|
304
|
+
area's 1.0 — the person whose code your change can break is exactly the
|
|
305
|
+
reviewer the diff alone would never surface. The markdown report gains a `Tag:`
|
|
306
|
+
line under the tests line and a collapsed `Who knows this code` table; the
|
|
307
|
+
exported page gains initials badges on each bubble, a *Who knows this* block in
|
|
308
|
+
the detail panel, and a `people` legend toggle.
|
|
309
|
+
|
|
310
|
+
A handle is never guessed: only a GitHub noreply commit address resolves to
|
|
311
|
+
`@mention`, and anyone else is printed as a plain unlinked name, because a
|
|
312
|
+
guessed mention pings a stranger. A repo can fix that for good with a
|
|
313
|
+
`.mailmap` entry, which git applies to the names `blast` reads. Merge commits,
|
|
314
|
+
bots, everyone who authored a commit in the diff range, and — for a local run
|
|
315
|
+
with no `--base` — your own git identity are all excluded. `--no-owners` turns
|
|
316
|
+
the layer off; `--pr-author <who...>` takes logins, names or emails; the
|
|
317
|
+
bundled action gains a `suggest-reviewers` input, defaulting true.
|
|
318
|
+
|
|
319
|
+
## 0.13.0
|
|
320
|
+
|
|
321
|
+
### Added
|
|
322
|
+
|
|
323
|
+
- **Grok (xAI) is a first-class `graft init` host.** Detects `~/.grok` or a
|
|
324
|
+
repo `.grok/` and writes `.grok/skills/graft/SKILL.md` plus a repo-level
|
|
325
|
+
`[mcp_servers.graft]` block in `.grok/config.toml` (Grok's MCP config).
|
|
326
|
+
Select it with `graft init --agents grok`.
|
|
327
|
+
- **R language support.** `tree-sitter-r` (`npm:@davisvaughan/tree-sitter-r`;
|
|
328
|
+
the unscoped npm name is a squatted placeholder) parses `.R`/`.r` files.
|
|
329
|
+
Plain functions: every `name <- function(...)` / `name = function(...)` /
|
|
330
|
+
`function(...) -> name` assignment becomes a `function` node (the grammar's
|
|
331
|
+
`function_definition` has no name field, so the name comes from the
|
|
332
|
+
enclosing assignment; right-assign has its own AST shape). Classes — R's
|
|
333
|
+
class systems are library convention, not syntax, so they are recognised by
|
|
334
|
+
call idiom: **R6** (`R6::R6Class(...)` — the class node, `public =`/
|
|
335
|
+
`private =`/`active =` entries as methods, `inherit =` heritage, and `self$`/
|
|
336
|
+
`private$`/`super$` calls resolving to the class or its parent), **S4**
|
|
337
|
+
(`setClass()`/`setMethod()` with `contains =` heritage), **S3**
|
|
338
|
+
(`generic.Class <- function()` only when `generic` is registered locally via
|
|
339
|
+
`UseMethod()` or is one of a small curated base-R set — false negatives over
|
|
340
|
+
false positives), and plain-list mixin bundles (`Foo <- list(public =
|
|
341
|
+
list(...), ...)`) that are spliced across classes instead of inherited. An
|
|
342
|
+
untyped `obj$method()` resolves by bare name to a uniquely-named method
|
|
343
|
+
(ambiguous drops). Visibility: a roxygen `#' @export` tag wins; a roxygen
|
|
344
|
+
block without it means "not exported"; no roxygen falls back to the
|
|
345
|
+
leading-dot convention; R6 `private =` members are unexported.
|
|
346
|
+
`library()`/`require()`/`source()` calls are the import edges. Known gaps:
|
|
347
|
+
S3 generics registered in another file aren't seen (per-file pass); S4
|
|
348
|
+
`signature()` multiple dispatch isn't handled; R6 active bindings are
|
|
349
|
+
ordinary methods.
|
|
350
|
+
- **Resumable `graft build --deep`.** The concept phase now checkpoints
|
|
351
|
+
summaries to disk atomically as it runs, so a build interrupted by a session
|
|
352
|
+
or rate limit resumes where it stopped on the next run (content-hash cached,
|
|
353
|
+
no repeated LLM cost) instead of restarting from zero.
|
|
354
|
+
- **Kotlin gets full-fidelity (depth-tier) extraction**, and **Lua** and **Nix**
|
|
355
|
+
join the breadth tier. **Dart** now indexes top-level functions and consts.
|
|
356
|
+
- **Hermes Agent** is a first-class `graft init` host.
|
|
357
|
+
- **Every reported edge quotes the source line** where the call or reference
|
|
358
|
+
happens, in the PR comment, the CLI, and one shared helper.
|
|
359
|
+
|
|
360
|
+
### Fixed
|
|
361
|
+
|
|
362
|
+
- **PHP.** Enums with array consts stay in the graph; trait-inherited method
|
|
363
|
+
calls (`$this->traitMethod()`) resolve through the `implements` edge;
|
|
364
|
+
attribute usage is wired as `references` edges; anonymous classes are minted
|
|
365
|
+
as nodes with their `implements` edges.
|
|
366
|
+
- **Java.** Generic type arguments (`Base<Item>`) no longer become bogus
|
|
367
|
+
`extends`/`implements` edges or poison call resolution; anonymous-class
|
|
368
|
+
methods no longer take the enclosing type's owner, so calls resolve to the
|
|
369
|
+
real method.
|
|
370
|
+
- **Python.** Constructor calls (`Foo()`) resolve to the class instead of being
|
|
371
|
+
dropped.
|
|
372
|
+
- **Deep tier.** An empty meaning reply is no longer cached as a permanent
|
|
373
|
+
`pending` state, and per-file failures surface instead of the build exiting
|
|
374
|
+
successfully.
|
|
375
|
+
- **`graft ask`.** Distinct files are ranked ahead of one file's sibling spans
|
|
376
|
+
under bounded output, and multi-scope workspaces score comparably across
|
|
377
|
+
scopes.
|
|
378
|
+
- **Claude hooks, sync-run, and statusline respect `GRAFT_DIR`**, and the hook
|
|
379
|
+
timeout is also read from user-level settings.
|
|
380
|
+
- **Ingest** skips the `_build/` directory (the underscore spelling of a build
|
|
381
|
+
tree).
|
|
382
|
+
|
|
383
|
+
## 0.12.0
|
|
384
|
+
|
|
385
|
+
### Added
|
|
386
|
+
|
|
387
|
+
- **Kotlin moves to full-fidelity extraction.** `.kt` and `.kts` files are now
|
|
388
|
+
parsed by a hand-written tree-sitter extractor — the same tier as TypeScript,
|
|
389
|
+
Python, Go, and Java — instead of the generic breadth grammar, so Kotlin
|
|
390
|
+
symbols, call edges, heritage, and imports resolve with scope awareness. The
|
|
391
|
+
kind mapping now matches tree-sitter-kotlin's real node types (the earlier
|
|
392
|
+
attempt reused Java's, which do not exist in the Kotlin grammar and emitted no
|
|
393
|
+
symbols at all): `class_declaration` is re-read off its own keyword into
|
|
394
|
+
class / interface / enum / annotation, `object` and `companion object` become
|
|
395
|
+
classes, secondary constructors and member functions become methods,
|
|
396
|
+
`typealias` becomes a type, and top-level `val`/`var` become variables.
|
|
397
|
+
- **Kotlin edges.** Calls resolve through `call_expression` (member calls via
|
|
398
|
+
`navigation_expression`, with `this`/`super` receivers), the `:` heritage
|
|
399
|
+
clause yields `extends` edges, `import_header` yields import edges, and
|
|
400
|
+
`internal`/`private`/`protected` visibility maps to the exported flag.
|
|
401
|
+
### Changed
|
|
402
|
+
|
|
403
|
+
- **graft now collects anonymous usage stats, and the README no longer says it
|
|
404
|
+
doesn't.** We had no way to tell whether a repo ever got past `graft build`,
|
|
405
|
+
or whether an agent reaches for graft over grep once it has — npm downloads
|
|
406
|
+
answer neither. Six events, all buckets and fixed enums: `first_run`,
|
|
407
|
+
`init_completed`, `build_completed`, `build_failed`, `query`,
|
|
408
|
+
`session_summary`. Never your code, file paths, repo name, symbols, queries,
|
|
409
|
+
prompts, or error messages — [`TELEMETRY.md`](TELEMETRY.md) is the complete
|
|
410
|
+
contract and `src/telemetry/contract.ts` enforces it as a hard allowlist, so
|
|
411
|
+
a property that is not in the document cannot be sent even by accident.
|
|
412
|
+
|
|
413
|
+
Identity is two random UUIDs (one per machine, one per checkout), derived from
|
|
414
|
+
nothing; events are anonymous in PostHog with no person profile. Nothing is
|
|
415
|
+
sent from a command you run — events queue locally and a detached process
|
|
416
|
+
posts them at most once a day, so no query ever waits on the network.
|
|
417
|
+
|
|
418
|
+
Off if you uncheck the box in `graft init`, run `graft telemetry disable`, set
|
|
419
|
+
`DO_NOT_TRACK`, are in CI, or built from source (the key is stamped in only at
|
|
420
|
+
publish time, so forks never send). `graft telemetry debug` prints the exact
|
|
421
|
+
batch your machine would send, and sends nothing.
|
|
422
|
+
|
|
423
|
+
## 0.11.0
|
|
424
|
+
|
|
425
|
+
### Fixed
|
|
426
|
+
|
|
427
|
+
- **Node 24 no longer aborts breadth-tier builds with `Fatal process out of
|
|
428
|
+
memory: Zone`.** The broader `tree-sitter-wasm` grammar bundle avoids the V8
|
|
429
|
+
Turboshaft failure triggered by the previous bundle. CI now exercises every
|
|
430
|
+
breadth grammar under Node 24 to keep that runtime compatibility pinned
|
|
431
|
+
([#122]).
|
|
432
|
+
- **`npm install -g @nanonets/graft@latest` could silently do nothing.** The
|
|
433
|
+
generated shims (`.claude/helpers/graft-*.cjs`, and Codex's
|
|
434
|
+
`~/.codex/hooks/graft/`) locate the installed package at runtime from four
|
|
435
|
+
candidates, and took the *first* one that existed. The first is the absolute
|
|
436
|
+
`dist/claude` path graft happened to be running from when `graft init` ran, so
|
|
437
|
+
switching Node versions (nvm/volta) or moving the install left that directory
|
|
438
|
+
on disk — still first, still winning — and the upgrade replaced a directory
|
|
439
|
+
the shim never looked at. The upgrade appeared to succeed and changed nothing.
|
|
440
|
+
The shims now read each candidate's `package.json` and load the
|
|
441
|
+
**highest-versioned** one. The `npm root -g` subprocess is still reached only
|
|
442
|
+
when all three cheap candidates miss, so hook latency is unchanged.
|
|
443
|
+
|
|
444
|
+
### Added
|
|
445
|
+
|
|
446
|
+
- **The wiring now follows the binary.** `graft init` writes files *into* a repo
|
|
447
|
+
(hooks, shims, skill, rule files) and into `~/.codex`; upgrading the npm
|
|
448
|
+
package replaced the binary and touched none of them, so a repo wired by 0.7
|
|
449
|
+
kept 0.7's prompts and 0.7's hook timeouts indefinitely — and nothing
|
|
450
|
+
agent-facing ever mentions `graft init`, so no agent would think to re-run it.
|
|
451
|
+
`graft init` now records a stamp (version, hosts, flags) in
|
|
452
|
+
`graft/.cache/wiring-stamp.json`; every entry point compares it against the
|
|
453
|
+
running binary and re-runs the writes on a mismatch. Hosts come from the union
|
|
454
|
+
of the stamp and what's on disk, so a rule file that went missing is restored
|
|
455
|
+
rather than dropped from all future refreshes. The init flags are replayed, so
|
|
456
|
+
a repo wired with `--no-global` or `--no-hooks` keeps that choice. The refresh
|
|
457
|
+
never builds the graph (it runs at session start, where a rebuild would stall
|
|
458
|
+
the first turn) and is fail-soft throughout.
|
|
459
|
+
- **An upgrade nudge.** A machine-global 24h cache
|
|
460
|
+
(`~/.graft/update-check.json` — one registry request a day per machine, not
|
|
461
|
+
per repo), filled by a detached `graft _update-check` child, feeds a one-line
|
|
462
|
+
"newer version available" notice. Hooks only ever *read* that cache; the CLI
|
|
463
|
+
and the MCP server are the fillers, because a hook that shelled out to
|
|
464
|
+
`npm view` would spend its whole timeout on the network.
|
|
465
|
+
- Both run from one shared code path, called at three entry points so no host
|
|
466
|
+
is left out: Claude Code's `SessionStart` hook, the MCP server's `initialize`
|
|
467
|
+
(the only channel that reaches Cursor, which has no hooks — the lines ride in
|
|
468
|
+
`instructions`, since stdout carries protocol messages only), and a CLI
|
|
469
|
+
`preAction` hook for every command except `version`, `upgrade`, `mcp` and
|
|
470
|
+
`_update-check`.
|
|
471
|
+
|
|
472
|
+
## 0.9.0
|
|
473
|
+
|
|
474
|
+
### Added
|
|
475
|
+
|
|
476
|
+
- **`graft build --include-dir <name>`** — an explicit, persisted override for
|
|
477
|
+
`SKIP_DIRS` (repeatable: `--include-dir build --include-dir tools`). Some
|
|
478
|
+
ecosystems keep genuine hand-written source under a directory name graft
|
|
479
|
+
otherwise treats as build output (e.g. a `build/` that isn't generated).
|
|
480
|
+
The override is persisted per repo in Git-ignored `.graft/config.json`: set
|
|
481
|
+
it once and every later no-flag `graft build`, plus the hooks/refresh path
|
|
482
|
+
(which never sees CLI flags at all), include it identically. It lifts only
|
|
483
|
+
graft's own skip list — in a
|
|
484
|
+
Git repository, Git's ignore rules stay authoritative, so a directory that
|
|
485
|
+
is both skip-listed and gitignored needs un-ignoring (or `git add -f`) too,
|
|
486
|
+
the same contract indexing already applies to tracked-but-ignored files.
|
|
487
|
+
Dot-directories are never overridable. Reaches the wiring graph, the Tier-2
|
|
488
|
+
markdown/concept pipeline, Go module discovery, and workspace child builds
|
|
489
|
+
alike, and is validated up front (a bare directory name only — no paths, no
|
|
490
|
+
dot-prefixes).
|
|
491
|
+
|
|
492
|
+
### Fixed
|
|
493
|
+
|
|
494
|
+
- **`graft map` no longer promotes unrelated methods into hubs and hotspots.**
|
|
495
|
+
A member call with an unknown receiver could be wired to the repository's
|
|
496
|
+
only method with the same bare name, so built-ins such as `Map.set()` inflated
|
|
497
|
+
an unrelated user-defined `set` method. Member calls now require an
|
|
498
|
+
owner-qualified receiver-type match; unresolved calls are dropped rather
|
|
499
|
+
than guessed ([#35]).
|
|
500
|
+
|
|
501
|
+
- **Indexing now respects `.gitignore`.** In Git repositories, graft indexes
|
|
502
|
+
tracked files plus untracked files that Git does not ignore, so generated
|
|
503
|
+
output such as `Scripts/bundles/` and `Scripts/transpiled/` is no longer
|
|
504
|
+
parsed merely because its extension is supported. Nested ignore files,
|
|
505
|
+
negations, and global Git excludes follow Git's own rules; non-Git directories
|
|
506
|
+
retain the existing filesystem walk and built-in skip list ([#39]).
|
|
507
|
+
|
|
508
|
+
- **`graft ask` no longer lets normalization undo test-file de-ranking.** Test
|
|
509
|
+
files were penalized before lexical scores were normalized, but the strongest
|
|
510
|
+
test match was still normalized back to the maximum score. The test prior now
|
|
511
|
+
also applies to the final lexical/graph blend, while test-seeking queries keep
|
|
512
|
+
the existing unpenalized behavior ([#37]).
|
|
513
|
+
|
|
514
|
+
- **`callers` now includes imported functions used as values.** Named imports that
|
|
515
|
+
are passed, returned, or stored are reported as weaker `references` edges,
|
|
516
|
+
while direct invocations remain `calls` ([#34]).
|
|
517
|
+
|
|
518
|
+
- **The build banner and repo map now name the language, not its parser.** JavaScript
|
|
519
|
+
files (`.js`, `.mjs`, `.cjs`) use the TypeScript grammar internally, and `.jsx`
|
|
520
|
+
uses the TSX grammar, but reporting those parser names made indexed files look
|
|
521
|
+
absent. Coverage now reports `javascript` and `jsx` alongside the existing
|
|
522
|
+
`typescript`, `tsx`, `python`, and `go` labels ([#36]).
|
|
523
|
+
|
|
524
|
+
- **README: `init` does not write a `CLAUDE.md` section.** Claude Code receives the
|
|
525
|
+
wholly-owned `.claude/skills/graft/SKILL.md`; existing `CLAUDE.md` content is
|
|
526
|
+
never touched ([#36]).
|
|
527
|
+
|
|
528
|
+
- **Windows: `graft upgrade` no longer reinstalls over an npx run.** The npx-cache check
|
|
529
|
+
matched `/_npx/` against a path that arrives with the platform separator, so it was
|
|
530
|
+
always false on Windows and `graft upgrade` ran `npm install -g` instead of explaining
|
|
531
|
+
that npx already fetches the latest build on every run.
|
|
532
|
+
|
|
533
|
+
- **Windows: a git worktree kept the graph it was seeded with, but not the record that
|
|
534
|
+
makes it cheap.** The seed's copy filter dropped every sidecar next to the graph — the
|
|
535
|
+
freshness fingerprint included — so the query right behind the seed found no
|
|
536
|
+
fingerprint, could not diff against the parent checkout, and re-parsed the whole repo.
|
|
537
|
+
It answered correctly the whole time, which is why nothing reported it; the only
|
|
538
|
+
visible trace was a `(? files changed)` note instead of a count.
|
|
539
|
+
|
|
540
|
+
- **`graft init` printed one path with two separators** on Windows (`~\.codex/`), from a
|
|
541
|
+
`/` concatenated onto an otherwise native display path.
|
|
542
|
+
|
|
543
|
+
- The `windows-latest` CI leg now **gates** rather than merely reporting. The 21 failures
|
|
544
|
+
it shipped with are resolved: two were the real bugs above, most of the rest were tests
|
|
545
|
+
asserting `/` in paths that are deliberately printed with the native separator or
|
|
546
|
+
pointing a child process at `HOME` (Windows reads `USERPROFILE`), and four are now
|
|
547
|
+
explicit named skips — nothing in Node's `fs` can deny a *read* on Windows, and there
|
|
548
|
+
is no exec bit or `SIGTERM` to test.
|
|
549
|
+
|
|
550
|
+
- **Windows: path scoping and `map` work again.** graft stores a repo-relative path
|
|
551
|
+
for every indexed file — in node ids, `node.path`, the extract cache, the freshness
|
|
552
|
+
fingerprint — and it was produced with `relative()`, which returns the *platform*
|
|
553
|
+
separator. So on Windows every stored path was `src\gate.ts`, while the query layer
|
|
554
|
+
parses those strings with `/` by hand. Nothing errored; it just matched nothing:
|
|
555
|
+
|
|
556
|
+
- `ask --in <path>` reported `nothing indexed under "…"` for **every** prefix,
|
|
557
|
+
making path scoping unusable on the platform ([#33]).
|
|
558
|
+
- `map` saw one path segment instead of several, so it emitted one single-file
|
|
559
|
+
"directory" per file — on a large repo spending its whole token budget describing
|
|
560
|
+
~16 arbitrary files instead of the repo's shape ([#35]).
|
|
561
|
+
- `callers <file.ts>`-style filename lookups missed.
|
|
562
|
+
|
|
563
|
+
Repo-relative paths are now normalized to posix once, where they are created
|
|
564
|
+
(`src/util/paths.ts`), instead of defensively at each consumer. Mac and Linux are
|
|
565
|
+
unaffected — the conversion is the identity there, and existing graphs are
|
|
566
|
+
byte-identical. **On Windows every cache key changes**, so the first `graft build`
|
|
567
|
+
after upgrading re-parses the repo once and `graft check` may report drift until it
|
|
568
|
+
runs. One-time, and `graft/` is a local gitignored cache — nothing to migrate.
|
|
569
|
+
|
|
570
|
+
CI now runs a `windows-latest` leg, because this whole class of bug is invisible to
|
|
571
|
+
a posix-only matrix.
|
|
572
|
+
|
|
573
|
+
### Changed
|
|
574
|
+
|
|
575
|
+
- **`--in` means the same thing on every command.** `ask --in` matched a segment-aware
|
|
576
|
+
path prefix while `grep --in` and `callers --in` matched a bare substring, so
|
|
577
|
+
`grep --in src` also swept up `lib/mysrc/`. All three now use the prefix rule, and
|
|
578
|
+
all three accept either separator (`--in server\src\gpu` works on Windows). A prefix
|
|
579
|
+
matching nothing indexed is now a loud error on all three rather than — for `grep`
|
|
580
|
+
and `callers` — empty output the caller had to interpret.
|
|
581
|
+
|
|
582
|
+
This is stricter: a mid-path fragment like `--in gpu` for `server/src/gpu` no longer
|
|
583
|
+
matches. Pass a real prefix (`--in server/src/gpu`), a full file path
|
|
584
|
+
(`--in src/a.ts`), or use `grep`'s pattern to match on content.
|
|
585
|
+
|
|
586
|
+
- **Duplicate-named definitions no longer silently collide onto one graph node
|
|
587
|
+
id.** A branch-guarded redeclaration, a reopened class, or any other same-name
|
|
588
|
+
definition within a file used to mint the exact same node id as an earlier
|
|
589
|
+
definition, so the second one silently overwrote the first in every id-keyed
|
|
590
|
+
lookup (`callers`, `ask`, MCP tools). Every definition now mints a unique id
|
|
591
|
+
(`~2`, `~3`, ... on a document-order duplicate), and a qualified query
|
|
592
|
+
(`Class.method`) now matches every duplicate, not just the first.
|
|
593
|
+
|
|
594
|
+
- **UTF-16LE source is now decoded consistently everywhere graft reads repo
|
|
595
|
+
source.** `graft build`'s parse, `check`'s and `fingerprint`'s drift hashes,
|
|
596
|
+
the context summarizer's input, `ask --source`'s span slicer, and `grep` each
|
|
597
|
+
read files with their own `readFileSync(file, "utf8")` — hashing what the
|
|
598
|
+
parser actually sees wasn't guaranteed, and a UTF-16LE file (the common
|
|
599
|
+
encoding Windows tooling writes) got silently mojibake'd by some readers and
|
|
600
|
+
not others. All of them now share one `readSourceFile`, so a file decodes
|
|
601
|
+
identically no matter which command reads it. UTF-16BE, unsupported by
|
|
602
|
+
Node's built-in decoders, is a clean skip (an empty entry) rather than a
|
|
603
|
+
mojibake read.
|
|
604
|
+
|
|
605
|
+
- **`graft callers`'s zero-hit note now says when the query name itself is
|
|
606
|
+
ambiguous.** When a symbol name is defined more than once, name resolution
|
|
607
|
+
drops a cross-file call to it rather than guessing which definition it means
|
|
608
|
+
— so a zero-hit result could really mean "something calls this, but the edge
|
|
609
|
+
was dropped for being ambiguous." The note now states how many definitions
|
|
610
|
+
share the name.
|
|
611
|
+
|
|
612
|
+
[#33]: https://github.com/NanoNets/Graft/issues/33
|
|
613
|
+
[#34]: https://github.com/NanoNets/Graft/issues/34
|
|
614
|
+
[#35]: https://github.com/NanoNets/Graft/issues/35
|
|
615
|
+
[#36]: https://github.com/NanoNets/Graft/issues/36
|
|
616
|
+
[#37]: https://github.com/NanoNets/Graft/issues/37
|
|
617
|
+
[#39]: https://github.com/NanoNets/Graft/issues/39
|
|
618
|
+
|
|
619
|
+
## 0.8.2
|
|
620
|
+
|
|
621
|
+
### Fixed
|
|
622
|
+
|
|
623
|
+
- **`graft ask` no longer buries source under test files on pytest-style repos.** The
|
|
624
|
+
test-de-rank (`isTestPath`) matched test directories (`tests/`, `spec/`) and suffix
|
|
625
|
+
names (`_test`, `.test`, `.spec`) but missed Python's dominant `test_*.py` filename
|
|
626
|
+
**prefix** and `conftest.py`. On repos whose tests live outside a `tests/`-named
|
|
627
|
+
directory (e.g. a `t/unit/` layout), tests were not de-ranked and swamped `ask`
|
|
628
|
+
results. The prefix and `conftest.py` are now recognized.
|
|
629
|
+
|
|
630
|
+
## 0.8.1
|
|
631
|
+
|
|
632
|
+
### Changed
|
|
633
|
+
|
|
634
|
+
- **Every graft query now refreshes the graph before it answers.** Freshness used to be the
|
|
635
|
+
`Stop` hook's job — it rebuilt once the turn had ended — so every query an agent made
|
|
636
|
+
between its first edit and the end of that turn answered from a graph that no longer
|
|
637
|
+
matched the file it had just changed, and it stayed that way indefinitely if the
|
|
638
|
+
background sync failed. Edits made outside the agent (your editor, a branch switch, a
|
|
639
|
+
stash) set no flag at all, so the statusline read `✓ synced` while the graph was behind.
|
|
640
|
+
|
|
641
|
+
`ask`, `grep`, `callers`, `skeleton` and `map` now stat the working tree against the last
|
|
642
|
+
build's fingerprint (~3ms) and rebuild only if something moved. `check` is exempt — it is
|
|
643
|
+
the drift report, and refreshing first would make it always say OK.
|
|
644
|
+
|
|
645
|
+
A refresh writes only what a query reads: the wiring graph, the `ask` sidecar, and the
|
|
646
|
+
freshness record. It does **not** rewrite the markdown cards, `INDEX.md`, or your
|
|
647
|
+
`.gitignore` — a query is a read, and those stay the job of an explicit `graft build`
|
|
648
|
+
(which is what the Claude Code `Stop` hook already runs at the end of a turn). So the
|
|
649
|
+
retrieval tools are always current, while the markdown you might `grep` by hand can lag
|
|
650
|
+
an edit until the turn ends.
|
|
651
|
+
|
|
652
|
+
The refresh is structural and `$0`: it never calls the LLM, so `graft check` still reports
|
|
653
|
+
concept-node drift and stale summaries until you run `graft build --deep` yourself. A
|
|
654
|
+
refresh that fails answers from the graph on disk rather than failing the query.
|
|
655
|
+
|
|
656
|
+
```bash
|
|
657
|
+
graft ask "..." --no-refresh # answer from the graph exactly as it is on disk
|
|
658
|
+
GRAFT_NO_REFRESH=1 # same, for every command in the process
|
|
659
|
+
```
|
|
660
|
+
|
|
661
|
+
### Added
|
|
662
|
+
|
|
663
|
+
- **Incremental extraction.** `graft build` memoizes each file's parse under `graft/.cache/`
|
|
664
|
+
and replays the files whose bytes have not moved, so a rebuild costs roughly the files
|
|
665
|
+
that changed: on this repo (124 files) **0.74s cold against 0.18s after one edit**. Output
|
|
666
|
+
is byte-identical to a cold build. The memo is discarded automatically when the extraction
|
|
667
|
+
code or the graft version changes, so a stale parse can't outlive an upgrade. `graft build`
|
|
668
|
+
now reports `parsed: N of M files (K replayed from cache)`, and `graft build --no-reuse`
|
|
669
|
+
forces a cold parse of everything.
|
|
670
|
+
|
|
671
|
+
Only the *parse* is skipped — every file is still read and hashed on every build. A stat
|
|
672
|
+
may decide whether a query bothers rebuilding; it may not decide what the rebuild itself
|
|
673
|
+
looks at, or `graft check` (which always re-hashes) could report drift that the `graft
|
|
674
|
+
build` it recommends refuses to repair.
|
|
675
|
+
|
|
676
|
+
- **`GRAFT_REFRESH=hash`** — confirm every file by hashing its contents instead of trusting
|
|
677
|
+
size and mtime, for tooling that rewrites files while preserving both.
|
|
678
|
+
|
|
679
|
+
### Fixed
|
|
680
|
+
|
|
681
|
+
- **A git worktree is no longer blind.** `graft/` is gitignored, so `git worktree add`
|
|
682
|
+
never checks it out — and the graph is the only thing the MCP tools read. Every tool in
|
|
683
|
+
a fresh worktree answered `no matching nodes` / `no graph found` for the whole session,
|
|
684
|
+
and `INDEX.md` and the cards were missing too, so `grep` and the repo map came up empty.
|
|
685
|
+
|
|
686
|
+
A query in a worktree now copies the parent checkout's graph and query sidecars in, then
|
|
687
|
+
treats the difference between the two checkouts as ordinary drift. The worktree's `.git`
|
|
688
|
+
is a file naming its parent, so there is nothing to configure; the copy is $0 and
|
|
689
|
+
offline, and the Tier-2 meaning layer survives it (a cold rebuild would have thrown away
|
|
690
|
+
every summary you paid for and re-parsed the repo). `graft build` in a worktree starts
|
|
691
|
+
from the same copy, so it is incremental too — and it is what writes the worktree's
|
|
692
|
+
cards and `INDEX.md`, generated from *this* checkout's code rather than copied from the
|
|
693
|
+
parent's branch. A query still writes only what a query reads.
|
|
694
|
+
|
|
695
|
+
Reads the parent, never writes to it. No-ops unless there is genuinely a built parent
|
|
696
|
+
checkout on disk — a fresh clone, CI, or a cloned (rather than worktree'd) cloud session
|
|
697
|
+
behaves exactly as before. `GRAFT_NO_SEED=1` turns it off.
|
|
698
|
+
|
|
699
|
+
## 0.8.0
|
|
700
|
+
|
|
701
|
+
### Changed
|
|
702
|
+
|
|
703
|
+
- **`graft init` now asks which agents to wire, instead of writing files for every
|
|
704
|
+
agent it detects.** Detection keyed off directories in `$HOME`, so anyone who had
|
|
705
|
+
tried several coding CLIs got instruction files and MCP configs for all of them —
|
|
706
|
+
plain `graft init` effectively behaved like `--all-agents`. On a terminal it now
|
|
707
|
+
shows every known agent, which ones were detected, and the exact files each would
|
|
708
|
+
write, and wires only what you select (Claude Code pre-selected).
|
|
709
|
+
|
|
710
|
+
**Migration —** `graft init` in CI, a Dockerfile, or any non-interactive shell now
|
|
711
|
+
writes **nothing** and prints the command to run instead. Add `--yes` for the old
|
|
712
|
+
behaviour, or `--agents <ids>` to be explicit:
|
|
713
|
+
|
|
714
|
+
```bash
|
|
715
|
+
graft init --yes # wire every detected agent (pre-0.8 default)
|
|
716
|
+
graft init --agents claude # or name them
|
|
717
|
+
```
|
|
718
|
+
|
|
719
|
+
### Added
|
|
720
|
+
|
|
721
|
+
- **`graft init --dry-run`** — print every path `init` would touch, then exit without
|
|
722
|
+
writing. Out-of-repo writes get their own section.
|
|
723
|
+
- **`graft init --no-global`** — skip every write outside the repo. Selecting the
|
|
724
|
+
`agents` host writes to `~/.codex/config.toml`, `~/.codex/hooks.json`, and
|
|
725
|
+
`~/.codex/hooks/graft/`; those are user-level and apply to every repo you open with
|
|
726
|
+
Codex, and previously nothing suppressed the `config.toml` write (`--no-hooks` only
|
|
727
|
+
covered the other two). These are now labelled `machine-wide` in the picker.
|
|
728
|
+
- **`graft init --yes`** — wire every detected agent without prompting.
|
|
729
|
+
|
|
730
|
+
## 0.7.0
|
|
731
|
+
|
|
732
|
+
### Changed
|
|
733
|
+
|
|
734
|
+
- **`graft/` is now a local, git-ignored cache, not a committed artifact.** Every
|
|
735
|
+
`graft build` adds `graft/` to the repo's `.gitignore` itself, so the graph is
|
|
736
|
+
regenerated locally (like `node_modules`) rather than shared through git. Commit
|
|
737
|
+
`.claude/` (hooks, skill, statusline, `.mcp.json`) so teammates' agents pick graft
|
|
738
|
+
up; each teammate runs `graft build` for their own graph. `graft check` is now a
|
|
739
|
+
local freshness signal rather than a CI merge gate.
|
|
740
|
+
|
|
741
|
+
### Removed
|
|
742
|
+
|
|
743
|
+
- The `bench/` benchmark harness is no longer part of the published repo.
|
|
744
|
+
|
|
745
|
+
## 0.6.0
|
|
746
|
+
|
|
747
|
+
Consolidates the structural-traversal surface and wires the MCP server into
|
|
748
|
+
Claude Code. **Breaking** — see migration below.
|
|
749
|
+
|
|
750
|
+
### Breaking
|
|
751
|
+
|
|
752
|
+
- **Removed `graft callees` and `graft impact`.** Both fold into `graft callers`:
|
|
753
|
+
- `graft callees <symbol>` → `graft callers <symbol> --direction out`
|
|
754
|
+
- `graft impact <symbol> -d N` → `graft callers <symbol> --depth N`
|
|
755
|
+
- `graft callers` with no new flags is unchanged (defaults `--direction in --depth 1`).
|
|
756
|
+
- **Removed MCP tools `graft_callees` and `graft_blast_radius`.** The `graft_callers`
|
|
757
|
+
tool now takes optional `direction` (`in`|`out`, default `in`) and `depth`
|
|
758
|
+
(default `1`) parameters covering both:
|
|
759
|
+
- callees → `graft_callers { direction: "out" }`
|
|
760
|
+
- blast radius → `graft_callers { depth: N }` (accepts a file path or symbol,
|
|
761
|
+
same file-seed aggregation the old `graft_blast_radius` did).
|
|
762
|
+
|
|
763
|
+
Rationale: a coding-agent tool-selection experiment showed agents never picked
|
|
764
|
+
`graft_blast_radius`/`impact` (they reconstructed it by calling `callers`
|
|
765
|
+
repeatedly) and never picked `callees` (they read the named file instead). One
|
|
766
|
+
well-named command with flags is selected more reliably than three.
|
|
767
|
+
|
|
768
|
+
### Added
|
|
769
|
+
|
|
770
|
+
- `graft callers --direction <in|out>` — walk incoming (callers, default) or
|
|
771
|
+
outgoing (callees) edges.
|
|
772
|
+
- `graft callers --depth <n>` — walk transitively out to depth N for the full
|
|
773
|
+
blast radius (default 1 = direct edges only). For a file seed at depth >1 the
|
|
774
|
+
walk aggregates over the symbols the file defines.
|
|
775
|
+
- `graft init` now registers the graft MCP server in the project's `.mcp.json`
|
|
776
|
+
for Claude Code (previously Claude Code got only hooks + statusline + skill).
|
|
777
|
+
Restart Claude Code to load it. Existing `.mcp.json` servers are preserved.
|
|
778
|
+
|
|
779
|
+
### Changed
|
|
780
|
+
|
|
781
|
+
- `graft mcp --help` and docs now list the full tool set
|
|
782
|
+
(`graft_ask`, `graft_callers`, `graft_grep`, `graft_skeleton`, `graft_map`,
|
|
783
|
+
`graft_check`) instead of only three.
|
|
784
|
+
- The bundled Claude Code skill and other-agent instructions document the
|
|
785
|
+
consolidated `callers` flags.
|