@voxgig/sdkgen 4.21.0 → 4.23.0

package/src/action/target.ts

@@ -82,7 +82,6 @@ async function cmd_target_add(args: string[], actx: ActionContext): Promise<Acti
 
 // Code API
 async function target_add(targets: string[], actx: ActionContext): Promise<ActionResult> {
-  // const jostraca = Jostraca()
   const jostraca = actx.jostraca
 
   const opts = {
@@ -96,13 +95,6 @@ async function target_add(targets: string[], actx: ActionContext): Promise<Actio
       content: loadContent(actx, 'target')
     },
     model: actx.model,
-    // Dry run must be passed per-call, not left to the Jostraca instance.
-    // jostraca's `generate` runs its own options through OptionsShape FIRST,
-    // which fills in `control.dryrun: false`, and only then merges
-    // `deep({}, gOpts.control, opts.control)` — so the shape default silently
-    // OVERRIDES the instance-level flag. `-y target add ts` printed
-    // ** DRY RUN ** and wrote every file. (Same trap as the `existing` FIX
-    // note in jostraca.js.)
     control: {
       dryrun: !!actx.opts.dryrun
     },
@@ -118,15 +110,6 @@ async function target_add(targets: string[], actx: ActionContext): Promise<Actio
   })
 
 
-  // The `test` feature is required by every generated target (SDK.test()
-  // depends on it), so ensure it is added even if the model does not yet
-  // declare it.
-  //
-  // Everything else has to be BOTH declared and active: `active` defaults to
-  // false in the schema, and a feature the model has switched off should not
-  // have its source land in the project. This used to be a plain
-  // Object.keys(), so `retry: { active: false }` still shipped every retry
-  // source file.
   const featuremodel: any = actx.model.main[KIT]?.feature ?? {}
   const features = Array.from(new Set([
     'test',
@@ -142,17 +125,6 @@ async function target_add(targets: string[], actx: ActionContext): Promise<Actio
     showDryrun(opts.log, 'target-result', jres, actx.folder)
   }
 
-  // The targets just written are not in the in-memory model — nothing
-  // recompiles `model/sdk.aontu` mid-process — so put them there before the
-  // fan-out below.
-  //
-  // TargetRoot copies each new target's feature source from ITS OWN TREE,
-  // which is the whole story only while every feature ships in the same
-  // package as every target. For a feature supplied by a DIFFERENT package,
-  // the source lives in that package's overlay, and only `feature_add`'s
-  // two-tree lookup consults it — for targets in the model. So a target added
-  // while such a feature was already active got no source for it at all:
-  // TargetRoot could not find it, and the fan-out could not see the target.
   registerInstalled('target', targets, actx)
 
   // feature_add copies feature templates for every target in the model,
@@ -180,8 +152,6 @@ const TargetRoot = cmp(function TargetRoot(props: any) {
   // jostraca, so it has to be told about the dry run itself.
   const dryrun = !!actx?.opts?.dryrun
 
-  // TODO: jostraca - make from value easier to specify 
-  // const tfolder = 'node_modules/@voxgig/sdkgen/project/.sdk'
 
   Project({}, () => {
     // Resolved names of every target in this run. The index File is
@@ -215,8 +185,6 @@ const TargetRoot = cmp(function TargetRoot(props: any) {
         note: tname + (tname != torigname ? 'original' + torigname : '') + ' from:' + tfolder
       })
 
-      // An ALIASED add (`target add go~go2`) installs the target under a new
-      // name, and every one of the three trees has to agree about that name.
       const aliased = tname !== torigname
 
       // The definition file and the index entry: the same for every kind, so
@@ -227,11 +195,6 @@ const TargetRoot = cmp(function TargetRoot(props: any) {
       }))
 
       if (aliased) {
-        // Components are dispatched by CONVENTION — `cmp/<t>/Main_<t>` — so
-        // an aliased tree whose files keep the origin suffix resolves
-        // nothing: `src/cmp/go2/Main_go.ts` is invisible to a lookup for
-        // `cmp/go2/Main_go2`. jostraca's tree Copy has no per-entry rename
-        // hook, so an aliased tree is emitted file by file instead.
         aliasCmpTree(ctx$, tfolder + '/src/cmp/' + torigname,
           'src/cmp/' + tname, torigname, tname)
       }
@@ -244,26 +207,8 @@ const TargetRoot = cmp(function TargetRoot(props: any) {
         })
       }
 
-      // Copy the whole template tree MINUS the source of every feature the
-      // model did not ask for. Which files those are is discovered from the
-      // tree rather than assumed (see helpers/featureSource), because each
-      // language puts feature source somewhere different.
       const trim = trimFeatures(ctx$, tfolder, torigname, tname, features)
 
-      // Copy only ADDS and overwrites — it never removes, and it never even
-      // looks at a file the trim excludes. So a template that this SDK should
-      // NOT have lived on at whatever revision it was first copied at, and
-      // kept being generated from.
-      //
-      // That is how 30 cedar repos ended up with tm/go/test/feature_test.go
-      // still declaring the nine fh* harness helpers after upstream moved them
-      // into feature_harness_test.go: feature_test.go is feature-source, so it
-      // is trimmed for an SDK without those features, so Copy skipped it, so
-      // the pre-move revision survived every `target add go` those repos ever
-      // ran. Generation then emitted it alongside the new harness and the go
-      // package failed to compile — "fhHasFeature redeclared in this block".
-      //
-      // The invariant this restores: tm/<target> == source tree MINUS trim.
       pruneStaleTemplates(
         ctx$, tfolder + '/tm/' + torigname, 'tm/' + tname, trim, dryrun)
 
@@ -282,9 +227,6 @@ const TargetRoot = cmp(function TargetRoot(props: any) {
 
     })
 
-    // ONCE, after the loop. See kindIndex: emitted per item it was one File
-    // component per target on the same output path, which jostraca 0.38
-    // refuses.
     if (0 < tnames.length) {
       Folder({ name: 'model/target' }, () => kindIndex({
         kind: 'target', names: tnames,
@@ -297,36 +239,12 @@ const TargetRoot = cmp(function TargetRoot(props: any) {
 
 
 
-// `<Cmp>_<origname>.<ext>` -> `<Cmp>_<tname>.<ext>`, for an aliased install.
-// Anything not carrying the suffix (tsconfig.json, the fragment sources)
-// keeps its name — the `.<ext>` anchor is what keeps this off
-// `Main.fragment.go`, whose `go` is a file extension.
-//
-// Shared with doctor for the same reason as aliasCmpText: doctor walks the
-// ORIGIN tree to decide what should be present, so it has to land each file
-// under the same name the writer gave it, or it reports the whole tree as
-// missing.
 function aliasCmpName(name: string, torigname: string, tname: string): string {
   return name.replace(
     new RegExp('_' + escapeRe(torigname) + '(\\.[^.]+)$'), '_' + tname + '$1')
 }
 
 
-// The origin name a component carries INSIDE its source, rewritten for an
-// aliased install. Shared with doctor, which re-applies it before comparing —
-// same discipline as templateReplacements: a writer and a reader that
-// disagree by a character make every file read as a fork.
-//
-// Rewritten here rather than through jostraca's `replace` map, because that
-// map canonicalises each key into a regex group NAME — `_go'` and `_go"` both
-// reduce to the same name, so the later entry silently won and every
-// single-quoted import came out as `from './Package_go2"`. One explicit regex
-// keeps the quote it matched.
-// `cmpbase` is the component tree's PREFIX — `src/cmp/` for a target,
-// `src/cmp/docs/` for a docs item. Taken from the caller rather than fixed
-// here: a docs item's components live one level deeper, and a rewrite that
-// looked for `src/cmp/<orig>/` left an aliased docs component pointing at the
-// ORIGIN's fragments — reading them silently when both are installed.
 function aliasCmpText(
   src: string, torigname: string, tname: string, cmpbase = 'src/cmp/',
 ): string {
@@ -344,20 +262,6 @@ function aliasCmpText(
 }
 
 
-// Emit an aliased `src/cmp` tree: every file renamed from the origin suffix
-// to the installed one, and its CONTENT rewritten to match.
-//
-// Renaming alone would break the tree, because a component names its origin
-// twice over: sibling imports (`from './Package_go'`) and the fragment
-// directory it reads through `__dirname` (`/../../../src/cmp/go/fragment/`,
-// in 67 of the shipped components). Both are rewritten here — the fragment
-// path because the fragments are copied to the ALIAS's folder, so the origin
-// path would either miss or, worse, silently read the origin target's
-// fragments if that target is also installed.
-//
-// Files are emitted through jostraca (`File`/`Content`) rather than copied
-// with `fs`, so a dry run reports them and writes nothing, exactly as the
-// tree Copy on the unaliased path does.
 function aliasCmpTree(
   ctx$: any,
   fromDir: string,
@@ -401,9 +305,6 @@ function aliasCmpTree(
 
       const renamed = aliasCmpName(name, torigname, tname)
 
-      // `template` against the model with no replace map, matching what Copy
-      // does for the unaliased tree — jostraca's Copy always interpolates
-      // `$$ref$$` against the model, so an aliased tree must too.
       const src = fs.readFileSync(child, 'utf8')
 
       File({ name: renamed }, () => Content(template(aliasText(src), ctx$.model)))
@@ -416,34 +317,6 @@ function aliasCmpTree(
 
 
 
-// Path patterns that keep a target's unwanted feature source out of the
-// project: the source of every AVAILABLE feature the model did not select,
-// plus the templates that only compile with the complete feature set.
-//
-// Returns an empty list — copy the whole tree, as before — when the target
-// opts out with `feature: { trim: false }`, or when its model cannot be
-// read. Trimming a target whose templates are not ready for it produces a
-// project that does not build, so an unreadable declaration must fail safe
-// rather than fail tidy.
-// Bring the consumer's `tm/<target>` back to the invariant that Copy alone
-// cannot maintain: it must contain EXACTLY the source tree minus the files
-// this SDK's feature set trims away.
-//
-// Copy adds and overwrites. It does not remove, and it does not touch an
-// excluded file at all — so both of these persist silently forever:
-//
-//   - a template the toolchain has RETIRED (absent from the source tree);
-//   - a template this SDK should not have (present in source, but trimmed),
-//     frozen at whatever revision it was first copied at.
-//
-// The second is the one that bit: tm/go/test/feature_test.go is feature
-// source, so it is trimmed for an SDK without those features, so it was never
-// refreshed after upstream moved the fh* harness helpers out of it.
-//
-// tm/ is toolchain-owned — the scaffold rewrites it on every add-target, and
-// model/guide/guide.aon is the one file a user owns (merged separately by
-// create-sdkgen) — so removing what the toolchain says should not be there is
-// consistent with how the rest of that tree is already treated.
 function pruneStaleTemplates(
   ctx$: any,
   fromDir: string,
@@ -467,12 +340,6 @@ function pruneStaleTemplates(
         return
       }
       for (const ent of entries) {
-        // Junk is invisible to this listing on BOTH sides, and it has to be
-        // both. In the source it is never copied, so counting it would want a
-        // file that can never arrive. In the destination it was never written
-        // by this toolchain, so counting it as stale would have `target add`
-        // delete a maintainer's own `__pycache__` out of their SDK repo —
-        // this prune's remit is the tree it writes, not the tree it finds.
         if (isJunk(ent.name)) {
           continue
         }
@@ -510,12 +377,6 @@ function pruneStaleTemplates(
     return
   }
 
-  // A DRY RUN must not delete. This prune calls `fs.unlinkSync` directly, and
-  // jostraca enforces `control.dryrun` only inside its own write layer — so
-  // `-y target add <t>` previewed the copies and then really removed every
-  // stale template, which is the opposite of what the flag promises and
-  // exactly the blast radius a maintainer runs `-y` to inspect. Report the
-  // deletions instead, in the same shape the copies are reported.
   if (dryrun) {
     log.info({
       point: 'target-template-prune', target: toRel, count: stale.length,
@@ -558,38 +419,6 @@ function pruneStaleTemplates(
 }
 
 
-// WHICH NAMES COUNT AS FEATURE SOURCE, when deciding what to trim.
-//
-// This used to be the SOURCE folder's own `model/feature/` listing, which is
-// right only while every target ships in the same package as every feature.
-// An external target package declares no feature models of its own — it has
-// no reason to — so nothing was discovered, nothing was trimmed, and the
-// consumer received the target's source for EVERY feature regardless of what
-// its model selected. Measured on a target copied from the bundled `go`: the
-// bundled one keeps 2 feature source files, the external one kept all 18.
-//
-// That is the failure `helpers/featureSource` was written to end (272 stray
-// files in one repo), arriving again by the one route it did not cover.
-//
-// The catalogue is therefore the union of every place a feature this project
-// could select can come from:
-//
-//   - the bundled scaffold, which is what a bare `feature add <name>` means;
-//   - the source package's own declarations, for a package shipping both;
-//   - the consumer's OWN installed feature models, which is how an EXTERNAL
-//     feature's source becomes trimmable at all.
-//
-// Every term is a place feature DEFINITIONS live, deliberately. Taking the
-// third from the model's feature KEYS instead would make any name a project
-// happens to declare a trim candidate — and a file in a `feature/` directory
-// is not necessarily a feature. `tm/rust/feature/support.rs` and its siblings
-// are shared machinery that `Main_rust` emits unconditionally (`pub mod
-// support`), so a project that declared a feature called `support` would have
-// had that file pruned and produced a crate that cannot compile. A definition
-// file is evidence that the name really denotes a feature; a model key is not.
-//
-// For a bundled add this is `bundled ∪ bundled ∪ (⊆ bundled)`, so the trim is
-// byte-identical to what it always was — the goldens hold it to that.
 function featureCatalogue(ctx$: any, tfolder: string): string[] {
   const fs = ctx$.fs()
   const root = ctx$.folder ?? '.'
@@ -651,12 +480,6 @@ function trimFeatures(
 }
 
 
-// Load a target's `feature` declaration from its own model file.
-//
-// The target being added is not in the in-memory model yet (that is what
-// `target add` is for), so this reads the very file that is about to be
-// copied into `model/target/`. Each shipped target model is self-contained,
-// so Aontu can resolve it on its own.
 function readTargetFeature(
   ctx$: any,
   tfolder: string,

package/src/cmp/AgentGuide.ts

@@ -32,8 +32,6 @@ const AgentGuide = cmp(function AgentGuide(props: any) {
   const surface = langCmd(lang).note
 
   const features = activeFeatures(model, target)
-  // go-cli/go-mcp disable the feature phase; ts/js lay features out as
-  // per-feature directories, the other SDK targets as flat files.
   const featuresOn = featuresEnabled(target)
   const dirLayout = isDirLayout(target)
 
@@ -78,7 +76,6 @@ component.* After editing a component run \`npm run build\` before
 
 `)
       if (dirLayout) {
-        // ts/js: each feature is a directory under src/feature/ with its own guide.
         features.forEach((f: any) => {
           const t = f.title ? ' — ' + f.title : ''
           Content(`- [\`${f.name}\`](./src/feature/${f.name}/AGENTS.md)${t}
@@ -90,8 +87,6 @@ Each feature's runtime and its own guide live in \`src/feature/<name>/\`.
 `)
       }
       else {
-        // go/py/php/rb/lua: flat files in the shared \`feature/\` package — no
-        // per-feature directory, so features are documented inline here.
         Content(`Each feature is a flat file in the \`feature/\` package. Its hooks and
 default activation come from \`.sdk/model/feature/<name>.aon\`; customise
 the runtime under \`.sdk/tm/${lang}/feature/\` and regenerate.
@@ -112,8 +107,6 @@ the runtime under \`.sdk/tm/${lang}/feature/\` and regenerate.
       }
     }
 
-    // Optional per-language enrichment (build/test specifics, idioms). Neutral
-    // content above stands alone; a language may add an AgentGuide_<lang>.
     const AgentGuide_sdk =
       requirePath(ctx$, `./cmp/${lang}/AgentGuide_${lang}`, { ignore: true })
     if (AgentGuide_sdk) {

package/src/cmp/AgentGuideContent.ts

@@ -1,13 +1,3 @@
-// Shared prose for the generated agent guides (AGENTS.md files emitted at the
-// project top level, per target language, and per feature). The workflow, the
-// two-layer template/component model, and the aontu primer are identical for
-// every generated SDK, so they live here once and the three AgentGuide
-// components (AgentGuideTop / AgentGuide / AgentGuideFeature) render them.
-//
-// IMPORTANT: these guides ship INSIDE a generated SDK project, so every path is
-// consumer-relative (`.sdk/tm/<lang>/`, `.sdk/src/cmp/<lang>/`,
-// `.sdk/model/...`) — NOT the `project/.sdk/...` form used by the sdkgen repo's
-// own developer docs.
 
 import { featureApplies } from '../helpers/applicability'
 
@@ -70,10 +60,7 @@ function langCommandsBlock(name: string): string {
 }
 
 
-// --- feature layout helpers (targets differ) --------------------------------
 
-// Whether a target generates per-feature output at all. go-cli / go-mcp
-// disable the feature phase (`phase.feature.active: false`).
 function featuresEnabled(target: any): boolean {
   return target?.phase?.feature?.active !== false
 }
@@ -89,8 +76,6 @@ function featureBase(target: any): string {
   return isDirLayout(target) ? 'src/feature' : 'feature'
 }
 
-// The generated runtime file for a feature in a flat-layout target:
-// `<name>_feature.<ext>` (go/py/rb/lua) or `<Name>Feature.php` (php).
 function featureRuntimeFile(target: any, feature: any): string {
   const ext = target?.ext || target?.name || ''
   if ('php' === target?.name) {
@@ -99,8 +84,6 @@ function featureRuntimeFile(target: any, feature: any): string {
   return feature.name + '_feature.' + ext
 }
 
-// A feature's active hook-stage names (feature.hook.<Stage>.active === true),
-// sorted (each() marks map keys as key$).
 function featureHooks(feature: any): string[] {
   return each(feature.hook || {})
     .filter((h: any) => h && h.active)
@@ -109,7 +92,6 @@ function featureHooks(feature: any): string[] {
 }
 
 
-// --- model readers (mirror the active-item pattern in ReadmeTop.ts) ---
 
 function activeTargets(model: any): any[] {
   const target = getModelPath(model, `main.${KIT}.target`) || {}
@@ -136,9 +118,7 @@ function projectName(model: any): string {
 }
 
 
-// --- shared markdown sections -----------------------------------------------
 
-// (a) basic generation & updating.
 function workflowSection(): string {
   return `## Generating and updating the SDK
 
@@ -201,7 +181,6 @@ regeneration in place cannot see stale output at all.
 }
 
 
-// (b) adding a new generated feature.
 function featureSection(): string {
   return `## Adding a feature
 
@@ -231,7 +210,6 @@ To author a **new** feature:
 }
 
 
-// (c) customising the model and templates (the two-layer mental model).
 function customiseSection(): string {
   return `## Customising: model, templates, components
 
@@ -257,7 +235,6 @@ deps live in \`.sdk/model/target/<lang>.aon\`; features in
 }
 
 
-// (d) how the aontu model language works.
 function aontuSection(): string {
   return `## The model language (aontu, \`.aon\` files)
 
@@ -296,7 +273,6 @@ do not "fix" these into literal disjunctions.
 }
 
 
-// A thin CLAUDE.md that points at the sibling AGENTS.md (same directory).
 function claudePointer(title: string): string {
   return `# ${title}
 

package/src/cmp/AgentGuideTop.ts

@@ -15,10 +15,6 @@ import {
 } from './AgentGuideContent'
 
 
-// Top-level agent guide for a generated SDK project. Emitted once at the
-// project root (no enclosing Folder), alongside README.md/Makefile. Teaches a
-// coding agent how to operate the whole project: regenerate, add features,
-// customise the model/templates, and read the aontu model language.
 const AgentGuideTop = cmp(function AgentGuideTop(props: any) {
   const { ctx$ } = props
   const { model } = ctx$
@@ -47,7 +43,6 @@ There are companion guides deeper in the tree: one per language
 
 `)
 
-    // Targets
     if (0 < targets.length) {
       Content(`**Targets** (${targets.length}):
 
@@ -63,7 +58,6 @@ There are companion guides deeper in the tree: one per language
 `)
     }
 
-    // Features
     if (0 < features.length) {
       Content(`**Features** (${features.length}): `)
       Content(features.map((f: any) => `\`${f.name}\``).join(', ') + `.
@@ -75,7 +69,6 @@ package (other languages). Each target's guide documents its features.
 `)
     }
 
-    // Entities
     if (0 < entities.length) {
       Content(`**Entities** (${entities.length}): `)
       Content(entities.map((e: any) => `\`${e.Name || e.name}\``).join(', ') + `.

package/src/cmp/Changelog.ts

@@ -1,20 +1,6 @@
 import { cmp, Content, File } from 'jostraca'
 
 
-// Root CHANGELOG.md seed. Generated as an initial "Keep a Changelog" skeleton;
-// the version reflects the lockstep SDK version at generation time. (Publish
-// history is carried by the git release tags <target>/vX.Y.Z.)
-//
-// WRITE-ONCE. A changelog is written by people: the skeleton is a starting
-// point, and every entry added after it is content this component cannot
-// reconstruct. Emitted unconditionally, it rewrote the seed over the real
-// file on every `npm run generate`, silently deleting released entries —
-// observed on univec-sdk, where a full model build dropped a committed
-// `## [release/v0.1.2]` section.
-//
-// `exclude: true` returns early when the file already exists (FileOp), the
-// same semantics `sdk-test-control.json` uses for the same reason: a
-// generated file a project is meant to edit must survive regeneration.
 const Changelog = cmp(function Changelog(props: any) {
   const { ctx$ } = props
   const { model } = ctx$

package/src/cmp/Deploy.ts

@@ -6,27 +6,6 @@ import {
 } from '../types'
 
 
-// Generate the SDK root deployment Makefile from the model's per-target
-// `publish` sections (see model/sdkgen.aon):
-//
-//   publish.tag       — git release tag `<prefix>/vX.Y.Z`; every port has
-//                       one, pushed with a token from the boru key vault
-//                       (--for recipe + alias, default github/github).
-//   publish.registry  — package registry details (name, url, vault
-//                       credential recipe or raw env mapping) plus a
-//                       `state` (pending | active | inactive; the legacy
-//                       `active: true` bool is honoured as an alias for
-//                       state === 'active'). While a registry is NOT
-//                       active (publish pending) a real deploy publishes
-//                       the git tag only; the package upload starts when
-//                       state flips to 'active'. Tag-only ports (go
-//                       family) have no registry.
-//
-// Follows the voxgig/struct root Makefile conventions: per-target deploy
-// targets, deliberately no all-targets real deploy (each upload is
-// irreversible), and an everything-at-once DRY run leaning on
-// `boru vault exec --dry-run` filler-token cooperation in each target's
-// publish recipe.
 const Deploy = cmp(function Deploy(props: any) {
   const { ctx$ } = props
   const { model } = ctx$
@@ -66,7 +45,7 @@ function registryOf(t: any): any | undefined {
 // means a deploy publishes the git tag only.
 function regIsActive(reg: any): boolean {
   if (null == reg) return false
-  if (true === reg.active) return true // legacy alias
+  if (true === reg.active) return true
   return 'active' === reg.state
 }
 
@@ -89,7 +68,6 @@ function vaultExecArgs(t: any): string {
   const regVar = reg ? aliasVarName(reg.name) : ''
 
   if (reg && '' === (regVault.recipe || '') && '' !== (regVault.env || '')) {
-    // Raw env mapping style: every credential as alias=ENV_VAR.
     return `'$(${regVar})=${regVault.env},$(${ghVar})=GITHUB_TOKEN'`
   }
 
@@ -103,8 +81,6 @@ function vaultExecArgs(t: any): string {
 
 
 function makeDeployMakefile(model: any, targets: any[]): string {
-  // Alias variables: one per distinct vault credential, defaulting to the
-  // model's alias (or the registry/recipe name).
   const aliasVars = new Map<string, string>()
   for (const t of targets) {
     const tagVault = t.publish?.tag?.vault || {}
@@ -128,7 +104,6 @@ function makeDeployMakefile(model: any, targets: any[]): string {
 
   const deployRules = targets.map((t: any) => {
     const reg = registryOf(t)
-    // The github token is the only credential a tag-only deploy needs.
     const tagVault = t.publish?.tag?.vault || {}
     const ghRecipe = tagVault.recipe || 'github'
     const ghArgs = `--for=${ghRecipe}=$(${aliasVarName(ghRecipe)})`
@@ -137,8 +112,6 @@ function makeDeployMakefile(model: any, targets: any[]): string {
     const via = t.publish?.tag?.via || 'port'
 
     if (!reg && 'root' === via) {
-      // Tag-only port with no Makefile of its own (e.g. go-cli): the
-      // root tag-push recipe is the whole deploy.
       return `
 deploy-${t.name}:
 \t@echo "deploy-${t.name}: tag-only port — publishing the git tag."
@@ -151,9 +124,6 @@ ${tagPushRecipe(t.name, 'tag-only port')}
     }
 
     if (reg && !regIsActive(reg)) {
-      // Publish pending: deploying this target publishes its git tag
-      // only. The package upload turns on by flipping
-      // publish.registry.state to 'active' in the model and regenerating.
       return `
 deploy-${t.name}:
 \t@echo "deploy-${t.name}: ${reg.name} publication is pending — publishing the git tag only."

package/src/cmp/Entity.ts

@@ -28,10 +28,6 @@ const Entity = cmp(function Entity(props: any) {
   const Entity_sdk = requirePath(ctx$, `./cmp/${target.name}/Entity_${target.name}`)
   Entity_sdk['Entity']({ target, entity, entitySDK })
 
-  // Log identifiers, not the model subtrees. `target` and `entity` are large
-  // aontu nodes and this fires once per entity per target (thousands of times
-  // for a big API x 22 targets), so passing them serialised the whole model
-  // fragment each time at default log level.
   log.info({
     point: 'generate-entity', target: target.name, entity: entity.name,
     note: 'target:' + target.name + ', ' + 'entity: ' + entity.name

package/src/cmp/ExternalTarget.ts

@@ -1,31 +1,3 @@
-// The Root for a target that generates OUTSIDE the SDK repo
-// (`main: kit: target: <t>: output: path`).
-//
-// WHY THIS EXISTS, rather than a folder name
-//
-// A target's files normally land in `<sdk-repo>/<target>/`, which the
-// consumer's own `Root.ts` arranges with `Folder({ name: target.name })`.
-// Two things stop that reaching a sibling repo:
-//
-//   - jostraca REFUSES a `..` segment in a Folder name (FileHandler.validName
-//     throws). Escaping the output root through a folder name is not an
-//     oversight to work around; it is the guard that keeps generation inside
-//     the tree it was pointed at.
-//   - the output root is `jopts.folder`, per generate() CALL. So writing
-//     somewhere else means another call, not another folder.
-//
-// So an out-of-tree target gets its own generate() pass, rooted at its
-// output path, with this as the Root. It renders ONE target and nothing
-// else: the consumer Root also emits the SDK repo's own furniture (its
-// README, AGENTS.md, the build scaffold), and none of that belongs in a
-// separate package's repo.
-//
-// No Folder wraps the target here — the destination IS the package, so its
-// files go at the root of the output path.
-//
-// The phase gate mirrors the consumer Root exactly, so `output.path` is not
-// a consumer-target feature: point a language target at another repo and it
-// generates there the same way it would in-tree.
 
 import { cmp, each, names } from 'jostraca'
 
@@ -56,14 +28,6 @@ const ExternalTarget = cmp(function ExternalTarget(props: any) {
   // output sits beside the SDK in a known layout.
   ctx$.sdkrelpath = sdkrelpath
 
-  // The same model preamble the consumer's Root.ts performs before it renders
-  // anything: the case-variant name constants (`Name`, `NAME`, ...) and the
-  // ProjectName replacement map that every template substitution reads.
-  //
-  // Done HERE rather than relied upon, because this pass gets the model the
-  // in-tree pass never touched — Root mutates the filtered copy it is handed,
-  // not this one — and because an SDK project with only out-of-tree targets
-  // must generate the same way as one with both.
   model.const = model.const || { name: model.name }
   names(model.const, model.name)
   if (null == model.const.year) {

package/src/cmp/Feature.ts

@@ -29,7 +29,6 @@ const Feature = cmp(function Feature(props: any) {
 
   if (false !== target.srcfeature) {
     Folder({ name: 'src/feature/' + feature.name }, () => {
-      // TODO: Copy should just warn if from not found
       Copy({
         from: 'tm/' + target.name + '/src/feature/' + feature.name,
         // An ACTIVE feature's INACTIVE plugins do not come with it. This
@@ -37,18 +36,6 @@ const Feature = cmp(function Feature(props: any) {
         // files, because this Copy has already written them.
         exclude: pluginExcludesFor(ctx$.model, feature.name),
         replace: {
-          // Feature templates reference the SDK class by placeholder — e.g.
-          // tm/ts/.../TestFeature.ts imports `ProjectNameSDK`. Without the
-          // standard replacements those placeholders reach the generated
-          // source verbatim and the target fails to COMPILE.
-          //
-          // This worked by accident everywhere it worked: Main_<lang> copies
-          // the whole tm/<lang> tree (feature dirs included) with stdrep
-          // afterwards, so the substituted version overwrote this one. Any
-          // target whose Main excludes src/ — or any consumer .sdk whose
-          // local Main_<lang> lost that Copy — got the raw placeholder.
-          // voxgig-solardemo-sdk hit exactly that and could not build its
-          // TypeScript at all.
           ...ensureStdrep(ctx$),
           FEATURE_VERSION: feature.version,
           FEATURE_Name: feature.Name,
@@ -58,7 +45,6 @@ const Feature = cmp(function Feature(props: any) {
   }
 
   log.info({
-    // Identifiers only — see the note in Entity.ts.
     point: 'generate-feature', target: target.name, feature: feature.name,
     note: 'target:' + target.name + ', ' + 'feature: ' + feature.name
   })