@skillcap/gdh 0.26.5 → 0.26.7

package/node_modules/@gdh/observability/package.json

@@ -11,7 +11,7 @@
     }
   },
   "dependencies": {
-    "@gdh/core": "0.26.5"
+    "@gdh/core": "0.26.7"
   },
-  "version": "0.26.5"
+  "version": "0.26.7"
 }

package/node_modules/@gdh/runtime/package.json

@@ -11,9 +11,9 @@
     }
   },
   "dependencies": {
-    "@gdh/core": "0.26.5",
+    "@gdh/core": "0.26.7",
     "ws": "^8.18.3",
     "yaml": "^2.8.3"
   },
-  "version": "0.26.5"
+  "version": "0.26.7"
 }

package/node_modules/@gdh/scan/package.json

@@ -11,8 +11,8 @@
     }
   },
   "dependencies": {
-    "@gdh/core": "0.26.5",
-    "@gdh/docs": "0.26.5"
+    "@gdh/core": "0.26.7",
+    "@gdh/docs": "0.26.7"
   },
-  "version": "0.26.5"
+  "version": "0.26.7"
 }

package/node_modules/@gdh/verify/package.json

@@ -11,13 +11,13 @@
     }
   },
   "dependencies": {
-    "@gdh/authoring": "0.26.5",
-    "@gdh/core": "0.26.5",
-    "@gdh/docs": "0.26.5",
-    "@gdh/observability": "0.26.5",
-    "@gdh/runtime": "0.26.5",
-    "@gdh/scan": "0.26.5",
+    "@gdh/authoring": "0.26.7",
+    "@gdh/core": "0.26.7",
+    "@gdh/docs": "0.26.7",
+    "@gdh/observability": "0.26.7",
+    "@gdh/runtime": "0.26.7",
+    "@gdh/scan": "0.26.7",
     "yaml": "^2.8.3"
   },
-  "version": "0.26.5"
+  "version": "0.26.7"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skillcap/gdh",
-  "version": "0.26.5",
+  "version": "0.26.7",
   "description": "Godot-specific authoring and validation harness for agentic development.",
   "license": "MIT",
   "type": "module",
