@bongos/core 1.24.79 → 1.24.80

package/scripts/bongos/gen-hall-sitemap.js

@@ -46,7 +46,7 @@ const vm = require('vm');
 const ROOT = path.resolve(__dirname, '..', '..');
 const HALL = 'modules/hall-ui/public';
 const OUT = 'docs/hall-sitemap.md';
-const CRAFTS = ['building', 'artistry', 'ideating', 'governing'];
+const CRAFTS = ['artisan', 'artist', 'patron']; // the game's characters (task 1005141)
 
 // URLs the server answers that are not a page file in the hall. A link to one is not broken.
 // A NEW route a page links to belongs here, with where the server serves it; the audit fails
@@ -69,7 +69,7 @@ const ROUTES = {
 // Targets that leave the hall on purpose: sign-in, the hub's /account (platform-server.js;
 // settings.js points the link at the hub), the API, module assets, and any file with an extension.
 const EXTERNAL = [/^\/api\//, /^\/auth\b/, /^\/login\b/, /^\/logout\b/, /^\/signin\b/, /^\/status\b/,
-  /^\/account\b/, /^\/modules\//, /^\/docs\b/, /^\/diagrams\//, /^\/healthz\b/, /^\/version\b/, /\.[a-z0-9]{2,5}$/i];
+  /^\/account\b/, /^\/modules\//, /^\/docs\b/, /^\/diagrams\//, /^\/characters\//, /^\/healthz\b/, /^\/version\b/, /\.[a-z0-9]{2,5}$/i];
 
 // Pages whose words come from a markdown file they fetch. A link in that file to a hall page's
 // own file (../../modules/hall-ui/public/<page>.html) opens the page in the hall (primer.js,
@@ -155,6 +155,7 @@ const LINK_RES = [
   /href=\\?["']\$\{(?![^}]*\bhub)[^}]*\}(\/[a-z0-9-][^"'\\\s$`{]*)/g,
   /Href\([^)]*\)\s*\{\s*return\s+'(\/[^'\s$]*)'/g,               // function itemHref(id) { return '/x?id=' + … }
   /\bhref\s*:\s*'(\/[^'\s$]*)'/g,                            // { href: '/x' }
+  /\bembed\s*:\s*'(\/[^'\s$]*)'/g,                           // { embed: '/x' } — an options menu entry opens it in a frame (task 1005144)
   /\.href\s*=\s*'(\/[^'\s$]*)'/g,                            // a.href = '/x'
   /setAttribute\(\s*'href'\s*,\s*'(\/[^'\s$]*)'/g,          // setAttribute('href', '/x')
   /location\.(?:assign|replace)\(\s*'(\/[^'\s$]*)'/g,       // location.assign('/x')
@@ -288,12 +289,11 @@ function dedupe(list) {
 }
 
 // ---- the document ----
-const CRAFT_NAME = { building: 'Building', artistry: 'Artistry', ideating: 'Ideating', governing: 'Governing' };
+const CRAFT_NAME = { artisan: 'Artisan', artist: 'Artist', patron: 'Patron' };
 const CRAFT_HOME = {
-  building: '/ — the project city',
-  artistry: '/ — the gallery',
-  ideating: '/ — the sky over the city',
-  governing: '/street — the governor\'s street (Home hops there)',
+  artisan: '/ — the project city',
+  artist: '/ — the gallery',
+  patron: '/street — the governor\'s street (Home hops there)',
 };
 function list(xs) { return xs.length ? xs.map((x) => '`' + x + '`').join(', ') : '—'; }
 function render(m) {

package/scripts/bongos/grade-smoke.js

@@ -35,7 +35,7 @@ Acceptance:
 - One unit test in tests/util.mjs covers two cases (positive + negative).
 Out of scope: anything to do with timezones; calendar-aware durations.`,
   kind: 'feature',
-  discipline: 'engineer',
+  discipline: 'artisan',
   version_id: 'GDS-V3',
 };
 const GOOD_VALUE_SUMMARY =
@@ -85,7 +85,7 @@ Acceptance:
 - One smoke test that exercises the charge → row → rollback paths.
 Out of scope: refund flow.`,
   kind: 'feature',
-  discipline: 'engineer',
+  discipline: 'artisan',
   version_id: 'GDS-V3',
 };
 const BAD_VALUE_SUMMARY =

package/scripts/bongos/init.js

