@bongos/core 1.24.79 → 1.24.81

package/modules/hall-ui/records/profile-roles.md

@@ -4,9 +4,9 @@
 
 ## What the page says now
 
-- **The main craft's headline** — "N works shipped" (engineer), "N pages approved" (artist), "N thoughts filed" (ideator) — leads the tally. It was also the subtitle under the h1 until task 1004827 removed the page's sub-line (no top block).
+- **The main craft's headline** — "N works shipped" (artisan), "N pages approved" (artist; an artist with ideas and no approved page leads with "N thoughts filed", since task 1005141 folded the ideator into the artist) — leads the tally. It was also the subtitle under the h1 until task 1004827 removed the page's sub-line (no top block).
 - **The identity band** keeps the avatar, name, rank badge, handle, member-since and the "Answerable for" block unchanged. The "Preferred work:" line became **craft chips**, main role first ("Artist, main role"), then every other craft the server lists in `roles.shown`, which is a craft that has *earned* credits (the owner's 2026-09-30 rule; the server decides it, never this page).
-- **The tally** replaces the credits/karma column: the studio's corner tally carried onto the profile, the total first and then the two numbers the main craft leads with (engineer: works shipped, karma; artist: pages approved, this week; ideator: thoughts filed, ignited).
+- **The tally** replaces the credits/karma column: the studio's corner tally carried onto the profile, the total first and then the two numbers the main craft leads with (artisan: works shipped, karma; artist: pages approved, thoughts filed — or thoughts filed, ignited when they have ideas and no approved page).
 - **By the numbers** is the main craft's set of tiles, then one headline tile per other shown craft. The artist adds the studio's "N of M tweaked" per surface underneath, on `OTBKit.barSeriesHtml` with this sheet only moving the three cells into the mock's layout (name and count on a line, the bar under them).
 
 ## Where the words live
@@ -16,28 +16,28 @@
 ## Rules an edit must keep
 
 - **A number the instance could not read is a dash, never a zero.** The role ports are optional; "0 pages approved" would be a claim about the person.
-- **The ~ on an ideator's total size** is the sky's historical-estimate mark; its tile's tooltip says how much is estimated.
+- **The ~ on an artist's total size** is the sky's historical-estimate mark; its tile's tooltip says how much is estimated.
 - **The per-surface rows follow the MAIN craft only.**
 - Every page that boots `profile.js` in a vm must load `profile-roles.js` first (`tests/helpers.mjs` `bootProfilePage` and `tests/profile_ui_cross_project.mjs` do).
 
 ## Harness
 
-Three fixtures, one per craft: `builders__profile` (the engineer, id 95, the viewer's own), `<redacted>` (an artist who never shipped), `builders__2002__profile` (an ideator who never shipped, part of whose size is estimated). `profile.states.json` renders them as `own`, `artist` and `ideator`.
+Three fixtures: `builders__profile` (the artisan, id 95, the viewer's own), `<redacted>` (an artist who never shipped), `builders__2002__profile` (an artist whose work is ideas, who never shipped, part of whose size is estimated; the ideator fixture until task 1005141). `profile.states.json` renders them as `own`, `artist` and `artist-ideas`.
 
 ## Deliberate differences from the mock
 
-- The engineer's tally shows **karma** where the mock shows "+120 this week", and the fourth engineer tile is **achievements** where the mock shows a shipping streak: neither weekly engineer credits nor a weekly streak is in the profile read, and a number the page cannot read is not drawn.
-- The engineer tile "works shipped" has no "across N goals" foot, the ideator's "thoughts filed" no "since <month>" foot, the artist's "credits from pages" no "N a page" foot, and the surface rows no "where" sub-label: none of those is in the read.
-- **Karma ends every artist's and ideator's set of tiles**, which the mock does not draw. The owner's call, reviewing this build on 2026-10-01: "karma for artists and ideators is definitely key". The engineer's set carries it already.
+- The artisan's tally shows **karma** where the mock shows "+120 this week", and the fourth artisan tile is **achievements** where the mock shows a shipping streak: neither weekly artisan credits nor a weekly streak is in the profile read, and a number the page cannot read is not drawn.
+- The artisan tile "works shipped" has no "across N goals" foot, the artist's "thoughts filed" no "since <month>" foot, the artist's "credits from pages" no "N a page" foot, and the surface rows no "where" sub-label: none of those is in the read.
+- **Karma ends the artist's set of tiles** (every main craft but the artisan's), which the mock does not draw. The owner's call, reviewing this build on 2026-10-01: "karma for artists and ideators is definitely key" (the ideator is part of the artist craft since task 1005141). The artisan's set carries it already.
 - The tiles' grid fits at 148px rather than 170px, so five tiles sit on one row inside the hall's narrower panel.
 
 ## The Activity tabs, one per role (task 1004435, WA6.RP05)
 
 The section used to offer All / Engineer / Artist / Ideator / UI tabs over one task ledger, so an ideator's tab listed tasks whose discipline happened to be "ideator" and an artist's listed only artist-labelled tasks they had shipped. Now there is **one tab per role the person has** (`roles.shown`, the header's chips, main first), each counted the way the header leads, each its craft's own record, each with its own panel:
 
-- **Engineer**: the works completed and goals created ledgers, WHOLE (no craft filter: most of the corpus is unclassified and a filter reads as "you did less").
-- **Ideator**: the room's public trail, `public/profile-crafts.js`. One read of up to the route's cap of thoughts (`GET /inbox/by-builder/:id`, which already carried each thought's `state` and `size`), drawn as the sky's five marks by the day each was filed (size = diameter, brightness = a star's opacity, a folded-in thought tethered to the one it joined), the legend in the sky's words from `OTBIdeaObjects`, and every drawn thought a row in the ledger under it: state, size (~ for a historical estimate), still alive, and the old trail's "what became of it" cell folded in whole. A mark and its row light together on hover or focus; clicking a mark focuses its row.
-- **Artist**: the pages they rewrote in Tweak Mode that were approved, four at a time with "Show N more", from `GET /copy-desk/artists/:id/pages` (signed in; copy-desk's `composeArtistPages`). Each row: page, surface, approval day, changed-line count, and a before/after: the round's first changed line beside the approval renders (`/tasks/:id/visuals`, `before-` and `after-desktop-light`) as small thumbnails.
+- **Artisan**: the works completed and goals created ledgers, WHOLE (no craft filter: most of the corpus is unclassified and a filter reads as "you did less").
+- **Artist, the ideas half** (its own Ideator tab until task 1005141; now drawn under the approved pages on the one Artist tab): the room's public trail, `public/profile-crafts.js`. One read of up to the route's cap of thoughts (`GET /inbox/by-builder/:id`, which already carried each thought's `state` and `size`), drawn as the sky's five marks by the day each was filed (size = diameter, brightness = a star's opacity, a folded-in thought tethered to the one it joined), the legend in the sky's words from `OTBIdeaObjects`, and every drawn thought a row in the ledger under it: state, size (~ for a historical estimate), still alive, and the old trail's "what became of it" cell folded in whole. A mark and its row light together on hover or focus; clicking a mark focuses its row.
+- **Artist, the pages half**: the pages they rewrote in Tweak Mode that were approved, four at a time with "Show N more", from `GET /copy-desk/artists/:id/pages` (signed in; copy-desk's `composeArtistPages`). Each row: page, surface, approval day, changed-line count, and a before/after: the round's first changed line beside the approval renders (`/tasks/:id/visuals`, `before-` and `after-desktop-light`) as small thumbnails.
 
 Signed out, the section is one sign-in line (owner decision (a)).
 
@@ -59,7 +59,7 @@ The Overview's charts used to stop at "No works shipped yet" before they read a
 - **The works charts still need a shipped task**, and without one they are a single line under the figure ("No works shipped yet ..."), not two empty cards. Someone with neither credits nor works gets one line for the whole section.
 - **On a phone** the figure stacks: the line, then "where it came from". The plot's viewBox is half again a card's on a wide screen so its type matches the cards', and the kit's own on a phone (read at draw time, at the same 720px the grid stacks).
 
-Harness: `builders__earnings.json` serves any id; the artist (2001) and the ideator (2002) carry their own earnings beside an empty `builders__<id>__activity.json`, and the `artist`/`ideator` states expect `#chart-drachmae` and `.pearn__kinds`.
+Harness: `builders__earnings.json` serves any id; the artist (2001) and the ideas artist (2002) carry their own earnings beside an empty `builders__<id>__activity.json`, and the `artist`/`artist-ideas` states expect `#chart-drachmae` and `.pearn__kinds`.
 
 ### Deliberate differences from the mock (RP06)
 

package/modules/hall-ui/records/sky.md

@@ -1,6 +1,6 @@
 # The sky — /thinking and /goal-map (tasks 1004231, 1004232, 1004233)
 
-**THE SKY landed at `/thinking` (task 1004231 / sky part 3 of 5, goal 1000095; [ADR 0331](../../../docs/adr/0331-the-sky-is-the-ideators-home.md), ADR 0227 §11)** — the ideator's home. It replaced BOTH the room (task 1004098, `/thinking`) and the first ambient sky (task 1004105, `/sky` — the URL 301s here now) with the prototype the owner adopted as the design of record: `docs/design/mocks/sky/sky.template.html` is the **pixel contract** — copy, layout, colours, the thirteen tour steps, the toggles, the keys (`L` list, `?` tour, `0` fit, `/` compose) — built for real over `GET /sky` and `GET /sky/mine` (part 2). The room survives inside it as the list drawer: every drawn thought is a row with its whole sentence, one key away. Eight things it settled:
+**THE SKY landed at `/thinking` (task 1004231 / sky part 3 of 5, goal 1000095; [ADR 0331](../../../docs/adr/0331-the-sky-is-the-ideators-home.md), ADR 0227 §11)** — the ideator's home (the artist craft's since task 1005141 folded the ideator into it). It replaced BOTH the room (task 1004098, `/thinking`) and the first ambient sky (task 1004105, `/sky` — the URL 301s here now) with the prototype the owner adopted as the design of record: `docs/design/mocks/sky/sky.template.html` is the **pixel contract** — copy, layout, colours, the thirteen tour steps, the toggles, the keys (`L` list, `?` tour, `0` fit, `/` compose) — built for real over `GET /sky` and `GET /sky/mine` (part 2). The room survives inside it as the list drawer: every drawn thought is a row with its whole sentence, one key away. Eight things it settled:
 
 - **The page has no hall chrome, on purpose.** `thinking.html` is the template's markup (no shell.js, no sidebar); `thinking.css` is its `<style>`, one file; the world's tokens are not loaded — the template's values ARE the contract. The hall's doors (the record, the goal, the task) open from the panel, resolved against `hallBase()` (apex `/builders` or the subdomain). The title stamps `{{worldName}}` like every hall page.
 - **One script became seven files under the 1,500-line ratchet, on ONE shared object.** `window.OTBSky`: `SKY.S` is every `let` the prototype's closure held; everything else is a function or a constant. Load order is pinned in the HTML — `sky-data.js` (helpers, the vocabulary, the two adaptors, the bands, the world, the thoughts, the five reads) → `sky-layout.js` (clock, routes, explore, camera) → `sky-draw.js` (the drawing, the hit test) → `sky-interaction.js` (card, menu, pointer, keys, lenses, stats, jump, legend) → `sky-panel.js` (the panel, the drawer) → `sky-composer.js` (gravity, quick + full filing, the nod) → `sky-tour.js` (the thirteen steps, the frame loop, the boot). A file only CALLS a later file through `SKY.name(...)`, never at load time. The README says a split is not a deviation; a changed behaviour inside one is — and every deviation a gate or a route forced is listed in the task's ship notes, one line each.
@@ -37,8 +37,8 @@ Pinned by `tests/hall_sky.mjs` (31 cases: the reads, the five objects, the two c
 
 **Owner decision 2026-09-27: "Your thinking is only your thinking."** Part 4's "one page, two doors" above is SUPERSEDED: the two pages share the renderer and nothing else. The owner confirmed that "the your projects tab" means the whole-project lens, its switch and the project-map features. What this settled:
 - **The lens and the features separate; the drawing does not.** `thinking.css`, the seven `sky-*.js` files and every draw path stay shared. What each page may be in is `S.lenses` (set once in `sky-data.js` from `data-sky-lens`): `['simple', 'mine']` on `/thinking`, `['all']` on `/goal-map`. `setLens` clamps to it, so nothing — a button, the tour, a jump, the panel's "descend" — can take a page into a lens it lacks, and no button leaves for the other page (`location.assign` is gone from `sky-interaction.js`).
-- **Absent, not hidden.** `/thinking` carries no "the whole project" button, no "my ideas", no "explore" and no "where do you begin" dialog; `/goal-map` carries no switcher at all and none of the ideator's pills (recent, claude layer, my influence). The scripts touch a one-page control through `SKY.hide` / `SKY.press` / `SKY.on`, which do nothing when the element is not there. `thinking.css` gained one rule, `.brand + .tools { margin-left: auto; }`, so `/goal-map`'s tools keep the switcher's push to the right and its top strip reads as before.
-- **Two tours from one list.** Every step in `ALL_STEPS` says which sky it belongs to; `/thinking` walks nine of the template's thirteen (the ideator's steps, the wells and rings, the clock, the composer, simple), `/goal-map` walks eight — the wells, rings, life, routes, settled systems, the clock and explore — opened by one new step, "This is the whole project.", because the template's first step is "This is your sky." and belongs to `/thinking`. The project tour turns explore off for its length and gives it back. Each tour has its own seen key (S.tourKey: sky-tour-seen here, sky-map-tour-seen on the map), so one does not silence the other.
+- **Absent, not hidden.** `/thinking` carries no "the whole project" button, no "my ideas", no "explore" and no "where do you begin" dialog; `/goal-map` carries no switcher at all and none of `/thinking`'s pills (recent, claude layer, my influence). The scripts touch a one-page control through `SKY.hide` / `SKY.press` / `SKY.on`, which do nothing when the element is not there. `thinking.css` gained one rule, `.brand + .tools { margin-left: auto; }`, so `/goal-map`'s tools keep the switcher's push to the right and its top strip reads as before.
+- **Two tours from one list.** Every step in `ALL_STEPS` says which sky it belongs to; `/thinking` walks nine of the template's thirteen (the thinking sky's steps, the wells and rings, the clock, the composer, simple), `/goal-map` walks eight — the wells, rings, life, routes, settled systems, the clock and explore — opened by one new step, "This is the whole project.", because the template's first step is "This is your sky." and belongs to `/thinking`. The project tour turns explore off for its length and gives it back. Each tour has its own seen key (S.tourKey: sky-tour-seen here, sky-map-tour-seen on the map), so one does not silence the other.
 - **"Descend into the well" stays in its sky.** On `/goal-map` it only flies; on `/thinking` it steps "simple" up to "your thinking" (the one lens there that zooms). The legend drops "unexplored" on `/thinking`, which has no explore.
 - **Kept on both:** the list drawer (the room on `/thinking`, the ledger on `/goal-map`), the clock, the composer, "what if", the panel. Filing a thought from the project map still works; the owner's decision names the lens and the overlay, not the composer.
 

package/modules/hall-ui/records/start-screen.md

@@ -0,0 +1,25 @@
+# The start screen and the load screen — a sign-in opens the game (task 1005143, BONGOS-V3 R03)
+
+Covers: Home (`shell-game.js` `start()`, `shell-game.css`, the hand-off in `welcome-boot.js`). Spec: `docs/specs/bongos-v3-game-conversion.md` C1 `game-opens-not-navigates`. Game mode itself is in `game-mode.md`.
+
+## What it settled
+
+- **A fresh sign-in opens on the start screen, on Home.** Home is where a sign-in lands (`postLoginLanding`), and `welcome-boot.js` already knows a fresh sign-in from a return visit (the flag the sign-in click leaves). On one, `OTBWelcome.onAccess` calls `OTBShellGame.start({ name, art, done })` in place of its own greeting. The day's first visit without a sign-in keeps the welcome; a signed-out visitor keeps the welcome. A sign-in that returns to a deep link or another page goes straight there, as the welcome always did. `shell.js` is untouched.
+- **Five choices, one column: Start, Options, Achievements, Extras, Quit.** Start is the one filled pill. Options is a link to `/settings`, which IS the one options menu since task 1005144 (`records/options-menu.md`); Achievements is `/profile`. Extras opens three links under the menu (the thinking sky, the atlas, the docs). Quit calls `window.close()`; a browser only closes a tab a script opened, so when the tab is still there 300ms later the screen says "Close it to quit" instead of doing nothing.
+- **Start turns game mode on** (`set(true)`), then shows the load screen. Nothing else in the hall's interface sets it.
+- **The load screen is the still, a tip, and the city building up.** The still is the welcome's painting for the time of day, handed in by `welcome-boot.js` (this file names no picture). In a card of the hall's own tokens, the project city is drawn by `home-city-draw.js` `citySvg` from the one bounded read Home already uses (`GET /home/city?weeks=10`), at 31 stops from the oldest week to now, about three seconds, with "The city, N weeks ago" under it. Each stop is a whole drawing set as state; nothing animates in JavaScript. With reduced motion it is the finished city at once. With no city to draw (the read failed, the scripts are missing) the still and the tip stand for 1.4s. Either way the world opens.
+- **Tips rotate** (`localStorage 'hall-game-tip'` counts them), so each load shows the next one. A tip must be true of the hall today; the first one is the Escape rule from `game-mode.md` (rewritten by task 1005144: Escape opens the options menu).
+- **The craft picker waits for the world.** While the start screen is up the shell asks no picker (`onAccess` returned true). `done` runs once the screen is gone and asks `OTBCraftMode.onAccess` then.
+- **Keys.** While either screen is up it keeps every key: the arrows and Tab walk the menu, Escape folds Extras away and does nothing else, so the shell's Escape cannot flip the bars underneath. Once the world shows, the last Escape opens the options menu (task 1005144); the screen's capture listener calls `preventDefault`, so the menu never opens from under it.
+- **The look is Helm (task 1005192, [ADR 0402](../../../docs/adr/0402-helm-is-the-halls-look-and-the-hall-is-dark-only.md)).** The start screen is one full-height night panel over the painting (`--night-glass`, an ice hairline left and right at `--line-strong`), `--helm-panel-w` wide. On a desk it stands off the left edge by `--helm-inset`; that token is a `clamp`, so on a phone the panel is the whole width and the sheet still has no `@media`. In it: the mark (the project's logo when it has one) over the name in the name voice; Start as a full-width accent bar under `--accent-on` that names its key ("Enter", drawn by CSS so the choice's own text stays "Start"); the other four as quiet rows on `--rule-soft` hairlines; and at the foot, over the strong hairline, the tip the load screen will show next (`#gs-line`), with the Quit note under it when the browser keeps the tab. The rows are list rows in a panel, so they are bars, not cut buttons. A row's focus is the inset two-tone ring (`--press-focus`), which is what makes focus visible on the accent bar.
+- **The load screen is the same panel, centred** over the painting under the hall's `--scrim`: the week in the name voice (`#gs-when`), one segment per week of the history (`#gs-segs`, the shared `.segs` / `.seg`; filled up to the week being shown, counted the way the sentence words it, and hidden from a screen reader because the sentence says the same), the city, and the tip under a hairline. With no city there are no segments.
+- **The literal floor is zero.** Every colour, size, corner, shadow, face and measure in `shell-game.css` is a hall-tier token (`style.css`); `tests/hall_start_screen.mjs` fails on a typed one. The fade into the world is one CSS opacity transition, stopped by the hall's reduced-motion rule.
+
+## For the tasks after this one
+
+- R04 (task 1005144): point Options at the options menu and move Achievements/Extras targets if those pages lose their interfaces. Escape on the start screen is free for the menu to use.
+- `shell-game.js` is loaded on every hall page but only Home calls `start()`; `shell-game.css` is linked on Home only. A second page that wants the start screen links the sheet and calls `start()` with its own still.
+
+- New art for the start screen (the city in the clouds) is task 1005196; `welcome-boot.js` still hands in the welcome's painting.
+
+Tests: `tests/hall_start_screen.mjs` (the hand-off and pure parts in a vm; both screens, the panel's place at desk and phone widths, the segments, Quit, the no-city and reduced-motion paths in a real browser).

package/modules/hall-ui/records/tweak-editor.md

@@ -6,7 +6,7 @@ Files: `tweak-editor.html` (the markup), `tweak-editor.css` (the artboard's inli
 
 - **Which page.** `?page=<page id>` (`landing:index`). With none, the page the caller holds (`GET /copy-desk/next`'s `resume`), and with nothing held, the "is in" panel's next up, so a bare link still leads somewhere. The studio (TW16) links here.
 - **One read opens it.** `GET /copy-desk/pages/:pageId/draft` (added here: `GET /copy-desk/pages/:pageId` carries neither the lines nor the draft) answers every reading line with its margin note, the open round and `held_by_you`, and the saved draft, only on the current reading (`draft_on_older_reading` otherwise). The note is the server's: `engineer` is `pages.goesToEngineer`, the submit's own rule, so a shared line with no registry row says "goes to an engineer", which is what the submit will do with it.
-- **The autosave is the whole draft, debounced (700ms) and on blur**, one save in flight at a time, skipped when the body equals the last accepted one; a last `keepalive` PUT on `pagehide`. An emptied box is saved as a removal, `{ key, remove: true }` (task 1004696): its margin note says it is to be removed and goes to an engineer, and the submit files that engineer task (an empty `after` alone is still the server's `line_empty`), and the counter reads "not saved" with the server's own words above the paper when a save is refused.
+- **The autosave is the whole draft, debounced (700ms) and on blur**, one save in flight at a time, skipped when the body equals the last accepted one; a last `keepalive` PUT on `pagehide`. An emptied box is saved as a removal, `{ key, remove: true }` (task 1004696): its margin note says it is to be removed and goes to an engineer, and the submit files that artisan task (an empty `after` alone is still the server's `line_empty`), and the counter reads "not saved" with the server's own words above the paper when a save is refused.
 - **Holding decides writing.** A page nobody holds is read-only with one button, "take this page" (the claim); another builder's is read-only and names them; a submitted one is frozen. Upload and submit are the holder's only, as their routes are.
 - **Every write is named** (`WRITES`: the draft PUT, the .docx POST, the submit, the claim on a server-given `take.path`), and `tests/hall_tweak_editor.mjs` pins the list. The upload is a raw `fetch` because the generated client JSON-encodes every body.
 - **It opens full screen.** The artboard is the whole window, so the first visit sets the shell's switch (task 1004327) on; after that the shell remembers the artist's choice for this page. In full screen the switch button wears the room's glass, since the stage is dark in both themes.

package/modules/hall-ui/records/update-pill.md

@@ -10,3 +10,15 @@ The owner, 2026-11-03: upgrading Bongos from a project's hall was "way too obstr
 - **shell.js got smaller.** The banner's 109 lines became a 61-line loader that fetches `/core-update` once per page and loads the pill only when there is news or a run in flight (1,499 → 1,451 lines).
 
 Tests: `tests/update_pill.mjs` (the pure half, and the real shell + pill in a DOM stub: who sees it, never a link, both doors, refusals, a blocked window, held, a run across pages, done → Reload), `tests/deploy_handoff.mjs` (the hub's three refusals, and its page run for real). Each origin, opener and version check was deleted once and watched to go red. Harness fixture: `core-update.json` (behind, so the pill shows).
+
+## The pop-up (task 1005191)
+
+The owner, 2026-11-10: the pill alone was not seen. Game mode (task 1005142) opens every page without its bars, and full screen hid everything in the top bar's right side except its own button, so a hosted project sat three minor versions behind with nobody told. What this settled:
+
+- **A ready update also asks, once.** `update-pill.js` `maybeAsk` opens the hall's one dialog (`OTBDialog.open`, no bespoke dialog): "Update the builders hall?", up to three release-note lines, the takes-a-few-minutes note, both versions, then *Later* and *Update now*. It reads the same `/software-update` answer the card reads, so both name one version and the two-step rule (ADR 0293 D4) holds.
+- **Update now runs inside the press.** A hosted project opens the hub's window, which a browser allows only from the click; the progress card then opens under the pill.
+- **Any other way of closing it is "later".** That version is not asked about again in this browser for a day (`bongos.update.later`); a newer version asks at once. The pill stays, so later never means lost.
+- **Who is not asked:** a viewer the door would refuse, the hub's handoff window, the `/deploy` page, a builder held at the setup screen, a held version, an update already running. A self-hosted project is told the command, with one *Close* button.
+- **The pill stays with the bars away** (`style.css`, `html[data-fullscreen="on"] .upd-pill`), beside the button that brings the bars back.
+
+Tests: `tests/update_pill.mjs`, the ten cases under "the pop-up".

package/modules/hall-ui/records/visor.md

@@ -0,0 +1,23 @@
+# The visor — the first-person HUD over every scene (task 1005148, BONGOS-V3 R08; ADR 0399)
+
+Covers: `visor.js` + `visor.css`, loaded on Home, `/city`, `/goal-map` and `/thinking`, and the three scene registrations (`sky-interaction.js`, `city.js`, `home-city.js`). Spec: `docs/specs/bongos-v3-game-conversion.md` C2 `you-are-a-character-in-first-person`. Game mode itself is in `game-mode.md`.
+
+## What it settled
+
+- **The look the owner agreed (2026-11-10, five mock-up rounds).** A quiet layout with "hairline instruments" from the helmet round: thin curved visor lines across the top, bottom and both sides, a small centre cross, and a compass of nine slanted cells along the top line with the one salmon marker under its centre. No tracker or radar (tried and dropped), no clipped corners: the pills stay round (DESIGN.md "pill or nothing"). No glow (DESIGN.md's rejected near-black-plus-neon HUD). The frame is one SVG in a 1000×1000 box stretched over the stage with non-scaling strokes, so it is a hairline at every size.
+- **What sits where.** Bottom-left: the character's main action, the one accent pill, with its key. Bottom-right: the sprite (task 1005147's art, `OTBCraftMode.spriteSrc`) with the character's name and the credit count (`/me` `builder.total_credits` through `OTBCraftMode.me()`; credits only, never a payout). Top-right: Actions (key A), which opens the sheet: the character's actions, then "This place" (the scene's own actions and keys), then Options on Escape. A place line under the compass names the scene; the sky leaves it empty because its own heading names it.
+- **Each character's actions** (`ACTIONS`): Artisan Claim a task C (`/work`), Blockers B, Goal sky G, Your thinking T. Artist Review this page R, Edit its words E, Write an idea I (the three craft-mode tools, through `OTBCraftMode.openTool`), Studio S. Patron Board room O, Governor city V, Blockers B, Watch W. Every one is a page or tool the hall already has; the visor gates nothing, and the server's rank checks answer exactly as before (ADR 0399 §2.5). No key a scene binds is reused (the sky's L 0 / ?, the gallery's F, the palette's K, the city card's digits, arrows and Tab).
+- **Glass, not layout (ADR 0399 §2.1).** `#visor` is `position: fixed` with `pointer-events: none`; only the pills and the sheet take a pointer. A drag across a frame line pans the sky (test-pinned).
+- **No camera (§2.2).** A scene registers once: `window.__visorScene = { name, place, actions, keys }`, then `OTBVisor.scene(...)` if the visor is already loaded (it also reads the global at start, so load order between the two does not matter). The sky offers "Back to centre" (its own `fitAll`); the Governor City and Home have no camera yet and offer none, with no disabled button. R13 adds Home's.
+- **Escape (§2.4).** The open sheet takes the press in capture with `preventDefault` and `stopPropagation`, so the sky's pick under it survives; the ambient glass never takes Escape, so the last press reaches the options menu. The letter keys listen in bubble on `window` and skip a press a scene already spent (`defaultPrevented`), one with a modifier, one in a field, and any press while the character picker, the start screen or an `aria-modal` dialog is up.
+- **When it shows.** Game mode (`html[data-game="on"]`) AND a registered scene AND a character (the held one, else this session's craft mode) AND not inside the options menu's frame. Otherwise the hall is exactly as before.
+- **Scenes keep clear of the glass.** While it shows, `visor.js` puts `visor-on` on `<html>`, and `thinking.css` moves the sky's top row, composer, jump field and side panels below the compass, and its foot and tour above the corner pills. A new scene with fixed furniture does the same in its own sheet.
+- **Stacking.** The glass is z 4: above the scene, under the sky's pop-ups (5–8). The Governor City's card lives inside `.city-main`'s stacking context, so the glass is drawn over it; nothing collides (the card is centred, the pills are in the corners).
+
+## For the tasks after this one
+
+- R09 (one hotkey registry): `ACTIONS` keys and the scene `keys` lines are what it registers; the sheet is where a rebind shows.
+- R13 (the sky camera on Home's city): register `fitAll` / `flyTo` as actions in `home-city.js`'s `__visorScene`.
+- R11 (Patron for everyone): no visor change; the Patron's actions already open pages whose routes keep their rank walls.
+
+Tests: `tests/hall_visor.mjs` (the pure parts in a vm; the glass, the pointer pass-through, the Escape order, the sheet, the Artist's tools and the key guards in a real browser over a stand-in scene). The script-order pins in `tests/hall_city.mjs` and `tests/goal_map_page.mjs` name the visor after the shell.

package/modules/hall-ui/records/welcome-tower.md

@@ -32,14 +32,14 @@ finally had Gemini paint the city by day and by night and asked for those to be
 - **Banner.** "Working on the core of <project>" from `__BRANDING__.identity` (never a hardcoded word),
   with `core <version>` under it when the public `GET /version` reports one.
 - **Sequence.** Veil lifts, the city powers up (pulses brighten), the greeting comes up at ~3.4s.
-  **Skip** jumps to the greeting; **Esc**, "Your home page" and Engineer leave slowly: the picture sinks
+  **Skip** jumps to the greeting; **Esc**, "Your home page" and Artisan leave slowly: the picture sinks
   past the rooftops while the welcome fades into the hall underneath (about 2.4s), and the hall can be
   clicked and scrolled from the first moment. A role bound for another room sinks into the veil, then
   opens that room. Under `prefers-reduced-motion` nothing moves and leaving is immediate.
-- **Roles** (the owner's mapping): Owner → `/city`, Ideator → `/thinking`, Artist → `/studio`,
-  Engineer → stays on Home. A pick also calls `OTBCraftMode.choose()` with governing / ideating /
-  artistry / building. **Owner shows only where `OTBCraftMode.offered('governing')`** — Governing is a
-  seat — and the list is built when "Start with your role" is pressed, after the seats have settled.
+- **Roles** (the owner's mapping, renamed by task 1005141): Patron → `/city`, Artist → `/studio`,
+  Artisan → stays on Home (the Ideator door, once `/thinking`, folded into Artist). A pick also calls
+  `OTBCraftMode.choose()` with patron / artist / artisan. **Patron shows only where
+  `OTBCraftMode.offered('patron')`** — the patron craft is a seat — and the list is built when "Start with your role" is pressed, after the seats have settled.
 - **No painting** (a 404) hides the image and leaves the sky gradient; everything else works.
 - **Colours are the paintings'**, in both hall themes: `welcome-boot.css` and `welcome-boot.js` are on
   `tests/hall_audit.mjs`'s literal exemptions with that reason.

package/modules/hall-ui/specimens/components.states.json

@@ -1,6 +1,7 @@
 {
-  "_": "The hall's shared components, each in each tone and state (task 1005086, goal 1000138): the status pill, the panel, the empty state, the loading state, the toast per kind, the tabs and view toggle, the buttons, the field and the dialog. Rendered by the ui-design kit in both modes at 1440/390/320: node modules/ui-design/kit/render.js --states modules/hall-ui/specimens/components.states.json. The public design-system reference (task 1005083) is meant to build on this.",
+  "_": "The hall's shared components, each in each tone and state (task 1005086, goal 1000138): the status pill, the panel, the empty state, the loading state, the toast per kind, the tabs and view toggle, the buttons, the field and the dialog. Rendered by the ui-design kit, dark only like the hall (task 1005192), at 1440/390/320: node modules/ui-design/kit/render.js --states modules/hall-ui/specimens/components.states.json. The public design-system reference (task 1005083) is meant to build on this.",
   "page": "/components",
+  "modes": ["dark"],
   "surface": "modules/hall-ui/specimens",
   "stub": {
     "prefix": "/"

package/modules/ideas/ideator-stats.js

@@ -132,7 +132,9 @@ async function readIdeatorStats(builderId, deps = {}) {
   if (reward && typeof reward.creditsByCraft === 'function') {
     const byCraft = await reward.creditsByCraft([builderId]);
     const row = byCraft.get(String(builderId));
-    ideatorCredits = row ? row.ideator : 0;
+    // The idea streams alone — artist credits also carry page money since the
+    // ideator folded into the artist (task 1005141), so `artist` would overstate this.
+    ideatorCredits = row ? (Number.isFinite(row.ideas) ? row.ideas : 0) : 0;
   }
 
   let ratifiedIds = null;

package/modules/ideas/inbox.js

@@ -396,9 +396,9 @@ async function routeIdeaToGoal({
     //    default — createTask auto-assigns the capped suggestion) and
     //    `discipline` — NO LONGER 'unclassified' (task 1002988). createTask refuses a
     //    craft it cannot infer; refusing a filer is the wrong trade for an INBOX, so we
-    //    ask the same question and fall back to 'engineer' (free to re-triage; a lost capture is not).
+    //    ask the same question and fall back to 'artisan' (free to re-triage; a lost capture is not).
     const task = await lifecycle.createTask({
-      discipline: (lifecycle.resolveWriteDiscipline?.({ title, description: bodyMd, touches: declaredTouches })?.discipline) || 'engineer',
+      discipline: (lifecycle.resolveWriteDiscipline?.({ title, description: bodyMd, touches: declaredTouches })?.discipline) || 'artisan',
       versionId: goal.version_id,
       title,
       description: bodyMd,

package/modules/lifecycle/activity.js

@@ -45,7 +45,7 @@ const { creditsEarnedBySql } = require('./db-tasks.js');
 // (migrations 086 + 176). Anything else is treated as "no filter" rather than
 // 400ing the read: a caller naming a craft that does not exist gets the honest
 // full list, not an error card in the middle of a profile.
-const CRAFTS = ['engineer', 'artist', 'ideator', 'ui', 'unclassified'];
+const CRAFTS = ['artisan', 'artist', 'ui', 'unclassified'];
 
 // One page of an activity list. Clamped here as well as at the route, because
 // these are the functions a CLI or a later surface will call directly.

package/modules/lifecycle/cascade.js

@@ -71,8 +71,8 @@
 //   key         string, stable + unique. It is half the source_ref, so RENAMING
 //               a key re-files every task the rule ever generated. Treat it as
 //               permanent.
-//   discipline  the role the generated work is FOR ('artist', 'ideator',
-//               'engineer'). This is the whole point of the mechanism: the
+//   discipline  the role the generated work is FOR ('artist' or
+//               'artisan'). This is the whole point of the mechanism: the
 //               discipline of the generated task is not the discipline of the
 //               ship that caused it.
 //   when(task, ctx)  a predicate over the shipped task row and the run CONTEXT.
@@ -216,7 +216,7 @@ const CASCADES = Object.freeze([
     key: REMOVAL_RULE_KEY,
     // ENGINEER, not artist: confirming asks whether deleted code is genuinely
     // gone or was moved, which is a question about the diff.
-    discipline: 'engineer',
+    discipline: 'artisan',
     kind: 'unclassified',
     // The anti-recursion guard FIRST: a cascade-generated task must never
     // cascade, so it is rejected before any other test runs.
@@ -250,7 +250,7 @@ const TRIGGERS = Object.freeze({
 const IDEA_CASCADES = Object.freeze([
   Object.freeze({
     key: 'engineer-scoping-on-full-idea',
-    discipline: 'engineer',
+    discipline: 'artisan',
     kind: 'unclassified',
     // A Full Idea is the ideator's hand-off point: the five questions are
     // answered and the thing is described well enough to cost. What it still

package/modules/lifecycle/goal-spec-task.js

@@ -50,7 +50,7 @@ function specTaskFields(goal, { createdBy = null } = {}) {
     ].join('\n'),
     status: 'ready',
     kind: 'spike',
-    discipline: 'ideator',
+    discipline: 'artist',
     source: SPEC_SOURCE,
     sourceRef: specSourceRef(id),
     createdBy,

package/modules/lifecycle/help-requests.js

@@ -14,19 +14,22 @@
 
 'use strict';
 
-const { pool } = require('../../src/module-api');
+const { pool, crafts: craftVocab } = require('../../src/module-api');
 
-// ADR 0174's crafts. Note the vocabulary seam: `builders.preferred_disciplines`
-// spells this same craft 'engineer', not 'builder'. THIS FUNCTION IS THE ONE PLACE
-// that knows the mapping — the matching surface (C02) must consume it rather than
-// re-deriving, or the two spellings drift and a builder silently matches nothing.
-const HELP_CRAFTS = Object.freeze(['artist', 'builder', 'ideator', 'ui']);
-const CRAFT_TO_DISCIPLINE = Object.freeze({ artist: 'artist', ideator: 'ideator', builder: 'engineer', ui: 'ui' });
+// The crafts a request can be addressed to: the two working characters plus the
+// module-contributed `ui`. Since task 1005141 (BONGOS-V3) the help-request spelling
+// and the discipline spelling are THE SAME WORD — the old seam where this craft was
+// 'builder' here and 'engineer' on a builder is closed. The maps stay, because they
+// are also where an OLD spelling is read as today's: a rolled-back release can still
+// write 'engineer'/'ideator' into preferred_disciplines, and craftMapSql() below runs
+// against that column.
+const HELP_CRAFTS = Object.freeze(['artisan', 'artist', 'ui']);
+const CRAFT_TO_DISCIPLINE = Object.freeze({ artisan: 'artisan', artist: 'artist', ui: 'ui' });
 
-const DISCIPLINE_TO_CRAFT = Object.freeze({ artist: 'artist', ideator: 'ideator', engineer: 'builder', ui: 'ui' });
+const DISCIPLINE_TO_CRAFT = Object.freeze({ artisan: 'artisan', artist: 'artist', ui: 'ui', engineer: 'artisan', ideator: 'artist' });
 
 function helpCrafts() { return [...HELP_CRAFTS]; }
-function disciplineForCraft(craft) { return CRAFT_TO_DISCIPLINE[craft] || null; }
+function disciplineForCraft(craft) { return CRAFT_TO_DISCIPLINE[craftVocab.normalizeCraft(craft)] || null; }
 function craftForDiscipline(d) { return DISCIPLINE_TO_CRAFT[d] || null; }
 
 // The caller's OWN crafts, read from builders.preferred_disciplines. This exists
@@ -90,7 +93,8 @@ function capRows(n) {
 function validateHelpRequest(input) {
   const errors = [];
   const b = input || {};
-  const craft = b.needs_craft == null ? null : String(b.needs_craft);
+  // An old spelling ('builder', 'engineer', 'ideator') is today's craft, not an unknown one.
+  const craft = b.needs_craft == null ? null : craftVocab.normalizeCraft(String(b.needs_craft));
   const person = b.needs_builder_id == null ? null : Number(b.needs_builder_id);
 
   if (craft === null && person === null) {
@@ -133,7 +137,7 @@ async function createHelpRequest(input, deps = {}) {
        (requested_by, needs_craft, needs_builder_id, what_is_stuck, task_id, goal_id)
      VALUES ($1, $2, $3, $4, $5, $6)
      RETURNING ${COLS}`,
-    [input.requestedBy, input.needsCraft ?? null, input.needsBuilderId ?? null,
+    [input.requestedBy, input.needsCraft == null ? null : craftVocab.normalizeCraft(String(input.needsCraft)), input.needsBuilderId ?? null,
       String(input.whatIsStuck).trim(), input.taskId ?? null, input.goalId ?? null]
   );
   return rows[0];
@@ -150,7 +154,7 @@ async function createHelpRequest(input, deps = {}) {
 // EXCEPT its author, since answering your own request is not help.
 async function listOpenForBuilder({ builderId, crafts = [], limit = MAX_ROWS }, deps = {}) {
   const activePool = deps.pool || pool;
-  const safeCrafts = (Array.isArray(crafts) ? crafts : []).filter((c) => HELP_CRAFTS.includes(c));
+  const safeCrafts = craftVocab.normalizeCrafts(Array.isArray(crafts) ? crafts : []).filter((c) => HELP_CRAFTS.includes(c));
   const { rows } = await activePool.query(
     `SELECT ${LIST_COLS} ${LIST_FROM}
       WHERE h.status = 'open'
@@ -193,7 +197,7 @@ async function countOpenForBuilder(builderId, deps = {}) {
 }
 
 // The DISCIPLINE_TO_CRAFT map as a SQL CASE, generated from the same object the
-// JS path uses — so the two can never disagree about what an 'engineer' is.
+// JS path uses — so the two can never disagree about what an 'artisan' is.
 function craftMapSql(col) {
   const whens = Object.entries(DISCIPLINE_TO_CRAFT)
     .map(([d, c]) => `WHEN '${d}' THEN '${c}'`).join(' ');
@@ -293,7 +297,7 @@ async function settleFromLedger(deps = {}) {
 // The author exclusion stays too: your own settled asks are the OTHER list.
 async function listArchivedForBuilder({ builderId, crafts = [], limit = MAX_ROWS }, deps = {}) {
   const activePool = deps.pool || pool;
-  const safeCrafts = (Array.isArray(crafts) ? crafts : []).filter((c) => HELP_CRAFTS.includes(c));
+  const safeCrafts = craftVocab.normalizeCrafts(Array.isArray(crafts) ? crafts : []).filter((c) => HELP_CRAFTS.includes(c));
   const { rows } = await activePool.query(
     `SELECT ${LIST_COLS} ${LIST_FROM}
       WHERE h.status <> 'open'
@@ -350,7 +354,7 @@ async function getHelpRequest(id, deps = {}) {
 // closing an ask is not accepting work, it is ending a question.
 async function setHelpRequestStatus({ id, builderId, status, crafts = [] }, deps = {}) {
   const activePool = deps.pool || pool;
-  const safeCrafts = (Array.isArray(crafts) ? crafts : []).filter((c) => HELP_CRAFTS.includes(c));
+  const safeCrafts = craftVocab.normalizeCrafts(Array.isArray(crafts) ? crafts : []).filter((c) => HELP_CRAFTS.includes(c));
   const askerOnly = status === 'withdrawn';
   const { rows } = await activePool.query(
     `UPDATE lifecycle_help_requests

package/modules/lifecycle/kickoff-checklist.js

@@ -59,11 +59,11 @@ const MERGE_GATE = {
 
 const INSTANCE_LOOK = {
   title: 'Fill the instance look with your own LLM',
-  // 'ideator' is a DISCIPLINE, not a kind — tasks_kind_check rejects it as a
+  // 'artist' is a DISCIPLINE, not a kind — tasks_kind_check rejects it as a
   // kind and the task silently vanished from the checklist (the one non-infra
   // kickoff step). Deciding the instance look is a decision by an ideator.
   kind: 'decision',
-  discipline: 'ideator',
+  discipline: 'artist',
   description: 'init wrote a lean config/branding.json and left the LOOK to you (a locked project rule: brand with your ' +
     'own LLM, not a generator). Hand docs/branding-fill-prompt.md to your AI to design a palette/fonts/wordmark, or keep the vanilla look.',
 };
@@ -178,7 +178,7 @@ function genesisChecklist({ existing = false } = {}) {
     // The ref names the step, never its position, so the brownfield step slotting in
     // ahead of scope's own cannot re-key it into a duplicate.
     out[stage] = list.map((t) => ({
-      ...t, kind: 'decision', discipline: 'ideator', ref: t === GENESIS_EXISTING_FIRST ? 'genesis:scope:existing' : `genesis:${stage}`,
+      ...t, kind: 'decision', discipline: 'artist', ref: t === GENESIS_EXISTING_FIRST ? 'genesis:scope:existing' : `genesis:${stage}`,
     }));
   }
   return out;

package/modules/lifecycle/kickoff-seed.js

@@ -57,7 +57,7 @@ async function seedKickoffIfEmpty({ builderId = null } = {}, deps = {}) {
       description: t.description || '',
       status: 'ready',
       kind: t.kind || 'infra',
-      discipline: t.discipline || 'engineer',
+      discipline: t.discipline || 'artisan',
       source: 'first-sign-in',
       createdBy: builderId,
       // BV1.R11 (task 1003598): this runs on an instance with zero tasks and, in

package/modules/lifecycle/migrations/lifecycle_021_crafts_artisan_artist.sql

@@ -0,0 +1,29 @@
+-- lifecycle_021_crafts_artisan_artist.sql — task 1005141 (BONGOS-V3 C1): the lifecycle
+-- module's craft columns follow core_296's rename (engineer → artisan, ideator → artist).
+--
+-- lifecycle_help_requests.needs_craft spelled the engineering craft 'builder' (ADR 0174);
+-- that seam closes here — it is 'artisan' like everywhere else. The CHECK is a superset
+-- of old and new words so a rolled-back release can still write (see core_296).
+--
+-- lifecycle_mingle_pairs records the two crafts AS MATCHED, for audit, under a
+-- cross-craft CHECK, in the help-request spelling. builder → artisan is renamed. An artist × ideator pair is left
+-- exactly as recorded: the fold would make it artist × artist, which is both a false
+-- record of why it was matched and a CHECK violation. The code normalizes on read.
+
+BEGIN;
+
+ALTER TABLE lifecycle_help_requests DROP CONSTRAINT IF EXISTS lifecycle_help_requests_craft_chk;
+UPDATE lifecycle_help_requests SET needs_craft = 'artisan' WHERE needs_craft IN ('builder', 'engineer');
+UPDATE lifecycle_help_requests SET needs_craft = 'artist'  WHERE needs_craft = 'ideator';
+ALTER TABLE lifecycle_help_requests ADD CONSTRAINT lifecycle_help_requests_craft_chk
+  CHECK (needs_craft IS NULL OR needs_craft IN ('artisan', 'artist', 'patron', 'ui', 'builder', 'ideator'));
+
+UPDATE lifecycle_mingle_pairs SET craft_lo = 'artisan'
+ WHERE craft_lo IN ('builder', 'engineer') AND craft_hi <> 'artisan';
+UPDATE lifecycle_mingle_pairs SET craft_hi = 'artisan'
+ WHERE craft_hi IN ('builder', 'engineer') AND craft_lo <> 'artisan';
+
+INSERT INTO schema_migrations (version) VALUES ('lifecycle_021_crafts_artisan_artist')
+ON CONFLICT (version) DO NOTHING;
+
+COMMIT;

package/modules/lifecycle/mingle.js

@@ -38,7 +38,7 @@
 //
 // THE CRAFT VOCABULARY IS NOT REDEFINED HERE. help-requests.js declares itself the
 // one place that knows how a craft maps to `builders.preferred_disciplines`
-// ('builder' the craft is 'engineer' the discipline), so this file consumes
+// (and reads an old 'engineer'/'ideator' discipline as today's), so this file consumes
 // `craftMapSql` / `craftForDiscipline` from it rather than re-deriving. Two
 // spellings of the same craft would silently match nobody.
 //
@@ -67,14 +67,14 @@ const MAX_ROWS = 100;
 const MATCHING = Object.freeze({
   rule: 'cross_craft',
   description:
-    'A pair is two builders whose crafts do not overlap at all — an engineer with '
-    + 'an artist or an ideator, never two of the same. The premise is that the '
+    'A pair is two builders whose crafts do not overlap at all — an artisan with '
+    + 'an artist or a UI designer, never two of the same. The premise is that the '
     + 'person you need is often not another one of you.',
   // Stated because it is the road not taken, and an unexplained absence reads as
   // an oversight to the next person holding the matcher.
   rejected: 'same_craft — it duplicates the craft-matched Collab request path (criterion collab-page-matches-my-craft).',
   // DISJOINT, not merely "different". A builder who is both an artist and an
-  // engineer shares a craft with every engineer, so pairing them would put two of
+  // artisan shares a craft with every artisan, so pairing them would put two of
   // the same in a room and call it cross-craft.
   overlap: 'none',
   consent: 'Both switches required: the project enables mingle AND the builder opts in. Either off means no pair.',

package/modules/lifecycle/page-tweak-write.js

@@ -161,7 +161,7 @@ async function submitPageTweak({ taskId, builderId, versionId = null, freeze },
         // page does not wait for it.
         status: 'backlog',
         kind: 'feature',
-        discipline: 'engineer',
+        discipline: 'artisan',
         priority: 4,
         touches: u.touches || [],
         source: u.source,

package/modules/lifecycle/routes/task-write-routes.js

@@ -23,7 +23,7 @@ const hierarchy = require('../hierarchy');
 const { suggestCriteria } = require('../criterion-suggest');
 const { buildGoalAdvisory } = require('../goal-advisory');
 const { buildDependencyAdvisory } = require('../dependency-advisory');
-const { classifyTaskKind, VALID_KINDS, WRITABLE_DISCIPLINES, resolveWriteDiscipline, VOTABLE_TASK_STATUSES, TASK_FIELD_BOUNDS } = require('../task-classifier');
+const { classifyTaskKind, VALID_KINDS, WRITABLE_DISCIPLINES, resolveWriteDiscipline, VOTABLE_TASK_STATUSES, TASK_FIELD_BOUNDS, normalizeDisciplineValue } = require('../task-classifier');
 const { isModuleKey, moduleKeys } = api.moduleScopeMap;
 const { validateOrRespond, LIMITS, parseId } = api;
 const { badKind, badNeeds, detectsMigration } = require('./task-route-helpers.js');
@@ -438,6 +438,8 @@ module.exports = function registerTaskWriteRoutes(router) {
     const hasParent = Object.prototype.hasOwnProperty.call(body, 'parent_task_id');
     const hasKind = Object.prototype.hasOwnProperty.call(body, 'kind');
     const hasDiscipline = Object.prototype.hasOwnProperty.call(body, 'discipline');
+    // An old craft spelling is today's craft (task 1005141): written as the new word.
+    if (hasDiscipline) body.discipline = normalizeDisciplineValue(body.discipline);
     // V3.R15 #239: newcomer_friendly is the canonical name; xenos_claimable is
     // the pre-rename alias and still accepted. Either presence triggers the
     // same update path.

package/modules/lifecycle/routes/tasks.js

@@ -63,7 +63,7 @@ const NO_PR_STATUS = Object.freeze({
   pr_state: 'none', merged: false, merge_sha: null, deploy_status: 'none', pr_url: null, pr_number: null, pr_title: null, pr_body: null,
   branch_hint: 'No pull request titled for this task is among the 100 most recent. Pass ?branch=<name> to ask about a specific branch.' });
 const seams = api;
-const { classifyTaskKind, VALID_KINDS, VALID_DISCIPLINES, VOTABLE_TASK_STATUSES, TASK_FIELD_BOUNDS } = require('../task-classifier');
+const { classifyTaskKind, VALID_KINDS, VALID_DISCIPLINES, VOTABLE_TASK_STATUSES, TASK_FIELD_BOUNDS, normalizeDisciplineValue } = require('../task-classifier');
 const { isModuleKey, moduleKeys } = api.moduleScopeMap;
 const { validateOrRespond, LIMITS, parseId } = api;
 // The onboarding state machine + the evergreen newcomer-chore restock carved into
@@ -146,7 +146,7 @@ module.exports = function buildTasksRouter() {
   const CREATED_BY_MSG = "created_by must be a positive builder id, or 'none' for the unattributed.";
 
   router.get('/tasks', auth.requireBuilder, async (req, res) => {
-    const { version, status, kind, discipline, goal_id } = req.query;
+    const { version, status, kind, goal_id } = req.query; const discipline = normalizeDisciplineValue(req.query.discipline); // old craft spellings read as today's (task 1005141)
     if (kind && !VALID_KINDS.has(kind)) {
       return badKind(res);
     }
@@ -203,7 +203,7 @@ module.exports = function buildTasksRouter() {
   router.get('/tasks/claimable',
     auth.requireBuilder,
     async (req, res) => {
-    const { version, discipline, fit } = req.query;
+    const { version, fit } = req.query; const discipline = normalizeDisciplineValue(req.query.discipline);
     if (discipline && !VALID_DISCIPLINES.has(discipline)) {
       return res.fail('bad_discipline', 400, { valid: Array.from(VALID_DISCIPLINES) });
     }

package/modules/lifecycle/ship-card.js

@@ -223,9 +223,8 @@ function fmtMins(n) {
 // "Open the work" button firing a slash command that no longer resolves. A
 // module-contributed discipline still routes to its skill ('ui' -> /design).
 const DISCIPLINE_PACK = {
-  engineer: 'docs/packs/engineer.md',
+  artisan: 'docs/packs/artisan.md',
   artist: 'docs/packs/artist.md',
-  ideator: 'docs/packs/ideator.md',
 };
 const DISCIPLINE_SKILL = { ui: 'design' };
 
@@ -241,7 +240,7 @@ function nextActionFor(stage, { taskId, discipline, sandboxUrl } = {}) {
     if (skill) return { kind: 'prompt', label: 'Open the work', cmd: `/${skill}` };
     // Default to the Engineer pack for an unknown or unset discipline, the same way
     // this used to default to /dev: engineering is the project's default loop.
-    const pack = DISCIPLINE_PACK[discipline] || DISCIPLINE_PACK.engineer;
+    const pack = DISCIPLINE_PACK[discipline] || DISCIPLINE_PACK.artisan;
     return { kind: 'prompt', label: 'Open the work', cmd: `Read ${pack} and start the work` };
   }
   return { kind: 'prompt', label: 'Continue', cmd: '/builder-start' };