@handsupmin/gc-tree 0.6.0 → 0.6.2

package/dist/src/markdown.js

@@ -70,7 +70,8 @@ export function renderIndexMarkdown(input) {
         for (const category of categories) {
             lines.push(`## ${displayCategory(category)}`, '');
             for (const doc of grouped.get(category).sort((a, b) => (a.label || a.title).localeCompare(b.label || b.title))) {
-                lines.push(`- ${doc.label || doc.title} -> ${doc.path}`);
+                lines.push(`- ${doc.label || doc.title}`);
+                lines.push(`  - ${doc.path}`);
             }
             lines.push('');
         }
@@ -107,25 +108,44 @@ export function displayCategory(category) {
 }
 export function parseIndexEntries(indexContent) {
     let currentCategory = 'general';
-    return String(indexContent || '')
-        .split(/\r?\n/)
-        .map((line) => line.trim())
-        .flatMap((line) => {
-        if (!line)
-            return [];
-        const heading = line.match(/^##\s+(.+)$/);
+    let pendingLabel = null;
+    const entries = [];
+    for (const rawLine of String(indexContent || '').split(/\r?\n/)) {
+        const line = rawLine.trimEnd();
+        const trimmed = line.trim();
+        if (!trimmed) {
+            pendingLabel = null;
+            continue;
+        }
+        const heading = trimmed.match(/^##\s+(.+)$/);
         if (heading) {
             currentCategory = normalizeCategory(heading[1] || 'general');
-            return [];
+            pendingLabel = null;
+            continue;
         }
-        if (!/^-\s+.+\s+->\s+.+$/.test(line) || line.startsWith('- gc-branch:') || line.startsWith('- summary:')) {
-            return [];
+        if (trimmed.startsWith('- gc-branch:') || trimmed.startsWith('- summary:') || trimmed === '- No source docs yet.') {
+            pendingLabel = null;
+            continue;
         }
-        const body = line.slice(2);
-        const [label, path] = body.split('->').map((part) => part.trim());
-        const category = deriveCategoryFromPath(path) || currentCategory;
-        return [{ id: docIdFromPath(path), title: label, label, category, path }];
-    });
+        const pathMatch = rawLine.match(/^\s{2,}-\s+(docs\/.+)$/);
+        if (pathMatch && pendingLabel) {
+            const path = pathMatch[1].trim();
+            const category = deriveCategoryFromPath(path) || currentCategory;
+            entries.push({
+                id: docIdFromPath(path),
+                title: pendingLabel,
+                label: pendingLabel,
+                category,
+                path,
+            });
+            continue;
+        }
+        const labelMatch = trimmed.match(/^-\s+(.+)$/);
+        if (labelMatch) {
+            pendingLabel = labelMatch[1].trim();
+        }
+    }
+    return entries;
 }
 export function extractIndexEntries(markdown) {
     const match = String(markdown || '').match(/## Index Entries\s+([\s\S]*?)(?:\n## |$)/);

package/dist/src/onboarding-protocol.js

@@ -43,9 +43,11 @@ export function onboardingCompletionLines() {
         'Do not claim onboarding is complete unless verification returns `status: "complete"`.',
         'After applying the onboarding docs, explicitly list which durable docs were saved.',
         'Then summarize what you now understand from the saved docs instead of stopping at the filenames alone.',
-        'Ask whether that final summary matches the user\'s reality, and capture any corrections before you wrap up.',
+        'For that final summary, do not ask an open-ended validation question first; present the summary and ask the user to choose only one structured confirmation: 1. This matches well enough. 2. Some parts are wrong. I will give the delta. 3. The frame is wrong. I will restate it.',
+        'If the user picks 2 or 3 for the final summary, ask only for the correction delta or replacement frame, then update the saved understanding instead of restarting the interview.',
         'Ask whether anything else should be saved while the context is still fresh.',
-        'After docs are confirmed correct, ask which repositories discussed during onboarding should be explicitly mapped to this gc-branch. For each confirmed repo, navigate to that directory and run `gctree set-repo-scope --branch <current-gc-branch> --include`. Skip this step only if the user explicitly says repo mapping is not needed.',
+        'After docs are confirmed correct, do not ask the user to recall repo-scope mappings from scratch; propose the concrete repository candidates that appear materially tied to this gc-branch, then ask the user to choose only one structured confirmation: 1. Map these candidates. 2. Map these, but with corrections. 3. Skip repo mapping for now.',
+        'If the user picks 2 for repo mapping, ask only for the repo delta to add or remove. If the user picks 1 or gives corrected candidates, navigate to each confirmed repository and run `gctree set-repo-scope --branch <current-gc-branch> --include`. Skip mapping only if the user picks 3 or explicitly says mapping is not needed.',
         'Do not finish onboarding while material related repos, workflows, or domain terms remain uninspected when recoverable local evidence is still available.',
         'Only after the related repos, workflows, glossary, default verification commands, and repo-scope mapping are either captured or explicitly skipped should you wrap up, then remind the user that future changes belong in `gctree update-global-context`.',
     ];

package/dist/src/paths.js

@@ -1,7 +1,6 @@
 import { homedir } from 'node:os';
 import { join } from 'node:path';
 export const DEFAULT_BRANCH = 'main';
-export const INDEX_WARNING_CHARS = 2000;
 export function resolveHome(explicitHome) {
     return explicitHome || process.env.GCTREE_HOME || join(homedir(), '.gctree');
 }

package/dist/src/store.js

@@ -1,7 +1,7 @@
 import { cp, mkdir, readFile, readdir, rm, writeFile } from 'node:fs/promises';
 import { existsSync } from 'node:fs';
 import { join } from 'node:path';
-import { branchDir, branchDocsDir, branchIndexPath, branchMetaPath, branchesRoot, DEFAULT_BRANCH, headPath, INDEX_WARNING_CHARS, } from './paths.js';
+import { branchDir, branchDocsDir, branchIndexPath, branchMetaPath, branchesRoot, DEFAULT_BRANCH, headPath, } from './paths.js';
 import { extractIndexEntries, renderIndexMarkdown } from './markdown.js';
 async function listDocRelativePaths(dir, prefix = '') {
     const entries = await readdir(dir, { withFileTypes: true }).catch(() => []);
@@ -150,9 +150,6 @@ export async function statusForBranch(home, branch) {
     const indexRaw = await readFile(branchIndexPath(home, branch), 'utf8');
     const docs = await listDocRelativePaths(branchDocsDir(home, branch));
     const warnings = [];
-    if (indexRaw.length > INDEX_WARNING_CHARS) {
-        warnings.push(`index.md is ${indexRaw.length} chars; keep it closer to an index than a knowledge dump.`);
-    }
     for (const doc of docs) {
         const raw = await readFile(join(branchDocsDir(home, branch), doc), 'utf8');
         if (!/^## Summary$/m.test(raw)) {

package/package.json

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

package/skills/onboard/SKILL.md

@@ -83,9 +83,17 @@ Use this when a user wants to create global context for a product, company, or w
 28. Do not claim onboarding is complete unless verification returns `status: "complete"`.
 29. After the onboarding docs are written, explicitly list which durable docs were saved.
 30. Summarize what you now understand from the saved docs instead of ending at the filenames alone.
-31. Ask whether that final summary matches the user's reality, and capture any corrections before you wrap up.
-32. Ask whether anything else should be saved while the context is still fresh.
-33. After docs are confirmed correct, ask which repositories discussed during onboarding should be explicitly mapped to this gc-branch. For each confirmed repo, navigate to that directory and run `gctree set-repo-scope --branch <gc-branch> --include`. Skip this step only if the user explicitly says repo mapping is not needed.
-34. Do not finish onboarding while material related repos, workflows, or domain terms remain uninspected when recoverable local evidence is still available.
-35. Only after the related repos, workflows, glossary, default verification commands, and repo-scope mapping are either captured or explicitly skipped should you wrap up, then remind the user that future changes belong in `gctree update-global-context`.
-36. Keep the current gc-branch explicit while gathering context.
+31. For that final summary, do not ask an open-ended validation question first. Present the summary and ask the user to choose only one:
+   - 1. This matches well enough.
+   - 2. Some parts are wrong. I will give the delta.
+   - 3. The frame is wrong. I will restate it.
+32. If the user picks 2 or 3 for the final summary, ask only for the correction delta or replacement frame, then update the saved understanding instead of restarting the interview.
+33. Ask whether anything else should be saved while the context is still fresh.
+34. After docs are confirmed correct, do not ask the user to recall repo-scope mappings from scratch. Propose the concrete repository candidates that appear materially tied to this gc-branch, then ask the user to choose only one:
+   - 1. Map these candidates.
+   - 2. Map these, but with corrections.
+   - 3. Skip repo mapping for now.
+35. If the user picks 2 for repo mapping, ask only for the repo delta to add or remove. If the user picks 1 or gives corrected candidates, navigate to each confirmed repo and run `gctree set-repo-scope --branch <gc-branch> --include`. Skip mapping only if the user picks 3 or explicitly says mapping is not needed.
+36. Do not finish onboarding while material related repos, workflows, or domain terms remain uninspected when recoverable local evidence is still available.
+37. Only after the related repos, workflows, glossary, default verification commands, and repo-scope mapping are either captured or explicitly skipped should you wrap up, then remind the user that future changes belong in `gctree update-global-context`.
+38. Keep the current gc-branch explicit while gathering context.