@neocompose/cli 0.38.5 → 0.39.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@neocompose/cli",
-  "version": "0.38.5",
+  "version": "0.39.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.38.5 -->
+<!-- reviewed-through-cli: 0.39.0 -->
 
 # Neo Compose CLI
 

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

@@ -83,7 +83,7 @@ wrappers.
 The marker near the top of `SKILL.md` must exactly match the package version:
 
 ```html
-<!-- reviewed-through-cli: 0.38.5 -->
+<!-- reviewed-through-cli: 0.39.0 -->
 ```
 
 The quoted version above is checked too, so this instruction cannot go stale

package/skills/neocompose-cli/references/commands-and-sync.md

@@ -94,6 +94,13 @@ rows its own file projection holds, so the plan would delete live server rows.
 Nothing is planned in that state; run `neo pull` and retry. The same message
 as a warning reports the inconsistency without blocking.
 
+When pull conflicts with a server-side deletion, keeping the authored record
+restores it as an explicit create guarded by an absent-record CAS check;
+removing it from the resolved source accepts the deletion without sending a
+write. Pull also warns immediately when a conflicted record's retained local
+base strands newly downloaded descendant value rows. Resolve that conflict
+with `neo resolve --mine` or `neo resolve --theirs` before pushing.
+
 For `base-hash-conflict`, pull and merge. For `version-bump-required`, inspect
 the classification and use `neo push --accept-bump` only when the bump is
 intended.

package/skills/neocompose-cli/references/declarations-and-construction.md

@@ -44,7 +44,7 @@ interface INamed {
 @storage(allowed: .Immutable)
 abstract class Item<TContext extends SomeClass> : INamed {
   @id("item-name-id")
-  @settings(localizable: true, searchKey: true)
+  @settings(searchBy: .MemberKey)
   public virtual string Name = "";
 
   @id("item-use-id")
@@ -80,17 +80,18 @@ that does not authorize copying the annotation onto authored records.
 
 Use context-aware typed annotations:
 
-- `@settings(...)` for localizable/search/index/editor constraints.
+- `@settings(...)` for format/search/selection/editor constraints.
 - `@storage(allowed: ...)` on classes and storage keys on members.
-- `@locked` for author-protected declarations supported by the contract.
-- `@hidden` only on a class; absence means visible.
+- `@visibility(.Hidden)` only on a class; absence means visible.
+- Stateful settings use contextual enum cases, such as
+  `@settings(format: .Plain)` and `@settings(selection: .Multi)`.
 - `@relations(...)` only on the source class of a specialized direct relation.
 
 Use numeric literals for numeric limits. Keep annotations separate instead of
 inventing a generic metadata bag.
 
-`@index(member: Field, unique: ...)` and
-`@column(member: Field, width: ..., hidden: ..., frozen: ..., wrapContent: ...)`
+`@index(member: Field, kind: .Unique)` and
+`@column(member: Field, width: ..., visibility: ..., pin: ..., overflow: ...)`
 are repeatable List annotations. `member:` is a bare field name on the entry
 class. An index accepts a non-localizable string or single-select enum. A column
 may target `__other__` for the default layout of subclass-added fields.

package/skills/neocompose-cli/references/values-identities-and-references.md

@@ -19,7 +19,6 @@ The root member name, type, member ID, lock, and storage metadata are read-only.
 ```neo
 Root root = new() {
   @id("root-assets-member-id")
-  @locked
   @storage(allowed: .Immutable)
   Assets Assets = new() {
     Outposts = [Assets.Capitol],