@handsupmin/gc-tree 0.7.10 → 0.7.12

package/dist/src/integration-files.js

@@ -81,7 +81,7 @@ function ensureObject(value) {
 function isGcTreeHook(entry, event) {
     const command = String(entry.command || '');
     const owner = ensureObject(entry.metadata).owner;
-    return owner === 'gctree' || command === `gctree __hook --event ${event}`;
+    return owner === 'gctree' || command.includes(`gctree __hook --event ${event}`);
 }
 function mergeHookJson(raw, target) {
     const parsed = raw ? ensureObject(JSON.parse(raw)) : {};

package/dist/src/onboarding-protocol.js

@@ -1,7 +1,8 @@
 export function onboardingProtocolLines() {
     return [
         'This is **global context onboarding**, not repo-local onboarding.',
-        'Ask **one question at a time** and keep using the saved workflow language all the way through.',
+        'Ask **one question at a time**.',
+        '**Language lock**: detect the language the user writes in from their very first response and use it for every subsequent message without exception — numbered confirmations (1/2/3), hypotheses, summaries, doc content, and wrap-up must all be in that language. Never revert to English mid-session regardless of what language appears in repo names, code comments, or source docs.',
         'Wait for the user\'s first answer before you inspect docs, repos, directories, or files on your own.',
         'Start by asking the user to paste or share organized docs or reference material if they have any; otherwise ask what kind of work they mainly do.',
         'Do **not** start with a repo scan, a company guess, or a broad hypothesis built from directories like `~/sources`.',

package/package.json

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

package/skills/onboard/SKILL.md

@@ -8,6 +8,7 @@ description: Launch guided onboarding for the active gc-branch through the confi
 Use this when a user wants to create global context for a product, company, or workstream in an empty gc-branch.
 
 ## Rules
+- **language lock**: detect the language the user writes in from their very first response; use that language for every subsequent message without exception — numbered confirmations (1/2/3), hypotheses, summaries, and wrap-up must all be in the user's language; never revert to English mid-session regardless of what language appears in repo names, code comments, or source docs
 - ask one question at a time
 - keep the active gc-branch explicit
 - this is global-context onboarding, not repo-local onboarding