@bongos/core 1.19.485 → 1.19.487

package/migrations/core_231_project_settings_and_attention_water.sql

@@ -0,0 +1,163 @@
+-- core_231_project_settings_and_attention_water.sql — the rot clock and the knob
+-- that sets it (task 1003279, goal 1000072, criterion legibility-sort-and-staleness).
+--
+-- THE GAP. Goal 1000072's rotting half asks that "untouched-for-X triggers a
+-- configured action rather than a silent decay". Two things were missing to make
+-- that sentence true, and this migration adds exactly those two:
+--
+--   1. X had nowhere to live. src/stale-timer.js (task 1003476, ADR 0226) owns the
+--      CLAIM-silence timer — hours, env-configured, and the sweep that ACTS on it
+--      releases someone's claim. The rot timer is a different measurement with a
+--      different unit and a different consequence (days; it asks a human a
+--      question), and task 1003280 requires it be "live, DB-backed" and warns
+--      "do not fork a second store". So: one generic project_settings table, with
+--      the rot timer as its first key.
+--
+--   2. "Water" had nothing to write. The owner's four verbs are prune, kill,
+--      prioritise and WATER — leave the thing alone and reset its clock. Without
+--      somewhere to record that, watering would have to fake a real edit, and the
+--      same line would come back on the next read; the inbox teaches people to
+--      ignore it within a week. attention_watered_at IS the reset.
+--
+-- WHY A COLUMN AND NOT AN ITEMS TABLE. There is deliberately no `attention_items`
+-- row anywhere in this design. The inbox line is DERIVED on read from the rot clock
+-- (below) vs the timer, which makes "exactly one open item per stale thing, not one
+-- per sweep" true by construction rather than by a de-duplicating sweep that has to
+-- be got right.
+-- Acting on the line (prune/kill/prioritise) changes status and the row stops
+-- matching; watering pushes the clock forward and it stops matching. Nothing to
+-- reconcile, nothing to garbage-collect, and no way to accrete duplicates.
+--
+-- Additive + forward-safe: every column is nullable with no backfill, nothing is
+-- renamed, and no existing reader changes meaning (tests/migrations_forward_safe.mjs).
+
+BEGIN;
+
+-- ---------------------------------------------------------------------------
+-- 1. project_settings — the instance's live, DB-backed knobs.
+-- ---------------------------------------------------------------------------
+--
+-- Deliberately a generic key/value table rather than one column per knob: task
+-- 1003280 puts five project fundamentals on one page, and a table that grows a
+-- migration per knob would make that page a schema change every time. Values are
+-- stored as TEXT and parsed by a typed accessor at the read edge
+-- (src/bongos/project-settings.js), the same shape src/stale-timer.js already uses
+-- for env values — one parser, one range check, one documented default.
+--
+-- A key that has never been set has NO ROW. Absence means "use the code default",
+-- which is what lets a fresh instance boot correctly with an empty table, and what
+-- lets a settings page distinguish "never configured" from "deliberately set to
+-- the same value the default happens to be".
+CREATE TABLE IF NOT EXISTS project_settings (
+  key         text PRIMARY KEY,
+  value       text NOT NULL,
+  updated_at  timestamptz NOT NULL DEFAULT now(),
+  updated_by  bigint REFERENCES builders(id)
+);
+
+COMMENT ON TABLE project_settings IS
+  'Live, DB-backed per-project knobs (task 1003279). Key/value so task 1003280''s settings page can grow a row without a migration. No row = never configured = use the code default; that absence is meaningful, so do not seed defaults here.';
+COMMENT ON COLUMN project_settings.value IS
+  'Stored as text and parsed by a typed accessor at the read edge (src/bongos/project-settings.js). A value that fails its range check is IGNORED with a receipt, never coerced silently — the ADR 0226 posture.';
+COMMENT ON COLUMN project_settings.updated_by IS
+  'The builder who last set this knob. NULL = set by a system path with no builder in the request (the goals.created_by convention, migration 160).';
+
+-- ---------------------------------------------------------------------------
+-- 2. The water mark, on both tiers that can rot.
+-- ---------------------------------------------------------------------------
+--
+-- NULL = never watered, and the thing's own activity timestamp is the whole clock.
+-- This is why the read expression is a GREATEST and not a bare COALESCE: a real edit
+-- after a watering must move the clock forward again, and a watering must never make
+-- a thing look OLDER than its last genuine touch.
+--
+-- THE ROT CLOCK, AND WHY IT IS SHAPED LIKE THIS:
+--
+--   tasks:  GREATEST(updated_at, COALESCE(shipped_at, updated_at),
+--                    COALESCE(attention_watered_at, updated_at))
+--   goals:  GREATEST(updated_at, COALESCE(attention_watered_at, updated_at))
+--
+-- The first two terms are NOT a new definition of "touched" — they are exactly the
+-- one modules/hall-ui/public/task-lib.js already publishes for the Tasks board and
+-- the Goals page (`taskActivityMs = max(updated_at, shipped_at)`, task 1003278, this
+-- same criterion), which folds in shipped_at because a ship path can stamp it
+-- without touching updated_at. This migration adds a THIRD term to that definition
+-- and nothing else. Had the server invented its own two-term clock, the board and
+-- the inbox would disagree about which rows are stale — which is the 6h-vs-24h
+-- failure of ADR 0226 reappearing one tier up, and the reason the indexes below
+-- spell the expression out in full rather than approximating it.
+-- (Goals carry no shipped_at column, so their clock has two terms, not three.)
+ALTER TABLE tasks
+  ADD COLUMN IF NOT EXISTS attention_watered_at timestamptz,
+  ADD COLUMN IF NOT EXISTS attention_watered_by bigint REFERENCES builders(id);
+
+ALTER TABLE goals
+  ADD COLUMN IF NOT EXISTS attention_watered_at timestamptz,
+  ADD COLUMN IF NOT EXISTS attention_watered_by bigint REFERENCES builders(id);
+
+COMMENT ON COLUMN tasks.attention_watered_at IS
+  'When a human last said "leave it, it is fine" about this task rotting (task 1003279). Resets the rot clock without touching the work. NULL = never watered.';
+COMMENT ON COLUMN goals.attention_watered_at IS
+  'When a human last said "leave it, it is fine" about this goal rotting (task 1003279). Resets the rot clock without touching the work. NULL = never watered.';
+
+-- The rot read is "open things whose clock is older than N days", so the index is
+-- on (status, clock) — status first because it is the equality predicate and it
+-- cuts the table to the open rows before the range scan ever runs.
+CREATE INDEX IF NOT EXISTS idx_tasks_attention_rot
+  ON tasks (status, (GREATEST(updated_at,
+                              COALESCE(shipped_at, updated_at),
+                              COALESCE(attention_watered_at, updated_at))));
+CREATE INDEX IF NOT EXISTS idx_goals_attention_rot
+  ON goals (status, (GREATEST(updated_at, COALESCE(attention_watered_at, updated_at))));
+
+-- ---------------------------------------------------------------------------
+-- 3. Rebuild the two `t.*` views so the new columns are projected.
+-- ---------------------------------------------------------------------------
+--
+-- A Postgres view created with `SELECT t.*` pins its column list at CREATE VIEW
+-- time. core_227's header records six columns that silently never reached the claim
+-- feed exactly this way; bodies below are identical to core_227's (the wildcard
+-- re-expands to every current column).
+
+DROP VIEW IF EXISTS claimable_tasks;
+CREATE VIEW claimable_tasks AS
+SELECT t.*,
+       pms_calibrated_minutes(t.est_minutes, t.kind) AS est_minutes_calibrated
+  FROM tasks t
+ WHERE t.status = 'ready'
+   AND t.title NOT LIKE '\_\_smoke\_\_%' ESCAPE '\'
+   AND NOT EXISTS (
+     SELECT 1 FROM task_blockers tb WHERE tb.task_id = t.id
+   )
+   AND NOT EXISTS (
+     SELECT 1 FROM claims c
+       JOIN tasks t2 ON t2.id = c.task_id
+      WHERE c.released_at IS NULL
+        AND t2.touches && t.touches
+   );
+
+DROP VIEW IF EXISTS tasks_session_fit;
+CREATE VIEW tasks_session_fit AS
+SELECT t.*,
+  CASE
+    WHEN t.automation_tag = 'overnight-safe' AND COALESCE(t.manual_degree, 5) <= 2
+         AND NOT EXISTS (SELECT 1 FROM task_blockers tb WHERE tb.task_id = t.id)
+      THEN ARRAY['autonomous','check-in','active']
+    WHEN t.automation_tag = 'live-only' OR COALESCE(t.manual_degree, 5) >= 4
+      THEN ARRAY['active']
+    ELSE ARRAY['check-in','active']
+  END AS fits_session_modes,
+  pms_calibrated_minutes(t.est_minutes, t.kind) AS est_minutes_calibrated,
+  CASE
+    WHEN t.credits_reward > 0
+     AND pms_calibrated_minutes(t.est_minutes, t.kind) IS NOT NULL
+     AND pms_calibrated_minutes(t.est_minutes, t.kind) > 0
+    THEN ROUND(t.credits_reward::numeric / pms_calibrated_minutes(t.est_minutes, t.kind), 3)
+    ELSE NULL
+  END AS credits_per_minute
+FROM tasks t;
+
+COMMIT;
+
+INSERT INTO schema_migrations (version) VALUES ('core_231_project_settings_and_attention_water')
+ON CONFLICT (version) DO NOTHING;

