@voxgig/sdkgen 4.21.0 → 4.23.0

package/project/.sdk/src/cmp/swift/PrepareAuth_swift.ts

@@ -14,131 +14,21 @@ import {
 import { swiftString, swiftTargetDir } from './utility_swift'
 
 
-// WHERE THE CREDENTIAL GOES IS A FACT ABOUT THE API, so it is generated
-// rather than templated. The swift peer of cmp/ts/PrepareAuth_ts.ts; read
-// that one first, it carries the full account of the defect.
-//
-// apidef has always resolved the scheme's `in` and `name` into
-// `main.kit.info.security` — joplin's says `in: "query", name: "token"` —
-// and generation dropped both, so the SDK sent a header the API does not
-// read and never sent the query parameter it does. Four repos in the cedar
-// fleet ship SDKs that cannot authenticate for this reason: joplin
-// (`token`), pipedrive (`api_token`), trello (`key`), lm-umbrella
-// (`apiKey`).
-//
-// A template cannot fix this, because the three placements need three
-// different bodies and a template has to pick one. A component emits the
-// branch this API actually uses and nothing else — no dead query code in a
-// bearer-token SDK, and no runtime `if` on a value that is fixed at
-// generation time.
-//
-// SWIFT WAS THE ODD ONE OUT: it had no prepare_auth template to delete.
-// `prepareAuthUtil` was one function among eight in
-// `tm/swift/Sources/ProjectNameSDK/utility/Prepare.swift`, beside
-// prepareMethod/Path/Params/Query/Headers/Body and paramUtil — none of
-// which is model-dependent. So the EXTRACTION is the move, not a rewrite of
-// the module: `prepareAuthUtil` and its three private constants move out of
-// Prepare.swift into this generated `utility/PrepareAuth.swift`, and the
-// other seven functions stay templated where they are.
-//
-// SWIFT LETS THAT WORK WITH NO REWIRING AT ALL. Every .swift file in the
-// SwiftPM target is one MODULE, and a top-level `func` is `internal` by
-// default — visible to the whole module, importable by nothing, declared
-// once. So moving the function to another file in the same target changes
-// no name and no import:
-//
-//   core/Utility.swift      `public var prepareAuth: ((Context) throws -> Spec)!`
-//   utility/Register.swift  `u.prepareAuth = prepareAuthUtil`   <- resolves here
-//   utility/Make.swift      `let spec = try utility.prepareAuth(ctx)`
-//   cmp/swift/fragment/Main.fragment.swift  `_ = try utility.prepareAuth(ctx)`
-//
-// all stand unchanged. The one thing swift does NOT tolerate is the
-// function existing in BOTH files — same module, same name, "invalid
-// redeclaration of 'prepareAuthUtil'", which fails the whole target — so
-// the template copy is deleted in the same change. That is the check that
-// makes a stale copy impossible here, and it is a compile error rather than
-// the silent double-life the ts port hit (see the folder note below).
 const PrepareAuth = cmp(async function PrepareAuth(props: any) {
   const { target } = props
   const { model } = props.ctx$
 
-  // AUTH SWITCHED OFF BY THE PROJECT — and ONLY by that.
-  //
-  // NOT `isAuthActive`, and the difference is load-bearing. That helper is
-  // false whenever `main.kit.info.auth` is false, which only says the SPEC
-  // declared no security scheme; such an SDK still carries a credential,
-  // because `optspec` always declares `apikey` and makeOptions fills
-  // `options.auth` from the optspec defaults — so the runtime
-  // `isNil(auth)` guard below never fires and these SDKs have ALWAYS sent
-  // `options.apikey`. Emitting a no-op for them silently breaks working
-  // authentication and takes the secrets feature with it (it resolves a
-  // secret into `options.apikey`, and prepareAuth then places nothing).
-  //
-  // `main.kit.config.auth.active: false` is the project saying "this SDK
-  // sends no credential, ever" — the only signal that can honestly be
-  // honoured before runtime. `isAuthSuppressed` in @voxgig/sdkgen IS that
-  // predicate (utility.ts), so it is used here rather than re-derived: the
-  // py port wrote its own `isAuthActive_py` before the shared helper
-  // existed, and two copies of one rule is how they drift.
   const suppressed = isAuthSuppressed(model)
 
   const where = resolveAuthIn(model)
 
-  // LOWERCASED FOR A HEADER, VERBATIM OTHERWISE. HTTP header names are
-  // case-insensitive on the wire (RFC 9110 5.1), but this SDK's header bag
-  // is a plain `VMap` keyed in lower case throughout: the code being
-  // extracted said `private let headerAuth = "authorization"`, the shared
-  // corpus asserts `ctx:spec:headers:authorization`, the shipped
-  // PipelineTest reads `headers.entries["authorization"]`, and
-  // SecretsFeature.swift writes `headers.entries["authorization"]` as the
-  // other credential writer. apidef writes `name: "Authorization"`, so
-  // emitting it verbatim would put the credential under a key nothing in
-  // this SDK reads. A query parameter and a cookie ARE case-sensitive
-  // (`?token=` is not `?Token=`), so those keep the spec's spelling.
   const resolvedName = resolveAuthName(model)
   const name = 'header' === where ? resolvedName.toLowerCase() : resolvedName
 
-  // Resolved, and deliberately NOT baked into the emitted source: the
-  // prefix is a RUNTIME option (`options.auth.prefix`) and the code being
-  // extracted read it from the options map, so a caller — and the secrets
-  // feature, which rewrites it there — can still override it per client.
-  // Only the PLACEMENT is fixed at generation time.
   const prefix = resolveAuthPrefix(model)
 
   const basic = isHttpBasicAuth(model)
 
-  // FOLDER NESTING, worked out from the template's own path and from
-  // Main_swift, not guessed.
-  //
-  // The file being replaced lives at
-  // `tm/swift/Sources/ProjectNameSDK/utility/Prepare.swift`, and Main_swift
-  // copies that tree with `Folder({name:'Sources'})` +
-  // `Copy({from:'tm/swift/Sources/ProjectNameSDK', to: swiftTargetDir(model)})`
-  // — note the `to`, which is why the runtime lands under the API's own
-  // name (`Sources/<Name>Sdk/utility/`) rather than under the placeholder
-  // directory. So the full destination is
-  // `Sources/<Name>Sdk/utility/PrepareAuth.swift`.
-  //
-  // ALL THREE SEGMENTS ARE OPENED HERE, and Main calls this at its TOP
-  // level, beside `EntityTypes({ target })` — which is the swift precedent
-  // for exactly this (EntityTypes_swift opens
-  // `Sources`/`swiftTargetDir`/`entity` itself). Two other call sites were
-  // available and both are wrong:
-  //
-  //   * inside Main's generated-sources block, beside `Config({target})`.
-  //     That block sits inside `Folder({name:'core'})`, so this would write
-  //     `Sources/<Name>Sdk/core/utility/PrepareAuth.swift`.
-  //   * inside that block but one level out, opening only `utility`. That
-  //     is correct TODAY and breaks the moment the surrounding folders
-  //     move; self-contained is what EntityTypes_swift chose.
-  //
-  // Getting it wrong is not merely a misplaced file: SwiftPM compiles
-  // EVERY .swift under `Sources/<target>/`, so a stray copy at the wrong
-  // path is still in the module and still collides with the real one. Here
-  // that is a hard build failure — which is the good case, and the reason
-  // the ts port's `src/src/utility/` accident (a second `Folder('src')`,
-  // the stale file still imported, invisible to the suite) cannot repeat on
-  // swift.
   Folder({ name: 'Sources' }, () => {
     Folder({ name: swiftTargetDir(model) }, () => {
       Folder({ name: 'utility' }, () => {
@@ -165,12 +55,6 @@ type AuthSpec = {
 
 
 function render(spec: AuthSpec): string {
-  // Foundation on every file is the tm/swift convention (Prepare.swift,
-  // Make.swift, MakeOptions.swift, Spec.swift all open with it), and the
-  // basic and cookie branches genuinely need it — `base64EncodedString()`
-  // and `trimmingCharacters(in:)` are Foundation. Swift does not warn on an
-  // unused import, so the header branch carrying it costs nothing and keeps
-  // the file shaped like its neighbours.
   const head = `// ${spec.Name} SDK utility: prepareAuth - place the API credential.
 //
 // GENERATED, not templated: WHERE the credential goes - header, query or
@@ -186,9 +70,6 @@ import Foundation
 `
 
   if (spec.suppressed) {
-    // The project set `main.kit.config.auth.active: false`. No credential,
-    // ever — so the SDK gets a prepareAuth that is honest about it rather
-    // than one that pops a header nobody set.
     return head + `
 // This SDK is configured with authentication OFF
 // (main.kit.config.auth.active is false), so there is no credential to
@@ -211,11 +92,6 @@ func prepareAuthUtil(_ ctx: Context) throws -> Spec {
 }
 
 
-// HEADER. Byte-for-byte the function that was in Prepare.swift when the
-// scheme resolves to the defaults (header / Authorization) and is not
-// Basic — same constant names, same `skip` shape, same removeValue /
-// entries[...] idioms, same error. Only the constant's VALUE moves with the
-// model, plus the Basic block, which is emitted only for a basic scheme.
 function renderHeader(spec: AuthSpec): string {
   const basicConst = spec.basic ? `
 private let optionSecret = "secret"` : ''
@@ -300,11 +176,6 @@ function basicBlock(spec: AuthSpec): string {
 }
 
 
-// QUERY. The credential is a query parameter, so it goes in `spec.query` and
-// the headers are never touched. `spec.query` is the bag makeUrl builds the
-// query string from (utility/Make.swift), and prepareAuth runs AFTER
-// prepareQuery in makeSpec, so the credential joins the op's own arguments
-// rather than being overwritten by them.
 function renderQuery(spec: AuthSpec): string {
   return `
 private let queryAuth = ${swiftString(spec.name)}
@@ -349,11 +220,6 @@ func prepareAuthUtil(_ ctx: Context) throws -> Spec {
 }
 
 
-// COOKIE. A cookie IS a header, so the credential rides the header bag -
-// but the `cookie` header is SHARED with whatever cookies the caller set, so
-// the pair is spliced in and out rather than the header assigned over.
-// Splicing is also what makes it idempotent: a retried request cannot end up
-// carrying the credential twice.
 function renderCookie(spec: AuthSpec): string {
   return `
 private let cookieHeader = "cookie"

package/project/.sdk/src/cmp/swift/ReadmeEntity_swift.ts

@@ -11,7 +11,6 @@ import { swiftVarName } from './utility_swift'
 
 // Type names come from the shared canonToType 'swift' column (single source of truth).
 
-// A type-correct Swift `Value` literal for a field's canonical type.
 function swiftLit(type: any, placeholder: string = 'example'): string {
   const k = canonScalarKey(type)
   if ('INTEGER' === k) return '.int(1)'
@@ -56,8 +55,7 @@ const ReadmeEntity = cmp(function ReadmeEntity(props: any) {
 
   publishedEntities.map((entity: any) => {
     const opnames = Object.keys(entity.op || {})
-    const fields = entity.fields || []
-    // Model-driven id key: null when this entity has no id-like field.
+    const fields = Object.values(entity.fields || {})
     const idF = entityIdField(entity)
     // Sanitise the local variable name — a camelCased Swift keyword gets a
     // trailing underscore (swiftVarName) so the snippet compiles.
@@ -105,8 +103,8 @@ const ReadmeEntity = cmp(function ReadmeEntity(props: any) {
 `)
 
       each(fields, (field: any) => {
-        const desc = field.short || ''
-        Content(`| \`${field.name}\` | \`${canonToType(field.type, target.name)}\` | ${desc} |
+        const desc = field.sh || ''
+        Content(`| \`${field.n}\` | \`${canonToType(field.t, target.name)}\` | ${desc} |
 `)
       })
 

package/project/.sdk/src/cmp/swift/ReadmeExamplesTest_swift.ts

@@ -2,28 +2,6 @@
 import { cmp, File, Content } from '@voxgig/sdkgen'
 
 
-// Emits Tests/ProjectNameSDKTests/ReadmeExamplesTest.swift — a PRESENCE +
-// STRUCTURE gate over every swift fenced block in the repository ROOT
-// README.md, the per-language swift/README.md, AND swift/REFERENCE.md. It is a
-// plain XCTestCase (no @testable import — it only reads the doc files off
-// disk), resolved relative to the test file via #filePath.
-//
-// SCOPE NOTE (deliberate, documented): the Python/TS/Go equivalents EXECUTE and
-// type-check every documented block. That is infeasible here — the generated
-// Swift SDK compiles with SwiftPM only (no in-process Swift compiler wired into
-// the test runtime), so a test cannot compile-and-run arbitrary doc snippets at
-// test time. This gate therefore guarantees the weaker-but-real invariant that
-// keeps the docs honest as the generator evolves:
-//   1. PRESENCE: every scanned doc that exists holds at least one swift block
-//      (nothing was dropped);
-//   2. STRUCTURE: every swift block's braces / parens / brackets balance
-//      (ignoring string literals and line comments), catching a truncated or
-//      malformed generated snippet.
-//
-// The emitted Swift is written WITHOUT literal backticks (the fence marker is
-// built at runtime as String(repeating: "\u{60}", count: 3)) so this TS
-// template literal stays clean, and uses string concatenation instead of Swift
-// interpolation to keep backslash-escaping in this template minimal.
 const ReadmeExamplesTest = cmp(function ReadmeExamplesTest(props: any) {
   const { ctx$: { model } } = props
 

package/project/.sdk/src/cmp/swift/ReadmeModel_swift.ts

@@ -115,13 +115,13 @@ On error, \`ok\` is \`false\` and \`err\` contains the error value.
 
 `)
   each(entityList, (ent: any) => {
-    const fields = ent.fields || []
+    const fields = Object.values(ent.fields || {})
     const opnames = Object.keys(ent.op || {})
     const ops = ent.op || {}
     const points = each(ops).map((op: any) =>
       op.points ? each(op.points) : []
     ).flat()
-    const path = points.length > 0 ? (points[0] as any).orig || '' : ''
+    const path = points.length > 0 ? (points[0] as any).o || '' : ''
 
     Content(`#### ${ent.Name}
 
@@ -129,7 +129,7 @@ On error, \`ok\` is \`false\` and \`err\` contains the error value.
 | --- | --- |
 `)
     each(fields, (field: any) => {
-      Content(`| \`${field.name}\` | ${field.short || ''} |
+      Content(`| \`${field.n}\` | ${field.sh || ''} |
 `)
     })
 

package/project/.sdk/src/cmp/swift/ReadmeRef_swift.ts

@@ -1,5 +1,5 @@
 
-import { cmp, each, Content, canonToType, canonKey, canonScalarKey, File, isAuthActive, entityIdField, opRequestShape } from '@voxgig/sdkgen'
+import { cmp, each, Content, canonToType, canonKey, canonScalarKey, File, isAuthActive, entityIdField, opRequestShape , targetFeatures } from '@voxgig/sdkgen'
 import { ReadmeRefFeatures } from '@voxgig/sdkgen'
 
 import {
@@ -60,7 +60,7 @@ const ReadmeRef = cmp(function ReadmeRef(props: any) {
   const SDK = model.const.Name + 'SDK'
 
   const entity = getModelPath(model, `main.${KIT}.entity`)
-  const feature = getModelPath(model, `main.${KIT}.feature`)
+  const feature = targetFeatures(model, target)
 
   const publishedEntities = each(entity).filter((e: any) => e.active !== false)
 
@@ -169,7 +169,7 @@ Prepare a fetch definition without sending. Returns the \`fetchdef\` and throws
     // Entity reference sections
     publishedEntities.map((ent: any) => {
       const opnames = Object.keys(ent.op || {})
-      const fields = ent.fields || []
+      const fields = Object.values(ent.fields || {})
       // Model-driven id key: null when this entity has no id-like field.
       const idF = entityIdField(ent)
       // Sanitise the local variable name — swiftVarName guards Swift keywords.
@@ -204,9 +204,9 @@ let ${eVar} = client.${accessor}()
 | --- | --- | --- | --- |
 `)
         each(fields, (field: any) => {
-          const req = field.req ? 'Yes' : 'No'
-          const desc = field.short || ''
-          Content(`| \`${field.name}\` | \`${canonToType(field.type, target.name)}\` | ${req} | ${desc} |
+          const req = field.r ? 'Yes' : 'No'
+          const desc = field.sh || ''
+          Content(`| \`${field.n}\` | \`${canonToType(field.t, target.name)}\` | ${req} | ${desc} |
 `)
         })
 
@@ -231,7 +231,7 @@ let ${eVar} = client.${accessor}()
               if (fop.active === false) return '-'
               return 'Yes'
             })
-            Content(`| \`${field.name}\` | ${cols.join(' | ')} |
+            Content(`| \`${field.n}\` | ${cols.join(' | ')} |
 `)
           })
 
@@ -377,9 +377,6 @@ let client = ${SDK}(options)
 \`\`\`
 
 `)
-      // The shared feature reference: options, defaults, usage and the
-      // considerations. Model facts, identical in every target, so they are
-      // written once in cmp/ReadmeRefFeatures.ts rather than here.
       ReadmeRefFeatures({ target })
     }
 

package/project/.sdk/src/cmp/swift/Schema_swift.ts

@@ -12,24 +12,6 @@ import {
 } from '@voxgig/apidef'
 
 
-// THE GENERATED SCHEMA MODULE: the model's schemas, as data the SDK can run.
-//
-// The swift peer of src/cmp/ts/Schema_ts.ts. Same two members, same source:
-// optspec from `main.kit.optspec` plus each feature's own `config.options`,
-// entityspec from the entity field sentinels — both built by the shared
-// helpers, so what swift validates against and what ts validates against
-// cannot drift.
-//
-// EMBEDDED AS JSON, PARSED AT LOAD, where ts emits an object literal: JSON is
-// a subset of TypeScript's own literal syntax and is not a subset of swift's.
-// A raw string literal, exactly as Config.swift carries its config — raw
-// (`#"""`) so the spec's own backslashes and quotes need no re-escaping.
-//
-// The round-trip is exact because the spec holds only strings and booleans:
-// pinned by "strings and booleans only, so the JSON round-trip is lossless"
-// in ts/test/optspec.test.ts. That is not incidental — JSON.parse decodes a
-// JSON number to one Value case and struct reads a spec BY EXAMPLE, so one
-// number in here would mean something different in swift than in ts.
 const Schema = cmp(async function Schema(props: any) {
   const ctx$ = props.ctx$
   const target = props.target
@@ -50,7 +32,7 @@ const Schema = cmp(async function Schema(props: any) {
 // do not edit by hand.
 //
 // Built from the model: \`main.kit.optspec\` and each feature's
-// \`config.options\` for optspec; entity \`fields[].type\` for entityspec.
+// \`config.options\` for optspec; entity \`fields{}.type\` for entityspec.
 
 import Foundation
 

package/project/.sdk/src/cmp/swift/TestEntity_swift.ts

@@ -33,10 +33,6 @@ final class ${entity.Name}EntityTest: XCTestCase {
   }
 `)
 
-    // Stream test (PR #4): the entity `stream` method runs the op pipeline and
-    // returns an AsyncStream. With the streaming feature active it yields from
-    // the feature's incremental iterator; otherwise it falls back to the
-    // materialised items. Only emitted for entities that support list.
     if (hasList) {
       Content(`
   func testStream() async throws {

package/project/.sdk/src/cmp/swift/utility_swift.ts

@@ -17,9 +17,6 @@ function projectPath(suffix?: string): string {
 }
 
 
-// A lowerCamelCase Swift local-variable identifier for a snake_case model name
-// (`planet_ref01` -> `planetRef01`). Swift keywords that are illegal as a plain
-// binding get a trailing underscore.
 function swiftVarName(name: string): string {
   const pascal = camelify(name)
   const lower = pascal.charAt(0).toLowerCase() + pascal.slice(1)
@@ -30,12 +27,6 @@ function swiftVarName(name: string): string {
 }
 
 
-// No Swift identifier may begin with a digit, but a model field may: a
-// `3d_id` field camelifies to `3DId`, and `public var 3DId: String` does not
-// merely fail to bind — the compiler reads it as a malformed number and the
-// whole module dies on "'D' is not a valid digit in integer literal", naming
-// nothing that leads back to the field. Prefixed with an underscore, the same
-// convention cmp/c/utility_c.ts already applies.
 function leadingDigitSafe(ident: string): string {
   return /^[0-9]/.test(ident) ? '_' + ident : ident
 }
@@ -71,29 +62,6 @@ function swiftString(val: string): string {
 }
 
 
-// Strip model-internal keys (ending in `$`) from a cloned value graph.
-// Emission-time normalisation of a model subtree (L0).
-//
-// Always drops jostraca's iteration metadata (`$`-suffixed keys: index$,
-// key$, val$). With `dropDefaults`, also drops keys whose value IS the
-// default the runtime already assumes when the key is absent, which is pure
-// payload — see CONFIG_DEFAULT.
-//
-// Rebuilds the tree rather than mutating during a walk. The previous
-// implementation walked a clone calling `delete p[k]`, but walk() assigns its
-// callback's result back over the child (`setprop(out, ckey, walk(...))`), so
-// the delete was undone on the way out and the helper silently did nothing.
-// Returning `undefined` from the callback does not fix it either: setprop
-// stores undefined rather than removing the key, which then emits as a null.
-//
-// `dropDefaults` is opt-in and must be passed ONLY for the entity subtree.
-// `active` means something different in feature config, where absent reads as
-// INACTIVE (see feature_init) — dropping `active: true` there would silently
-// disable the feature.
-// jostraca's iteration metadata, injected by each()/names() while it walks the
-// model. Listed explicitly rather than matched by trailing-dollar suffix: a
-// trailing dollar is not exclusive to jostraca -- Seneca uses entity$ as real
-// data -- so a blanket suffix match can silently drop a legitimate API field.
 const MODEL_META = ['index$', 'key$', 'val$']
 
 // Keys whose value IS the default the runtime already assumes when the key is
@@ -133,10 +101,6 @@ function clean(o: any, dropDefaults?: boolean): any {
 }
 
 
-// SwiftPM's convention is Sources/<target>/ and Tests/<target>Tests/, and the
-// target is named <Name>Sdk in Package_swift. These name the two directories
-// so the copied runtime lands under the API's own name rather than under the
-// template's placeholder — see the note in Main_swift.
 function swiftTargetDir(model: any): string {
   return model.const.Name + 'Sdk'
 }
@@ -147,21 +111,6 @@ function swiftTestDir(model: any): string {
 }
 
 
-// Is the `secrets` feature ACTIVE for this target - i.e. do the three
-// vendored trees under Sources/ProjectNameSDK/feature/secrets/ ship, and
-// does Package.swift declare them?
-//
-// ONE RULE, ONE PLACE: Package_swift (the manifest's three extra targets
-// plus the SDK target's `exclude:`) and Main_swift (the Copy that ships or
-// withholds the trees) both read this, so the manifest and the tree cannot
-// disagree - a manifest naming a path that is not there fails the WHOLE
-// SwiftPM package, not just the feature, and a tree without its manifest
-// entries folds three modules' worth of colliding `Value`/`Point`/`Json`
-// declarations into the SDK module.
-//
-// `targetFeatures` is the applicability gate (helpers/applicability): the
-// feature counts only when the model activates it AND this target
-// `provides: { sekreto: true }`.
 function swiftSecretsActive(model: any, target: any): boolean {
   return null != targetFeatures(model, target)['secrets']
 }

package/project/.sdk/src/cmp/ts/Config_ts.ts

@@ -43,9 +43,6 @@ const Config = cmp(async function Config(props: any) {
   const model: Model = ctx$.model
 
   const entity = getModelPath(model, `main.${KIT}.entity`)
-  // Gated by the applicability tags, so this target never imports or
-  // registers a feature it has no source for. One rule, one place:
-  // helpers/applicability.
   const feature = targetFeatures(model, target)
 
   const ff = Path.normalize(__dirname + '/../../../src/cmp/ts/fragment/')
@@ -53,7 +50,6 @@ const Config = cmp(async function Config(props: any) {
   const headers = getModelPath(model, `main.${KIT}.config.headers`) || {}
 
   const authActive = isAuthActive(model)
-  // config.auth.prefix override -> spec-derived info.security.prefix -> 'Bearer'
   const authPrefix = resolveAuthPrefix(model)
   const authBasic = isHttpBasicAuth(model)
   // `in` and `name` travel with the prefix now. They were resolved by
@@ -74,30 +70,17 @@ const Config = cmp(async function Config(props: any) {
     `
     : ''
 
-  // Templated server URL: emit the spec's server-variable defaults so the
-  // runtime can substitute {name} placeholders in base (see makeOptions).
   const svars = serverVariables(model)
   const serverBlock = 0 === svars.length ? '' :
     'server: {\n' +
     svars.map((v: any) => `      ${JSON.stringify(v.name)}: ${JSON.stringify(v.dflt)},\n`).join('') +
     '    },\n\n    '
 
-  // Read the base URL here rather than leaving it to a `$$...$$` stdrep
-  // placeholder in the fragment. stdrep can only substitute a path the model
-  // actually has: a model with no `info.servers` left the placeholder itself in
-  // the generated source, so `options.base` came out as the literal string
-  // '$main.kit.info.servers.0.url$'. Reading it explicitly yields '' in that
-  // case, which is what every other target already emits, and is identical to
-  // the old output whenever the model does define a server.
   let baseUrl = ''
   try {
     baseUrl = getModelPath(model, `main.${KIT}.info.servers.0.url`)
   } catch (_e) { }
 
-  // The same config as an OBJECT, built by the shared helper so this target's
-  // literal and the data that replaces it above the threshold are the same
-  // config by construction. The JSON is what the threshold is measured on -
-  // emitted source size varies by language, the model does not.
   const { def: configDef, json: configJson } = configDefinition(model, target.name)
   const asData = isConfigData(configJson, configReprSetting(model))
 
@@ -125,9 +108,6 @@ const Config = cmp(async function Config(props: any) {
 
           '// #FeaturePlugins': () => pluginDefs(feature),
 
-          // A JS string literal, so the JSON survives verbatim. JSON.stringify
-          // escapes the quotes and backslashes the model contains (values like
-          // `$STRING` carry backticks, which a template literal could not).
           "'CONFIGJSON'": JSON.stringify(configJson),
         }
       })
@@ -165,8 +145,6 @@ const Config = cmp(async function Config(props: any) {
 
         '// #FeatureClasses': () => {
           each(feature, (f: any) => {
-            // Trailing comma: the map has one entry per feature, so entries
-            // must be comma-separated (a single feature hid this until now).
             Line(` ${f.name}: ${nom(f, 'Name')}Feature,`)
           })
         },
@@ -192,12 +170,6 @@ const Config = cmp(async function Config(props: any) {
           })
         },
 
-        // configDefinition's `def.entity` verbatim, NOT rebuilt here. This
-        // reduce was a second copy of that function's entityDefs loop, and
-        // when configDefinition started reconstructing a point's `parts`
-        // from apidef's segment vector (its ADR-003), only the data
-        // representation got it — the literal one emitted empty paths. The
-        // config-repr equivalence test caught it, which is what it is for.
         "'ENTITYMAP'": formatJson(configDef.entity, { margin: 2 }).trim(),
       }
     })
@@ -206,24 +178,8 @@ const Config = cmp(async function Config(props: any) {
 
 
 
-// PLUGIN DEFINITION IMPORTS AND THE FEATURE_PLUGINS MAP.
-//
-// Upstream sekreto replaced its self-registration registry with
-// voxgig/plugin definitions: a provider kind the caller did not pass in
-// via `plugins: [...]` is unknown to that Sekreto. So Config no longer
-// imports provider modules for their side effects — it imports each
-// active plugin's exported Definition BY NAME (the model's `def` map)
-// and hands the list to the feature through FEATURE_PLUGINS.
-//
-// Emitted here because Config already imports every active feature from
-// the model, and this is the same list one level down. The `def` map is
-// declared in the model rather than derived from filenames because one
-// file may export several definitions (sekreto's aws.ts exports
-// awssecrets AND awsparams).
 function pluginImports(feature: any) {
   each(feature, (f: any) => {
-    // path -> [symbol, ...], so one import line serves a two-definition
-    // module.
     const bypath: Record<string, string[]> = {}
 
     each(f.plugin, (plugin: any) => {
@@ -247,8 +203,6 @@ function pluginImports(feature: any) {
   })
 }
 
-// The FEATURE_PLUGINS entries: one line per feature that has any active
-// plugin definitions, listing the imported symbols.
 function pluginDefs(feature: any) {
   each(feature, (f: any) => {
     const syms: string[] = []