@voxgig/sdkgen 4.21.0 → 4.22.0

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

@@ -14,11 +14,6 @@ main: kit: target: kotlin: {
   # import nor the registry entry.
   provides: { sekreto: true, schema: true }
 
-  # Files earlier toolchains generated that this target has RETIRED
-  # (vendor-tag rollout): the struct-corpus runner class
-  # (test/RunnerSupport.kt is support-only and RETAINED, name unchanged
-  # so emitted call sites need no churn). `doctor` reports leftovers;
-  # `doctor prune` deletes them.
   superseded: [
     'test/StructRunner.kt'
   ]
@@ -27,10 +22,6 @@ main: kit: target: kotlin: {
     kind: *'prod' | string
   }
 
-  # struct is inlined under utility/struct — no external runtime dep.
-  # JSON parsing is the zero-dep utility/Json.kt; HTTP transport is
-  # java.net.http.HttpClient (JDK built-in). Tests need only JUnit,
-  # declared directly in the generated build.gradle.kts (test scope).
   deps: {}
 }
 
@@ -40,24 +31,6 @@ 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 overlay
-# (`model/project.aon`), which create-sdkgen creates once and never
-# overwrites — NOT `model/sdk.aon`, which it rewrites on every scaffold.
-#
-# 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.aon)
-# 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: {
   registry: {
     name: 'maven-central'
@@ -67,10 +40,6 @@ main: kit: target: kotlin: publish: {
 }
 
 
-# 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/lua.aon

@@ -8,21 +8,6 @@ main: kit: target: lua: {
   base: 'BASE'
   srcfeature: false
 
-  # Applicability (docs/design/feature-tags.md). A vendored sekreto port
-  # lives in this target's feature container (tm/lua/feature/secrets/), so
-  # a feature that resolves secrets through sekreto can apply here.
-  #
-  # What lua ships: the four built-in kinds (env, memory, dotenv, file) in
-  # the vendored core, and every plugin kind as a trimmable group. The
-  # plugin kinds reach `sekreto.plugins.net`, which runs a small COMPILED
-  # helper (feature/secrets/native/sekretonet.c, -lssl -lcrypto) because
-  # Lua 5.4 has no sockets and no TLS. The helper is vendored with the
-  # feature and built by the generated Makefile ONLY when a plugin group is
-  # active (Main_lua emits feature/secrets/native.mk then), so an SDK
-  # without secrets - or with the built-in chain alone - runs no compiler
-  # and links no OpenSSL. `sekreto.plugins.net` finds the binary through
-  # its own adapted helperpath() (vendor/routes.json), at
-  # feature/secrets/native/sekreto-net.
   provides: { sekreto: true, schema: true }
 
   # Files earlier toolchains generated that this target has RETIRED
@@ -49,23 +34,6 @@ 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 overlay
-# (`model/project.aon`), which create-sdkgen creates once and never
-# overwrites — NOT `model/sdk.aon`, which it rewrites on every scaffold.
-#
-# 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.aon)
-# 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: {
   registry: {
     name: 'luarocks'

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

@@ -8,22 +8,6 @@ main: kit: target: ocaml: {
   base: 'BASE'
   srcfeature: false
 
-  # Applicability (docs/design/feature-tags.md). A vendored sekreto port
-  # lives in this target's feature container (tm/ocaml/feature/secrets/:
-  # the sekreto core under sekreto/, the voxgig/plugin host under plugin/
-  # and the provider kinds under plugins/), so a feature that resolves
-  # secrets through sekreto can apply here.
-  #
-  # What ocaml ships: the four built-in kinds (env, memory, dotenv, file)
-  # in the vendored core, and every plugin kind as a trimmable group. The
-  # four HTTPS groups (vault, cloud, saas, aws) reach plugins/http.ml ->
-  # plugins/tls.ml, whose externals are bound in plugins/tls_stubs.c
-  # against OpenSSL (-lssl -lcrypto, and `ocamlc -custom` to carry the
-  # stub). That dependency is scoped INSIDE the gated feature: the
-  # generated feature/secrets/feature.mk (Main_ocaml) compiles the stub
-  # and links OpenSSL ONLY when a plugin group that needs a transport is
-  # active, so an SDK without secrets, or with the built-in chain alone,
-  # or with `secretspec` alone, runs no C compiler and links no OpenSSL.
   provides: { sekreto: true, schema: true }
 
   # Files earlier toolchains generated that this target has RETIRED
@@ -39,20 +23,6 @@ main: kit: target: ocaml: {
     kind: *'prod' | string
   }
 
-  # struct is vendored under utility/ (voxgig_struct.ml + vregex.ml) — the
-  # runtime is dependency-free: it compiles with the stock ocamlc, no opam
-  # packages, no dune. So there are no manifest dependencies.
-  #
-  # The CORE also bundles no HTTP transport (sdk_runtime.ml
-  # fetch_no_transport): a live request needs a caller-supplied
-  # `options.system.fetch`. The only external dependency an ocaml SDK can
-  # have arrives with the `secrets` feature, and only when a plugin group
-  # needing a transport is active: the vendored HTTPS kinds bind OpenSSL
-  # through plugins/tls_stubs.c, and the feature's token-exchange transport
-  # of last resort rides the same vendored HTTP client. The generated
-  # feature/secrets/feature.mk turns both on from the trimmed tree, so an
-  # SDK with secrets inactive, or with no plugin group, links the OCaml
-  # distribution alone (unix.cma for the dotenv/file built-ins).
   deps: {}
 }
 
@@ -62,23 +32,6 @@ 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 overlay
-# (`model/project.aon`), which create-sdkgen creates once and never
-# overwrites — NOT `model/sdk.aon`, which it rewrites on every scaffold.
-#
-# 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.aon)
-# 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: {
   registry: {
     name: 'opam'
@@ -88,23 +41,6 @@ main: kit: target: ocaml: publish: {
 }
 
 
-# Feature source IS trimmed to the model's selection. The eighteen pipeline
-# features live inside one template module (sdk_features.ml), which is not
-# feature source and is never a trim candidate - so for a long time there
-# was nothing per-feature to leave out and trim stayed off. `secrets`
-# changed that: it is the first ocaml feature carried as a CONTAINER
-# (feature/secrets_feature.ml, feature/secrets/ with the vendored sekreto
-# and voxgig/plugin trees, test/feature/secrets/), some 5.5k lines that a
-# project which never selected the feature must not carry. With trim on,
-# `target add ocaml` copies that container only when the project's model
-# selects `secrets`; the per-feature placeholder dirs under src/feature/
-# (never generated - Main_ocaml excludes src/) are trimmed on the same
-# rule, which is what every trim:true target does.
-#
-# fullset is EMPTY on purpose: test/t_feature.ml gates every block on
-# `has_feature`, and the harness only constructs features the generated
-# config knows, so the cross-feature suite compiles and runs against any
-# trimmed set. Nothing else references a feature by name.
 main: kit: target: ocaml: feature: {
   trim: true
   fullset: []

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

@@ -25,9 +25,6 @@ main: kit: target: perl: {
     kind: *'prod' | string
   }
 
-  # Zero non-core runtime deps: HTTP transport uses HTTP::Tiny and the
-  # struct utility is vendored under tm/perl/lib/Voxgig/Struct.pm (both
-  # pure-Perl / core) - no manifest deps needed.
   deps: {
   }
 }
@@ -38,23 +35,6 @@ 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 overlay
-# (`model/project.aon`), which create-sdkgen creates once and never
-# overwrites — NOT `model/sdk.aon`, which it rewrites on every scaffold.
-#
-# 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.aon)
-# 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: {
   registry: {
     name: 'cpan'

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

@@ -35,23 +35,6 @@ 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 overlay
-# (`model/project.aon`), which create-sdkgen creates once and never
-# overwrites — NOT `model/sdk.aon`, which it rewrites on every scaffold.
-#
-# 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.aon)
-# 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: {
   registry: {
     name: 'packagist'

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

@@ -1,12 +1,3 @@
-# Python Data target — a Python package that *consumes* the sibling Python
-# SDK (generated by the `py` target into the same SDK repo) and presents it
-# to data analysts working in notebooks (Colab, Jupyter) as pandas
-# DataFrames. It is not a language SDK in its own right, so the standard
-# per-entity / per-feature / readme / test generation phases are switched
-# off via the `phase` map below and Main_py-data emits the whole package.
-#
-# Requires the `py` target in the same SDK repo (Main_py-data throws when it
-# is absent), exactly as go-cli/go-mcp require `go`.
 
 main: kit: target: 'py-data': {
 
@@ -17,10 +8,6 @@ main: kit: target: 'py-data': {
   base: 'BASE'
   srcfeature: false
 
-  # Per-generation-phase activation. Mirrors go-cli/go-mcp: every standard
-  # phase is off and Main emits the package. README, agent guides 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 }
@@ -44,31 +31,11 @@ main: kit: target: 'py-data': {
 }
 
 
-# Feature-deps map slot — every target carries this so the same feature can
-# specify per-target dep variants.
 main: kit: feature: &: target: 'py-data': deps: &: {
   kind: *'prod' | string
 }
 
 
-# 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 overlay
-# (`model/project.aon`), which create-sdkgen creates once and never
-# overwrites — NOT `model/sdk.aon`, which it rewrites on every scaffold.
-#
-# 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.aon)
-# 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: {
   registry: {
     name: 'pypi'

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

@@ -37,23 +37,6 @@ 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 overlay
-# (`model/project.aon`), which create-sdkgen creates once and never
-# overwrites — NOT `model/sdk.aon`, which it rewrites on every scaffold.
-#
-# 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.aon)
-# 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: {
   registry: {
     name: 'pypi'

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

@@ -37,23 +37,6 @@ 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 overlay
-# (`model/project.aon`), which create-sdkgen creates once and never
-# overwrites — NOT `model/sdk.aon`, which it rewrites on every scaffold.
-#
-# 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.aon)
-# 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: {
   registry: {
     name: 'rubygems'

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

@@ -13,12 +13,6 @@ main: kit: target: rust: {
   # a feature that resolves secrets through sekreto can apply here.
   provides: { sekreto: true, schema: true }
 
-  # Files earlier toolchains generated that this target has RETIRED
-  # (vendor-tag rollout): the hand-written struct corpus runner, superseded
-  # by the vendored @voxgig/omni engine driven through
-  # tests/omni_resolver/mod.rs. `doctor` reports leftovers; `doctor prune`
-  # deletes them. (tests/common/mod.rs is NOT listed: it kept its name and
-  # its support half, and only the corpus engine inside it was retired.)
   superseded: [
     'tests/struct_runner/mod.rs'
   ]
@@ -27,8 +21,6 @@ main: kit: target: rust: {
     kind: *'prod' | string
   }
 
-  # struct is vendored under utility/voxgigstruct — no external dep.
-  # ureq is the blocking HTTP transport (the whole pipeline is synchronous).
   deps: {
     'ureq': { active: true, version: '2', kind: prod }
   }
@@ -40,23 +32,6 @@ 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 overlay
-# (`model/project.aon`), which create-sdkgen creates once and never
-# overwrites — NOT `model/sdk.aon`, which it rewrites on every scaffold.
-#
-# 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.aon)
-# 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: {
   registry: {
     name: 'crates.io'

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

@@ -12,33 +12,12 @@ main: kit: target: scala: {
   # secrets through sekreto can apply here.
   provides: { sekreto: true, schema: true }
 
-  # Retired by the move to the vendored @voxgig/omni corpus runner
-  # (vendor-tag rollout): NOTHING, deliberately, and the empty list says so
-  # rather than leaving the key off.
-  #
-  # Scala's corpus ENGINE was never a file of its own. It lived FUSED inside
-  # sdktest/StructCorpus.scala — `object Runner`'s own JSON reader, fixJson,
-  # deep equality, matchval/doMatch, resolveArgs, checkResult, handleError and
-  # runSet — and sdktest/PrimaryCorpus.scala drove the same object. Both files
-  # were rewritten IN PLACE onto sdktest/OmniResolver.scala, so both KEEP
-  # THEIR NAMES, `object Runner` keeps its name (the Makefile still runs
-  # `--main-class Runner`), and no emitted call site needed churn.
-  # sdktest/SdkTestSupport.scala is support-ONLY and is RETAINED, exactly as
-  # java's RunnerSupport.java and csharp's Runner.cs. There is therefore no
-  # whole-file leftover for `doctor` to report or `doctor prune` to delete.
   superseded: []
 
   deps: &: {
     kind: *'prod' | string
   }
 
-  # struct is inlined under utility/struct — no external runtime dep.
-  # JSON parsing is the zero-dep utility/Json.java; HTTP transport is
-  # java.net.http.HttpClient (JDK built-in). The corpus ENGINE is the vendored
-  # @voxgig/omni scala port under sdktest/vendor/omni — source, not a
-  # dependency, and scala-cli compiles it with everything else. The corpus
-  # runners, the omni smoke test and the pipeline tests are plain scala-cli
-  # mains (no test-framework dependency).
   deps: {}
 }
 
@@ -48,24 +27,6 @@ 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 overlay
-# (`model/project.aon`), which create-sdkgen creates once and never
-# overwrites — NOT `model/sdk.aon`, which it rewrites on every scaffold.
-#
-# 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.aon)
-# 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: {
   registry: {
     name: 'maven-central'
@@ -75,41 +36,6 @@ main: kit: target: scala: publish: {
 }
 
 
-# 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, and that file constructs fifteen feature classes BY NAME
-# (NetsimFeature, RetryFeature, TimeoutFeature, RatelimitFeature,
-# CacheFeature, ...), so a trim that dropped an unselected feature's source
-# would stop the whole suite compiling. Every other target that trims has a
-# `fullset` file to drop with it (java's test/FeatureTest.java, go's
-# test/feature_test.go); scala's equivalent is fused into SdkTestMain, so
-# `fullset: ['sdktest/SdkTestMain.scala']` would take 137 runtime assertions
-# with it. Trimming stays off until that suite is split per feature.
-#
-# WHAT THAT COSTS, stated rather than left to be discovered. Every feature's
-# source ships to every scala SDK whatever the model selected, and the
-# secrets feature is by far the largest: measured on a feature-OFF SDK it
-# adds 26 files / 6,443 lines - SecretsFeature.scala, the vendored sekreto
-# core (6 files) and voxgig/plugin core (16), and the two UNGROUPED plugin
-# files. Those two are the ones with teeth: plugins/Sigv4.scala links
-# javax.crypto for AWS HMAC-SHA256 request signing, and
-# plugins/Httpjson.scala carries both the shared HTTP client and `runcmd`,
-# a ProcessBuilder child-process launcher. Neither can join a plugin group -
-# four and eight provider kinds respectively compile against them, so any
-# group owning them would let another group's trim delete them (which is
-# exactly how Sigv4.scala broke the saas and cloud groups once).
-#
-# The NINE provider clients ARE trimmed, in both directions: Main_scala
-# applies pluginExcludes for an active feature's inactive groups, and every
-# declared group of a feature that is itself off - so a secrets-off SDK
-# carries no vault, cloud, saas, aws or secretspec client. Both ends are
-# pinned, in ts/test/generate.test.ts and in the generated suite itself
-# (SecretsTestMain's vocabulary case reads the compiled module set).
-#
-# Flipping trim on is therefore a THREE-part change, not a one-line one:
-# split the feature tests out of SdkTestMain.scala into a `fullset` file,
-# stop the Makefile naming a per-feature suite that may not have shipped,
-# and re-measure. It is deliberately not part of the secrets work.
 main: kit: target: scala: feature: {
   trim: false
 }

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

@@ -7,32 +7,8 @@ main: kit: target: swift: {
   base: 'BASE'
   srcfeature: false
 
-  # Applicability (docs/design/feature-tags.md). A vendored sekreto port
-  # lives in this target's feature container
-  # (tm/swift/Sources/ProjectNameSDK/feature/secrets/{plugin,sekreto,plugins}),
-  # so a feature that resolves secrets through sekreto can apply here. The
-  # three vendored trees are SEPARATE SwiftPM modules (VoxgigPlugin, Sekreto,
-  # SekretoPlugins - upstream's own module boundary, and load-bearing: the
-  # SDK, plugin and sekreto each declare a `Value`, a `Point` or a `Json`),
-  # which Package_swift declares only when the feature is active.
   provides: { sekreto: true, schema: true }
 
-  # Retired by the move to the vendored @voxgig/omni corpus runner
-  # (vendor-tag rollout): NOTHING, deliberately, and the empty list says so
-  # rather than leaving the key off.
-  #
-  # Swift's corpus ENGINE was never a file of its own. It lived inline in
-  # two places - `SdkRunner.runSet`/`matchDeep` inside
-  # Tests/ProjectNameSDKTests/Runner.swift, and a second, independent
-  # engine (`runset`/`canon`/`fixNull`) private to
-  # Tests/ProjectNameSDKTests/StructUtilityTest.swift. Both were rewritten
-  # IN PLACE onto Tests/ProjectNameSDKTests/OmniResolver.swift, so both
-  # files KEEP THEIR NAMES and every emitted call site needs no churn:
-  # Runner.swift is support-ONLY now (testJsonPath, makeCtxFromMap, fixCtx,
-  # errFromMap, and the deepEqual/matchString/errCode the behavioural
-  # suites use) and is RETAINED, exactly as csharp's Runner.cs and java's
-  # RunnerSupport.java. There is therefore no whole-file leftover for
-  # `doctor` to report or `doctor prune` to delete.
   superseded: []
 
   deps: &: {
@@ -50,23 +26,6 @@ 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 overlay
-# (`model/project.aon`), which create-sdkgen creates once and never
-# overwrites — NOT `model/sdk.aon`, which it rewrites on every scaffold.
-#
-# 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.aon)
-# 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: {
   registry: {
     name: 'swiftpm'

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

@@ -1,6 +1,6 @@
 
 main: kit: target: ts: {
-  
+
   title: TypeScript
   ext: ts
   comment: line: "//"
@@ -26,14 +26,10 @@ main: kit: target: ts: {
   ]
 
   deps: &: {
-    # TODO: fix aontu disjunctions!
-    kind: *'prod' | string # 'peer' |'dev'
+    kind: *'prod' | string
   }
-  
+
   deps: {
-    # dotenv was dropped when the generated entity tests moved to
-    # `loadEnvLocal` (tm/ts/test/utility.ts) — the SDK's last non-tooling
-    # dependency of any kind.
     'typescript': { active: true, version: '^5.9.3', kind: dev }
     '@types/node': { active: true, version: '^25.6.0', kind: dev }
   }
@@ -41,28 +37,10 @@ main: kit: target: ts: {
 
 
 main: kit: feature: &: target: ts: deps: &: {
-  # TODO: fix aontu disjunctions!
   kind: *'prod' | string # 'peer' |'dev'
 }
 
 
-# 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 overlay
-# (`model/project.aon`), which create-sdkgen creates once and never
-# overwrites — NOT `model/sdk.aon`, which it rewrites on every scaffold.
-#
-# 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.aon)
-# 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: {
   registry: {
     name: 'npm'