package/modules/dev-box/app/src/vendor/bongos-client.cjs

@@ -386,6 +386,8 @@ function createClient(opts = {}) {
       postGoalsIdTransfer: (args) => request("POST", "/goals/{id}/transfer", { hasBody: true }, args),
       // PATCH /goals/{id}/visibility — rank: any-builder — PATCH /goals/:id/visibility
       patchGoalsIdVisibility: (args) => request("PATCH", "/goals/{id}/visibility", { hasBody: true }, args),
+      // POST /goals/{id}/water — rank: any-builder — POST /goals/:id/water
+      postGoalsIdWater: (args) => request("POST", "/goals/{id}/water", { hasBody: true }, args),
       // GET /goals/inbox — rank: any-builder — GET /goals/inbox
       getGoalsInbox: (args) => request("GET", "/goals/inbox", { hasBody: false }, args),
       // POST /goals/reorder — rank: metic+archon — POST /goals/reorder
@@ -466,6 +468,8 @@ function createClient(opts = {}) {
       getInboxAwaitingNod: (args) => request("GET", "/inbox/awaiting-nod", { hasBody: false }, args),
       // GET /inbox/by-builder/{id} — rank: any-builder — GET /inbox/by-builder/:id
       getInboxByBuilderId: (args) => request("GET", "/inbox/by-builder/{id}", { hasBody: false }, args),
+      // GET /inbox/rotting — rank: any-builder — GET /inbox/rotting
+      getInboxRotting: (args) => request("GET", "/inbox/rotting", { hasBody: false }, args),
       // POST /inbox/score — rank: any-builder — POST /inbox/score
       postInboxScore: (args) => request("POST", "/inbox/score", { hasBody: true }, args),
       // GET /inbox/sparks — rank: any-builder — GET /inbox/sparks
@@ -838,6 +842,8 @@ function createClient(opts = {}) {
       postTasksIdVisual: (args) => request("POST", "/tasks/{id}/visual", { hasBody: true }, args),
       // POST /tasks/{id}/vote — rank: metic+archon — POST /tasks/:id/vote
       postTasksIdVote: (args) => request("POST", "/tasks/{id}/vote", { hasBody: true }, args),
+      // POST /tasks/{id}/water — rank: any-builder — POST /tasks/:id/water
+      postTasksIdWater: (args) => request("POST", "/tasks/{id}/water", { hasBody: true }, args),
       // GET /tasks/claimable — rank: any-builder — GET /tasks/claimable
       getTasksClaimable: (args) => request("GET", "/tasks/claimable", { hasBody: false }, args),
       // GET /tasks/newcomer-floor — rank: any-builder — GET /tasks/newcomer-floor

package/modules/hall-ui/public/dom-utils.js

@@ -106,6 +106,28 @@
     return m.enabled[name] === true;
   }
 
+  // The crafts THIS instance offers, in the server's own order (task 1003487).
+  // serve-internal.js injects it beside `enabled` from clientModules(), and it is
+  // the very list `db.updateBuilderDisciplines` validates a PATCH against — so a
+  // picker built from it can never offer a craft the API would 422. A module adds
+  // its own via `contributes.disciplines` (art-pipeline → artist, ui-design → ui),
+  // which is why no picker needs a moduleOn() branch per craft any more. Falls back
+  // to the two core crafts when an older server sent no list, never to an empty
+  // picker.
+  function disciplines() {
+    const m = window.__MODULES__;
+    const list = m && Array.isArray(m.disciplines) ? m.disciplines : null;
+    return list && list.length ? list.slice() : ['engineer', 'ideator'];
+  }
+
+  // How a craft is named in a picker. An acronym stays upper-case ('ui' → 'UI');
+  // anything else is Title Case, so a craft a module adds later needs no new entry.
+  function disciplineLabel(d) {
+    const s = String(d || '');
+    if (!s) return '';
+    return s === 'ui' ? 'UI' : s.charAt(0).toUpperCase() + s.slice(1);
+  }
+
   // Module→core settings-panel contribution seam (BV1.R42, ADR 0083) — the
   // browser twin of the server's 'profile.fields' seam (src/module-seams.js). A
   // module that has left core registers a Settings panel from its own client
@@ -301,7 +323,7 @@
   }
 
   window.OTB = {
-    escapeHtml, $, fmtNum, num, fmtInt, fmtCompact, fmtDate, rankLabel, toast, moduleOn,
+    escapeHtml, $, fmtNum, num, fmtInt, fmtCompact, fmtDate, rankLabel, toast, moduleOn, disciplines, disciplineLabel,
     errCode, errMessage, errDetails, // task 1002462 — ADR 0116 envelope readers
     contributeSettingsPanel, settingsPanels,
     contributeHallWidget, hallWidgets, hallWidgetIds,

package/modules/hall-ui/public/goal-inbox.js

@@ -167,6 +167,19 @@
   }
 
   function onClick(e) {
+    // task 1003279: a rot verb. Handled FIRST because its rows carry no data-goal —
+    // the path is server-declared and already tier-correct, so this branch needs to
+    // know nothing about which of the four verbs was pressed beyond what to say
+    // afterwards. Refreshes the ROT slice only: repainting the goals list would
+    // leave the acted-on row sitting there (the task-1003066 lesson).
+    const rotBtn = e.target.closest('[data-rot-path]');
+    if (rotBtn) {
+      const verb = rotBtn.dataset.rotVerb;
+      act(() => postJSON(`${API}${rotBtn.dataset.rotPath}`, {}),
+        ROT_TOASTS[verb] || 'Done.', loadRot);
+      return;
+    }
+
     // task 1003066 (BV1.R05): the nod. It reuses the EXISTING promote route —
     // POST /tasks/:id/promote, already Metic+ via task.promote — so giving a nod
     // adds no endpoint and no permission. Handled before the membership branches
@@ -262,6 +275,104 @@
       .catch(() => { /* a non-triager's 403, or a hiccup: never break the hall */ });
   }
 
+  // ---- the rot queue (task 1003279, goal 1000072) ---------------------------
+  //
+  // "Untouched-for-X triggers a configured action rather than a silent decay."
+  // The owner's decision (2026-08-25): the action is a LINE IN THIS CARD, not an
+  // automatic status change and not a nightly digest. Auto-demoting mutates real
+  // work with no human in the loop, and a wrong timer then silently freezes it; a
+  // digest is a notification, not an action, and gets scrolled past.
+  //
+  // THE BUTTONS ARE SERVER-DECLARED. Each row arrives carrying its own `verbs`
+  // array — label, method and path — and this renders exactly those. It is not
+  // decoration: three of the four verbs reuse EXISTING routes (promote, demote,
+  // abandon, archive) whose permissions differ by tier, and a hardcoded button list
+  // here would be a second copy of that mapping, free to drift into offering a
+  // button the server will refuse. A goal legitimately gets two verbs where a task
+  // gets four; this file does not need to know why.
+  //
+  // No client-side rank gate, for the same reason the nod slice has none: the read
+  // is scoped server-side, so a builder is only ever handed rows that are theirs to
+  // act on and the button list is already narrowed to what they can press.
+  const MAX_ROT_ROWS = 5;
+
+  function untouchedFor(iso) {
+    const t = iso ? Date.parse(iso) : NaN;
+    if (Number.isNaN(t)) return 'untouched';
+    const days = Math.floor((Date.now() - t) / 86400000);
+    if (days < 1) return 'untouched today';
+    return `untouched ${days} day${days === 1 ? '' : 's'}`;
+  }
+
+  function rotRowHtml(r) {
+    const href = r.tier === 'goal'
+      ? goalHref(r.id)
+      : `/task/${encodeURIComponent(r.id)}`;
+    const where = r.tier === 'goal'
+      ? 'goal'
+      : (r.goal_title ? escapeHtml(r.goal_title) : `goal ${escapeHtml(String(r.goal_id || '—'))}`);
+    // `watered` is worth showing: a row that is back DESPITE having been watered is
+    // a different message from one nobody has ever looked at, and hiding that would
+    // make the second watering feel like the first one did nothing.
+    const again = r.ever_watered ? ' · watered before' : '';
+    const buttons = (Array.isArray(r.verbs) ? r.verbs : []).map((v) => {
+      const path = String(v.path || '').replace(':id', encodeURIComponent(r.id));
+      return `<button class="btn-ghost" type="button" data-rot-path="${escapeHtml(path)}"`
+        + ` data-rot-verb="${escapeHtml(String(v.verb || ''))}"`
+        + ` title="${escapeHtml(String(v.hint || ''))}">${escapeHtml(String(v.label || v.verb || '?'))}</button>`;
+    }).join('');
+    return `<li class="ginbox__item" data-rot-tier="${escapeHtml(String(r.tier))}">
+        <div class="ginbox__main">
+          <a class="ginbox__goal" href="${href}">${escapeHtml(r.title || `${r.tier} #${r.id}`)}</a>
+          <span class="ginbox__sub">${escapeHtml(String(r.status || ''))} · ${where} · ${escapeHtml(untouchedFor(r.last_touched_at))}${again}</span>
+        </div>
+        <div class="ginbox__acts">${buttons}</div>
+      </li>`;
+  }
+
+  // What each verb says when it lands. Keyed by the SERVER's verb name so a new verb
+  // degrades to a neutral confirmation instead of a blank toast.
+  const ROT_TOASTS = {
+    prioritise: 'Prioritised — it’s claimable now.',
+    prune: 'Pruned — back in the backlog.',
+    kill: 'Killed — it won’t come back.',
+    water: 'Watered — the clock is reset.',
+  };
+
+  function renderRot(data) {
+    const box = host && host.querySelector('#attention-rot');
+    if (!box) return;
+    const rows = (data && Array.isArray(data.rows)) ? data.rows : [];
+    if (!rows.length) {
+      box.innerHTML = '';
+      window.OTBAttention?.refresh();
+      return;
+    }
+    const shown = rows.slice(0, MAX_ROT_ROWS);
+    const more = rows.length > shown.length
+      ? `<p class="ginbox__pending">…${rows.length - shown.length} more going quiet.</p>`
+      : '';
+    // The heading names the TIMER, not just the count. A reader who disagrees with
+    // the line ("30 days is too short for a backlog") needs to know which number
+    // produced it before they can go change it — and when that number came from a
+    // value the server could not use, the receipt says so here, on the screen of
+    // somebody who can fix it.
+    const t = (data && data.timer) || {};
+    const timerNote = t.invalid
+      ? `<span class="ginbox__sub"> — ${escapeHtml(String(t.describe || ''))}</span>`
+      : `<span class="ginbox__sub"> — untouched ${escapeHtml(String(t.rot_days ?? '?'))}+ days</span>`;
+    box.innerHTML = '<h3 class="ginbox__sec-h">Going quiet '
+      + `<span class="count-pill">${rows.length}</span>${timerNote}</h3>`
+      + `<ul class="ginbox__list">${shown.map(rotRowHtml).join('')}</ul>${more}`;
+    window.OTBAttention?.refresh();
+  }
+
+  function loadRot() {
+    return getJSON(`${API}/inbox/rotting`)
+      .then((data) => renderRot(data))
+      .catch(() => { /* signed out, older server, or a hiccup: never break the hall */ });
+  }
+
   // task 2169: this widget IS the "Needs your attention" card — ONE capped
   // summary hosting every actionable item class: goal invitations +
   // join-requests (this file) and ideas awaiting triage (builders.js renders
@@ -294,10 +405,17 @@
       // awaiting a nod inside a goal sits nearer the goals slice than idea
       // triage. Its rows carry the shared .ginbox__item class, so refresh()
       // counts them with no change to the selector below.
-      '<div id="attention-nod"></div>';
+      '<div id="attention-nod"></div>' +
+      // task 1003279 (goal 1000072): work going quiet — a goal or task untouched
+      // past the project's rot timer, with the owner's four verbs on it. LAST in
+      // the card on purpose: every slice above is somebody waiting on YOU right
+      // now, while rot is a standing question that has already waited weeks and
+      // can wait until they are read.
+      '<div id="attention-rot"></div>';
     host.addEventListener('click', onClick);
     load();
     loadNodQueue();
+    loadRot();
     // task 1002802 (P06): the profile slice lives in its own file (builders.js is
     // over the size budget); this card owns its div, so it boots it here.
     window.OTBProfileNudge?.load();

package/modules/hall-ui/public/hall-render.js

@@ -923,17 +923,16 @@
             ? ctx.lastMeState.builder.preferred_disciplines : [];
           const discBtn = (value, label) => {
             const on = prefs.includes(value);
-            return `<button type="button" class="btn-ghost onboarding-item__disc${on ? ' onboarding-item__disc--on' : ''}" data-disc="${value}" aria-pressed="${on}">${label}</button>`;
+            return `<button type="button" class="btn-ghost onboarding-item__disc${on ? ' onboarding-item__disc--on' : ''}" data-disc="${escapeHtml(value)}" aria-pressed="${on}">${escapeHtml(label)}</button>`;
           };
-          // R59 (task 1198): 'artist' is offered only when the art-pipeline module
-          // is enabled — engineer + ideator are methodology core. moduleOn defaults
-          // to true if the flag is missing, so OTB (art on) is unchanged; a vanilla
-          // instance hides the button the server would reject anyway.
+          // The offered crafts come from the server (task 1003487): window.__MODULES__
+          // .disciplines IS enabledDisciplines(), the same list the PATCH validates
+          // against, so this can never render a button the API would reject. Was a
+          // hardcoded triple with a moduleOn('art-pipeline') branch for 'artist', so
+          // a module-contributed craft (ui-design → ui) never appeared here at all.
           action = `
             <div class="onboarding-item__action onboarding-item__disc-pick">
-              ${discBtn('engineer', 'Engineer')}
-              ${OTB.moduleOn('art-pipeline') ? discBtn('artist', 'Artist') : ''}
-              ${discBtn('ideator', 'Ideator')}
+              ${OTB.disciplines().map((d) => discBtn(d, OTB.disciplineLabel(d))).join('')}
             </div>`;
         } else if (s.id === 'ship_three') {
           action = `

package/modules/hall-ui/public/settings.js

@@ -732,12 +732,13 @@
 
   // ---- section 2: CRAFT (discipline preferences) ---------------------------
 
-  // Valid disciplines are limited (see me.js + db.updateBuilderDisciplines):
-  // engineer | ideator (core) + artist when the art-pipeline module is on
-  // (R59 / task 1198). moduleOn defaults true if the flag is missing, so OTB
-  // (art on) keeps all three; a vanilla instance offers only the two it accepts.
-  const DISCIPLINES = ['engineer', 'artist', 'ideator']
-    .filter((d) => (d === 'artist' ? window.OTB.moduleOn('art-pipeline') : true));
+  // The crafts this instance offers, straight from the server (task 1003487):
+  // window.__MODULES__.disciplines IS enabledDisciplines(), which is also what
+  // db.updateBuilderDisciplines validates against, so what this renders and what
+  // the PATCH accepts cannot drift. Was a hardcoded triple gated on
+  // moduleOn('art-pipeline'), which silently dropped a module-contributed craft
+  // (ui-design → ui) from BOTH the chips and the saved-state echo below.
+  const DISCIPLINES = window.OTB.disciplines();
 
   // Current selection mutated in place as the builder toggles chips; saved on
   // the "Save" button (the hall's profile card behaviour) via PATCH.
@@ -751,7 +752,7 @@
       return (
         `<label class="craft-chip" data-disc="${escapeHtml(d)}" data-on="${on ? '1' : '0'}">` +
         `<input type="checkbox" class="craft-pref" value="${escapeHtml(d)}"${on ? ' checked' : ''}>` +
-        `${escapeHtml(d)}</label>`
+        `${escapeHtml(window.OTB.disciplineLabel(d))}</label>`
       );
     }).join('');
   }

