Repository navigation
feat(init): a new install starts on strategy "index" and the "locate" MCP profile (Candidate A of #1071) - #1084
Open
manojmallick wants to merge 1 commit into
Open
manojmallick wants to merge 1 commit into
manojmallick wants to merge 1 commit into
Conversation
… MCP profile (Candidate A of #1071) `sigmap --init` now writes "strategy": "index" and "mcp": { "tools": "locate" } on both paths (the example config and the lone-bundle fallback); it wrote "full" and "core". DEFAULTS are unchanged: a project with no config keeps strategy full and all 22 tools, and a config that exists is never rewritten. The choice rests on three pre-registered runs of exactly this setup against no SigMap in Claude Code, bar met each time with no repository clearly costing more: Haiku 5.5 on 20 repositories -16.6% [-23.2, -9.7], Sonnet 5.5 on the same 20 -8.8% [-15.5, -2.0], Haiku 5.5 on 16 repositories of 3,026 to 7,756 files -18.5% [-22.5, -14.3]. The docs state the limits: file found was 4.2 points lower on the large set, Sonnet's saving is in cost not tokens, and nothing was measured for subscription sessions, Opus, repositories above 7,756 files, answer quality or editing work. T1 pins now say Candidate A on both paths and T1c runs instead of skipping; T2 (upgrade invariance) is unchanged and passes. New tests pin the words in --help, the README and the guides, and the example config's comments. Docs: README, choosing-a-setup (new section), cli, config, mcp, troubleshooting, memory; llms-full.txt regenerated. No version bump, no CHANGELOG entry.
This branch has not been deployed
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.
Summary
Option A of #1071, on the maintainer's decision: a new
sigmap --initproject starts onstrategy: "index"andmcp.tools: "locate"(it wasfullandcore). Existing installs do not change.gen-context.config.json.example(what--initcopies) and the lone-bundle fallback ingen-context.js(what--initwrites with no example beside it) now carry"strategy": "index"and"tools": "locate", with comments that say so. The--inithelp line says it.DEFAULTSare untouched. A project with no config keeps strategyfulland all 22 tools; a project with a config keeps it byte for byte (T2 below).--init: README,choosing-a-setup(a new section, "What a new install starts on", with the three runs and their limits),cli,config,mcp,troubleshooting,memory;llms-full.txtregenerated./update-docsowns those, and nothing is released by this PR.Why (the evidence, with its limits)
Pre-registered runs of exactly this setup against no SigMap in Claude Code (
--bare, an API key, one question per run, the repository as the unit), bar B1 to B4 inbenchmarks/agent-study/confirm-bar.mjs, met each time, no repository clearly costing more:Not shown, and said in the docs: B3 in T7 passes by 0.8 points (an interval computed afterwards is [-7.8, -1.0] points); with Sonnet total tokens rose 9% while cost fell; nothing about a logged-in session or subscription allowance, Opus, repositories above 7,756 files, Python or JavaScript above about 2,400 files, answer quality, editing work, or the
askcommand and prefetch hook.locatedrops the impact, callee and verification tools;"tools": "core"gets them back.The guard rails of #1071, now meeting their own bar
new-install-default-guard.test.js):--initproposes Candidate A on both paths, and it equals the study'slocatearm (T1c no longer skips). The pin that saidfull+corewas changed on purpose; nothing else in T1.--initnever rewrites a config.--initleads to are 1.9 to 2.7 KB each.node, not wall-clock withnpx(disclosed on defaults: choose the new-install setup from the agent study - the default-config arm cost +9% andlocateis the only setup where no repository cost more #1071): Candidate A used 10 to 16% less CPU than v8.87.0. Not re-measured here.--help, README and the five guides sayindexandlocate; no page says--initwritescoreorfull; the example config's comments say what a new install starts on.Checks
node test/integration/all.js): 291 files passed, 0 failed, run on these same files before committing (only the hook-regeneratedAGENTS.mddiffers, and it is not in the commit). Of those,new-install-default-guard14 passed,mcp/tool-profile44 passed (its two--inittests now pinlocateandindex),build-bundle.mjs --checkandvalidate-llms.mjscurrent.sigmap --initwritesindex+locate; generating writes four files of 1.9 to 2.7 KB;sigmap doctorprints "MCP tool profile — locate (2 of 22 tools, ~278 tokens of definitions)";sigmap askranks files.DEFAULTSflipped toindexor tolocate(which would change every existing install),--initmade to rewrite an existing config, the--helpline and each of the README and five guides reverted to the old claim, a stale page saying--initwritescore, and the example config losing its new-install comment.Refs #1071 (stays open until the maintainer closes it).
🤖 Generated with Claude Code