@voxgig/sdkgen 2.0.2 → 3.1.0

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,35 @@ 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.
+#
+# `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,34 @@ main: kit: feature: &: target: lean: deps: &: {
 
 # Publication: Reservoir (Lean package index) — declared, publish pending
 # (git-tag only for now).
+#
+# `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,23 @@ main: kit: feature: &: target: 'py-data': deps: &: {
 
 # Publication: pypi registry (declared, publish pending — git-tag only),
 # same posture as the `py` target.
+#
+# `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' }

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

@@ -24,11 +24,23 @@ main: kit: feature: &: target: rb: deps: &: {
 
 
 # Publication: rubygems 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: rb: publish: {
-  tag: { active: true }
   registry: {
-    state: 'pending'
-    active: false
     name: 'rubygems'
     url: 'https://rubygems.org'
     vault: { recipe: 'gem', alias: 'gem' }

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

@@ -25,13 +25,35 @@ main: kit: feature: &: target: rust: deps: &: {
 
 
 # Publication: crates.io 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: rust: publish: {
-  tag: { active: true }
   registry: {
-    state: 'pending'
-    active: false
     name: 'crates.io'
     url: 'https://crates.io'
     vault: { alias: 'cratesio', env: 'CARGO_REGISTRY_TOKEN' }
   }
 }
+
+
+# Feature source may be trimmed to the model's selection. The one template
+# needing the COMPLETE set is the cross-feature test suite, which `use`s
+# every feature module — so it is dropped alongside the features it
+# exercises whenever the set is trimmed.
+main: kit: target: rust: feature: {
+  trim: true
+  fullset: ['tests/feature_test.rs']
+}

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

@@ -25,13 +25,34 @@ main: kit: feature: &: target: scala: deps: &: {
 
 # Publication: tag-only for now (tag scala/vX.Y.Z) — Maven Central
 # publication via the Sonatype Central Portal is declared but pending.
+#
+# `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: scala: publish: {
-  tag: { active: true }
   registry: {
-    state: 'pending'
-    active: false
     name: 'maven-central'
     url: 'https://central.sonatype.com'
     vault: { recipe: 'maven', alias: 'central' }
   }
 }
+
+
+# Feature source is NOT trimmed to the model's selection here: the cross-
+# feature tests live inside sdktest/SdkTestMain.scala, the single test
+# entry point, so they cannot be dropped without losing every other test
+# too. Trimming stays off until that suite is split per feature.
+main: kit: target: scala: feature: {
+  trim: false
+}

package/project/.sdk/model/target/seneca-provider.aontu

@@ -0,0 +1,118 @@
+# Seneca provider target — a Seneca plugin that exposes this API's entities
+# as Seneca entities (`provider/<name>/<entity>`), layered on the sibling
+# `ts` SDK. It is not a language SDK in its own right, so every standard
+# generation phase is switched off below and Main_seneca-provider emits the
+# whole package, exactly as go-cli / go-mcp / py-data do.
+#
+# Requires the `ts` target in the same SDK project (Main throws when it is
+# absent): the plugin imports the published TypeScript SDK.
+#
+# UNLIKE the other consumer targets, this one generates into ITS OWN REPO.
+# A Seneca provider is an independently released npm package under the
+# @seneca scope, with its own LICENSE, CI workflow and release cadence, and
+# it depends on the SDK as an ordinary published dependency rather than by
+# path. Point it at that repo from the PROJECT model:
+#
+#   main: kit: target: 'seneca-provider': output: path: '../../seneca/seneca-acme-provider'
+#
+# Relative to the SDK repo root. Left unset here on purpose — every project's
+# provider repo is somewhere different, and a concrete value here would
+# CONFLICT with the project's rather than yield to it (see the publication
+# note below). Unset means the ordinary in-tree `<sdk-repo>/seneca-provider/`,
+# which is a usable default for a first look at the output.
+
+main: kit: target: 'seneca-provider': {
+
+  title: 'Seneca Provider'
+  ext: ts
+  comment: line: "//"
+  module: name: '$$name$$'
+  srcfeature: false
+
+  # Per-generation-phase activation. Mirrors py-data: every standard phase is
+  # off and Main emits the package. README, docs and tests ARE generated — by
+  # Main, not by the standard cmps, which assume an SDK-shaped package and
+  # would emit wrong content here.
+  phase: {
+    entity:     { active: false }
+    feature:    { active: false }
+    readme:     { active: false }
+    agentguide: { active: false }
+    test:       { active: false }
+  }
+
+  # `kind` is a COMMA-SEPARATED LIST of manifest sections, not a single one.
+  # collectDeps deduplicates by package name and this map is keyed by name, so
+  # a package belonging in two sections cannot be declared twice — it says so
+  # here instead. See `seneca` below for the case that forced it.
+  deps: &: {
+    kind: *'prod' | string
+  }
+
+  # The Seneca plugin contract. `@seneca/provider` supplies entityBuilder and
+  # the keymap message this plugin's `prepare` posts; the rest are the host
+  # framework a plugin runs inside and so are PEER deps — a plugin that
+  # bundled its own seneca would run against a different instance than the
+  # application it is loaded into.
+  #
+  # The ts SDK dependency is emitted by Main from the model's published
+  # package name, so it is not declared here.
+  deps: {
+    '@seneca/maintain':  { active: true, version: '^0.1.0', kind: prod }
+
+    '@seneca/env':       { active: true, version: '>=0.4',  kind: peer }
+    '@seneca/provider':  { active: true, version: '>=4',    kind: peer }
+
+    # PEER *and* DEV. Peer for the reason above — the plugin must attach to
+    # the host application's seneca instance. Dev because the generated test
+    # suite does `require('seneca')` itself, so a clean `npm install && npm
+    # test` in a fresh checkout has to produce one. Relying on npm's automatic
+    # peer installation instead is what dropping this from the manifest
+    # amounted to, and that is npm-version- and client-specific: pnpm and
+    # `--legacy-peer-deps` both leave the suite with no seneca to require.
+    'seneca':            { active: true, version: '>=3||>=4.0.0-rc2', kind: 'peer,dev' }
+
+    'seneca-entity':     { active: true, version: '>=26',   kind: peer }
+    'seneca-promisify':  { active: true, version: '>=3',    kind: peer }
+
+    '@seneca/doc':       { active: true, version: '^8.0.0', kind: dev }
+    '@types/node':       { active: true, version: '^24.0.0', kind: dev }
+    'seneca-msg-test':   { active: true, version: '^4.1.0', kind: dev }
+    'typescript':        { active: true, version: '^5.4.5', kind: dev }
+  }
+}
+
+
+# Feature-deps map slot — every target carries this so the same feature can
+# specify per-target dep variants.
+main: kit: feature: &: target: 'seneca-provider': deps: &: {
+  kind: *'prod' | string
+}
+
+
+# Publication: npm registry, under the @seneca scope rather than the SDK's
+# own. The package name is NOT derived from the SDK slug the way a language
+# target's is — a provider is `@seneca/<name>-provider` — so Main sets it
+# from the model and a project can pin it like any other.
+#
+# `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: 'seneca-provider': publish: {
+  registry: {
+    name: 'npm'
+    url: 'https://registry.npmjs.org'
+    vault: { recipe: 'npm', alias: 'npm' }
+  }
+}

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

@@ -23,13 +23,35 @@ main: kit: feature: &: target: swift: deps: &: {
 
 
 # Publication: SwiftPM registry is git-tag only (publish pending).
+#
+# `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: swift: publish: {
-  tag: { active: true }
   registry: {
-    state: 'pending'
-    active: false
     name: 'swiftpm'
     url: 'https://swift.org/package-manager'
     vault: { alias: 'swiftpm', env: 'SWIFTPM_TOKEN' }
   }
 }
+
+
+# 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 type — so it is dropped alongside the
+# features it exercises whenever the set is trimmed.
+main: kit: target: swift: feature: {
+  trim: true
+  fullset: ['Tests/ProjectNameSDKTests/FeatureTest.swift']
+}

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

@@ -27,11 +27,23 @@ main: kit: feature: &: target: ts: 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: ts: 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/zig.aontu

@@ -25,13 +25,35 @@ main: kit: feature: &: target: zig: deps: &: {
 # routes deploy-zig to the root tag-push recipe. WITHOUT it, Deploy.ts falls
 # through to `make -C zig publish` — but zig's Makefile has no `publish` target,
 # so the deploy fails. Mirror c.aontu exactly.
+#
+# `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: zig: publish: {
-  tag: { active: true }
   registry: {
-    state: 'pending'
-    active: false
     name: 'none'
     url: ''
     vault: { alias: 'none', env: 'NONE' }
   }
 }
+
+
+# Feature source is NOT trimmed to the model's selection here: root.zig
+# re-exports every feature type with @import("feature/<name>.zig"), and
+# build.zig names test/feature_test.zig explicitly, so a trimmed tree
+# fails to build. Trimming stays off until root.zig's feature exports are
+# driven from the model.
+main: kit: target: zig: feature: {
+  trim: false
+}

package/project/.sdk/src/cmp/c/Config_c.ts

@@ -90,17 +90,16 @@ voxgig_value* make_config(void) {
 Feature* make_feature(const char* name) {
 `)
 
-    // The C target ships the full transport/observability feature set as
-    // fixed runtime templates (tm/c/feature/*.c, declared in core/sdk.h), so
-    // make_feature must dispatch to every shipped feature — not only those the
-    // current API model happens to configure. Merge the model's feature names
-    // with the standard shipped set; emit in sorted order for byte-stability.
-    const SHIPPED_FEATURES = [
-      'audit', 'cache', 'clienttrack', 'debug', 'idempotency', 'log',
-      'metrics', 'netsim', 'paging', 'proxy', 'ratelimit', 'rbac', 'retry',
-      'streaming', 'telemetry', 'test', 'timeout',
-    ]
-    const featureNames = new Set<string>(SHIPPED_FEATURES)
+    // Dispatch to the features the MODEL declares, and only those.
+    //
+    // This used to merge in a hardcoded list of every feature the C target
+    // ships, on the reasoning that the runtime templates
+    // (tm/c/feature/*.c) are always present. `target add` now trims feature
+    // source to the model's selection, so that reasoning is false: a
+    // reference to `feature_timeout_new` for an undeclared feature is an
+    // unresolved symbol at LINK time — the whole test suite fails to link,
+    // which is how this was found. Sorted for byte-stability.
+    const featureNames = new Set<string>()
     each(feature, (f: any) => {
       if (f.name && f.name !== 'base') featureNames.add(f.name)
     })

package/project/.sdk/src/cmp/c/Entity_c.ts

@@ -46,7 +46,11 @@ const Entity = cmp(function Entity(props: any) {
           (a['#' + camelify(opname) + 'Op'] =
             !opnames.includes(opname) ?
               ({ indent }: any) => {
-                Content({ indent }, `static voxgig_value* ${evar}_${opname}(Entity* e, voxgig_value* reqarg, voxgig_value* ctrl, PNError** err) {
+                // The stub mirrors the real signature: ops resolve to the
+                // ENTITY (`list` to a NULL-terminated array of them), so an
+                // unsupported op declares the same return type as the vtable.
+                const ret = 'list' === opname ? 'Entity**' : 'Entity*'
+                Content({ indent }, `static ${ret} ${evar}_${opname}(Entity* e, voxgig_value* reqarg, voxgig_value* ctrl, PNError** err) {
   (void)e; (void)reqarg; (void)ctrl;
   *err = unsupported_op("${opname}", "${entity.name}");
   return NULL;