@neocompose/cli 0.73.2 → 0.75.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@neocompose/cli",
-  "version": "0.73.2",
+  "version": "0.75.0",
   "description": "Neo Compose native project-source CLI with bidirectional sync.",
   "license": "MIT",
   "type": "module",

package/skills/neocompose-cli/SKILL.md

@@ -9,7 +9,7 @@ description: >-
   `@neocompose/cli` or `node cli/bin/neo.mjs` in the neo-compose repository.
 ---
 
-<!-- reviewed-through-cli: 0.73.2 -->
+<!-- reviewed-through-cli: 0.75.0 -->
 
 # Neo Compose CLI
 

package/skills/neocompose-cli/references/cli-development.md

@@ -118,21 +118,18 @@ wrappers.
 The marker near the top of `SKILL.md` must exactly match the package version:
 
 ```html
-<!-- reviewed-through-cli: 0.73.2 -->
+<!-- reviewed-through-cli: 0.75.0 -->
 ```
 
 The quoted version above is checked too, so this instruction cannot go stale
 while the skill advances.
 
-For every CLI version bump, audit all behavior and public syntax added since the
-marker, update the skill/references where needed, then advance the marker. Never
-bump it mechanically. `npm run doctor` and package verification both fail when
-it drifts, so the audit lands in the same change as the bump rather than
-blocking a publish after the release has merged.
-
-Every version bump also gets a `CHANGELOG.md` entry, newest first, under a
-`## [version] - date` heading. The same check grades it, so an undocumented
-release fails alongside a stale marker.
+For every CLI behavior change, audit the affected skill/references in the same
+feature PR and add a unique `.changeset/*.md` release note. Leave versions,
+changelogs, and these markers unchanged. `npm run version:packages` combines
+fragments in a release PR and advances the markers after those feature reviews.
+`npm run doctor` and package verification still check marker/version agreement
+and the newest changelog entry. See `.changeset/README.md` in the repository.
 
 Keep `agents/openai.yaml` and every directly linked reference inside the
 published `skills/neocompose-cli/` tree. Keep the frontmatter limited to

package/skills/neocompose-cli/references/neoscript.md

@@ -557,7 +557,24 @@ receiver.Handler`; use `-=` to remove the same receiver/handler pair. Handlers
 are noncapturing, return void, and accept the field's type. Bindings to Session
 receivers stay Session-only. Gameplay hosts dispatch after the write batch.
 Authoring, replay, migration, and dialogue dry-run hosts retain wiring without
-invoking callbacks.
+invoking callbacks. `owner.Field.OnChanged.Clear()` removes every handler,
+including `@listeners` defaults, in both Save and Session wiring.
+
+Instance getters take the same syntax, for example
+`this._quantity.Value.OnChanged += this.QuantityChanged`. A getter
+subscription lives only in memory for the play session, so subscribe from a
+function, effect, lifecycle hook, or dialogue action, never a constructor,
+initializer, or migration. Subscribing reads the getter once. The SDK calls the
+handler with a fresh result whenever something that read depended on changes,
+even if the result is equal, and several changes before the next read call it
+once. `Clear()` ends the subscription, and a constructor can't call it on a
+getter. Static getters, `base.Value`, and `@listeners` can't observe a getter.
+`neo test` dispatches getter subscriptions the same way, treating the test body
+as the host: handlers run after each of its statements, so the next statement
+sees their effects. A getter that reads through `Clone()` or a grid query can
+run more often in `neo test` than in Unity: any write but its own handlers'
+counts as a change. Other TypeScript hosts validate getter subscriptions and
+never call the handler.
 
 Persist wiring on the owning class value with named arguments, for example: