@voxgig/sdkgen 2.0.2 → 3.0.0

package/project/.sdk/model/target/c.aontu

@@ -25,13 +25,38 @@ main: kit: feature: &: target: c: deps: &: {
 
 
 # Publication: C has no central registry — publishing IS the git tag.
+#
+# `target add <t>` OVERWRITES this file, so a project must never set its
+# publication values here — voxgig-solardemo-sdk lost its pinned npm package
+# name exactly that way. Set them in the project's own model
+# (`model/sdk.aontu`), where they survive a resync.
+#
+# For that to work this file must LEAVE THOSE KEYS UNSET: in aontu a concrete
+# value does not yield to another concrete value, it CONFLICTS, and two
+# defaults conflict too. The schema (@voxgig/sdkgen/model/sdkgen.aontu)
+# already defaults `tag.active`, `registry.state`, `registry.active` and
+# `registry.package`, so a project's concrete value wins over the default and
+# repeating them here would only take that away.
+#
+# What remains below is per-target registry IDENTITY, which is not a project
+# choice and stays concrete.
 main: kit: target: c: publish: {
-  tag: { active: true }
   registry: {
-    state: 'pending'
-    active: false
     name: 'none'
     url: ''
     vault: { alias: 'none', env: 'NONE' }
   }
 }
+
+
+# Feature source may be trimmed to the model's selection. Two templates need
+# the COMPLETE set, so both are dropped alongside the features they exercise
+# whenever the set is trimmed:
+#   tests/feature_test.c      — calls every feature_*_new()
+#   tests/sdk_pipeline_test.c — drives the retry feature by NAME through the
+#                               options map, so it fails at RUNTIME rather
+#                               than at link time when retry is absent
+main: kit: target: c: feature: {
+  trim: true
+  fullset: ['tests/feature_test.c', 'tests/sdk_pipeline_test.c']
+}

package/project/.sdk/model/target/clojure.aontu

@@ -24,13 +24,34 @@ main: kit: feature: &: target: clojure: deps: &: {
 
 
 # Publication: Clojars registry (declared, publish pending — git-tag only).
+#
+# `target add <t>` OVERWRITES this file, so a project must never set its
+# publication values here — voxgig-solardemo-sdk lost its pinned npm package
+# name exactly that way. Set them in the project's own model
+# (`model/sdk.aontu`), where they survive a resync.
+#
+# For that to work this file must LEAVE THOSE KEYS UNSET: in aontu a concrete
+# value does not yield to another concrete value, it CONFLICTS, and two
+# defaults conflict too. The schema (@voxgig/sdkgen/model/sdkgen.aontu)
+# already defaults `tag.active`, `registry.state`, `registry.active` and
+# `registry.package`, so a project's concrete value wins over the default and
+# repeating them here would only take that away.
+#
+# What remains below is per-target registry IDENTITY, which is not a project
+# choice and stays concrete.
 main: kit: target: clojure: publish: {
-  tag: { active: true }
   registry: {
-    state: 'pending'
-    active: false
     name: 'clojars'
     url: 'https://clojars.org'
     vault: { alias: 'clojars' }
   }
 }
+
+
+# Feature source is NOT trimmed to the model's selection here: every
+# feature lives inside a single generated module (src/sdk/features.clj),
+# not in per-feature source files, so there is nothing per-feature to
+# leave out. Trimming waits on that module becoming model-driven.
+main: kit: target: clojure: feature: {
+  trim: false
+}

package/project/.sdk/model/target/cpp.aontu

@@ -24,12 +24,34 @@ main: kit: feature: &: target: cpp: deps: &: {
 
 
 # Publication: header-only; publishing is the git tag cpp/vX.Y.Z (no registry).
+#
+# `target add <t>` OVERWRITES this file, so a project must never set its
+# publication values here — voxgig-solardemo-sdk lost its pinned npm package
+# name exactly that way. Set them in the project's own model
+# (`model/sdk.aontu`), where they survive a resync.
+#
+# For that to work this file must LEAVE THOSE KEYS UNSET: in aontu a concrete
+# value does not yield to another concrete value, it CONFLICTS, and two
+# defaults conflict too. The schema (@voxgig/sdkgen/model/sdkgen.aontu)
+# already defaults `tag.active`, `registry.state`, `registry.active` and
+# `registry.package`, so a project's concrete value wins over the default and
+# repeating them here would only take that away.
+#
+# What remains below is per-target registry IDENTITY, which is not a project
+# choice and stays concrete.
 main: kit: target: cpp: publish: {
-  tag: { active: true }
   registry: {
-    state: 'pending'
-    active: false
     name: 'none'
     url: ''
   }
 }
+
+
+# Feature source may be trimmed to the model's selection. The one template
+# needing the COMPLETE set is the cross-feature test suite, which includes
+# every feature/<name>.hpp — so it is dropped alongside the features it
+# exercises whenever the set is trimmed.
+main: kit: target: cpp: feature: {
+  trim: true
+  fullset: ['test/feature_test.cpp']
+}

package/project/.sdk/model/target/csharp.aontu

@@ -23,13 +23,35 @@ main: kit: feature: &: target: csharp: deps: &: {
 
 
 # Publication: NuGet registry (declared, publish pending — git-tag only).
+#
+# `target add <t>` OVERWRITES this file, so a project must never set its
+# publication values here — voxgig-solardemo-sdk lost its pinned npm package
+# name exactly that way. Set them in the project's own model
+# (`model/sdk.aontu`), where they survive a resync.
+#
+# For that to work this file must LEAVE THOSE KEYS UNSET: in aontu a concrete
+# value does not yield to another concrete value, it CONFLICTS, and two
+# defaults conflict too. The schema (@voxgig/sdkgen/model/sdkgen.aontu)
+# already defaults `tag.active`, `registry.state`, `registry.active` and
+# `registry.package`, so a project's concrete value wins over the default and
+# repeating them here would only take that away.
+#
+# What remains below is per-target registry IDENTITY, which is not a project
+# choice and stays concrete.
 main: kit: target: csharp: publish: {
-  tag: { active: true }
   registry: {
-    state: 'pending'
-    active: false
     name: 'nuget'
     url: 'https://www.nuget.org'
     vault: { alias: 'nuget', env: 'NUGET_API_KEY' }
   }
 }
+
+
+# Feature source may be trimmed to the model's selection. The one template
+# needing the COMPLETE set is the cross-feature test suite, which
+# constructs every *Feature class — so it is dropped alongside the
+# features it exercises whenever the set is trimmed.
+main: kit: target: csharp: feature: {
+  trim: true
+  fullset: ['test/FeatureTest.cs']
+}

package/project/.sdk/model/target/dart.aontu

@@ -22,11 +22,23 @@ main: kit: feature: &: target: dart: deps: &: {
 
 
 # Publication: pub.dev registry (declared, publish pending — git-tag only).
+#
+# `target add <t>` OVERWRITES this file, so a project must never set its
+# publication values here — voxgig-solardemo-sdk lost its pinned npm package
+# name exactly that way. Set them in the project's own model
+# (`model/sdk.aontu`), where they survive a resync.
+#
+# For that to work this file must LEAVE THOSE KEYS UNSET: in aontu a concrete
+# value does not yield to another concrete value, it CONFLICTS, and two
+# defaults conflict too. The schema (@voxgig/sdkgen/model/sdkgen.aontu)
+# already defaults `tag.active`, `registry.state`, `registry.active` and
+# `registry.package`, so a project's concrete value wins over the default and
+# repeating them here would only take that away.
+#
+# What remains below is per-target registry IDENTITY, which is not a project
+# choice and stays concrete.
 main: kit: target: dart: publish: {
-  tag: { active: true }
   registry: {
-    state: 'pending'
-    active: false
     name: 'pub.dev'
     url: 'https://pub.dev'
     vault: { alias: 'pubdev', env: 'PUB_CREDENTIALS' }

package/project/.sdk/model/target/elixir.aontu

@@ -21,11 +21,23 @@ main: kit: feature: &: target: elixir: deps: &: {
 
 
 # Publication: hex registry (declared, publish pending — git-tag only).
+#
+# `target add <t>` OVERWRITES this file, so a project must never set its
+# publication values here — voxgig-solardemo-sdk lost its pinned npm package
+# name exactly that way. Set them in the project's own model
+# (`model/sdk.aontu`), where they survive a resync.
+#
+# For that to work this file must LEAVE THOSE KEYS UNSET: in aontu a concrete
+# value does not yield to another concrete value, it CONFLICTS, and two
+# defaults conflict too. The schema (@voxgig/sdkgen/model/sdkgen.aontu)
+# already defaults `tag.active`, `registry.state`, `registry.active` and
+# `registry.package`, so a project's concrete value wins over the default and
+# repeating them here would only take that away.
+#
+# What remains below is per-target registry IDENTITY, which is not a project
+# choice and stays concrete.
 main: kit: target: elixir: publish: {
-  tag: { active: true }
   registry: {
-    state: 'pending'
-    active: false
     name: 'hex'
     url: 'https://hex.pm'
     vault: { recipe: 'hex', alias: 'hex' }

package/project/.sdk/model/target/go-cli.aontu

@@ -43,6 +43,22 @@ main: kit: feature: &: target: 'go-cli': deps: &: {
 
 # Publication: tag-only — the Go module proxy resolves versions from the
 # go-cli/vX.Y.Z GitHub tag; there is no package registry to upload to.
+# Publication.
+#
+# `target add <t>` OVERWRITES this file, so a project must never set its
+# publication values here — voxgig-solardemo-sdk lost its pinned npm package
+# name exactly that way. Set them in the project's own model
+# (`model/sdk.aontu`), where they survive a resync.
+#
+# For that to work this file must LEAVE THOSE KEYS UNSET: in aontu a concrete
+# value does not yield to another concrete value, it CONFLICTS, and two
+# defaults conflict too. The schema (@voxgig/sdkgen/model/sdkgen.aontu)
+# already defaults `tag.active`, `registry.state`, `registry.active` and
+# `registry.package`, so a project's concrete value wins over the default and
+# repeating them here would only take that away.
+#
+# What remains below is per-target registry IDENTITY, which is not a project
+# choice and stays concrete.
 main: kit: target: 'go-cli': publish: {
-  tag: { active: true, via: 'root' }
+  tag: { via: 'root' }
 }

package/project/.sdk/model/target/go-mcp.aontu

@@ -37,6 +37,22 @@ main: kit: feature: &: target: 'go-mcp': deps: &: {
 
 # Publication: tag-only — the Go module proxy resolves versions from the
 # go-mcp/vX.Y.Z GitHub tag; there is no package registry to upload to.
+# Publication.
+#
+# `target add <t>` OVERWRITES this file, so a project must never set its
+# publication values here — voxgig-solardemo-sdk lost its pinned npm package
+# name exactly that way. Set them in the project's own model
+# (`model/sdk.aontu`), where they survive a resync.
+#
+# For that to work this file must LEAVE THOSE KEYS UNSET: in aontu a concrete
+# value does not yield to another concrete value, it CONFLICTS, and two
+# defaults conflict too. The schema (@voxgig/sdkgen/model/sdkgen.aontu)
+# already defaults `tag.active`, `registry.state`, `registry.active` and
+# `registry.package`, so a project's concrete value wins over the default and
+# repeating them here would only take that away.
+#
+# What remains below is per-target registry IDENTITY, which is not a project
+# choice and stays concrete.
 main: kit: target: 'go-mcp': publish: {
-  tag: { active: true, via: 'root' }
+  tag: { via: 'root' }
 }

package/project/.sdk/model/target/go.aontu

@@ -21,8 +21,18 @@ main: kit: feature: &: target: go: deps: &: {
 }
 
 
-# Publication: tag-only — the Go module proxy resolves versions from the
-# go/vX.Y.Z GitHub tag; there is no package registry to upload to.
-main: kit: target: go: publish: {
-  tag: { active: true }
+# Publication: a go/vX.Y.Z GitHub tag only — the Go proxy resolves from tags,
+# so there is no package registry to upload to. Nothing is set here: every
+# value is defaulted by the schema, and a project that needs to change one
+# sets it in its own model (`model/sdk.aontu`), which `target add <t>` does
+# not overwrite.
+
+
+# Feature source may be trimmed to the model's selection. The one template
+# needing the COMPLETE set is the cross-feature test suite, which
+# constructs every feature.New*Feature — so it is dropped alongside the
+# features it exercises whenever the set is trimmed.
+main: kit: target: go: feature: {
+  trim: true
+  fullset: ['test/feature_test.go']
 }

package/project/.sdk/model/target/haskell.aontu

@@ -38,13 +38,34 @@ main: kit: feature: &: target: haskell: deps: &: {
 
 
 # Publication: Hackage registry (declared, publish pending — git-tag only).
+#
+# `target add <t>` OVERWRITES this file, so a project must never set its
+# publication values here — voxgig-solardemo-sdk lost its pinned npm package
+# name exactly that way. Set them in the project's own model
+# (`model/sdk.aontu`), where they survive a resync.
+#
+# For that to work this file must LEAVE THOSE KEYS UNSET: in aontu a concrete
+# value does not yield to another concrete value, it CONFLICTS, and two
+# defaults conflict too. The schema (@voxgig/sdkgen/model/sdkgen.aontu)
+# already defaults `tag.active`, `registry.state`, `registry.active` and
+# `registry.package`, so a project's concrete value wins over the default and
+# repeating them here would only take that away.
+#
+# What remains below is per-target registry IDENTITY, which is not a project
+# choice and stays concrete.
 main: kit: target: haskell: publish: {
-  tag: { active: true }
   registry: {
-    state: 'pending'
-    active: false
     name: 'hackage'
     url: 'https://hackage.haskell.org'
     vault: { alias: 'hackage', env: 'HACKAGE_TOKEN' }
   }
 }
+
+
+# Feature source is NOT trimmed to the model's selection here: every
+# feature lives inside a single generated module (src/SdkFeatures.hs), not
+# in per-feature source files, so there is nothing per-feature to leave
+# out. Trimming waits on that module becoming model-driven.
+main: kit: target: haskell: feature: {
+  trim: false
+}

package/project/.sdk/model/target/java.aontu

@@ -25,13 +25,36 @@ main: kit: feature: &: target: java: deps: &: {
 
 # Publication: tag-only for now (tag java/vX.Y.Z) — Maven Central
 # publication via the Sonatype Central Portal is declared but pending.
+# Publication.
+#
+# `target add <t>` OVERWRITES this file, so a project must never set its
+# publication values here — voxgig-solardemo-sdk lost its pinned npm package
+# name exactly that way. Set them in the project's own model
+# (`model/sdk.aontu`), where they survive a resync.
+#
+# For that to work this file must LEAVE THOSE KEYS UNSET: in aontu a concrete
+# value does not yield to another concrete value, it CONFLICTS, and two
+# defaults conflict too. The schema (@voxgig/sdkgen/model/sdkgen.aontu)
+# already defaults `tag.active`, `registry.state`, `registry.active` and
+# `registry.package`, so a project's concrete value wins over the default and
+# repeating them here would only take that away.
+#
+# What remains below is per-target registry IDENTITY, which is not a project
+# choice and stays concrete.
 main: kit: target: java: publish: {
-  tag: { active: true }
   registry: {
-    state: 'pending'
-    active: false
     name: 'maven-central'
     url: 'https://central.sonatype.com'
     vault: { recipe: 'maven', alias: 'central' }
   }
 }
+
+
+# Feature source may be trimmed to the model's selection. The one template
+# needing the COMPLETE set is the cross-feature test suite, which
+# constructs every *Feature class — so it is dropped alongside the
+# features it exercises whenever the set is trimmed.
+main: kit: target: java: feature: {
+  trim: true
+  fullset: ['test/FeatureTest.java']
+}

package/project/.sdk/model/target/js.aontu

@@ -24,11 +24,23 @@ main: kit: feature: &: target: js: deps: &: {
 
 
 # Publication: npm registry (declared, publish pending — git-tag only).
+#
+# `target add <t>` OVERWRITES this file, so a project must never set its
+# publication values here — voxgig-solardemo-sdk lost its pinned npm package
+# name exactly that way. Set them in the project's own model
+# (`model/sdk.aontu`), where they survive a resync.
+#
+# For that to work this file must LEAVE THOSE KEYS UNSET: in aontu a concrete
+# value does not yield to another concrete value, it CONFLICTS, and two
+# defaults conflict too. The schema (@voxgig/sdkgen/model/sdkgen.aontu)
+# already defaults `tag.active`, `registry.state`, `registry.active` and
+# `registry.package`, so a project's concrete value wins over the default and
+# repeating them here would only take that away.
+#
+# What remains below is per-target registry IDENTITY, which is not a project
+# choice and stays concrete.
 main: kit: target: js: publish: {
-  tag: { active: true }
   registry: {
-    state: 'pending'
-    active: false
     name: 'npm'
     url: 'https://registry.npmjs.org'
     vault: { recipe: 'npm', alias: 'npm' }

package/project/.sdk/model/target/kotlin.aontu

@@ -25,13 +25,36 @@ main: kit: feature: &: target: kotlin: deps: &: {
 
 # Publication: tag-only for now (tag kotlin/vX.Y.Z) — Maven Central
 # publication via the Sonatype Central Portal is declared but pending.
+# Publication.
+#
+# `target add <t>` OVERWRITES this file, so a project must never set its
+# publication values here — voxgig-solardemo-sdk lost its pinned npm package
+# name exactly that way. Set them in the project's own model
+# (`model/sdk.aontu`), where they survive a resync.
+#
+# For that to work this file must LEAVE THOSE KEYS UNSET: in aontu a concrete
+# value does not yield to another concrete value, it CONFLICTS, and two
+# defaults conflict too. The schema (@voxgig/sdkgen/model/sdkgen.aontu)
+# already defaults `tag.active`, `registry.state`, `registry.active` and
+# `registry.package`, so a project's concrete value wins over the default and
+# repeating them here would only take that away.
+#
+# What remains below is per-target registry IDENTITY, which is not a project
+# choice and stays concrete.
 main: kit: target: kotlin: publish: {
-  tag: { active: true }
   registry: {
-    state: 'pending'
-    active: false
     name: 'maven-central'
     url: 'https://central.sonatype.com'
     vault: { recipe: 'maven', alias: 'central' }
   }
 }
+
+
+# Feature source may be trimmed to the model's selection. The one template
+# needing the COMPLETE set is the cross-feature test suite, which
+# constructs every *Feature class — so it is dropped alongside the
+# features it exercises whenever the set is trimmed.
+main: kit: target: kotlin: feature: {
+  trim: true
+  fullset: ['test/FeatureTest.kt']
+}

package/project/.sdk/model/target/lean.aontu

@@ -39,13 +39,35 @@ main: kit: feature: &: target: lean: deps: &: {
 
 # Publication: Reservoir (Lean package index) — declared, publish pending
 # (git-tag only for now).
+# Publication.
+#
+# `target add <t>` OVERWRITES this file, so a project must never set its
+# publication values here — voxgig-solardemo-sdk lost its pinned npm package
+# name exactly that way. Set them in the project's own model
+# (`model/sdk.aontu`), where they survive a resync.
+#
+# For that to work this file must LEAVE THOSE KEYS UNSET: in aontu a concrete
+# value does not yield to another concrete value, it CONFLICTS, and two
+# defaults conflict too. The schema (@voxgig/sdkgen/model/sdkgen.aontu)
+# already defaults `tag.active`, `registry.state`, `registry.active` and
+# `registry.package`, so a project's concrete value wins over the default and
+# repeating them here would only take that away.
+#
+# What remains below is per-target registry IDENTITY, which is not a project
+# choice and stays concrete.
 main: kit: target: lean: publish: {
-  tag: { active: true }
   registry: {
-    state: 'pending'
-    active: false
     name: 'reservoir'
     url: 'https://reservoir.lean-lang.org'
     vault: { alias: 'reservoir', env: 'RESERVOIR_TOKEN' }
   }
 }
+
+
+# Feature source is NOT trimmed to the model's selection here: every
+# feature lives inside a single generated module (src/SdkFeatures.lean),
+# not in per-feature source files, so there is nothing per-feature to
+# leave out. Trimming waits on that module becoming model-driven.
+main: kit: target: lean: feature: {
+  trim: false
+}

package/project/.sdk/model/target/lua.aontu

@@ -24,11 +24,23 @@ main: kit: feature: &: target: lua: deps: &: {
 
 
 # Publication: luarocks registry (declared, publish pending — git-tag only).
+#
+# `target add <t>` OVERWRITES this file, so a project must never set its
+# publication values here — voxgig-solardemo-sdk lost its pinned npm package
+# name exactly that way. Set them in the project's own model
+# (`model/sdk.aontu`), where they survive a resync.
+#
+# For that to work this file must LEAVE THOSE KEYS UNSET: in aontu a concrete
+# value does not yield to another concrete value, it CONFLICTS, and two
+# defaults conflict too. The schema (@voxgig/sdkgen/model/sdkgen.aontu)
+# already defaults `tag.active`, `registry.state`, `registry.active` and
+# `registry.package`, so a project's concrete value wins over the default and
+# repeating them here would only take that away.
+#
+# What remains below is per-target registry IDENTITY, which is not a project
+# choice and stays concrete.
 main: kit: target: lua: publish: {
-  tag: { active: true }
   registry: {
-    state: 'pending'
-    active: false
     name: 'luarocks'
     url: 'https://luarocks.org'
     vault: { alias: 'luarocks', env: 'LUAROCKS_API_KEY' }

package/project/.sdk/model/target/ocaml.aontu

@@ -24,13 +24,34 @@ main: kit: feature: &: target: ocaml: deps: &: {
 
 
 # Publication: opam registry (declared, publish pending — git-tag only).
+#
+# `target add <t>` OVERWRITES this file, so a project must never set its
+# publication values here — voxgig-solardemo-sdk lost its pinned npm package
+# name exactly that way. Set them in the project's own model
+# (`model/sdk.aontu`), where they survive a resync.
+#
+# For that to work this file must LEAVE THOSE KEYS UNSET: in aontu a concrete
+# value does not yield to another concrete value, it CONFLICTS, and two
+# defaults conflict too. The schema (@voxgig/sdkgen/model/sdkgen.aontu)
+# already defaults `tag.active`, `registry.state`, `registry.active` and
+# `registry.package`, so a project's concrete value wins over the default and
+# repeating them here would only take that away.
+#
+# What remains below is per-target registry IDENTITY, which is not a project
+# choice and stays concrete.
 main: kit: target: ocaml: publish: {
-  tag: { active: true }
   registry: {
-    state: 'pending'
-    active: false
     name: 'opam'
     url: 'https://opam.ocaml.org'
     vault: { alias: 'opam', env: 'OPAM_PUBLISH_TOKEN' }
   }
 }
+
+
+# Feature source is NOT trimmed to the model's selection here: every
+# feature lives inside a single generated module (sdk_features.ml), not in
+# per-feature source files, so there is nothing per-feature to leave out.
+# Trimming waits on that module becoming model-driven.
+main: kit: target: ocaml: feature: {
+  trim: false
+}

package/project/.sdk/model/target/perl.aontu

@@ -25,11 +25,23 @@ main: kit: feature: &: target: perl: deps: &: {
 
 
 # Publication: CPAN registry (declared, publish pending — git-tag only).
+#
+# `target add <t>` OVERWRITES this file, so a project must never set its
+# publication values here — voxgig-solardemo-sdk lost its pinned npm package
+# name exactly that way. Set them in the project's own model
+# (`model/sdk.aontu`), where they survive a resync.
+#
+# For that to work this file must LEAVE THOSE KEYS UNSET: in aontu a concrete
+# value does not yield to another concrete value, it CONFLICTS, and two
+# defaults conflict too. The schema (@voxgig/sdkgen/model/sdkgen.aontu)
+# already defaults `tag.active`, `registry.state`, `registry.active` and
+# `registry.package`, so a project's concrete value wins over the default and
+# repeating them here would only take that away.
+#
+# What remains below is per-target registry IDENTITY, which is not a project
+# choice and stays concrete.
 main: kit: target: perl: publish: {
-  tag: { active: true }
   registry: {
-    state: 'pending'
-    active: false
     name: 'cpan'
     url: 'https://www.cpan.org'
     vault: { recipe: 'cpan', alias: 'cpan' }

package/project/.sdk/model/target/php.aontu

@@ -22,11 +22,23 @@ main: kit: feature: &: target: php: deps: &: {
 
 
 # Publication: packagist registry (declared, publish pending — git-tag only).
+#
+# `target add <t>` OVERWRITES this file, so a project must never set its
+# publication values here — voxgig-solardemo-sdk lost its pinned npm package
+# name exactly that way. Set them in the project's own model
+# (`model/sdk.aontu`), where they survive a resync.
+#
+# For that to work this file must LEAVE THOSE KEYS UNSET: in aontu a concrete
+# value does not yield to another concrete value, it CONFLICTS, and two
+# defaults conflict too. The schema (@voxgig/sdkgen/model/sdkgen.aontu)
+# already defaults `tag.active`, `registry.state`, `registry.active` and
+# `registry.package`, so a project's concrete value wins over the default and
+# repeating them here would only take that away.
+#
+# What remains below is per-target registry IDENTITY, which is not a project
+# choice and stays concrete.
 main: kit: target: php: publish: {
-  tag: { active: true }
   registry: {
-    state: 'pending'
-    active: false
     name: 'packagist'
     url: 'https://packagist.org'
     vault: { alias: 'packagist', env: 'PACKAGIST_API_TOKEN' }

package/project/.sdk/model/target/py-data.aontu

@@ -52,11 +52,24 @@ main: kit: feature: &: target: 'py-data': deps: &: {
 
 # Publication: pypi registry (declared, publish pending — git-tag only),
 # same posture as the `py` target.
+# Publication.
+#
+# `target add <t>` OVERWRITES this file, so a project must never set its
+# publication values here — voxgig-solardemo-sdk lost its pinned npm package
+# name exactly that way. Set them in the project's own model
+# (`model/sdk.aontu`), where they survive a resync.
+#
+# For that to work this file must LEAVE THOSE KEYS UNSET: in aontu a concrete
+# value does not yield to another concrete value, it CONFLICTS, and two
+# defaults conflict too. The schema (@voxgig/sdkgen/model/sdkgen.aontu)
+# already defaults `tag.active`, `registry.state`, `registry.active` and
+# `registry.package`, so a project's concrete value wins over the default and
+# repeating them here would only take that away.
+#
+# What remains below is per-target registry IDENTITY, which is not a project
+# choice and stays concrete.
 main: kit: target: 'py-data': publish: {
-  tag: { active: true }
   registry: {
-    state: 'pending'
-    active: false
     name: 'pypi'
     url: 'https://pypi.org'
     vault: { recipe: 'pypi', alias: 'pypi' }

package/project/.sdk/model/target/py.aontu

@@ -24,11 +24,23 @@ main: kit: feature: &: target: py: deps: &: {
 
 
 # Publication: pypi registry (declared, publish pending — git-tag only).
+#
+# `target add <t>` OVERWRITES this file, so a project must never set its
+# publication values here — voxgig-solardemo-sdk lost its pinned npm package
+# name exactly that way. Set them in the project's own model
+# (`model/sdk.aontu`), where they survive a resync.
+#
+# For that to work this file must LEAVE THOSE KEYS UNSET: in aontu a concrete
+# value does not yield to another concrete value, it CONFLICTS, and two
+# defaults conflict too. The schema (@voxgig/sdkgen/model/sdkgen.aontu)
+# already defaults `tag.active`, `registry.state`, `registry.active` and
+# `registry.package`, so a project's concrete value wins over the default and
+# repeating them here would only take that away.
+#
+# What remains below is per-target registry IDENTITY, which is not a project
+# choice and stays concrete.
 main: kit: target: py: publish: {
-  tag: { active: true }
   registry: {
-    state: 'pending'
-    active: false
     name: 'pypi'
     url: 'https://pypi.org'
     vault: { recipe: 'pypi', alias: 'pypi' }