@neocompose/cli 0.47.1 → 0.48.0

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## [0.48.0] - 2026-09-10
+
+- Preserve current declaration and managed asset paths through pull, force, and reset, including files moved since the previous synchronization.
+- Support typed local initializer declarations in any project folder, with one owner per aggregate and explicit `Reference(NAME)` uses. Pull preserves extracted initializers and aliases; divergent scalar uses retain the server values.
+- Add shared editor actions to extract an initializer into a file, inline its sole use, or duplicate it with fresh nested identities.
+- Place newly encountered system declarations in their category's `System` subfolder, including classes, enums, interfaces, templates, localization statuses, and priority/dialogue groups.
+- Recognize migration headers outside `Migrations` and preserve migration ordering with `@order`.
+
 ## [0.47.1] - 2026-09-09
 
 ### Changed

package/README.md

@@ -57,9 +57,9 @@ neo/
   neo.json                         # formatVersion: 4
   Project.neo                      # project defaults/settings
   Root.neo                         # protected root shape; editable root values
-  Classes/
-  Interfaces/
-  Enums/
+  Classes/{System/, ...}
+  Interfaces/{System/, ...}
+  Enums/{System/, ...}
   Relations.neo                    # generic project relations, when present
   Templates/
   Localization.neo
@@ -105,6 +105,47 @@ In Unity projects, `neo.json` may use `unityConfigPath` instead of storing
 `projectId` and `versionId`. The referenced `NeoComposeConfig.asset` then owns
 those IDs and receives branch/version switches.
 
+### Organize source locally
+
+Move `.neo` and `.neoflow` files into any project folder, and group declarations
+in files as you prefer. Keep existing IDs. Pull, force, and reset read your
+current placement before applying server state. New server declarations use
+the default folders. System declarations use a `System` subfolder, such as
+`Classes/System`, `Enums/System`, or `Interfaces/System`. Ownership comes from
+the reserved system identity, so project types keep their normal defaults.
+Managed images and audio can also move. Update their typed registry paths.
+
+Extract large Root or static initializers into typed declarations without imports:
+
+```neo
+// Configuration/ProjectSortingLayers.neo
+List<NeoSortingLayer> SORTING_LAYERS = [
+  new NeoSortingLayer() { Name = "Default" }
+];
+
+// Inside the Root Assets initializer
+SortingLayers = SORTING_LAYERS
+```
+
+Existing nested `@id` annotations stay with the extracted initializer. The
+consuming member keeps its value ID; no ID is required at the use. An aggregate
+has one owning assignment. Additional references use `Reference(NAME)` where
+the member supports references. Independent copies need fresh nested IDs;
+the editor's duplicate action removes the old IDs. Scalars may have several
+owners. If web edits make those values differ, pull inlines the differing uses.
+
+The shared language service offers extract-to-file for a selected complete
+initializer, inline for a sole use, and duplicate. These declarations are local
+project setup and do not create runtime globals. Use them as complete value
+initializers; using their names inside executable expressions such as
+`BASE + 1` is rejected. Initializer cycles and ambiguous
+aggregate ownership fail validation before synchronization. Fix source errors
+before resetting a checkout with extracted initializers so their layout can be
+recovered safely.
+
+Migrations can move too. Keep their `/// @migration` header and `/// @order N`
+directive, or retain the numeric filename prefix for ordering.
+
 ## Native Neo authoring
 
 Classes, interfaces, and enums are top-level declarations. Schema functions,