@skillcap/gdh 0.9.0 → 0.11.0

package/INSTALL-BUNDLE.json

@@ -1,5 +1,5 @@
 {
   "product": "GDH",
-  "version": "0.9.0",
+  "version": "0.11.0",
   "installMode": "packaged_install"
 }

package/README.md

@@ -12,10 +12,16 @@ GDH detects your Godot project, configures your AI agents, and gives them the co
 ## Install
 
 ```sh
-npx -y @skillcap/gdh@0.9.0 setup
+npx -y @skillcap/gdh@0.11.0 setup
 ```
 
-Replace `0.9.0` with the GDH version you want to pin this project to. `gdh setup` records the pinned version in `.gdh/project.yaml`; every managed surface generated from that config invokes GDH at that exact pinned version, so future sessions stay reproducible.
+Replace `0.11.0` with the GDH version you want to pin this project to. `gdh setup` records the pinned version in `.gdh/project.yaml`; every managed surface generated from that config invokes GDH at that exact pinned version, so future sessions stay reproducible.
+
+From `0.9.0` onward, the shipped package also carries bounded release-span update metadata in `RELEASE-SPAN-UPDATE-CONTRACTS.json` so update flows can explain release-specific migration steps without reading repo-only `docs/releases/` files at target runtime.
+
+The current update flow is preview-first and sequential on apply: `gdh self-update --dry-run` emits machine-readable release-span preview data, and approved apply runs one ordered update -> migrate -> validate path. Apply now ends in an explicit terminal class: `healthy`, `follow_up_required`, `manual_review_required`, or `blocked`.
+
+Automatic backup and patch reapply for customized managed surfaces are not shipped yet; that preservation work remains future backlog, not part of the current update contract.
 
 The full install and update contract lives in [install-and-update.md](docs/development/install-and-update.md).
 
@@ -30,7 +36,7 @@ The full install and update contract lives in [install-and-update.md](docs/devel
 
 ```sh
 # 1. Run setup in your Godot project
-npx -y @skillcap/gdh@0.9.0 setup
+npx -y @skillcap/gdh@0.11.0 setup
 
 # 2. Open your AI agent (Claude, Cursor, Codex) in the repo
 
@@ -83,7 +89,7 @@ Normal usage happens through your AI agent, not by memorizing CLI commands.
 2. The agent uses GDH surfaces to check readiness, pick validation, run checks
 3. You intervene only for narrow decisions or missing environment input
 
-The CLI exists for advanced operators, debugging, and automation. See [Advanced CLI Usage](docs/development/advanced-cli-usage.md).
+The CLI exists for advanced operators, debugging, and automation. Update preview now uses a structured `preview` payload instead of changelog scraping, and update apply surfaces exact terminal follow-up data in `migration` + `terminal`. See [Advanced CLI Usage](docs/development/advanced-cli-usage.md).
 
 ## Documentation
 
@@ -94,7 +100,7 @@ The CLI exists for advanced operators, debugging, and automation. See [Advanced
 
 ## Status
 
-GDH now ships the current `0.9.0` release line and remains ready for broader internal use within the documented support contract. The current release line is `0.9.0` at the `broader_internal_release` stage.
+GDH now ships the current `0.11.0` release line and remains ready for broader internal use within the documented support contract. The current release line is `0.11.0` at the `broader_internal_release` stage.
 
 The release-stage label applies only to the documented support window in [runtime-support-matrix.md](docs/development/runtime-support-matrix.md) and [runtime-release-readiness.md](docs/development/runtime-release-readiness.md). It is not a blanket claim that every Godot project shape is supported or that this implementation checkout should behave like a GDH-managed target repo.
 
@@ -120,3 +126,4 @@ If you are working on the GDH implementation repo itself, use these contributor
 When cutting a GDH release in this repo with Claude, Codex, or Cursor, use `/gdh-release` so the agent loads the canonical release guidance and runs `corepack yarn check:public-release` before `release:apply`. Use `/gdh-migration-verify` for the dedicated migration-proof step before the final release gate. Use `/gdh-publish` only when you explicitly want an already-cut release published to npm.
 
 Release history lives in the generated root [CHANGELOG.md](CHANGELOG.md); curated release notes live under [docs/releases/](docs/releases/README.md).
+Each live release line also carries a machine-readable update contract in [docs/releases/migrations/](docs/releases/migrations/README.md), which is compiled into the packaged `RELEASE-SPAN-UPDATE-CONTRACTS.json` asset for runtime update guidance.