@handsupmin/gc-tree 0.8.16 → 0.8.17

package/dist/src/onboarding-protocol.js

@@ -45,6 +45,7 @@ export function onboardingCompletionLines() {
         '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"` **and** `quality_issues` is an empty array.',
         'If `quality_issues` is non-empty, do **not** tell the user onboarding is done. Self-heal immediately without asking the user: (a) identify which docs have `category: "general"`, (b) assign each a correct category from `role | repos | domain | workflows | conventions | infra | verification` based on content, (c) rebuild the full onboarding JSON with every doc having an explicit `category` field set to one of those values, (d) run `gctree __apply-onboarding --input <temp-file>` again, (e) rerun `gctree verify-onboarding` and repeat until `quality_issues` is empty. Never use `"general"` as a category in the JSON — it is a fallback for missing data, not a valid category.',
+        'After quality_issues passes, perform an index coverage check: for every written doc, verify that its key concepts (repo names, workflow names, domain terms, convention patterns) appear as searchable index labels in the verify output. If any important concept is missing from the index, add it as an index entry and re-apply. Do not skip this step — a doc that exists but cannot be found by search is useless.',
         'If verification returns `status: "incomplete"` for reasons other than quality_issues, do not tell the user onboarding is done; inspect the reported failures, heal what can be healed automatically, rerun verification, and repeat until it passes or a real blocker remains.',
         '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.',

package/dist/src/scaffold.js

@@ -104,18 +104,35 @@ function renderCodexOnboardSkill() {
         '',
     ].join('\n');
 }
+function renderUpdateProtocol() {
+    return [
+        '1. Run `gctree status` and state the active gc-branch.',
+        '2. Understand what changed — read the user\'s request, inspect relevant code or docs if needed, and determine the right content to capture.',
+        '3. Decide category and path automatically based on content — never ask the user about scope or placement:',
+        '   - `docs/workflows/<name>.md` — cross-repo action sequences, step-by-step procedures',
+        '   - `docs/conventions/<repo>.md` — code patterns, naming, validation, DTO/service conventions for a repo',
+        '   - `docs/repos/<repo>.md` — repo role, key paths, cross-repo dependencies',
+        '   - `docs/domain/<concept>.md` — domain terms, acronyms, business logic',
+        '   - `docs/infra/<topic>.md` — infra, deployment, environment config',
+        '   - `docs/role/<name>.md` — team member roles, responsibilities',
+        '4. Write a `## Summary` that is actionable: actual patterns/commands/constraints a developer needs — not a sentence about what the doc covers.',
+        '5. Create a temporary JSON file with the updated `docs[]` and run `gctree __apply-update --input <temp-file>`.',
+        '6. Run `gctree verify-onboarding --branch <gc-branch>` and inspect the output:',
+        '   - Check that every updated doc appears in the verified doc list.',
+        '   - Check that index entries for the new content exist and are searchable (not just generic titles).',
+        '   - Check that no doc has `category: "general"` — reassign to correct category if so.',
+        '   - Check that important concepts from the update are present as index labels — if missing, re-apply with added index entries.',
+        '   - Self-heal any issues without asking the user: fix category, add index entries, re-run `gctree __apply-update`, re-verify.',
+        '7. Show the user which docs were updated and confirm the index now covers the new content.',
+    ];
+}
 function renderCodexUpdateSkill() {
     return [
         '---',
         'description: Guided durable update for the active gc-branch in gctree.',
         '---',
         '',
-        '1. Run `gctree status` and explicitly state the active gc-branch to the user.',
-        '2. Ask what durable context should change, one question at a time.',
-        '3. If this repo clearly belongs to the current gc-branch but is not mapped yet, ask the user whether it should be added to the branch-repo map and run `gctree set-repo-scope --branch <current-gc-branch> --include` when they approve.',
-        '4. Create a temporary JSON file containing the updated `docs[]` and optional `branchSummary`.',
-        '5. Run `gctree __apply-update --input <temp-file>`.',
-        '6. Show the updated docs back to the user.',
+        ...renderUpdateProtocol(),
         '',
     ].join('\n');
 }
@@ -222,12 +239,7 @@ function renderClaudeUpdateCommand() {
         'description: Guided durable update for the active gc-branch in gctree.',
         '---',
         '',
-        '1. Run `gctree status` and explicitly state the active gc-branch to the user.',
-        '2. Ask what durable context should change, one question at a time.',
-        '3. If this repo clearly belongs to the current gc-branch but is not mapped yet, ask the user whether it should be added to the branch-repo map and run `gctree set-repo-scope --branch <current-gc-branch> --include` when they approve.',
-        '4. Create a temporary JSON file containing the updated `docs[]` and optional `branchSummary`.',
-        '5. Run `gctree __apply-update --input <temp-file>`.',
-        '6. Show the updated docs back to the user.',
+        ...renderUpdateProtocol(),
         '',
     ].join('\n');
 }

package/package.json

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