@handsupmin/gc-tree 0.4.1 → 0.4.2

package/dist/src/cli.js

@@ -11,6 +11,7 @@ import { scaffoldHostIntegration } from './scaffold.js';
 import { requirePreferredProvider, writeSettings, readSettings } from './settings.js';
 import { checkoutBranch, initHome, listBranches, readHead, resetBranchContext, statusForBranch, ensureBranchExists, isBranchContextEmpty } from './store.js';
 import { updateBranchContext } from './update.js';
+import { verifyOnboarding } from './verify-onboarding.js';
 function readArg(flag) {
     const index = process.argv.indexOf(flag);
     return index === -1 ? undefined : process.argv[index + 1];
@@ -28,6 +29,7 @@ function usage() {
   gctree set-repo-scope --branch NAME [--repo NAME] [--cwd DIR] (--include|--exclude) [--home DIR]
   gctree status [--home DIR] [--cwd DIR]
   gctree onboard [--home DIR] [--branch NAME] [--provider <codex|claude-code>] [--target DIR] [--no-launch]
+  gctree verify-onboarding [--home DIR] [--branch NAME]
   gctree reset-gc-branch [--home DIR] [--branch NAME] --yes
   gctree resolve --query TEXT [--home DIR] [--branch NAME] [--cwd DIR]
   gctree show-doc --id ID [--home DIR] [--branch NAME]
@@ -246,6 +248,12 @@ async function main() {
             console.log(JSON.stringify({ mode: 'guided_onboarding', gc_branch: gcBranch, preferred_provider: provider, scaffold, launch }, null, 2));
             return;
         }
+        case 'verify-onboarding': {
+            const gcBranch = readArg('--branch') || (await readHead(home)) || DEFAULT_BRANCH;
+            const result = await verifyOnboarding({ home, branch: gcBranch });
+            console.log(JSON.stringify(result, null, 2));
+            return;
+        }
         case '__apply-onboarding': {
             const inputPath = readArg('--input');
             if (!inputPath)

package/dist/src/onboarding-protocol.js

@@ -28,6 +28,8 @@ export function onboardingProtocolLines() {
 }
 export function onboardingCompletionLines() {
     return [
+        'Before you claim onboarding is complete, run `gctree verify-onboarding --branch <current-gc-branch>` and inspect the real gc-tree files.',
+        '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.',

package/dist/src/verify-onboarding.js

@@ -0,0 +1,24 @@
+import { readFile } from 'node:fs/promises';
+import { parseIndexEntries } from './markdown.js';
+import { branchIndexPath, DEFAULT_BRANCH } from './paths.js';
+import { ensureBranchExists, statusForBranch } from './store.js';
+export async function verifyOnboarding({ home, branch, }) {
+    const gcBranch = branch || DEFAULT_BRANCH;
+    await ensureBranchExists(home, gcBranch);
+    const status = await statusForBranch(home, gcBranch);
+    const indexRaw = await readFile(branchIndexPath(home, gcBranch), 'utf8');
+    const docs = parseIndexEntries(indexRaw);
+    const indexedDocCount = docs.length;
+    const complete = status.doc_count > 0 && indexedDocCount > 0;
+    return {
+        status: complete ? 'complete' : 'incomplete',
+        gc_branch: gcBranch,
+        doc_count: status.doc_count,
+        indexed_doc_count: indexedDocCount,
+        docs,
+        warnings: status.warnings,
+        message: complete
+            ? `Onboarding is complete for gc-branch "${gcBranch}".`
+            : `Onboarding is incomplete for gc-branch "${gcBranch}". Docs or index entries are missing.`,
+    };
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@handsupmin/gc-tree",
-  "version": "0.4.1",
+  "version": "0.4.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

@@ -64,10 +64,12 @@ Use this when a user wants to create global context for a product, company, or w
 18. Ask for company/domain glossary terms and acronyms that should become durable context.
 19. Ask which verification commands should be treated as defaults for this gc-branch.
 20. Launch the guided onboarding flow with `gctree onboard [--branch <name>]`.
-21. After the onboarding docs are written, explicitly list which durable docs were saved.
-22. Summarize what you now understand from the saved docs instead of ending at the filenames alone.
-23. Ask whether that final summary matches the user's reality, and capture any corrections before you wrap up.
-24. Ask whether anything else should be saved while the context is still fresh.
-25. Do not finish onboarding while material related repos, workflows, or domain terms remain uninspected when recoverable local evidence is still available.
-26. Only after the related repos, workflows, glossary, and default verification commands are either captured or explicitly unavailable should you wrap up, then remind the user that future changes belong in `gctree update-global-context`.
-27. Keep the current gc-branch explicit while gathering context.
+21. Before you claim onboarding is complete, run `gctree verify-onboarding --branch <current-gc-branch>` and inspect the real gc-tree files.
+22. Do not claim onboarding is complete unless verification returns `status: "complete"`.
+23. After the onboarding docs are written, explicitly list which durable docs were saved.
+24. Summarize what you now understand from the saved docs instead of ending at the filenames alone.
+25. Ask whether that final summary matches the user's reality, and capture any corrections before you wrap up.
+26. Ask whether anything else should be saved while the context is still fresh.
+27. Do not finish onboarding while material related repos, workflows, or domain terms remain uninspected when recoverable local evidence is still available.
+28. Only after the related repos, workflows, glossary, and default verification commands are either captured or explicitly unavailable should you wrap up, then remind the user that future changes belong in `gctree update-global-context`.
+29. Keep the current gc-branch explicit while gathering context.