package/modules/lifecycle/help-requests.js

@@ -20,10 +20,10 @@ const { pool } = require('../../src/module-api');
 // 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']);
-const CRAFT_TO_DISCIPLINE = Object.freeze({ artist: 'artist', ideator: 'ideator', builder: 'engineer' });
+const HELP_CRAFTS = Object.freeze(['artist', 'builder', 'ideator', 'ui']);
+const CRAFT_TO_DISCIPLINE = Object.freeze({ artist: 'artist', ideator: 'ideator', builder: 'engineer', ui: 'ui' });
 
-const DISCIPLINE_TO_CRAFT = Object.freeze({ artist: 'artist', ideator: 'ideator', engineer: 'builder' });
+const DISCIPLINE_TO_CRAFT = Object.freeze({ artist: 'artist', ideator: 'ideator', engineer: 'builder', ui: 'ui' });
 
 function helpCrafts() { return [...HELP_CRAFTS]; }
 function disciplineForCraft(craft) { return CRAFT_TO_DISCIPLINE[craft] || null; }

package/modules/lifecycle/migrations/lifecycle_006_help_requests_ui_craft.sql

@@ -0,0 +1,38 @@
+-- lifecycle_006_help_requests_ui_craft.sql — the `ui` craft becomes addressable in
+-- a help request (task 1003487, the routing half of goal 1000025's UI-reachability
+-- pair).
+--
+-- WHY THIS MIGRATION EXISTS AT ALL. lifecycle_004 fixed the craft vocabulary to
+-- ADR 0174's three (artist, builder, ideator) in a CHECK. `ui` became a real
+-- discipline later (migration 176 widened `builders.preferred_disciplines`, and
+-- discipline-modes.json routes a ui task to /design), and task 1003487 makes it
+-- selectable everywhere a builder chooses work. Every OTHER surface inherits that
+-- automatically because it validates against enabledDisciplines() at run time —
+-- this one does not, because a CHECK is compiled into the table. Without this the
+-- app would accept a help request addressed to `ui` (helpCrafts() now offers it)
+-- and Postgres would reject the INSERT, which is the worst shape of all: a
+-- constraint violation surfacing as a 500 on a feature that reads as supported.
+--
+-- THE VOCABULARY SEAM IS UNCHANGED. `builders.preferred_disciplines` spells the
+-- engineering craft 'engineer' while a help request spells it 'builder'; `ui` is
+-- spelled the same on both sides, so it simply joins the list. help-requests.js
+-- stays the single place that knows the mapping (CRAFT_TO_DISCIPLINE /
+-- DISCIPLINE_TO_CRAFT), and craftMapSql() generates its SQL CASE from that same
+-- object — so nothing here needs to restate it.
+--
+-- SAFE TO RE-RUN. Dropping by name and re-adding is idempotent in effect; existing
+-- rows all carry one of the three older values (or NULL) and satisfy the wider
+-- CHECK, so the ADD VALIDATE cannot fail on live data. No data is rewritten.
+
+ALTER TABLE lifecycle_help_requests
+  DROP CONSTRAINT IF EXISTS lifecycle_help_requests_craft_chk;
+
+ALTER TABLE lifecycle_help_requests
+  ADD CONSTRAINT lifecycle_help_requests_craft_chk
+    CHECK (needs_craft IS NULL OR needs_craft IN ('artist', 'builder', 'ideator', 'ui'));
+
+COMMENT ON COLUMN lifecycle_help_requests.needs_craft IS
+  'The craft this request is addressed to: ADR 0174''s three (artist, builder, ideator) plus ui, which the ui-design module contributes as a discipline (task 1003487). helpCrafts() in modules/lifecycle/help-requests.js is the single place that knows this vocabulary and its spelling seam with builders.preferred_disciplines.';
+
+INSERT INTO schema_migrations (version) VALUES ('lifecycle_006_help_requests_ui_craft')
+ON CONFLICT (version) DO NOTHING;

package/modules/lifecycle/module.json

@@ -22,7 +22,8 @@
       "recommendations",
       "closeness",
       "visuals",
-      "kickoff-seed"
+      "kickoff-seed",
+      "rot"
     ],
     "pollers": [
       "publish-reconciler"