@bongos/core 1.19.528 → 1.19.529

package/docs/module-api-changelog.md

@@ -1493,5 +1493,7 @@ is load-bearing: the script throws rather than guess if it is missing, and
         landed since 1.19.526 with no explicit bump. run 33827382028. (task 1002620)
   1.19.528 — CI auto-patch (publish-on-merge, ADR 0161): carrier for merges
         landed since 1.19.527 with no explicit bump. run 33829339717. (task 1002620)
+  1.19.529 — CI auto-patch (publish-on-merge, ADR 0161): carrier for merges
+        landed since 1.19.528 with no explicit bump. run 33877197857. (task 1002620)
 ---------------------------------------------------------------------------
 ```

package/modules/provisioning/recommendations.js

@@ -39,42 +39,20 @@
 
 'use strict';
 
-const { bundleForProjectType, ALWAYS_ON_CORE } = require('./starter-bundles');
+const { bundleForAnswers, TEAM_SHAPE_RULES, ALWAYS_ON_CORE } = require('./starter-bundles');
 const { PROJECT_DETAIL_VOCAB } = require('./provisioning');
 
-// How the team shape adjusts the type's starter bundle, in application order.
-// Each entry is one condition (`teamShape`) and one effect on ONE opt-in module,
-// carrying the sentence a picker shows when it fires. Deliberately tiny: ADR 0237
-// already made the per-type preset the opinion, and today's opt-in catalog is
-// three modules wide (`agents`, `dev-box`, `discord`) — so this table's job is to
-// correct a preset the owner's answer contradicts, not to re-derive it.
+// `TEAM_SHAPE_RULES` MOVED to starter-bundles.js (BV1.R22, task 1002341; ADR 0243)
+// and is re-exported here so this file's public surface is unchanged. It went to
+// the bundle layer because a bundle adjustment is not advice about the bundle —
+// it IS the bundle once the owner has answered, and `effectiveModules` is the
+// function ADR 0240 §2 hangs the whole skip contract on. A rule the creation
+// picker applies but that fallback does not is two lists kept in agreement by
+// hand, which is the failure ADR 0240 §2 was written to make impossible.
 //
-// A rule may only ever name an OPT-IN module. Adding or removing an always-on one
-// would be a toggle that toggles nothing (ADR 0237 §3's argument, and
-// `tests/provisioning_recommendations.mjs` fails the build over it).
-const TEAM_SHAPE_RULES = Object.freeze([
-  Object.freeze({
-    id: 'a-community-needs-somewhere-to-gather',
-    teamShape: 'community',
-    effect: 'add',
-    module: 'discord',
-    reason: 'You said an open community is building this, so somewhere for it to gather is switched on.',
-  }),
-  Object.freeze({
-    id: 'a-team-shares-one-environment',
-    teamShape: 'small-team',
-    effect: 'add',
-    module: 'dev-box',
-    reason: 'A small team gets one shared environment to build in, so nobody is debugging their own laptop.',
-  }),
-  Object.freeze({
-    id: 'building-alone-needs-no-shared-environment',
-    teamShape: 'solo',
-    effect: 'remove',
-    module: 'dev-box',
-    reason: 'You are building this alone, so the shared cloud environment is off — your own machine is the setup.',
-  }),
-]);
+// What stays HERE is the advice: a governance preset that is only ever previewed,
+// and an invite SEEK nothing in this module may run. Neither is a thing a project
+// silently ends up with, so neither belongs in the read-time resolution.
 
 // The governance presets, by key. A preset is a NAME plus the one sentence that
 // says what living under it feels like — never a set of roles or permissions,
@@ -167,25 +145,6 @@ function normalizeTeamShape(value) {
   return PROJECT_DETAIL_VOCAB.team_shape.includes(value) ? value : null;
 }
 
-// Apply the team-shape rules to one type's opt-in bundle. Returns the adjusted
-// list plus the adjustments that ACTUALLY changed it — a rule whose module the
-// bundle already carries (or already lacks) records nothing, because a stated
-// reason for a change that did not happen is a lie the owner cannot check.
-// Never touches the always-on core. PURE.
-function adjustBundle(bundle, teamShape) {
-  const modules = [...bundle];
-  const adjustments = [];
-  for (const rule of TEAM_SHAPE_RULES) {
-    if (rule.teamShape !== teamShape) continue;
-    const at = modules.indexOf(rule.module);
-    if (rule.effect === 'add' && at === -1) modules.push(rule.module);
-    else if (rule.effect === 'remove' && at !== -1) modules.splice(at, 1);
-    else continue;
-    adjustments.push({ rule: rule.id, effect: rule.effect, module: rule.module, reason: rule.reason });
-  }
-  return { modules, adjustments };
-}
-
 // The whole recommendation for one set of creation answers:
 //
 //   {
@@ -211,8 +170,10 @@ function adjustBundle(bundle, teamShape) {
 function recommendationsForDetails(answers) {
   const given = answers && typeof answers === 'object' && !Array.isArray(answers) ? answers : {};
   const teamShape = normalizeTeamShape(given.team_shape);
-  const preset = bundleForProjectType(given.type);
-  const { modules, adjustments } = adjustBundle(preset.bundle, teamShape);
+  // The SAME resolver the picker preselects from and effectiveModules falls back
+  // to (ADR 0243) — so the recommendation, the panel and the project a skipped
+  // picker ends up with are one function's answer, not three that agree.
+  const preset = bundleForAnswers(given.type, teamShape);
 
   const gov = GOVERNANCE_RULES.find((r) => r.teamShape === teamShape) || GOVERNANCE_DEFAULT;
   const invite = INVITE_RULES.find((r) => r.teamShape === teamShape) || INVITE_DEFAULT;
@@ -226,9 +187,9 @@ function recommendationsForDetails(answers) {
       label: preset.label,
       summary: preset.summary,
       core: [...ALWAYS_ON_CORE],
-      bundle: modules,
-      modules: [...ALWAYS_ON_CORE, ...modules],
-      adjustments,
+      bundle: preset.bundle,
+      modules: preset.modules,
+      adjustments: preset.adjustments,
     },
     governance: {
       preset: gov.preset,

package/modules/provisioning/routes/provisioning.js

@@ -36,7 +36,7 @@ const auth = api;
 const { pool, validateOrRespond, parseId } = api;
 const provisioning = require('../provisioning');
 const { onboardPlan, stepsForShape } = require('../onboard-plan');
-const { ALWAYS_ON_CORE, OPTIONAL_MODULES, allStarterBundles, optionalModules } = require('../starter-bundles');
+const { ALWAYS_ON_CORE, OPTIONAL_MODULES, starterBundleAnswerTable, optionalModules, effectiveModules } = require('../starter-bundles');
 const { recommendationsForDetails } = require('../recommendations');
 const { makeAskRateLimiter, clientIp } = require('../rate-limit');
 // task 1003208: structured logging (pino via the doorway) — was console.*.
@@ -840,6 +840,8 @@ module.exports = function provisioningRoutes() {
         // project is now on the map, and one who cleared it learns it just left.
         // Re-deriving it from a follow-up GET would let the two answers disagree.
         publish: publishVerdict(updated),
+        // `team_shape` MOVES a bundle-sourced project's modules — effect with cause (ADR 0243 §5).
+        modules: effectiveModules(updated),
       });
     } catch (err) {
       log.error('[provisioning] PATCH /provisioning/instances/:id/detail', err);
@@ -1337,8 +1339,10 @@ module.exports = function provisioningRoutes() {
   // row for. The alternatives were both worse: `GET /modules` needs a session
   // (this wizard is read signed-out) and `GET /public/modules` serves booleans,
   // not copy. Additive — `core` and `bundles` keep their shape.
+  // `byTeamShape` re-resolves each bundle for every answer the About step can give,
+  // riding THIS payload rather than a second read (task 1002341; ADR 0243 §4).
   router.get('/provisioning/starter-bundles', (req, res) => {
-    res.json({ core: [...ALWAYS_ON_CORE], bundles: allStarterBundles(), optional: optionalModules() });
+    res.json({ core: [...ALWAYS_ON_CORE], bundles: starterBundleAnswerTable(), optional: optionalModules() });
   });
 
   // GET /provisioning/recommendations?type=<project type>&team_shape=<interview answer>

package/modules/provisioning/starter-bundles.js

@@ -106,6 +106,60 @@ const OPTIONAL_MODULES = Object.freeze([
 // so the declaration above stays the single place a choice is written down.
 const OPTIONAL_MODULE_KEYS = Object.freeze(OPTIONAL_MODULES.map((m) => m.key));
 
+// How the interview's team-shape answer ADJUSTS the type's starter bundle, in
+// application order. Each entry is one condition (`teamShape`) and one effect on
+// ONE opt-in module, carrying the sentence the picker shows when it fires.
+//
+// WHY THE TABLE LIVES HERE and not in recommendations.js beside the governance
+// and invite tables it shipped with (task 1002336, ADR 0239). A bundle adjustment
+// is not advice about the bundle — it IS the bundle, once the owner has answered.
+// `effectiveModules` below is the function ADR 0240 §2 leans the whole skip
+// contract on ("the preselect and the fallback are the same declaration — one
+// function, called twice"), and a rule the picker applies but that function does
+// not is exactly two lists kept in agreement by hand. So the rules sit at the
+// bundle layer, `effectiveModules` applies them, and recommendations.js re-exports
+// them unchanged — its governance preview and invite seam are genuinely advice and
+// stay there. Decision: ADR 0243 (BV1.R22, task 1002341).
+//
+// Deliberately tiny: ADR 0237 already made the per-type preset the opinion, and
+// today's opt-in catalog is three modules wide — so this table's job is to correct
+// a preset the owner's answer contradicts, not to re-derive it.
+//
+// A rule may only ever name an OPT-IN module. Adding or removing an always-on one
+// would be a toggle that toggles nothing (ADR 0237 §3's argument, and
+// `tests/provisioning_recommendations.mjs` fails the build over it).
+const TEAM_SHAPE_RULES = Object.freeze([
+  Object.freeze({
+    id: 'a-community-needs-somewhere-to-gather',
+    teamShape: 'community',
+    effect: 'add',
+    module: 'discord',
+    reason: 'You said an open community is building this, so somewhere for it to gather is switched on.',
+  }),
+  Object.freeze({
+    id: 'a-team-shares-one-environment',
+    teamShape: 'small-team',
+    effect: 'add',
+    module: 'dev-box',
+    reason: 'A small team gets one shared environment to build in, so nobody is debugging their own laptop.',
+  }),
+  Object.freeze({
+    id: 'building-alone-needs-no-shared-environment',
+    teamShape: 'solo',
+    effect: 'remove',
+    module: 'dev-box',
+    reason: 'You are building this alone, so the shared cloud environment is off — your own machine is the setup.',
+  }),
+]);
+
+// The team shapes the rules above can fire on. Derived from the table rather than
+// imported from provisioning.js's PROJECT_DETAIL_VOCAB, because importing it would
+// point this file UP at the module that requires it. It costs nothing to derive:
+// an off-vocabulary shape matches no rule and adjusts nothing, which is already
+// the right answer — `tests/provisioning_recommendations.mjs` pins the two lists
+// against each other so a fourth interview answer cannot arrive unhandled.
+const RULED_TEAM_SHAPES = Object.freeze([...new Set(TEAM_SHAPE_RULES.map((r) => r.teamShape))]);
+
 // The curated presets, keyed by the declared project type (the closed vocabulary
 // owner-decided 2026-08-13 and mirrored in provisioning.PROJECT_TYPES + the
 // provisioning_007 CHECK). `label` and `summary` are the owner-facing copy the
@@ -192,6 +246,69 @@ function optionalModules() {
   return OPTIONAL_MODULES.map((m) => ({ ...m }));
 }
 
+// Apply the team-shape rules to one type's opt-in bundle. Returns the adjusted
+// list plus the adjustments that ACTUALLY changed it — a rule whose module the
+// bundle already carries (or already lacks) records nothing, because a stated
+// reason for a change that did not happen is a lie the owner cannot check.
+// A null/unknown/off-vocabulary shape fires no rule and adjusts nothing, which is
+// the same answer `normalizeProjectDetail` gives such a value on the way in.
+// Never touches the always-on core. PURE.
+function adjustBundle(bundle, teamShape) {
+  const held = new Set(bundle);
+  const adjustments = [];
+  for (const rule of TEAM_SHAPE_RULES) {
+    if (rule.teamShape !== teamShape) continue;
+    if (rule.effect === 'add' && !held.has(rule.module)) held.add(rule.module);
+    else if (rule.effect === 'remove' && held.has(rule.module)) held.delete(rule.module);
+    else continue;
+    adjustments.push({ rule: rule.id, effect: rule.effect, module: rule.module, reason: rule.reason });
+  }
+  // CATALOG order, not append order — `normalizeModuleSelection` stores a chosen
+  // set this way and the picker re-derives its toggles this way, so an adjusted
+  // bundle that appended would make the same set of modules read as a different
+  // list depending on whether the owner answered the picker or skipped it.
+  return { modules: OPTIONAL_MODULE_KEYS.filter((k) => held.has(k)), adjustments };
+}
+
+// What the creation flow preselects for one set of ANSWERS — `bundleForProjectType`
+// with the team-shape rules applied, in the same `{ type, label, summary, core,
+// bundle, modules }` shape plus the `adjustments` delta that got it there.
+//
+// This is the single resolver the picker paints from and `effectiveModules` falls
+// back to, so an owner who answers the interview and then skips the picker gets
+// the set the panel was showing them (ADR 0240 §2's property, extended to the
+// interview's answer — BV1.R22, ADR 0243). PURE; arrays are fresh.
+function bundleForAnswers(type, teamShape) {
+  const preset = bundleForProjectType(type);
+  const { modules, adjustments } = adjustBundle(preset.bundle, teamShape);
+  return {
+    ...preset,
+    bundle: modules,
+    modules: [...ALWAYS_ON_CORE, ...modules],
+    adjustments,
+  };
+}
+
+// Every curated bundle resolved for every team shape the rules can fire on, plus
+// the no-answer resolution — the whole preselect table in ONE read.
+//
+// The picker needs this shape rather than a per-answer query because ADR 0240 §4's
+// rule is that what may be chosen and what is preselected have to arrive together
+// or the panel can preselect a key it has no row for. The owner flips the type
+// question and the team-shape question freely on two earlier panels; re-preselecting
+// must not cost a round trip, and a round trip it did pay could land after they had
+// moved on. PURE — five types by four answers is twenty small rows.
+function starterBundleAnswerTable() {
+  return allStarterBundles().map((preset) => {
+    const byTeamShape = {};
+    for (const shape of RULED_TEAM_SHAPES) {
+      const { modules, adjustments } = adjustBundle(preset.bundle, shape);
+      byTeamShape[shape] = { bundle: modules, adjustments };
+    }
+    return { ...preset, byTeamShape };
+  });
+}
+
 // A MODULE SELECTION as it may be STORED (BV1.R20, task 1002339): opt-in keys
 // only, deduped, in catalog order. Everything else is dropped — an always-on
 // module (it was never a choice), a hub-only one (the control plane's own), and
@@ -218,22 +335,39 @@ function normalizeModuleSelection(input) {
 
 // What a row's modules READ as: the always-on floor, plus whatever the owner
 // chose — or, when they never answered, the starter bundle for their declared
-// type. `source` says which of the two it is, so a surface can tell a chosen
-// empty set from an unanswered one without re-deriving the rule.
+// type ADJUSTED by what they told the interview. `source` says which of the two
+// it is, so a surface can tell a chosen empty set from an unanswered one without
+// re-deriving the rule.
 //
 // This is what makes skipping the picker a supported default rather than a
 // project with nothing on it: the flow's preselect and the server's fallback are
 // the SAME declaration, so the owner gets exactly the set the panel showed them.
-// PURE — takes a row-shaped `{ type, modules }`, touches no database.
+// The team-shape adjustment is INSIDE that fallback (BV1.R22, ADR 0243) for
+// exactly that reason — the picker paints the adjusted set, so a picker skipped
+// after an answered interview has to resolve to the adjusted set too, or the
+// panel's promise stops being true the moment the interview is answered.
+//
+// Reads `detail.team_shape` straight off the row rather than through
+// provisioning.js's `normalizeProjectDetail` — importing it would point this file
+// up at the module that requires it, and it would buy nothing: an off-vocabulary
+// shape fires no rule and adjusts nothing, which is the answer the normalizer
+// would have produced anyway.
+//
+// PURE — takes a row-shaped `{ type, modules, detail }`, touches no database.
 function effectiveModules(row) {
   const chosen = normalizeModuleSelection(row && row.modules);
-  const preset = bundleForProjectType(row && row.type);
+  const detail = row && row.detail && typeof row.detail === 'object' ? row.detail : null;
+  const preset = bundleForAnswers(row && row.type, detail ? detail.team_shape : null);
   const selected = chosen === null ? preset.bundle : chosen;
   return {
     core: [...ALWAYS_ON_CORE],
     selected,
     modules: [...ALWAYS_ON_CORE, ...selected],
     source: chosen === null ? 'bundle' : 'chosen',
+    // Why the unanswered set is what it is, in the owner's own words — empty when
+    // nothing adjusted it, and never populated for a `chosen` set, because an
+    // owner's own toggle needs no reason given back to them.
+    adjustments: chosen === null ? preset.adjustments : [],
   };
 }
 
@@ -242,9 +376,14 @@ module.exports = {
   HUB_ONLY_MODULES,
   OPTIONAL_MODULES,
   STARTER_BUNDLES,
+  TEAM_SHAPE_RULES,
+  RULED_TEAM_SHAPES,
   bundleForProjectType,
   allStarterBundles,
   optionalModules,
+  adjustBundle,
+  bundleForAnswers,
+  starterBundleAnswerTable,
   normalizeModuleSelection,
   effectiveModules,
 };

package/modules/public-landing/public/projects.html

@@ -328,6 +328,14 @@ summary{min-height:24px;padding:3px 0;}
 .tpill:hover::before{border-color:var(--ink-faint);}
 .tpill[aria-pressed=true]{background:none;border-color:var(--rule-soft);color:var(--ink);}
 .tpill[aria-pressed=true]::before{background:var(--accent);border-color:var(--accent);outline:4px solid color-mix(in srgb,var(--accent) 22%,transparent);}
+/* Why the picker preselected what it did (task 1002341) — one line per rule that
+   moved something, between the band and the always-on clause. Wears .reassure's
+   weight on purpose: this is the panel explaining itself, never a thing to act on,
+   so it must not compete with the toggles it is explaining. */
+.modWhy{display:none;}
+.modWhy.on{display:grid;gap:6px;margin:0 0 14px;max-width:62ch;}
+.modWhy span{font-size:13.5px;font-weight:400;color:var(--ink-soft);line-height:1.5;}
+
 /* the module picker (task 1002339) wears the SAME band as the type and team
    questions — one hairline cell per choice, the dot on the chosen ones. The only
    difference is that a module carries a one-line summary under its name, so its
@@ -1017,11 +1025,12 @@ summary{min-height:24px;padding:3px 0;}
                to make, when in fact they were never choices. -->
           <section class="panel" id="panel-modules" aria-labelledby="mod-h">
             <h1 id="mod-h">What it comes with</h1>
-            <p class="lede">Optional — skip it and you get the suggested set below. These are extras on top of everything every project already has, and you can switch any of them on or off later.</p>
+            <p class="lede">Optional — skip it and you get the suggested set below, shaped by what you just told us. These are extras on top of everything every project already has, and you can switch any of them on or off later.</p>
             <form data-next="5">
               <div class="wizField"><span id="modLbl">Extras for this project</span>
                 <div class="typeCards" id="modCards" role="group" aria-labelledby="modLbl"></div>
               </div>
+              <div class="modWhy" id="modWhy" aria-live="polite"></div>
               <div class="reassure" id="modCoreNote"></div>
               <div class="hint" id="h-modules">&nbsp;</div>
               <div class="nav">
@@ -3204,10 +3213,39 @@ summary{min-height:24px;padding:3px 0;}
       if (state.step === 4) renderModules();
       else if (state.step === 7) renderReview();
     }
+    /* The row for the declared type, or null before the read lands / for a type
+       the table has no row for (including no type at all). */
+    function bundleRow() {
+      if (!starterBundles) return null;
+      return (starterBundles.bundles || []).filter(function (b) { return b.type === state.projType; })[0] || null;
+    }
+    /* The type's preselect AS THE ABOUT STEP'S ANSWER SHAPES IT (task 1002341,
+       BV1.R22). The server resolved every combination into byTeamShape, so
+       answering "just me" three panels back re-preselects here with no round trip
+       and no rule applied twice in two languages — the wizard reads the same
+       table `effectiveModules` falls back to (ADR 0243).
+
+       An older payload without byTeamShape, or a team shape no rule fires on,
+       falls through to the unadjusted bundle: the answer this panel showed before
+       R22, which is never wrong, only untailored. */
+    function tailoredRow() {
+      var row = bundleRow();
+      if (!row) return null;
+      var forShape = row.byTeamShape && state.teamShape ? row.byTeamShape[state.teamShape] : null;
+      return forShape || { bundle: row.bundle || [], adjustments: [] };
+    }
     function preselectedModules() {
-      if (!starterBundles) return [];
-      var forType = (starterBundles.bundles || []).filter(function (b) { return b.type === state.projType; })[0];
-      return forType ? forType.bundle.slice() : [];
+      var row = tailoredRow();
+      return row ? row.bundle.slice() : [];
+    }
+    /* Why the preselect is what it is, in the owner's own words — one sentence per
+       rule that ACTUALLY moved something. Empty when nothing did, and empty once
+       the owner has answered for themselves: a reason given back for a toggle they
+       flipped reads as the panel arguing with them. */
+    function preselectReasons() {
+      if (state.modules !== null) return [];
+      var row = tailoredRow();
+      return row ? (row.adjustments || []) : [];
     }
     /* What the panel paints and the review names: the owner's answer if they
        gave one, otherwise the type's preselect. */
@@ -3233,6 +3271,8 @@ summary{min-height:24px;padding:3px 0;}
            a moment; only a read that ANSWERED badly gets the clause, so a slow
            network never tells the owner something is broken when it isn't. */
         band.innerHTML = '';
+        $('modWhy').innerHTML = '';
+        $('modWhy').classList.remove('on');
         note.textContent = bundlesFailed
           ? 'We couldn’t load the list of extras just now. Your project is created with everything it needs either way, and you can add extras from its settings.'
           : '';
@@ -3245,6 +3285,17 @@ summary{min-height:24px;padding:3px 0;}
           + (on.indexOf(m.key) === -1 ? 'false' : 'true') + '"><span><b>' + esc(m.label)
           + '</b><small>' + esc(m.summary) + '</small></span></button>';
       }).join('');
