@bakers-build/addon-bakers-ui 0.1.2-next.93 → 0.2.0

package/dist/src/Entity/ticket/Component/edit-form/index.js

@@ -58,7 +58,7 @@ const WARNING_INDENT = 2;
  *  silently left unwritten, so the accepted spelling has to be on screen. */
 const LEGEND = 'Assignee = human ownership · Reviewers = named reviewers · Conductor = who works it next · ' +
     'Estimate/Spent = accounted time, not the run footprint (1d 2h 30m, 90m, or a bare number as minutes) · ' +
-    'Parent = optional parent ticket · Labels = multi-select from bb_labels · ' +
+    'Parent = optional parent ticket · Labels = multi-select from label · ' +
     'Cancel ticket abandons a non-terminal ticket (Esc closes and writes nothing)';
 /**
  * A block of chrome prose, wrapped so the frame never has to clip it.

package/dist/src/Entity/ticket/Component/ticket-detail/index.js

@@ -43,12 +43,15 @@ function headerLineNodes(id, content, fg) {
     }));
 }
 export function ticketHeaderTree(document, identifier, title, lastRow, labels) {
-    // One compact meta line — state · assignee · labels — under the title. The
+    // One compact meta line — state · assignee · type · recipe · labels — under
+    // the title. The
     // full set (created by, branch, …) lives in the Overview sidebar, so the
     // header stays two lines rather than five. Empty fields drop out.
     const meta = [
         headerState(document),
         headerAssignee(document, labels),
+        termName(document, 'ticket_type', 'bb_term--type'),
+        termName(document, 'recipe', 'bb_term--recipe'),
         headerLabels(document),
     ]
         .filter((part) => part !== '' && part !== '—')
@@ -513,7 +516,18 @@ function typedCommentLines(document, type) {
 }
 /** The `bb_term` label names of the ticket, resolved include → uuid (D4/D8). */
 function labelNames(document) {
-    return toManyIds(document, 'labels').map((id) => asString(included(document, 'bb_term--bb_labels', id)?.attributes?.name) ?? id);
+    return toManyIds(document, 'labels').map((id) => asString(included(document, 'bb_term--label', id)?.attributes?.name) ??
+        id);
+}
+/**
+ * A single-valued `bb_term` relationship's name (BAKERS-17 `ticket_type` /
+ * `recipe`), resolved include → uuid like the labels; `''` when unset.
+ */
+function termName(document, name, type) {
+    const id = relId(document, name);
+    if (id === null)
+        return '';
+    return asString(included(document, type, id)?.attributes?.name) ?? id;
 }
 /**
  * The ticket's labels as ONE row of text — the header box's labels row (AC-8) and
@@ -669,6 +683,15 @@ export function detailSections(document, labels, nowSeconds = 0, baseUrl) {
         heading: 'Labels',
         lines: labelNames(document).length ? labelNames(document) : ['No labels.'],
     });
+    // BAKERS-17: Type and Recipe sit beside Labels, for the same reason.
+    sections.push({
+        heading: 'Type',
+        lines: [termName(document, 'ticket_type', 'bb_term--type') || 'No type.'],
+    });
+    sections.push({
+        heading: 'Recipe',
+        lines: [termName(document, 'recipe', 'bb_term--recipe') || 'No recipe.'],
+    });
     // BB-678: the upstream ticket this one was imported from — above `Parent`,
     // matching the interactive Related pane's row order.
     sections.push({ heading: 'Source', lines: sourceLines(document) });

package/dist/src/Entity/ticket/Data/detail.d.ts

@@ -16,8 +16,10 @@ import type { DropshClient, TicketDetailDocument } from '../../../types.js';
  * BB-255 added `parent_id,labels` for the same reason: the Parent row (AC-3)
  * and the header box's labels row (AC-8) would otherwise be raw uuids. Both were
  * re-measured live on BB-255 — `labels` sideloads
- * `bb_term--bb_labels` carrying `name`, and `parent_id` is `{data: null}` on
- * a parentless ticket. The `runs` include already ships each run's FULL attribute
+ * `bb_term--label` carrying `name`, and `parent_id` is `{data: null}` on
+ * a parentless ticket. BAKERS-17 added `ticket_type,recipe` for the header's
+ * type and recipe names, sideloading `bb_term--type` / `bb_term--recipe`.
+ * The `runs` include already ships each run's FULL attribute
  * set, which is why the Runs tab and the run detail screen add no request at all.
  *
  * `parent_id` serves BB-252 as well: after a save from the ticket list, this

package/dist/src/Entity/ticket/Data/detail.js

@@ -15,8 +15,10 @@
  * BB-255 added `parent_id,labels` for the same reason: the Parent row (AC-3)
  * and the header box's labels row (AC-8) would otherwise be raw uuids. Both were
  * re-measured live on BB-255 — `labels` sideloads
- * `bb_term--bb_labels` carrying `name`, and `parent_id` is `{data: null}` on
- * a parentless ticket. The `runs` include already ships each run's FULL attribute
+ * `bb_term--label` carrying `name`, and `parent_id` is `{data: null}` on
+ * a parentless ticket. BAKERS-17 added `ticket_type,recipe` for the header's
+ * type and recipe names, sideloading `bb_term--type` / `bb_term--recipe`.
+ * The `runs` include already ships each run's FULL attribute
  * set, which is why the Runs tab and the run detail screen add no request at all.
  *
  * `parent_id` serves BB-252 as well: after a save from the ticket list, this
@@ -52,6 +54,8 @@ export function loadTicketDetail(client, ticketId, includes = [
     'assignee_user_id',
     'parent_id',
     'labels',
+    'ticket_type',
+    'recipe',
     'blocked_by',
     'owner_user_id',
     'reviewers',

package/dist/src/Entity/ticket/Data/query.js

@@ -21,15 +21,14 @@ export { CLOSED_FILTER_VALUES, cycleValue } from '../../cycle.js';
 import { LIST_PAGE_SIZE as PAGE_SIZE } from '../../cycle.js';
 import { TICKET_CONDUCTOR_INCLUDE_FIELDS, TICKET_LIST_FIELDS, } from './tickets.js';
 // Ticket states from web/modules/custom/bb_core/bb_core.workflows.yml
-// (feature/bug/chore workflows) plus the import/backlog states seen on tickets.
+// (the `bb_work` workflow) plus the import/backlog states seen on tickets.
 // Hardcoded so the cycle is deterministic and independent of the loaded page.
 export const STATE_FILTER_VALUES = [
     'triage',
     'backlog',
     'todo',
-    'spec',
-    'diagnose',
-    'coding',
+    'plan',
+    'working',
     'review',
     'done',
     'cancelled',

package/dist/src/Entity/ticket/Data/store.js

@@ -19,8 +19,11 @@ const ticketKey = (id) => dataKey(`ticket/${id}`);
  * `includes` (`ticket-detail.ts:23`) without joining this list. Every include
  * a screen's `includes` can name belongs here too.
  */