@@ -31,17 +31,17 @@
     "releaseStage": "broader_internal_release"
   },
   "dependencies": {
-    "@gdh/cli": "0.26.5",
+    "@gdh/cli": "0.26.7",
     "@clack/prompts": "^1.2.0",
-    "@gdh/adapters": "0.26.5",
-    "@gdh/authoring": "0.26.5",
-    "@gdh/core": "0.26.5",
-    "@gdh/docs": "0.26.5",
-    "@gdh/mcp": "0.26.5",
-    "@gdh/observability": "0.26.5",
-    "@gdh/runtime": "0.26.5",
-    "@gdh/scan": "0.26.5",
-    "@gdh/verify": "0.26.5",
+    "@gdh/adapters": "0.26.7",
+    "@gdh/authoring": "0.26.7",
+    "@gdh/core": "0.26.7",
+    "@gdh/docs": "0.26.7",
+    "@gdh/mcp": "0.26.7",
+    "@gdh/observability": "0.26.7",
+    "@gdh/runtime": "0.26.7",
+    "@gdh/scan": "0.26.7",
+    "@gdh/verify": "0.26.7",
     "picocolors": "^1.1.1"
   },
   "bundledDependencies": [

package/node_modules/@gdh/docs/dist/templates/guidance/gdh-glossary.md.tpl

@@ -1,34 +0,0 @@
-# {{projectName}}: GDH Operational Terms
-
-Use this unit when a GDH skill, command, or guidance file uses GDH-specific vocabulary. Do not repeat the words without understanding the operational meaning.
-
-- `target`: the Godot project root GDH should inspect, prepare, validate, or manage.
-- `authoring`: editing or validating Godot-facing files such as `.gd`, `.tscn`, `.tres`, and `project.godot`.
-- `authoring check`: `gdh authoring check`, the command that collects validator diagnostics and blocking summaries.
-- `diagnostics broker`: GDH's persistent diagnostics snapshot service backed by the managed LSP; exposes `current`, `refresh`, `status`, `doctor`, and `prune` operations under `gdh authoring diagnostics`.
-- `diagnostics snapshot`: the last set of normalized diagnostics GDH collected from the managed LSP, scoped to files that were opened or refreshed; not whole-project coverage.
-- `validation evidence`: concrete diagnostics from validators; capability availability or LSP lifecycle health alone is not validation evidence.
-- `LSP lifecycle`: whether GDH can launch, reuse, inspect, restart, prune, or stop the editor-backed Godot LSP service for this target.
-- `readiness`: GDH's structured status for whether the target is detected, onboarded, authorable, blocked, degraded, or unavailable.
-- `capability`: an available GDH feature surface, such as scan, authoring readiness, authoring LSP lifecycle, or runtime bridge support.
-- `inventory`: discovered Godot projects, addons, scenes, tests, and related filesystem evidence.
-- `inventory cache`: `.gdh-state/inventory.json`, derived machine-local project discovery data used by onboarded targets.
-- `.gdh/`: durable project truth owned by the repository, including GDH config, rules, run configurations, scenarios, project-owned bridge entries, and runtime knowledge.
-- `.gdh-state/`: ignored machine-local operational state, such as inventory cache, readiness snapshots, local paths, hook state, and logs.
-- `.godot/ generated state`: Godot's editor/import cache; useful for validation and import readiness, but not durable project truth.
-- `cold worktree`: a checkout/worktree whose generated Godot editor/import state is missing, stale, or incomplete.
-- `hydration`: copying reusable `.godot/` generated state from another local checkout to make this worktree ready faster.
-- `source target`: a sibling checkout used as the source for `.godot/` hydration.
-- `import refresh`: running Godot to rebuild or update generated import state for the target.
-- `machine-local path`: a path valid only on this computer, such as the Godot editor binary path; keep it in `.gdh-state/`, not committed project config.
-- `managed surface`: a GDH-owned or GDH-merge-managed file that must match the selected GDH version, such as guidance, rules, agent adapters, MCP config, or runtime bridge output.
-- `terminal.state`: the structured lifecycle outcome from migration or update flows; use it instead of prose, stderr, or action count guesses.
-- `manual review`: project-owned judgment GDH cannot safely automate; stop for the user after surfaced commands and validations.
-- `validationCommands`: exact GDH-surfaced commands to run after apply or follow-up work.
-- `runtime reachability knowledge`: scene-scoped route, waypoint, transition, dynamic-blocker, trust, and stale-status notes under `.gdh/runtime-knowledge/`.
-- `player_reachable`: a bounded action that a normal player could do through ordinary game input.
-- `internal_route`: bounded direct control used only when no practical player path exists.
-- `waiter`: a bounded runtime polling primitive for property, node, or signal conditions.
-
-If a shipped skill uses a GDH term not defined locally, load this glossary before acting. If the term is still ambiguous, ask for clarification rather than guessing.
-

package/node_modules/@gdh/docs/dist/templates/guidance/persistence-semantics.md.tpl

@@ -1,24 +0,0 @@
-# {{projectName}}: Persistence Semantics
-
-Use this unit when the task touches `gdh scan`, `gdh onboard`, `gdh status`, or any reasoning about whether a command warms `.gdh-state/` cache or not.
-
-Anchor on the command → effect table:
-
-| Command | Reads from disk | Writes to disk | Precondition | Session event |
-|---------|-----------------|----------------|--------------|---------------|
-| scan | `.gdh-state/inventory.json` (cache-first on onboarded targets) | `.gdh-state/inventory.json` (onboarded targets only) | Any filesystem path | `kind: "scan"` on onboarded branch only |
-| onboard | `.gdh/project.yaml` (if exists, for migration check), `.gitignore` | `.gitignore` (GDH-managed `.gdh-state/` section only), `.gdh/project.yaml`, `.gdh-state/inventory.json`, skill files | No precondition | `kind: "onboard"` |
-| status | `.gdh-state/inventory.json` (cache-first when onboarded) | None | Any filesystem path | None |
-
-Key facts agents keep getting wrong:
-
-- The inventory cache is `.gdh-state/inventory.json`: derived, machine-local project inventory used to avoid rescanning unchanged onboarded targets.
-- `gdh scan` on a target with no ancestor `.gdh/project.yaml` writes nothing — it is stdout-only and `persisted` is `null`. It does not "warm the cache" because there is no cache to warm.
-- `gdh scan` on an onboarded target writes `.gdh-state/inventory.json` atomically and emits `persisted.mode` of `create`, `unchanged`, or `overwrite`.
-- `gdh status` never writes to disk. It reads the cached inventory when present and live-scans when it is missing, corrupt, or schema-mismatched (degraded path).
-- `gdh onboard` may update `.gitignore`, but only for the GDH-managed `.gdh-state/` ignore section. It does not take ownership of `.godot/` ignore policy.
-- `gdh onboard` writes durable project truth (`.gdh/project.yaml`), derived state (`.gdh-state/inventory.json`), and skill files. It is not a synonym for scan.
-- Run `gdh scan` when you need fresh filesystem discovery: before first setup/onboard, after project structure changed, when the user asks what Godot projects/addons/scenes/tests were detected, or when cache freshness is explicitly in doubt. For normal readiness, migration, or validation questions, start with `gdh status` or `gdh authoring check` instead.
-
-Do not infer behavior from command names. Read the table, run the command, and check the envelope.
-

package/node_modules/@gdh/docs/dist/templates/guidance/project-migration.md.tpl

@@ -1,19 +0,0 @@
-# {{projectName}}: Project Migration
-
-Use this unit when `gdh status` or `gdh migrate` says the managed target needs migration, repair, or follow-up before normal implementation work.
-
-Follow this order:
-
-- run `gdh status` first and name the exact migration or degraded-compatibility reasons GDH reports
-- run `gdh migrate` before proposing manual edits so GDH can preview the supported repair or migration actions
-- only run `gdh migrate --apply` after explaining the planned changes and confirming the target path is correct
-- after apply, read `terminal.state` in the stdout JSON instead of guessing from prose summaries
-- if `terminal.state` is `healthy`, stop — no further migration action is required
-- if `terminal.state` is `follow_up_required`, run the surfaced `terminal.commands`, then run the surfaced `terminal.validationCommands` before treating the target as healthy
-- if `terminal.state` is `manual_review_required`, complete the surfaced `terminal.manualSteps`, then run the surfaced `terminal.validationCommands`; do not collapse review-gated work into an automatic repair
-- if runtime bridge compatibility remains degraded, enable the `GDH Runtime Bridge` plugin in the Godot editor so the addon can register `GDHBridge` itself
-- read `brokerTransition` when present: old pre-broker active sessions are unrecoverable, new broker-backed sessions are reconnectable, `.gdh-state/` remains untracked runtime state, and host-side broker migration alone does not require `gdh bridge repair`
-- if `terminal.state` is `blocked`, stop and review the surfaced reasons before making repo-local changes
-
-Do not hand-edit `project.godot` to register `GDHBridge`, and do not treat a migrated target as healthy until GDH's structured surfaces agree. GDH does not yet back up or reapply customized managed-surface patches automatically.
-