+      /* The tailoring, said out loud (task 1002341). A preselect an owner cannot
+         see the reason for is one they have to audit, which is the thing ADR 0237
+         says is worse than no preselect at all. Rendered as its own block above the
+         core clause, because it is about THIS project's answers while the clause
+         below is about every project. */
+      var why = $('modWhy');
+      var reasons = preselectReasons();
+      why.innerHTML = reasons.length
+        ? reasons.map(function (a) { return '<span>' + esc(a.reason) + '</span>'; }).join('')
+        : '';
+      why.classList.toggle('on', reasons.length > 0);
       var core = (starterBundles.core || []).length;
       note.textContent = core
         ? 'Every project also starts with the same ' + core + ' core parts — the platform itself, the way it tracks work, and the builders’ hall. They are always on, so they are not part of this choice.'

package/package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "@bongos/core",
-  "version": "1.19.528",
+  "version": "1.19.529",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@bongos/core",
-      "version": "1.19.528",
+      "version": "1.19.529",
       "license": "AGPL-3.0-or-later",
       "dependencies": {
         "express": "^4.21.2",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bongos/core",
-  "version": "1.19.528",
+  "version": "1.19.529",
   "description": "Cloud Bongos — the AI-first build platform core (GDS + platform surfaces + module system), installed as a versioned dependency (ADR 0108).",
   "license": "AGPL-3.0-or-later",
   "main": "src/platform-server.js",

package/src/module-api.js

@@ -45,7 +45,7 @@ const { validateOrRespond, LIMITS, parseId, asyncHandler, corsPublicGet, parsePa
 // there. scripts/gds/bump-version.js still rewrites the literal below; it appends
 // the entry to that file. Look for a version's history there, not here.
 // ---------------------------------------------------------------------------
-const CORE_VERSION = '1.19.528'; // CI auto-patch carrier (ADR 0161); changelog: docs/module-api-changelog.md
+const CORE_VERSION = '1.19.529'; // CI auto-patch carrier (ADR 0161); changelog: docs/module-api-changelog.md
 
 // A namespaced logger so a module's log lines are attributable + consistent.
 // Usage: const log = api.logger('dev-box'); log.info('mounted');