+// What the header box reads on every tab (labels, and BAKERS-17's type and
+// recipe), so every ticket view loads it whatever its own includes.
+const headerIncludes = ['labels', 'ticket_type', 'recipe'];
 const allIncludes = [
-    'labels',
+    ...headerIncludes,
     'parent_id',
     'blocked_by',
     'conductor_id',
@@ -88,7 +91,9 @@ export function readTicket(context, fallback = {}) {
 }
 export function ticketLoaded(context, includes) {
     const id = context.params?.ticketId;
-    return (!!id && (context.store?.has(ticketKey(id), [...includes, 'labels']) ?? true));
+    return (!!id &&
+        (context.store?.has(ticketKey(id), [...includes, ...headerIncludes]) ??
+            true));
 }
 export function loadTicketView(context, includes) {
     const supplied = context.contexts?.has(ticketDetailInputContext)
@@ -108,7 +113,7 @@ export function loadTicketView(context, includes) {
     const key = ticketKey(id);
     if (supplied && !store.get(key))
         store.set(key, supplied, allIncludes);
-    return store.load(key, [...includes, 'labels'], async (missing) => {
+    return store.load(key, [...includes, ...headerIncludes], async (missing) => {
         if (!context.services) {
             if (supplied)
                 return supplied;

package/dist/src/Entity/ticket/Data/workflow.js

@@ -7,9 +7,9 @@
 // The declaration stays because the `workflow` ATTRIBUTE stays (spec F4).
 /** The single source of truth, in the create form picker's order. */
 export const WORKFLOW_KINDS = [
-    { id: 'bb_feature', label: 'feature' },
-    { id: 'bb_bug', label: 'bug' },
-    { id: 'bb_chore', label: 'chore' },
+    // BAKERS-17: one workflow for every work ticket; feature/bug/chore is the
+    // ticket's `ticket_type` term now, not its workflow.
+    { id: 'bb_work', label: 'work' },
 ];
 /** The picker's `{id, label}` list — what the create form's `workflow` field offers. */
 export const WORKFLOW_OPTIONS = WORKFLOW_KINDS.map((k) => ({

package/dist/src/Entity/ticket/Data/write.d.ts

@@ -33,7 +33,7 @@ export declare const TICKET_DESCRIPTION_FORMAT = "bb_rich";
  *   1. NOTHING server-owned is written — no `state` (the server lands the
  *      ticket in the workflow's first state), no `identifier`, no `number`, no
  *      `branch_name`, no `base_branch`. Acceptance criterion 5 is satisfied by
- *      OMISSION, which is also what `@bakers-build/create-ticket` does.
+ *      OMISSION, which is also what `@bakers-build/bb-create-ticket` does.
  *   2. A relationship with nothing picked is OMITTED, not sent as an explicit
  *      `null`. A create has nothing to unset, so `null` would carry no
  *      information a missing key does not — the exact opposite of the PATCH in

package/dist/src/Entity/ticket/Data/write.js

@@ -42,7 +42,7 @@ const one = (type, id) => id ? { data: { type, id } } : undefined;
  *   1. NOTHING server-owned is written — no `state` (the server lands the
  *      ticket in the workflow's first state), no `identifier`, no `number`, no
  *      `branch_name`, no `base_branch`. Acceptance criterion 5 is satisfied by
- *      OMISSION, which is also what `@bakers-build/create-ticket` does.
+ *      OMISSION, which is also what `@bakers-build/bb-create-ticket` does.
  *   2. A relationship with nothing picked is OMITTED, not sent as an explicit
  *      `null`. A create has nothing to unset, so `null` would carry no
  *      information a missing key does not — the exact opposite of the PATCH in
@@ -61,10 +61,16 @@ export function buildTicketCreateBody(payload, projectId) {
     const conductor = one('bb_conductor--bb_conductor', payload.conductor?.id);
     if (conductor)
         relationships.conductor_id = conductor;
+    const ticketType = one('bb_term--type', payload.ticketType?.id);
+    if (ticketType)
+        relationships.ticket_type = ticketType;
+    const recipe = one('bb_term--recipe', payload.recipe?.id);
+    if (recipe)
+        relationships.recipe = recipe;
     if (payload.labels.length > 0) {
         relationships.labels = {
             data: payload.labels.map((l) => ({
-                type: 'bb_term--bb_labels',
+                type: 'bb_term--label',
                 id: l.id,
             })),
         };

package/dist/src/Entity/ticket/Form/create-data.js

@@ -49,7 +49,18 @@ const toOption = (row) => ({ id: row.id, label: row.label });
  * the data service returns terms for whatever purpose, and which of the entity
  * type's vocabularies a given widget wants is the widget's business.
  */
-const LABEL_VOCABULARY = 'bb_labels';
+const LABEL_VOCABULARY = 'label';
+/** The vocabularies of the single-valued `ticket_type` / `recipe` (BAKERS-17). */
+const TYPE_VOCABULARY = 'type';
+const RECIPE_VOCABULARY = 'recipe';
+/** A vocabulary's terms as one option bag, under the bag key `bag`. */
+const termSource = (client, bag, vocabulary) => ({
+    bag,
+    async load() {
+        const outcome = await listTerms(client, vocabulary);
+        return { options: outcome.rows.map(toOption), error: outcome.error };
+    },
+});
 /**
  * The `conductors` option source for one (possibly absent) project.
  *
@@ -145,13 +156,9 @@ export function createFormSources(client, hints = {}) {
             ownerUserId,
             ownConductorMachineId,
         }),
-        labels: {
-            bag: 'labels',
-            async load() {
-                const outcome = await listTerms(client, LABEL_VOCABULARY);
-                return { options: outcome.rows.map(toOption), error: outcome.error };
-            },
-        },
+        ticketType: termSource(client, 'ticketTypes', TYPE_VOCABULARY),
+        recipe: termSource(client, 'recipes', RECIPE_VOCABULARY),
+        labels: termSource(client, 'labels', LABEL_VOCABULARY),
     };
     // No project in scope ⇒ NO source, so the bag stays absent rather than empty:
     // "nothing can be offered" and "searched, nothing matched" are different
@@ -183,6 +190,8 @@ export async function composeCreateFormOptions(sources) {
         users: [],
         reviewers: [],
         conductors: [],
+        ticketTypes: [],
+        recipes: [],
         labels: [],
         workflows: WORKFLOW_OPTIONS,
         // Spread over the defaults, so a bag with no source stays ABSENT (D8) while

package/dist/src/Entity/ticket/Form/create.d.ts

@@ -14,6 +14,8 @@ export interface CreateOptionErrors {
     users?: string | undefined;
     reviewers?: string | undefined;
     conductors?: string | undefined;
+    ticketTypes?: string | undefined;
+    recipes?: string | undefined;
     labels?: string | undefined;
     parents?: string | undefined;
     workflows?: string | undefined;
@@ -45,6 +47,10 @@ export interface CreateFormOptions {
     users: Option[];
     reviewers: Option[];
     conductors: Option[];
+    /** The `type` vocabulary, for the single-valued `ticket_type` (BAKERS-17). */
+    ticketTypes: Option[];
+    /** The `recipe` vocabulary, for the single-valued `recipe` (BAKERS-17). */
+    recipes: Option[];
     labels: Option[];
     workflows: Option[];
     /**
@@ -85,7 +91,7 @@ export type FieldDef<Id extends string = string> = Omit<FieldDecl, 'id'> & {
  */
 export declare const AGENT_ACTION_ID = "submit";
 export declare const DIRECT_ACTION_ID = "direct";
-export type CreateFieldId = 'project' | 'title' | 'description' | 'parent' | 'assignee' | 'reviewers' | 'conductor' | 'labels' | 'workflow' | 'template' | 'submit' | 'direct';
+export type CreateFieldId = 'project' | 'title' | 'description' | 'parent' | 'assignee' | 'reviewers' | 'conductor' | 'ticketType' | 'recipe' | 'labels' | 'workflow' | 'template' | 'submit' | 'direct';
 /** What the form HOLDS. `active`/`cursor` are the kernel's and must not appear. */
 export interface CreateValues {
     /**
@@ -114,6 +120,8 @@ export interface CreateValues {
     assignee: string | null;
     reviewers: ReadonlySet<string>;
     conductor: string | null;
+    ticketType: string | null;
+    recipe: string | null;
     labels: ReadonlySet<string>;
     workflow: string | null;
     /** The picked ticket template's uuid, or null. Never remembered. */
@@ -134,6 +142,8 @@ export interface CreateFormPayload {
     assignee: Option | null;
     reviewers: Option[];
     conductor: Option | null;
+    ticketType: Option | null;
+    recipe: Option | null;
     labels: Option[];
     /**
      * The ticket the new one goes under, or null when none was picked (AC-7).
@@ -146,9 +156,9 @@ export interface CreateFormPayload {
 export declare const optionFor: (list: Option[], id: string | null) => Option | null;
 /**
  * The declaration used whenever a project is already in scope (unchanged,
- * BB-664 AC-8). No field carries a function. Exactly ONE select is
- * `clearable` — the conductor (BB-309 D2); every other one cycles over real
- * options only, exactly as before BB-233.
+ * BB-664 AC-8). No field carries a function. The `clearable` selects are the
+ * conductor (BB-309 D2) and the template, type and recipe, which open empty;
+ * every other one cycles over real options only, exactly as before BB-233.
  */
 export declare const CREATE_FORM: {
     fields: FieldDecl[];
@@ -192,9 +202,10 @@ export type CreateFormState = FormState<CreateValues>;
  * value shape, so renaming a field breaks the build instead of silently
  * dropping it out of the memory.
  *
- * `workflow` is NOT here, deliberately. A ticket type is a per-ticket decision,
- * and a silently retained `bb_bug` on the next feature ticket is a wrong
- * value nobody looks at (D5). The parent contributes BOTH of its keys, because
+ * `workflow`, `ticketType` and `recipe` are NOT here, deliberately. They are
+ * per-ticket decisions, and a silently retained `bug` type on the next feature
+ * ticket is a wrong value nobody looks at (D5). The parent contributes BOTH
+ * of its keys, because
  * an autocomplete owns two and `apply` never produces one without the other
  * (D4).
  */

package/dist/src/Entity/ticket/Form/create.js

@@ -85,6 +85,10 @@ const sharedFields = (f) => [
     // from `listOf(options)[0]` regardless of `clearable`, and `ownFirst` in
     // `create-data.ts` puts the machine's own conductor there.
     f.select('conductor', 'Conductor', { from: 'conductors', clearable: true }),
+    // Clearable and opened EMPTY by the screen, like the template: a type or
+    // recipe is chosen, never preselected.
+    f.select('ticketType', 'Type', { from: 'ticketTypes', clearable: true }),
+    f.select('recipe', 'Recipe', { from: 'recipes', clearable: true }),
     f.multi('labels', 'Labels', { from: 'labels' }),
     f.select('workflow', 'Workflow', { from: 'workflows' }),
     // A template replaces the ordinary create, so it sits right above
@@ -103,14 +107,16 @@ const toCreatePayload = (v, o) => ({
     assignee: optionFor(o.users, v.assignee),
     reviewers: (o.reviewers ?? []).filter((x) => v.reviewers.has(x.id)),
     conductor: optionFor(o.conductors, v.conductor),
+    ticketType: optionFor(o.ticketTypes, v.ticketType),
+    recipe: optionFor(o.recipes, v.recipe),
     labels: o.labels.filter((x) => v.labels.has(x.id)),
     parent: parentFor(o.parents ?? [], v.parent),
 });
 /**
  * The declaration used whenever a project is already in scope (unchanged,
- * BB-664 AC-8). No field carries a function. Exactly ONE select is
- * `clearable` — the conductor (BB-309 D2); every other one cycles over real
- * options only, exactly as before BB-233.
+ * BB-664 AC-8). No field carries a function. The `clearable` selects are the
+ * conductor (BB-309 D2) and the template, type and recipe, which open empty;
+ * every other one cycles over real options only, exactly as before BB-233.
  */
 export const CREATE_FORM = declareForm({
     fields: sharedFields,
@@ -177,6 +183,8 @@ const NO_OPTIONS = {
     users: [],
     reviewers: [],
     conductors: [],
+    ticketTypes: [],
+    recipes: [],
     labels: [],
     workflows: [],
 };

package/dist/src/Entity/ticket/Form/edit-data.js

@@ -4,7 +4,8 @@
 // this module knows both sides and therefore owns the mapping to `Option` and this
 // popup's policy: read write-client-first for users/conductors, drop Anonymous, filter
 // conductors to the ticket's project, put liveness in the label, load the
-// `bb_labels` vocabulary for the Labels multi-select, and reorder ONLY the
+// `label` vocabulary for the Labels multi-select (and `type`/`recipe` for the
+// Type and Recipe selects), and reorder ONLY the
 // conductor ring owner-first (BB-460) — the assignee ring is unordered because
 // the popup preselects the ticket's current assignee. Each rule has exactly one
 // user, so each is written once, here, beside the create adapter it differs from.
@@ -17,7 +18,10 @@ import { listUsersPreferringWrite } from '../../user/Data/users.js';
 import { ownFirst } from './create-data.js';
 import { loadReviewerOptions } from './reviewer-options.js';
 /** The vocabulary this popup offers as its labels (BB-360 D9 / D11). */
-const LABEL_VOCABULARY = 'bb_labels';
+const LABEL_VOCABULARY = 'label';
+/** The vocabularies of the single-valued `ticket_type` / `recipe` (BAKERS-17). */
+const TYPE_VOCABULARY = 'type';
+const RECIPE_VOCABULARY = 'recipe';
 /**
  * uid 0 is Drupal's Anonymous and never a valid human assignee. A row whose uid never
  * loaded is `undefined` — NOT Anonymous — and stays.
@@ -37,11 +41,11 @@ const withStatusSuffix = (c) => ({
     label: c.status ? `${c.label} (${c.status})` : c.label,
 });
 export async function loadEditFormOptions(clients, hints = {}) {
-    // Labels have no write-preferring helper: terms are not write-gated the way
+    // Terms have no write-preferring helper: they are not write-gated the way
     // assignees/conductors are. Fail-open to [] when the read client is absent or
     // the vocabulary throws (D11).
-    const labelsPromise = clients.read
-        ? listTerms(clients.read, LABEL_VOCABULARY).then((outcome) => outcome.rows.map((t) => ({ id: t.id, label: t.label })), () => [])
+    const termsPromise = (vocabulary) => clients.read
+        ? listTerms(clients.read, vocabulary).then((outcome) => outcome.rows.map((t) => ({ id: t.id, label: t.label })), () => [])
         : Promise.resolve([]);
     const reviewerClient = clients.write ?? clients.read;
     const reviewersPromise = reviewerClient
@@ -50,16 +54,20 @@ export async function loadEditFormOptions(clients, hints = {}) {
             options: [],
             error: 'no client — reviewers cannot be loaded',
         });
-    const [users, conductors, labels, reviewers] = await Promise.all([
+    const [users, conductors, ticketTypes, recipes, labels, reviewers] = await Promise.all([
         listUsersPreferringWrite(clients),
         listConductorsPreferringWrite(clients),
-        labelsPromise,
+        termsPromise(TYPE_VOCABULARY),
+        termsPromise(RECIPE_VOCABULARY),
+        termsPromise(LABEL_VOCABULARY),
         reviewersPromise,
     ]);
     return {
         users: excludeAnonymous(users).map((u) => ({ id: u.id, label: u.label })),
         reviewers: reviewers.options,
         conductors: ownFirst(inProject(conductors, hints.projectId).filter((c) => c.active), (c) => hints.ownerUserId !== undefined && c.ownerUserId === hints.ownerUserId).map(withStatusSuffix),
+        ticketTypes,
+        recipes,
         labels,
         ...(reviewers.error === undefined
             ? {}

package/dist/src/Entity/ticket/Form/edit.d.ts

@@ -1,7 +1,7 @@
 import { type FormState } from '../../../Form/index.js';
 import type { TicketDetailDocument } from '../../../types.js';
 import type { FieldDef, Option } from './create.js';
-export type EditFieldId = 'assignee' | 'reviewers' | 'conductor' | 'estimate' | 'spent' | 'parent' | 'labels' | 'submit' | 'cancelTicket';
+export type EditFieldId = 'assignee' | 'reviewers' | 'conductor' | 'estimate' | 'spent' | 'parent' | 'ticketType' | 'recipe' | 'labels' | 'submit' | 'cancelTicket';
 /**
  * BB-313 / BB-360 — the ONE lifecycle move this popup offers, as a named
  * constant.
@@ -11,10 +11,9 @@ export type EditFieldId = 'assignee' | 'reviewers' | 'conductor' | 'estimate' |
  * `cancelled`, so no served fact carries the cancel edge. The precedent is
  * `STATE_FILTER_VALUES` in `Data/query.ts`, hardcoded for the same reason.
  *
- * One constant serves every ticket workflow because in ALL of them
- * (`bb_feature`, `bb_bug`, `bb_chore`, `bb_deployment`,
- * `bb_verification`) `cancel.from` is exactly the set of non-terminal states —
- * so "non-terminal" and "the workflow permits cancelling" are the same
+ * One constant serves every ticket workflow because in the ticket workflow
+ * (`bb_work`) `cancel.from` is exactly the set of non-terminal states — so
+ * "non-terminal" and "the workflow permits cancelling" are the same
  * predicate, and no workflow id is needed to tell them apart.
  */
 export declare const CANCELLED_STATE = "cancelled";
@@ -29,7 +28,7 @@ export declare const CANCEL_TICKET_ACTION_ID = "cancelTicket";
  * The states no transition leaves, in every ticket workflow.
  *
  * The server's own definition (`TypeWorkflows::isTerminal` — "a state no
- * transition leaves") evaluates to exactly this pair for all five workflows.
+ * transition leaves") evaluates to exactly this pair for `bb_work`.
  */
 export declare const TERMINAL_TICKET_STATES: ReadonlySet<string>;
 /** The option lists the popup offers (loaded by `loadEditFormOptions`). */
@@ -37,6 +36,10 @@ export interface EditFormOptions {
     users: Option[];
     reviewers: Option[];
     conductors: Option[];
+    /** The `type` vocabulary, for the single-valued `ticket_type` (BAKERS-17). */
+    ticketTypes: Option[];
+    /** The `recipe` vocabulary, for the single-valued `recipe` (BAKERS-17). */
+    recipes: Option[];
     labels: Option[];
     errors?: {
         reviewers?: string | undefined;
@@ -63,6 +66,8 @@ interface EditValues {
     /** The PICKED parent's uuid, or null. `parentQuery` holds what was typed. */
     parent: string | null;
     parentQuery: string;
+    ticketType: string | null;
+    recipe: string | null;
     labels: ReadonlySet<string>;
 }
 /** The payload of the ordinary Save PATCH (BB-233 Decision 2). */
@@ -81,6 +86,18 @@ export interface EditFormPayload {
                 id: string;
             } | null;
         };
+        ticket_type: {
+            data: {
+                type: string;
+                id: string;
+            } | null;
+        };
+        recipe: {
+            data: {
+                type: string;
+                id: string;
+            } | null;
+        };
         labels: {
             data: {
                 type: string;

package/dist/src/Entity/ticket/Form/edit.js

@@ -21,10 +21,9 @@ import { PARENT_PAGE_SIZE } from '../Data/parents.js';
  * `cancelled`, so no served fact carries the cancel edge. The precedent is
  * `STATE_FILTER_VALUES` in `Data/query.ts`, hardcoded for the same reason.
  *
- * One constant serves every ticket workflow because in ALL of them
- * (`bb_feature`, `bb_bug`, `bb_chore`, `bb_deployment`,
- * `bb_verification`) `cancel.from` is exactly the set of non-terminal states —
- * so "non-terminal" and "the workflow permits cancelling" are the same
+ * One constant serves every ticket workflow because in the ticket workflow
+ * (`bb_work`) `cancel.from` is exactly the set of non-terminal states — so
+ * "non-terminal" and "the workflow permits cancelling" are the same
  * predicate, and no workflow id is needed to tell them apart.
  */
 export const CANCELLED_STATE = 'cancelled';
@@ -39,7 +38,7 @@ export const CANCEL_TICKET_ACTION_ID = 'cancelTicket';
  * The states no transition leaves, in every ticket workflow.
  *
  * The server's own definition (`TypeWorkflows::isTerminal` — "a state no
- * transition leaves") evaluates to exactly this pair for all five workflows.
+ * transition leaves") evaluates to exactly this pair for `bb_work`.
  */
 export const TERMINAL_TICKET_STATES = new Set([
     'done',
@@ -51,7 +50,7 @@ const linkage = (type, id) => ({
 });
 /** Multi-value term linkage for labels (always present on ordinary Save). */
 const labelsLinkage = (ids) => ({
-    data: [...ids].map((id) => ({ type: 'bb_term--bb_labels', id })),
+    data: [...ids].map((id) => ({ type: 'bb_term--label', id })),
 });
 /**
  * The two time attributes of the PATCH, in seconds.
@@ -89,7 +88,8 @@ const timeAttributes = (v) => {
  *
  * BOTH assignment selects are `clearable`: AC-4 requires REMOVING an assignment,
  * not only changing it, so `null` is a real position in each cycle. Parent is
- * clearable for the same reason (D7). Labels always PATCH the full selected set,
+ * clearable for the same reason (D7), and so are Type and Recipe. Labels
+ * always PATCH the full selected set,
  * including empty.
  *
  * Ordinary Save NEVER includes `attributes.state` — a self-transition is not a
@@ -119,6 +119,8 @@ const declareEditForm = (savable, cancellable) => declareForm({
             absentNote: '(no project context — open a project to pick a parent)',
             pageSize: PARENT_PAGE_SIZE,
         }),
+        f.select('ticketType', 'Type', { from: 'ticketTypes', clearable: true }),
+        f.select('recipe', 'Recipe', { from: 'recipes', clearable: true }),
         f.multi('labels', 'Labels', { from: 'labels' }),
         ...(savable ? [f.action('Save', 'submit')] : []),
         ...(cancellable
@@ -131,6 +133,8 @@ const declareEditForm = (savable, cancellable) => declareForm({
         relationships: {
             assignee_user_id: linkage('user--user', v.assignee),
             conductor_id: linkage('bb_conductor--bb_conductor', v.conductor),
+            ticket_type: linkage('bb_term--type', v.ticketType),
+            recipe: linkage('bb_term--recipe', v.recipe),
             labels: labelsLinkage(v.labels),
             parent_id: linkage('bb_ticket--bb_ticket', v.parent),
             ...(v.reviewersLoaded || v.reviewers.size > 0
@@ -191,6 +195,8 @@ export const EMPTY_EDIT_FORM_OPTIONS = {
     users: [],
     reviewers: [],
     conductors: [],
+    ticketTypes: [],
+    recipes: [],
     labels: [],
 };
 const relId = (document, name) => {
@@ -266,6 +272,8 @@ export function initialEditForm(document) {
         spent: timeValue(document, 'time_spent'),
         parent,
         parentQuery: parentQueryFromDocument(document, parent),
+        ticketType: relId(document, 'ticket_type'),
+        recipe: relId(document, 'recipe'),
         labels: labelIds(document),
     });
 }

package/dist/src/Entity/ticket/Screen/create-ticket-form.d.ts

@@ -73,8 +73,9 @@ export declare class CreateTicketFormScreen extends AsyncModalScreen<CreateFormO
     enter(context: ScreenContext): void;
     protected didLoad(options: CreateFormOptions): void;
     /**
-     * A new ticket's form. The template is forced to none: a select opens on its
-     * first option, and a template must be chosen, never preselected.
+     * A new ticket's form. The template, type and recipe are forced to none: a
+     * select opens on its first option, and each must be chosen, never
+     * preselected.
      */
     private freshForm;
     /** The template picked in the form, or null. */

package/dist/src/Entity/ticket/Screen/create-ticket-form.js

@@ -124,6 +124,8 @@ export class CreateTicketFormScreen extends AsyncModalScreen {
             users: [],
             reviewers: [],
             conductors: [],
+            ticketTypes: [],
+            recipes: [],
             labels: [],
             workflows: [],
             errors: {
@@ -171,13 +173,16 @@ export class CreateTicketFormScreen extends AsyncModalScreen {
         this.startOptionLoader();
     }
     /**
-     * A new ticket's form. The template is forced to none: a select opens on its
-     * first option, and a template must be chosen, never preselected.
+     * A new ticket's form. The template, type and recipe are forced to none: a
+     * select opens on its first option, and each must be chosen, never
+     * preselected.
      */
     freshForm(options) {
         return this.declaration().initial(options, {
             ...(this.remembered ?? {}),
             template: null,
+            ticketType: null,
+            recipe: null,
         });
     }
     /** The template picked in the form, or null. */

package/dist/src/Entity/ticket/Screen/ticket-detail.js

@@ -5,6 +5,8 @@ import { TicketContentScreen } from './ticket-content-screen.js';
 export { ticketDetailInputContext } from '../Data/input.js';
 const INCLUDES = [
     'labels',
+    'ticket_type',
+    'recipe',
     'parent_id',
     'blocked_by',
     'conductor_id',

package/dist/src/Entity/ticket/Screen/ticket-filter-bar.js

@@ -66,9 +66,8 @@ export class TicketFilterBar {
                     'triage',
                     'backlog',
                     'todo',
-                    'spec',
-                    'diagnose',
-                    'coding',
+                    'plan',
+                    'working',
                     'review',
                     'done',
                     'cancelled',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bakers-build/addon-bakers-ui",
-  "version": "0.1.2-next.93",
+  "version": "0.2.0",
   "description": "bakers.build TUI: interactive terminal UI (dashboard, projects, tickets) as a dropsh `tui` renderer plugin.",
   "type": "module",
   "license": "MIT",
@@ -29,7 +29,7 @@
     "zustand": "^5.0.15"
   },
   "peerDependencies": {
-    "@bakers-build/core": "^0.1.2-next.93",
-    "@bakers-build/message": "^0.1.2-next.93"
+    "@bakers-build/core": "^0.2.0",
+    "@bakers-build/message": "^0.2.0"
   }
 }