@handsupmin/gc-tree 0.8.4 → 0.8.5

package/dist/src/repo-map.js

@@ -132,7 +132,8 @@ export async function resolveBranchForRepo({ home, head, explicitBranch, cwd = p
 }
 export async function promptResolveScopeDecision(branch, repo, preferredLanguage = 'English') {
     if (!stdin.isTTY && process.env.GCTREE_ALLOW_STDIN_PROMPT !== '1') {
-        throw new Error(`current repo \"${repo}\" is not mapped to gc-branch \"${branch}\". Run interactively to choose whether to continue, include this repo, or ignore this gc-branch here.`);
+        process.stderr.write(`gc-tree: repo "${repo}" is not mapped to gc-branch "${branch}" — continuing without scope decision.\n`);
+        return 'continue-once';
     }
     const rl = createInterface({ input: stdin, output: stderr });
     try {

package/dist/src/scaffold.js

@@ -8,11 +8,12 @@ function renderCodexAgentsSnippet() {
         '',
         '- Treat the active gctree branch as a **gc-branch** when you describe it to users.',
         '- gctree init installs SessionStart and UserPromptSubmit hooks that auto-check gc-tree before work.',
-        '- When you encounter an unfamiliar term, acronym, concept, or domain word, follow this protocol **before** grepping or reading code files:',
-        '  1. Run `gctree resolve --query "<term>"` — if matched, use the result directly.',
-        '  2. If no match, try broader related queries to check if the concept lives in any doc.',
-        '  3. If the concept exists in a doc but was not indexed → propose adding it as an Index Entry to that doc (so future resolves find it).',
+        '- When you encounter an unfamiliar term, acronym, concept, or domain word, follow this scope-aware protocol **before** grepping or reading code files:',
+        '  1. Always run `gctree resolve --query "<term>"` first. If matched, use the result directly.',
+        '  2. Only if the current repo scope is **included** (not unmapped/excluded): if step 1 found nothing, try broader related queries to check if the concept exists in any doc.',
+        '  3. If the concept exists in a doc but was not indexed → propose adding it as an Index Entry to that doc.',
         '  4. If it does not exist anywhere → decide whether a new doc is needed and propose it to the user.',
+        '  — If the repo is **unmapped** or **excluded**: do step 1 only; if no match, skip and proceed normally.',
         '- When a UserPromptSubmit hook provides `[gc-tree] PRE-TASK CONTEXT`, treat it as mandatory pre-reading before any tool use.',
         '- If the injected summaries contain enough information to answer the question or complete the task, respond directly from them **without calling any tools**. Do not grep, explore, or read code files to confirm what the summaries already cover.',
         '- Only use tools if the summaries are clearly insufficient — meaning the answer cannot be derived from them at all.',
@@ -123,11 +124,12 @@ function renderClaudeSnippet() {
         '',
         '- Treat the active gctree branch as a **gc-branch** in user-facing language.',
         '- gctree init installs SessionStart and UserPromptSubmit hooks that auto-inject gc-tree context before every prompt.',
-        '- When you encounter an unfamiliar term, acronym, concept, or domain word, follow this protocol **before** grepping or reading code files:',
-        '  1. Run `gctree resolve --query "<term>"` — if matched, use the result directly.',
-        '  2. If no match, try broader related queries to check if the concept lives in any doc.',
-        '  3. If the concept exists in a doc but was not indexed → propose adding it as an Index Entry to that doc (so future resolves find it).',
+        '- When you encounter an unfamiliar term, acronym, concept, or domain word, follow this scope-aware protocol **before** grepping or reading code files:',
+        '  1. Always run `gctree resolve --query "<term>"` first. If matched, use the result directly.',
+        '  2. Only if the current repo scope is **included** (not unmapped/excluded): if step 1 found nothing, try broader related queries to check if the concept exists in any doc.',
+        '  3. If the concept exists in a doc but was not indexed → propose adding it as an Index Entry to that doc.',
         '  4. If it does not exist anywhere → decide whether a new doc is needed and propose it to the user.',
+        '  — If the repo is **unmapped** or **excluded**: do step 1 only; if no match, skip and proceed normally.',
         '- When a UserPromptSubmit hook provides `[gc-tree] PRE-TASK CONTEXT`, treat it as mandatory pre-reading before any tool use.',
         '- If the injected summaries contain enough information to answer the question or complete the task, respond directly from them **without calling any tools**. Do not grep, explore, or read code files to confirm what the summaries already cover.',
         '- Only use tools if the summaries are clearly insufficient — meaning the answer cannot be derived from them at all.',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@handsupmin/gc-tree",
-  "version": "0.8.4",
+  "version": "0.8.5",
   "description": "Global Context Tree, a lightweight branch-aware global context orchestrator for AI coding tools",
   "type": "module",
   "private": false,