@@ -784,7 +784,7 @@ async function seedViaApi(spec, { dryRun, log = console.log, api = apiCall } = {
     attempted++;
     const res = await api('POST', '/api/bongos/tasks', {
       version_id: vp.id, goal_id: goalId, title: t.title, description: t.description || '', status: 'ready',
-      kind: t.kind || 'infra', discipline: t.discipline || 'engineer', source: 'bongos-init', ...extra,
+      kind: t.kind || 'infra', discipline: t.discipline || 'artisan', source: 'bongos-init', ...extra,
     });
     if (!res.ok) failures.push({ title: t.title, status: res.status, detail: JSON.stringify(res.data) });
     return res.ok;
@@ -794,7 +794,7 @@ async function seedViaApi(spec, { dryRun, log = console.log, api = apiCall } = {
   let created = 0;
   for (const t of starters) {
     // task 1002988: `discipline: undefined` used to sit in this extras object, and
-    // because `...extra` spreads AFTER postTask's own `t.discipline || 'engineer'`
+    // because `...extra` spreads AFTER postTask's own `t.discipline || 'artisan'`
     // it clobbered that default back to nothing — which is why a freshly scaffolded
     // instance was born with role-less starter tasks. Dropped, so starters inherit
     // the same default every other seeded task already got.

package/scripts/bongos/newcomer-floor.config.json

@@ -6,9 +6,8 @@
   "auto_promote": true,
   "max_generate_per_run": 8,
   "disciplines": {
-    "engineer": { "floor": 2 },
+    "artisan": { "floor": 2 },
     "artist": { "floor": 3 },
-    "ideator": { "floor": 2 },
     "ui": { "floor": 2 }
   }
 }

package/scripts/bongos/newcomer-floor.js

@@ -10,8 +10,8 @@
 // session, so the floor silently drained to 0/0/0 and stayed there.
 //
 // WHAT THIS DOES NOW: each discipline defines a LIST of EVERGREEN chores in
-// `newcomer-floor.templates.json` (engineer = "add a unit test" + the constrained
-// docs-hygiene sweep; artist = generate an asset; ideator = file ideas). A chore's
+// `newcomer-floor.templates.json` (artisan = "add a unit test" + the constrained
+// docs-hygiene sweep; artist = generate an asset, or file ideas). A chore's
 // definition never changes, yet running it is always valuable. Each chore keeps its
 // OWN standing pool to its OWN per-template `floor`; when a chore's ready copies drop
 // below that floor, this script stamps fresh IDENTICAL claimable COPIES of it. No AI,
@@ -64,7 +64,7 @@ const HARD_MAX_MINUTES = 60; // newcomer scope ceiling, never exceeded (task 614
 // It is the craft VOCABULARY, which is why 'unclassified' is absent. Keep in step
 // with the keys in newcomer-floor.templates.json ('ui' added by task 1003487); the
 // server-side restock reads the live offered set instead (newcomer-restock.js).
-const VALID_DISCIPLINES = new Set(['engineer', 'artist', 'ideator', 'ui']);
+const VALID_DISCIPLINES = new Set(['artisan', 'artist', 'ui']);
 // Every status a copy's source_ref could occupy — scanned so `seq` is globally
 // monotonic and never recycles a ref already used by a shipped/abandoned copy.
 const ALL_STATUSES = ['backlog', 'ready', 'active', 'completed', 'confirmed', 'shipped', 'blocked', 'abandoned'];
@@ -307,6 +307,7 @@ async function main() {
     discipline: arg('--discipline', args),
     configPath: arg('--config', args) || DEFAULT_CONFIG_PATH,
   };
+  if (FLAGS.discipline) FLAGS.discipline = ({ engineer: 'artisan', ideator: 'artist' })[FLAGS.discipline] || FLAGS.discipline;
   if (FLAGS.discipline && !VALID_DISCIPLINES.has(FLAGS.discipline)) {
     console.error(`bad --discipline "${FLAGS.discipline}"; valid: ${[...VALID_DISCIPLINES].join(', ')}`);
     process.exit(2);

package/scripts/bongos/newcomer-floor.templates.json

@@ -1,16 +1,16 @@
 {
-  "_doc": "The evergreen newcomer chores, grouped BY DISCIPLINE. Each discipline maps to a LIST of chore templates (was a single object before task 1488 — a discipline can now offer several first-builder chores so newcomers are not funnelled into one). The deterministic replenisher (scripts/bongos/newcomer-floor.js) and the on-claim restock (modules/onboarding/newcomer-restock.js) stamp disposable claimable COPIES from each template; the TEMPLATE is never claimed and never ships. Each copy's source_ref is tmpl:<discipline>:<template_id>:<seq> (monotonic), so identical-title copies never collide with the dedup. Per-template `floor` sets that chore’s standing pool depth; if a template omits it, the discipline default in newcomer-floor.config.json applies. credits_reward, est_minutes and floor all live here (per chore). version_id is per-template so each chore lands on the correct track; it MUST point at an open (non-shipped) version — update it at version close, or the replenisher's open-version guard refuses to stamp and the floor silently stops refilling (task 1002958: the engineer pins still read the long-shipped GDS-V4 and artist+ideator read V2, a version this ladder never had, so NO discipline could restock). touches[] is intentionally empty so multiple same-discipline newcomers can claim copies concurrently; git-merge is the real collision detector. To ADD a chore: append an entry to the discipline's array. To CHANGE one: edit it here — no code change needed. UI offers two browser-free chores (a token-drift fix measured by validate-design.js, and an accessible-name fix) so a newcomer whose only craft is ui is never starved for work on a machine with no Chrome/Edge for the kit — task 1003487. Engineer offers a SAFE coding chore (add a unit test — touches only tests/, which auto-ships) and the docs-hygiene sweep (constrained to non-protected docs so a sub-Metic ship does not stall on the authority core).",
-  "engineer": [
+  "_doc": "The evergreen newcomer chores, grouped BY DISCIPLINE. Each discipline maps to a LIST of chore templates (was a single object before task 1488 — a discipline can now offer several first-builder chores so newcomers are not funnelled into one). The deterministic replenisher (scripts/bongos/newcomer-floor.js) and the on-claim restock (modules/onboarding/newcomer-restock.js) stamp disposable claimable COPIES from each template; the TEMPLATE is never claimed and never ships. Each copy's source_ref is tmpl:<discipline>:<template_id>:<seq> (monotonic), so identical-title copies never collide with the dedup. Per-template `floor` sets that chore’s standing pool depth; if a template omits it, the discipline default in newcomer-floor.config.json applies. credits_reward, est_minutes and floor all live here (per chore). version_id is per-template so each chore lands on the correct track; it MUST point at an open (non-shipped) version — update it at version close, or the replenisher's open-version guard refuses to stamp and the floor silently stops refilling (task 1002958: the engineer pins still read the long-shipped GDS-V4 and artist+ideator read V2, a version this ladder never had, so NO discipline could restock). touches[] is intentionally empty so multiple same-discipline newcomers can claim copies concurrently; git-merge is the real collision detector. To ADD a chore: append an entry to the discipline's array. To CHANGE one: edit it here — no code change needed. UI offers two browser-free chores (a token-drift fix measured by validate-design.js, and an accessible-name fix) so a newcomer whose only craft is ui is never starved for work on a machine with no Chrome/Edge for the kit — task 1003487. Artisan offers a SAFE coding chore (add a unit test — touches only tests/, which auto-ships) and the docs-hygiene sweep (constrained to non-protected docs so a sub-Metic ship does not stall on the authority core).",
+  "artisan": [
     {
       "template_id": "unit-test-pass",
       "version_id": "BONGOS-V1",
-      "discipline": "engineer",
+      "discipline": "artisan",
       "kind": "feature",
       "est_minutes": 45,
       "credits_reward": 15,
       "floor": 2,
       "title": "Add a unit test for an untested pure exported helper (assert its real behaviour)",
-      "description": "## What you're doing\n\nThe repo's safety net is its **unit suite** — every `tests/*.mjs` file, run by `scripts/bongos/run-unit-tests.js` in CI on every PR. New pure tests are **auto-discovered** (there is no allowlist to edit), so the moment you add one it joins the gate. Your first ship as an engineer: pick ONE exported helper that has thin or no test coverage and add a focused, DB-free unit test for it.\n\nIt is identical for every newcomer and **always valuable** — coverage is never \"done\", the codebase has hundreds of small pure helpers, and a good test both guards behaviour and teaches you how a corner of the system works. It is also **safe to auto-ship**: you add ONE file under `tests/`, which is not a protected surface, so a clean test merges on green with no owner approval.\n\n## How to pick a target (a PURE helper)\n\nPick a **pure** function — deterministic, with no database, network, filesystem, or live-server dependency — so the test runs standalone. Do not hunt by hand: run the finder, which reads the live tree every time (so this task never goes stale the way a written list does):\n\n```\nnode scripts/bongos/find-untested.js\n```\n\nIt lists modules that **no test file names**, best candidates first — ones no test reaches at all, then ones that look pure, then the smallest. Its purity column is a heuristic: open the module and confirm the helper you pick really needs no database, network or files. If the list is empty, run it with `--all` and pick a module that still exports a helper you can test DB-free.\n\n## How to write it (mirror an existing test — there is no framework)\n\nThese tests are plain Node scripts using `node:assert`; there is no test runner. Open a small existing one as your model — for example `tests/criterion_ref_parse.mjs` or `tests/task_classifier_vocab.mjs` — and copy the shape:\n1. `import` / `require` the helper from its module.\n2. Assert **several** cases, including at least one **edge / boundary** case (empty input, null, a tricky value).\n3. Print a one-line success message at the end (an assert that throws exits non-zero, which is how the gate sees a failure).\n\nName the file `tests/<helper-or-module>.mjs`.\n\n## Verify + ship\n\nRun BOTH and confirm both are green:\n- `node tests/<your-file>.mjs` — your test alone, exits 0.\n- `node scripts/bongos/run-unit-tests.js` — the whole gate, with your test auto-included.\n\nThen `/builder-ship`. The ship notes must name the helper and file you tested.\n\n## Stay safe (off-limits)\n\nAdd exactly ONE new file under `tests/`. Do NOT edit `scripts/bongos/run-unit-tests.js` (it auto-discovers your test, and it is a protected file you may not touch), and do NOT change the helper you are testing. Your test must be **DB-free**: anything needing Postgres, the network, or a live server belongs in the integration gate and will fail standalone here. Touch no permission, pipeline, migration, or infra file.",
+      "description": "## What you're doing\n\nThe repo's safety net is its **unit suite** — every `tests/*.mjs` file, run by `scripts/bongos/run-unit-tests.js` in CI on every PR. New pure tests are **auto-discovered** (there is no allowlist to edit), so the moment you add one it joins the gate. Your first ship as an artisan: pick ONE exported helper that has thin or no test coverage and add a focused, DB-free unit test for it.\n\nIt is identical for every newcomer and **always valuable** — coverage is never \"done\", the codebase has hundreds of small pure helpers, and a good test both guards behaviour and teaches you how a corner of the system works. It is also **safe to auto-ship**: you add ONE file under `tests/`, which is not a protected surface, so a clean test merges on green with no owner approval.\n\n## How to pick a target (a PURE helper)\n\nPick a **pure** function — deterministic, with no database, network, filesystem, or live-server dependency — so the test runs standalone. Do not hunt by hand: run the finder, which reads the live tree every time (so this task never goes stale the way a written list does):\n\n```\nnode scripts/bongos/find-untested.js\n```\n\nIt lists modules that **no test file names**, best candidates first — ones no test reaches at all, then ones that look pure, then the smallest. Its purity column is a heuristic: open the module and confirm the helper you pick really needs no database, network or files. If the list is empty, run it with `--all` and pick a module that still exports a helper you can test DB-free.\n\n## How to write it (mirror an existing test — there is no framework)\n\nThese tests are plain Node scripts using `node:assert`; there is no test runner. Open a small existing one as your model — for example `tests/criterion_ref_parse.mjs` or `tests/task_classifier_vocab.mjs` — and copy the shape:\n1. `import` / `require` the helper from its module.\n2. Assert **several** cases, including at least one **edge / boundary** case (empty input, null, a tricky value).\n3. Print a one-line success message at the end (an assert that throws exits non-zero, which is how the gate sees a failure).\n\nName the file `tests/<helper-or-module>.mjs`.\n\n## Verify + ship\n\nRun BOTH and confirm both are green:\n- `node tests/<your-file>.mjs` — your test alone, exits 0.\n- `node scripts/bongos/run-unit-tests.js` — the whole gate, with your test auto-included.\n\nThen `/builder-ship`. The ship notes must name the helper and file you tested.\n\n## Stay safe (off-limits)\n\nAdd exactly ONE new file under `tests/`. Do NOT edit `scripts/bongos/run-unit-tests.js` (it auto-discovers your test, and it is a protected file you may not touch), and do NOT change the helper you are testing. Your test must be **DB-free**: anything needing Postgres, the network, or a live server belongs in the integration gate and will fail standalone here. Touch no permission, pipeline, migration, or infra file.",
       "done_when": [
         "A NEW tests/<name>.mjs file was added (it did not exist before) that unit-tests a PURE exported helper — no Postgres, network, filesystem, or live server.",
         "`node tests/<name>.mjs` exits 0 and the test makes real assertions about the helper's behaviour — at least two cases including one edge/boundary case — not a trivial always-true assertion.",
@@ -23,12 +23,12 @@
     {
       "template_id": "docs-hygiene-pass",
       "version_id": "BONGOS-V1",
-      "discipline": "engineer",
+      "discipline": "artisan",
       "kind": "cleanup",
       "est_minutes": 40,
       "credits_reward": 15,
       "title": "Docs-hygiene sweep: fix one piece of real drift (broken link, dead anchor, or bare #NNN ref) in a Markdown doc",
-      "description": "## What you're doing\n\nThe project's docs drift constantly — links break when files are renamed, heading anchors go dead, formatting breaks, and bare `#NNN` refs creep back (a bare `#123` autolinks to GitHub's issue space and 404s — see CLAUDE.md §8). Your job: find **one** genuine piece of drift in **one** SAFE doc and ship the fix.\n\n## First — do NOT open these (they will stall your ship)\n\nA newcomer (Xenos / Thetes, sub-Metic) may not modify the authority / pipeline core. Picking one of these as your target will **fail your grade or block your ship**, so don't even go looking for drift in them: `CLAUDE.md`, `docs/canonical-permissions.md`, the authority ADRs (`docs/adr/0016-*`, `docs/adr/0043-*`), and anything under `migrations/`, `infra/`, `.github/`, `.husky/`, `.claude/hooks/`, plus `package.json` and the ship / grade / deploy scripts. (The authoritative list is the glob set in `src/bongos/permission-path-check.js`.) The most *visible* drift often lives in `CLAUDE.md` itself — resist it; it is off-limits to you.\n\n## Pick from the SAFE docs only\n\nAll fair game: a recipe under `docs/recipes/`, a session log under `docs/session-logs/`, `docs/architecture.md`, `docs/file-map.md`, `docs/TRACKS.md`, a **non-authority** ADR, `README.md`, or `art/README.md`.\n\n## How to find a real target (don't ship a no-op)\n\n1. **Bare `#NNN` refs (easiest):** run `node scripts/bongos/linkify-refs.js` (read-only) — it lists docs with upgradeable refs. Pick one from the SAFE list above and fix it with `node scripts/bongos/linkify-refs.js --apply <safe-file.md>`.\n2. **Broken / renamed links:** open a safe doc and check its `](path)` links resolve to a real file (cross-check `docs/file-map.md`).\n3. **Dead anchors:** `](#heading)` where that heading no longer exists in the target doc.\n4. **Formatting drift:** a broken list nest, an unclosed code fence, a mangled table.\n\n## Verify + ship\n\nRun `node scripts/bongos/linkify-refs.js --check <your-file.md>` (scoped to YOUR one safe file — exit 0) and confirm any link you touched resolves, then `/builder-ship`. The ship notes must name the specific drift you fixed and the one file.\n\n_Prefer writing code to prose? Claim the \"add a unit test\" engineer chore instead — it's the other first-builder engineer task._",
+      "description": "## What you're doing\n\nThe project's docs drift constantly — links break when files are renamed, heading anchors go dead, formatting breaks, and bare `#NNN` refs creep back (a bare `#123` autolinks to GitHub's issue space and 404s — see CLAUDE.md §8). Your job: find **one** genuine piece of drift in **one** SAFE doc and ship the fix.\n\n## First — do NOT open these (they will stall your ship)\n\nA newcomer (Xenos / Thetes, sub-Metic) may not modify the authority / pipeline core. Picking one of these as your target will **fail your grade or block your ship**, so don't even go looking for drift in them: `CLAUDE.md`, `docs/canonical-permissions.md`, the authority ADRs (`docs/adr/0016-*`, `docs/adr/0043-*`), and anything under `migrations/`, `infra/`, `.github/`, `.husky/`, `.claude/hooks/`, plus `package.json` and the ship / grade / deploy scripts. (The authoritative list is the glob set in `src/bongos/permission-path-check.js`.) The most *visible* drift often lives in `CLAUDE.md` itself — resist it; it is off-limits to you.\n\n## Pick from the SAFE docs only\n\nAll fair game: a recipe under `docs/recipes/`, a session log under `docs/session-logs/`, `docs/architecture.md`, `docs/file-map.md`, `docs/TRACKS.md`, a **non-authority** ADR, `README.md`, or `art/README.md`.\n\n## How to find a real target (don't ship a no-op)\n\n1. **Bare `#NNN` refs (easiest):** run `node scripts/bongos/linkify-refs.js` (read-only) — it lists docs with upgradeable refs. Pick one from the SAFE list above and fix it with `node scripts/bongos/linkify-refs.js --apply <safe-file.md>`.\n2. **Broken / renamed links:** open a safe doc and check its `](path)` links resolve to a real file (cross-check `docs/file-map.md`).\n3. **Dead anchors:** `](#heading)` where that heading no longer exists in the target doc.\n4. **Formatting drift:** a broken list nest, an unclosed code fence, a mangled table.\n\n## Verify + ship\n\nRun `node scripts/bongos/linkify-refs.js --check <your-file.md>` (scoped to YOUR one safe file — exit 0) and confirm any link you touched resolves, then `/builder-ship`. The ship notes must name the specific drift you fixed and the one file.\n\n_Prefer writing code to prose? Claim the \"add a unit test\" artisan chore instead — it's the other first-builder artisan task._",
       "done_when": [
         "Exactly one non-protected Markdown file was changed (NOT CLAUDE.md, canonical-permissions.md, an authority ADR, or anything under migrations/ infra/ .github/ .husky/ .claude/hooks/ — see src/bongos/permission-path-check.js), and the change is a genuine hygiene fix (a broken/renamed link path, a dead heading anchor, a bare `#NNN` ref linkified, or formatting drift) — not a content/meaning edit and not a cosmetic no-op.",
         "`node scripts/bongos/linkify-refs.js --check <your-file.md>` (scoped to the one file you changed) exits 0.",
@@ -49,7 +49,7 @@
       "est_minutes": 55,
       "credits_reward": 15,
       "title": "Generate one new in-world art asset of your choice (a prop, plant, animal, or accessory) via the pixel-art pipeline",
-      "description": "## What you're doing\n\nThis instance's world always needs more to look at. Your first ship as an artist is to **generate ONE new in-world asset of your own choosing** and add it to the world. You pick the subject — that's the fun part. Good candidates, all in-world (Mediterranean coast just south of Athens, mythic 'discovered secret' tone):\n- **Props**: amphora, fishing net, basket, crate, urn, torch, market awning, oar, clay pot.\n- **Plants**: olive tree, cypress, reeds, grapevine, shrub, wild herbs.\n- **Animals**: goat, chicken, duck, donkey, fish, gull, lizard.\n- **Accessories**: a sandal, a sun hat, a length of rope, a string of beads.\n\nIt is identical for every newcomer and **always valuable**, because a growing world has effectively unbounded demand for new props, flora, fauna, and detail — every newcomer picks a different subject, so two runs never collide.\n\n## How to find your way in\n\n1. Read `art/README.md` and `docs/recipes/pixel-art-pipeline.md`, plus `modules/art-pipeline/template/style_guide.md`, `modules/art-pipeline/template/rubric.json`, and `modules/art-pipeline/template/palette.json` — that's the look you must hit: 16-bit pixel art, early-Pokémon (FireRed) touchstone, top-down, 32×32, locked 64-colour Mediterranean palette (olive greens, warm tans, turquoise sea, weathered marble — NOT spring green, NOT navy, NOT pine).\n2. **Pick ONE subject.** Keep it to a SINGLE 32×32 tile/sprite — not a whole spritesheet or family (that's a bigger task).\n3. **Check the budget first**: `python3 modules/art-pipeline/pipeline/cost_ledger.py status` (the pipeline hard-stops at $80; one asset is ~$0.05–0.45).\n4. **Generate via the pipeline — do not hand-draw or freelance.** Use the `/otb-tile-generate` skill: it appends your new entry to `modules/art-pipeline/template/vocabulary.json`, runs the generate → post-process-to-32×32 → score-against-rubric → retry orchestrator, saves the final PNG to `modules/art-pipeline/generated/tiles/<id>.png`, and logs cost. (This needs the art pipeline's `GOOGLE_AI_STUDIO_KEY`, which resolves from `~/.config/otb/env`; most builder setups have it. If yours doesn't, claim the engineer or ideator newcomer chore instead, or ask an Archon to enable it.)\n5. **Confirm it PASSED** the rubric (`modules/art-pipeline/iterations/run_summary.json` shows `status: \"pass\"`). If it only reached best-effort, regenerate with the fix_hint — never paper over a fail.\n6. **See it in-game**: `node scripts/bongos/art-stage.js` rebuilds the atlas and surfaces it on your sandbox preview (`sandbox-<login>.<instance-apex>`).\n7. Ship via `/builder-ship`; the ship notes name your asset and its rubric score.\n\n## Stay clear of (READ-ONLY)\n\nNever modify the locked palette (`modules/art-pipeline/template/palette.json`) or the rubric (`modules/art-pipeline/template/rubric.json`) — those are theme-defining and changing them needs an ADR (out of scope for a first ship). Touch only art assets/vocabulary under `art/` (and, only if your asset is a genuinely new base-tile TYPE, the `public/game/world/tilePalette.js` mapping). Do not touch any permission/pipeline-core/migration/infra file.",
+      "description": "## What you're doing\n\nThis instance's world always needs more to look at. Your first ship as an artist is to **generate ONE new in-world asset of your own choosing** and add it to the world. You pick the subject — that's the fun part. Good candidates, all in-world (Mediterranean coast just south of Athens, mythic 'discovered secret' tone):\n- **Props**: amphora, fishing net, basket, crate, urn, torch, market awning, oar, clay pot.\n- **Plants**: olive tree, cypress, reeds, grapevine, shrub, wild herbs.\n- **Animals**: goat, chicken, duck, donkey, fish, gull, lizard.\n- **Accessories**: a sandal, a sun hat, a length of rope, a string of beads.\n\nIt is identical for every newcomer and **always valuable**, because a growing world has effectively unbounded demand for new props, flora, fauna, and detail — every newcomer picks a different subject, so two runs never collide.\n\n## How to find your way in\n\n1. Read `art/README.md` and `docs/recipes/pixel-art-pipeline.md`, plus `modules/art-pipeline/template/style_guide.md`, `modules/art-pipeline/template/rubric.json`, and `modules/art-pipeline/template/palette.json` — that's the look you must hit: 16-bit pixel art, early-Pokémon (FireRed) touchstone, top-down, 32×32, locked 64-colour Mediterranean palette (olive greens, warm tans, turquoise sea, weathered marble — NOT spring green, NOT navy, NOT pine).\n2. **Pick ONE subject.** Keep it to a SINGLE 32×32 tile/sprite — not a whole spritesheet or family (that's a bigger task).\n3. **Check the budget first**: `python3 modules/art-pipeline/pipeline/cost_ledger.py status` (the pipeline hard-stops at $80; one asset is ~$0.05–0.45).\n4. **Generate via the pipeline — do not hand-draw or freelance.** Use the `/otb-tile-generate` skill: it appends your new entry to `modules/art-pipeline/template/vocabulary.json`, runs the generate → post-process-to-32×32 → score-against-rubric → retry orchestrator, saves the final PNG to `modules/art-pipeline/generated/tiles/<id>.png`, and logs cost. (This needs the art pipeline's `GOOGLE_AI_STUDIO_KEY`, which resolves from `~/.config/otb/env`; most builder setups have it. If yours doesn't, claim the artisan newcomer chore or the artist idea-seed chore instead, or ask an Archon to enable it.)\n5. **Confirm it PASSED** the rubric (`modules/art-pipeline/iterations/run_summary.json` shows `status: \"pass\"`). If it only reached best-effort, regenerate with the fix_hint — never paper over a fail.\n6. **See it in-game**: `node scripts/bongos/art-stage.js` rebuilds the atlas and surfaces it on your sandbox preview (`sandbox-<login>.<instance-apex>`).\n7. Ship via `/builder-ship`; the ship notes name your asset and its rubric score.\n\n## Stay clear of (READ-ONLY)\n\nNever modify the locked palette (`modules/art-pipeline/template/palette.json`) or the rubric (`modules/art-pipeline/template/rubric.json`) — those are theme-defining and changing them needs an ADR (out of scope for a first ship). Touch only art assets/vocabulary under `art/` (and, only if your asset is a genuinely new base-tile TYPE, the `public/game/world/tilePalette.js` mapping). Do not touch any permission/pipeline-core/migration/infra file.",
       "done_when": [
         "Exactly one NEW in-world asset (your chosen subject) was generated via the pixel-art pipeline (`/otb-tile-generate` / orchestrator.py); the final PNG exists at modules/art-pipeline/generated/tiles/<id>.png.",
         "It PASSED the rubric (modules/art-pipeline/iterations/run_summary.json status 'pass', or /otb-design-review numbers reported at/above the bar) and every pixel is on the locked palette (modules/art-pipeline/template/palette.json).",
@@ -59,18 +59,16 @@
       ],
       "touches": [],
       "floor": 3
-    }
-  ],
-  "ideator": [
+    },
     {
       "template_id": "idea-seed-pass",
       "version_id": "BONGOS-V1",
-      "discipline": "ideator",
+      "discipline": "artist",
       "kind": "feature",
       "est_minutes": 45,
       "credits_reward": 12,
       "title": "Idea-seed pass: file 5-8 fresh in-world ideas (names, lore, or builder-UX) into the idea inbox",
-      "description": "## What you'll do\n\nThe seed of almost everything built here is the **idea_inbox** — a queue anyone can drop ideas into, which trusted builders later triage into real tasks. Your first ship as an ideator is simple and concrete: **add a small batch of fresh ideas to that inbox.** You write no code, touch no game, change no system — you think, write a few short well-shaped ideas, and file them with one command each.\n\nIt is identical for every newcomer and **always valuable**: the inbox is never \"done\" — every triage pass consumes ideas (promote/discard/merge), so it is permanently hungry for fresh input, and a growing world always wants more names, more lore, more texture. Your batch is brand-new content, so it can never duplicate \"the work\" — the supply IS the work.\n\n## Pick ONE branch\n\n- **Branch A — PRODUCT flavour (default).** Ideas that grow the world players see: **names + one line of lore** for a character, structure, landmark, district, ship, or festival; or a world-background snippet (a custom, a superstition, a line a named NPC says). Tone: mythic, mysterious, a \"discovered secret\"; Mediterranean ancient-Greek coast (just south of Athens); NOT modern, NOT tongue-in-cheek-modern. Ground it in CLAUDE.md §3/§6/§7.\n- **Branch B — INTERNAL / builder-UX.** Small user-experience improvement ideas for the GDS / builders' hall (the surfaces builders use, not the game): a clearer label, a confusing onboarding message, a quality-of-life tweak to a status page or a slash-command's output. See `docs/TRACKS.md` for product vs internal.\n\n## How to find your way in\n\n1. (Branch A) Read CLAUDE.md §3/§6/§7 for tone. (Branch B) Skim `docs/TRACKS.md` and click around your instance's /builders hall for the rough edge you'll write up.\n2. See what's already filed so you don't repeat it: `node scripts/bongos/api.js GET /api/bongos/inbox`.\n3. File each idea with `node scripts/bongos/capture.js \"<title>\" --body-file <path>` (filing an idea is the open-to-all path — a Xenos/Thetes session is allowed to do it; you just can't triage them). Put one line of detail + a `track: product` or `track: internal` line in each body file.",
+      "description": "## What you'll do\n\nThe seed of almost everything built here is the **idea_inbox** — a queue anyone can drop ideas into, which trusted builders later triage into real tasks. Your first ship here is simple and concrete: **add a small batch of fresh ideas to that inbox.** You write no code, touch no game, change no system — you think, write a few short well-shaped ideas, and file them with one command each.\n\nIt is identical for every newcomer and **always valuable**: the inbox is never \"done\" — every triage pass consumes ideas (promote/discard/merge), so it is permanently hungry for fresh input, and a growing world always wants more names, more lore, more texture. Your batch is brand-new content, so it can never duplicate \"the work\" — the supply IS the work.\n\n## Pick ONE branch\n\n- **Branch A — PRODUCT flavour (default).** Ideas that grow the world players see: **names + one line of lore** for a character, structure, landmark, district, ship, or festival; or a world-background snippet (a custom, a superstition, a line a named NPC says). Tone: mythic, mysterious, a \"discovered secret\"; Mediterranean ancient-Greek coast (just south of Athens); NOT modern, NOT tongue-in-cheek-modern. Ground it in CLAUDE.md §3/§6/§7.\n- **Branch B — INTERNAL / builder-UX.** Small user-experience improvement ideas for the GDS / builders' hall (the surfaces builders use, not the game): a clearer label, a confusing onboarding message, a quality-of-life tweak to a status page or a slash-command's output. See `docs/TRACKS.md` for product vs internal.\n\n## How to find your way in\n\n1. (Branch A) Read CLAUDE.md §3/§6/§7 for tone. (Branch B) Skim `docs/TRACKS.md` and click around your instance's /builders hall for the rough edge you'll write up.\n2. See what's already filed so you don't repeat it: `node scripts/bongos/api.js GET /api/bongos/inbox`.\n3. File each idea with `node scripts/bongos/capture.js \"<title>\" --body-file <path>` (filing an idea is the open-to-all path — a Xenos/Thetes session is allowed to do it; you just can't triage them). Put one line of detail + a `track: product` or `track: internal` line in each body file.",
       "done_when": [
         "You filed 5–8 fresh ideas into the idea_inbox via `node scripts/bongos/capture.js` (each prints a `Captured idea #N` confirmation), all in ONE branch (A product, or B internal/UX).",
         "Each idea has a clear title and a body with at least one sentence of detail — for Branch A, one line of in-world lore (who/what it is); for Branch B, what the rough edge is and what 'better' looks like.",

package/scripts/bongos/newcomer-floor.test.js

@@ -24,13 +24,13 @@ function test(name, fn) {
 }
 
 // per-discipline DEFAULT floors (the fallback when a template omits its own).
-const FLOOR_DEFAULTS = { engineer: 2, artist: 3, ideator: 2 };
+const FLOOR_DEFAULTS = { artisan: 2, artist: 3 };
 
 // templates-by-discipline fixture (each discipline -> LIST of chores).
 const TEMPLATES = {
-  engineer: [
-    { template_id: 'unit-test-pass', version_id: 'GDS-V4', discipline: 'engineer', floor: 2, title: 'Add a unit test', done_when: ['a', 'b'], est_minutes: 45 },
-    { template_id: 'docs-hygiene-pass', version_id: 'GDS-V4', discipline: 'engineer', floor: 1, title: 'Docs sweep', done_when: ['a', 'b'], est_minutes: 40 },
+  artisan: [
+    { template_id: 'unit-test-pass', version_id: 'GDS-V4', discipline: 'artisan', floor: 2, title: 'Add a unit test', done_when: ['a', 'b'], est_minutes: 45 },
+    { template_id: 'docs-hygiene-pass', version_id: 'GDS-V4', discipline: 'artisan', floor: 1, title: 'Docs sweep', done_when: ['a', 'b'], est_minutes: 40 },
   ],
   artist: [
     { template_id: 'asset-generate-pass', version_id: 'V2', discipline: 'artist', title: 'Asset', done_when: ['a', 'b'], est_minutes: 55 }, // no own floor -> default
@@ -40,7 +40,7 @@ const TEMPLATES = {
 // ---- templateFloor ----
 
 test('templateFloor: own floor wins over the discipline default', () => {
-  assert.strictEqual(nf.templateFloor({ floor: 5 }, 'engineer', FLOOR_DEFAULTS), 5);
+  assert.strictEqual(nf.templateFloor({ floor: 5 }, 'artisan', FLOOR_DEFAULTS), 5);
 });
 
 test('templateFloor: falls back to the discipline default when omitted', () => {
@@ -48,7 +48,7 @@ test('templateFloor: falls back to the discipline default when omitted', () => {
 });
 
 test('templateFloor: 0 is a valid explicit floor (not treated as missing)', () => {
-  assert.strictEqual(nf.templateFloor({ floor: 0 }, 'engineer', FLOOR_DEFAULTS), 0);
+  assert.strictEqual(nf.templateFloor({ floor: 0 }, 'artisan', FLOOR_DEFAULTS), 0);
 });
 
 test('templateFloor: unknown discipline with no default -> 0', () => {
@@ -69,7 +69,7 @@ test('computeTemplateDeficits: empty supply -> each chore needs its full floor',
 });
 
 test('computeTemplateDeficits: ready + backlog both count as supply (idempotency)', () => {
-  const supply = { 'engineer:unit-test-pass': { ready: 1, backlog: 1 } }; // fills floor 2
+  const supply = { 'artisan:unit-test-pass': { ready: 1, backlog: 1 } }; // fills floor 2
   const rows = nf.computeTemplateDeficits(supply, TEMPLATES, FLOOR_DEFAULTS);
   assert.strictEqual(deficitFor(rows, 'unit-test-pass').needed, 0);
   assert.strictEqual(deficitFor(rows, 'docs-hygiene-pass').needed, 1, 'sibling chore is independent');
@@ -77,7 +77,7 @@ test('computeTemplateDeficits: ready + backlog both count as supply (idempotency
 
 test('computeTemplateDeficits: supply is per-template, not shared across a discipline', () => {
   // over-supplying one engineer chore must NOT satisfy the other.
-  const supply = { 'engineer:unit-test-pass': { ready: 9, backlog: 0 } };
+  const supply = { 'artisan:unit-test-pass': { ready: 9, backlog: 0 } };
   const rows = nf.computeTemplateDeficits(supply, TEMPLATES, FLOOR_DEFAULTS);
   assert.strictEqual(deficitFor(rows, 'unit-test-pass').needed, 0);
   assert.strictEqual(deficitFor(rows, 'docs-hygiene-pass').needed, 1);
@@ -102,48 +102,48 @@ test('computeTemplateDeficits: ignores non-floor disciplines', () => {
 // ---- instanceSourceRef + parseSeq + parseRef ----
 
 test('instanceSourceRef: tmpl:<disc>:<template_id>:<seq>', () => {
-  assert.strictEqual(nf.instanceSourceRef('engineer', 'unit-test-pass', 7), 'tmpl:engineer:unit-test-pass:7');
+  assert.strictEqual(nf.instanceSourceRef('artisan', 'unit-test-pass', 7), 'tmpl:artisan:unit-test-pass:7');
 });
 
 test('parseSeq: returns seq only for the matching discipline+template', () => {
-  assert.strictEqual(nf.parseSeq('tmpl:engineer:unit-test-pass:4', 'engineer', 'unit-test-pass'), 4);
-  assert.strictEqual(nf.parseSeq('tmpl:engineer:unit-test-pass:4', 'artist', 'unit-test-pass'), null, 'wrong discipline');
-  assert.strictEqual(nf.parseSeq('tmpl:engineer:other:4', 'engineer', 'unit-test-pass'), null, 'wrong template');
-  assert.strictEqual(nf.parseSeq('manual:engineer:some-title', 'engineer', 'unit-test-pass'), null, 'foreign ref');
-  assert.strictEqual(nf.parseSeq('tmpl:engineer:unit-test-pass:abc', 'engineer', 'unit-test-pass'), null, 'malformed seq');
+  assert.strictEqual(nf.parseSeq('tmpl:artisan:unit-test-pass:4', 'artisan', 'unit-test-pass'), 4);
+  assert.strictEqual(nf.parseSeq('tmpl:artisan:unit-test-pass:4', 'artist', 'unit-test-pass'), null, 'wrong discipline');
+  assert.strictEqual(nf.parseSeq('tmpl:artisan:other:4', 'artisan', 'unit-test-pass'), null, 'wrong template');
+  assert.strictEqual(nf.parseSeq('manual:artisan:some-title', 'artisan', 'unit-test-pass'), null, 'foreign ref');
+  assert.strictEqual(nf.parseSeq('tmpl:artisan:unit-test-pass:abc', 'artisan', 'unit-test-pass'), null, 'malformed seq');
 });
 
 test('parseRef: decomposes a chore ref into discipline/template/seq', () => {
-  assert.deepStrictEqual(nf.parseRef('tmpl:engineer:unit-test-pass:7'), { discipline: 'engineer', templateId: 'unit-test-pass', seq: 7 });
-  assert.strictEqual(nf.parseRef('manual:engineer:x'), null, 'not a chore ref');
-  assert.strictEqual(nf.parseRef('tmpl:engineer:unit-test-pass:0'), null, 'seq must be positive');
-  assert.strictEqual(nf.parseRef('tmpl:engineer:unit-test-pass'), null, 'too few parts');
+  assert.deepStrictEqual(nf.parseRef('tmpl:artisan:unit-test-pass:7'), { discipline: 'artisan', templateId: 'unit-test-pass', seq: 7 });
+  assert.strictEqual(nf.parseRef('manual:artisan:x'), null, 'not a chore ref');
+  assert.strictEqual(nf.parseRef('tmpl:artisan:unit-test-pass:0'), null, 'seq must be positive');
+  assert.strictEqual(nf.parseRef('tmpl:artisan:unit-test-pass'), null, 'too few parts');
   assert.strictEqual(nf.parseRef('tmpl:a:b:c:d'), null, 'too many parts');
 });
 
 // ---- nextSeq (monotonic across all refs) ----
 
 test('nextSeq: empty set -> 1', () => {
-  assert.strictEqual(nf.nextSeq(new Set(), 'engineer', 'unit-test-pass'), 1);
+  assert.strictEqual(nf.nextSeq(new Set(), 'artisan', 'unit-test-pass'), 1);
 });
 
 test('nextSeq: 1 + max matching seq, ignoring other templates/disciplines', () => {
   const refs = new Set([
-    'tmpl:engineer:unit-test-pass:1',
-    'tmpl:engineer:unit-test-pass:3', // gap is fine; max is 3
-    'tmpl:engineer:unit-test-pass:2',
-    'tmpl:engineer:docs-hygiene-pass:9', // sibling chore — ignored
+    'tmpl:artisan:unit-test-pass:1',
+    'tmpl:artisan:unit-test-pass:3', // gap is fine; max is 3
+    'tmpl:artisan:unit-test-pass:2',
+    'tmpl:artisan:docs-hygiene-pass:9', // sibling chore — ignored
     'tmpl:artist:asset-generate-pass:5', // different discipline — ignored
-    'manual:engineer:something',         // foreign — ignored
+    'manual:artisan:something',         // foreign — ignored
   ]);
-  assert.strictEqual(nf.nextSeq(refs, 'engineer', 'unit-test-pass'), 4);
-  assert.strictEqual(nf.nextSeq(refs, 'engineer', 'docs-hygiene-pass'), 10, 'sibling seq is independent');
-  assert.strictEqual(nf.nextSeq(refs, 'ideator', 'idea-seed-pass'), 1);
+  assert.strictEqual(nf.nextSeq(refs, 'artisan', 'unit-test-pass'), 4);
+  assert.strictEqual(nf.nextSeq(refs, 'artisan', 'docs-hygiene-pass'), 10, 'sibling seq is independent');
+  assert.strictEqual(nf.nextSeq(refs, 'artist', 'idea-seed-pass'), 1);
 });
 
 test('nextSeq: never recycles a shipped/abandoned seq (max over ALL statuses)', () => {
-  const refs = new Set(['tmpl:ideator:idea-seed-pass:1', 'tmpl:ideator:idea-seed-pass:2']);
-  assert.strictEqual(nf.nextSeq(refs, 'ideator', 'idea-seed-pass'), 3);
+  const refs = new Set(['tmpl:artist:idea-seed-pass:1', 'tmpl:artist:idea-seed-pass:2']);
+  assert.strictEqual(nf.nextSeq(refs, 'artist', 'idea-seed-pass'), 3);
 });
 
 // ---- buildProposalFromTemplate ----
@@ -151,7 +151,7 @@ test('nextSeq: never recycles a shipped/abandoned seq (max over ALL statuses)',
 const SAMPLE_TEMPLATE = {
   template_id: 'docs-hygiene-pass',
   version_id: 'GDS-V4',
-  discipline: 'engineer',
+  discipline: 'artisan',
   kind: 'cleanup',
   est_minutes: 40,
   credits_reward: 15,
@@ -163,14 +163,14 @@ const SAMPLE_TEMPLATE = {
 };
 
 test('buildProposalFromTemplate: carries fields, normalizes touches, sets seq ref', () => {
-  const p = nf.buildProposalFromTemplate(SAMPLE_TEMPLATE, 5, { discipline: 'engineer' });
+  const p = nf.buildProposalFromTemplate(SAMPLE_TEMPLATE, 5, { discipline: 'artisan' });
   assert.strictEqual(p.title, 'Docs-hygiene sweep', 'trimmed');
   assert.strictEqual(p.version_id, 'GDS-V4');
   assert.strictEqual(p.kind, 'cleanup');
   assert.strictEqual(p.credits_reward, 15);
   assert.strictEqual(p.est_minutes, 40);
   assert.deepStrictEqual(p.touches, ['docs/', '42'], 'empties dropped, coerced to strings');
-  assert.strictEqual(p.source_ref, 'tmpl:engineer:docs-hygiene-pass:5');
+  assert.strictEqual(p.source_ref, 'tmpl:artisan:docs-hygiene-pass:5');
   assert.deepStrictEqual(p.done_when, ['a', 'b']);
 });
 
@@ -191,20 +191,22 @@ test('buildProposalFromTemplate: null on a titleless template', () => {
 test('buildDescription: folds done-when + evergreen footer', () => {
   const desc = nf.buildDescription(
     { title: 't', description: 'Body text.', done_when: ['x', 'y'], est_minutes: 30 },
-    'engineer'
+    'artisan'
   );
   assert.ok(desc.includes('Body text.'));
   assert.ok(desc.includes('**Done when:**'));
   assert.ok(desc.includes('- x') && desc.includes('- y'));
   assert.ok(desc.includes('Evergreen newcomer chore'), 'footer present');
-  assert.ok(desc.includes('engineer'), 'discipline in footer');
+  assert.ok(desc.includes('artisan'), 'discipline in footer');
 });
 
 // ---- loadTemplates: the REAL templates.json is well-formed (multi-chore shape) ----
 
 test('loadTemplates: real templates.json is a valid per-discipline list', () => {
   const templates = nf.loadTemplates(path.join(__dirname, 'newcomer-floor.templates.json'));
-  for (const disc of ['engineer', 'artist', 'ideator']) {
+  // task 1005141: two crafts, not three — ideator folded into artist, engineer is artisan.
+  assert.ok(!('engineer' in templates) && !('ideator' in templates), 'no old-spelling keys remain');
+  for (const disc of ['artisan', 'artist']) {
     const list = templates[disc];
     assert.ok(Array.isArray(list) && list.length >= 1, `${disc} is a non-empty list`);
     for (const t of list) {
@@ -219,15 +221,22 @@ test('loadTemplates: real templates.json is a valid per-discipline list', () =>
   }
 });
 
-test('loadTemplates: engineer now offers BOTH the unit-test chore and the docs sweep', () => {
+test('loadTemplates: artist holds BOTH the asset chore and the (former ideator) idea-seed chore', () => {
   const templates = nf.loadTemplates(path.join(__dirname, 'newcomer-floor.templates.json'));
-  const ids = templates.engineer.map((t) => t.template_id);
+  const ids = templates.artist.map((t) => t.template_id);
+  assert.ok(ids.includes('asset-generate-pass'), 'the asset chore is present');
+  assert.ok(ids.includes('idea-seed-pass'), 'the idea chore moved under artist');
+});
+
+test('loadTemplates: artisan offers BOTH the unit-test chore and the docs sweep', () => {
+  const templates = nf.loadTemplates(path.join(__dirname, 'newcomer-floor.templates.json'));
+  const ids = templates.artisan.map((t) => t.template_id);
   assert.ok(ids.includes('unit-test-pass'), 'the safe coding chore is present');
   assert.ok(ids.includes('docs-hygiene-pass'), 'the docs sweep is retained');
   // every engineer chore touches only safe (non-protected) surfaces by design:
   // touches[] is empty (git-merge is the collision detector), so this asserts the
   // contract that engineer chores carry no protected-path touches.
-  for (const t of templates.engineer) {
+  for (const t of templates.artisan) {
     assert.deepStrictEqual(t.touches || [], [], `${t.template_id} declares no touches[]`);
   }
 });

package/scripts/bongos/role-pack-guard.js

@@ -123,10 +123,11 @@ function checkRolePacks(fsImpl = fs) {
   }
 
   // The split's own shape, asserted so a later edit cannot quietly drop a craft
-  // back into the kernel: three core packs, and Governor deliberately absent
-  // (criterion wa6-kernel-and-packs — "three packs, not four, until the owner decides").
-  if (packCount < 3) {
-    violations.push(`only ${packCount} craft(s) name a pack — the split is one kernel plus three packs (Engineer, Artist, Ideator). A craft with no pack has nowhere to keep what the role-neutral kernel does not.`);
+  // back into the kernel: two core packs since the game conversion folded the
+  // ideator into the artist (task 1005141, BONGOS-V3) — Artisan and Artist; Patron
+  // is a character, not a task craft, and has no pack.
+  if (packCount < 2) {
+    violations.push(`only ${packCount} craft(s) name a pack — the split is one kernel plus two packs (Artisan, Artist). A craft with no pack has nowhere to keep what the role-neutral kernel does not.`);
   }
 
   return {

package/scripts/bongos/seed-tasks.example.json

@@ -10,7 +10,7 @@
       "title": "Spike: where the welcome checklist is stored",
       "description": "Output an ADR naming the table and who writes it.",
       "kind": "spike",
-      "discipline": "engineer",
+      "discipline": "artisan",
       "priority": 4,
       "est_minutes": 90,
       "criterion_ids": ["newcomer-knows-what-to-do-next"]
@@ -20,7 +20,7 @@
       "title": "The welcome checklist API",
       "description": "Build to R01's ADR. Done-when: a new builder's checklist is returned by one GET.",
       "kind": "feature",
-      "discipline": "engineer",
+      "discipline": "artisan",
       "priority": 4,
       "est_minutes": 180,
       "criterion_ids": ["newcomer-knows-what-to-do-next"],
@@ -42,7 +42,7 @@
       "title": "Proof: a newcomer finds their next step without asking",
       "description": "A brand-new builder signs in and finds what to do next unaided.",
       "kind": "verify",
-      "discipline": "engineer",
+      "discipline": "artisan",
       "priority": 3,
       "est_minutes": 60,
       "criterion_ids": ["newcomer-knows-what-to-do-next"],