@anchrd/intel-contract 0.26.0 → 0.28.0

package/dist/contract/board.d.ts

@@ -9,10 +9,23 @@ import { z } from "zod";
  * draws first.
  */
 export declare const ARCHIVE_COLUMN_ID = "archived";
+/**
+ * What a colour picker starts on for a column that has none (#725).
+ *
+ * ⚠️ **Here rather than in the browser package, and that is not tidiness.** The token linter refuses
+ * a hard-coded hex in `packages/ui`, and it is right to: a colour written into a component bypasses
+ * the theme. This one is not a theme colour, it is DATA — the value a person is about to choose
+ * from and the api writes as a default — so it belongs where both sides may read it, which is here.
+ *
+ * ⚠️ **It is the widget's starting point, never a written value.** `color` stays absent until
+ * somebody picks one, so opening the dialog does not repaint a board that predates colours.
+ */
+export declare const DEFAULT_COLUMN_COLOR = "#9ca3af";
 export declare const BoardColumn: z.ZodObject<{
     id: z.ZodString;
     title: z.ZodString;
     terminal: z.ZodDefault<z.ZodBoolean>;
+    color: z.ZodOptional<z.ZodString>;
 }, z.core.$strict>;
 export type BoardColumn = z.infer<typeof BoardColumn>;
 export declare const BoardTask: z.ZodObject<{
@@ -53,6 +66,7 @@ export declare const BoardView: z.ZodObject<{
         id: z.ZodString;
         title: z.ZodString;
         terminal: z.ZodDefault<z.ZodBoolean>;
+        color: z.ZodOptional<z.ZodString>;
     }, z.core.$strict>>;
     archiveVisible: z.ZodBoolean;
     tasks: z.ZodArray<z.ZodObject<{
@@ -76,6 +90,7 @@ export declare const BoardUpdateInput: z.ZodObject<{
         id: z.ZodString;
         title: z.ZodString;
         terminal: z.ZodDefault<z.ZodBoolean>;
+        color: z.ZodOptional<z.ZodString>;
     }, z.core.$strict>>;
     archiveVisible: z.ZodOptional<z.ZodBoolean>;
     idempotencyKey: z.ZodString;
@@ -130,5 +145,6 @@ export declare const BoardAssigneeList: z.ZodObject<{
         email: z.ZodEmail;
         isMachine: z.ZodBoolean;
     }, z.core.$strict>>;
+    more: z.ZodDefault<z.ZodNumber>;
 }, z.core.$strict>;
 export type BoardAssigneeList = z.infer<typeof BoardAssigneeList>;

package/dist/contract/board.js

@@ -13,6 +13,18 @@ import { IdempotencyKey, IntelId, IsoDateTime } from "./contract.js";
  * draws first.
  */
 export const ARCHIVE_COLUMN_ID = "archived";
+/**
+ * What a colour picker starts on for a column that has none (#725).
+ *
+ * ⚠️ **Here rather than in the browser package, and that is not tidiness.** The token linter refuses
+ * a hard-coded hex in `packages/ui`, and it is right to: a colour written into a component bypasses
+ * the theme. This one is not a theme colour, it is DATA — the value a person is about to choose
+ * from and the api writes as a default — so it belongs where both sides may read it, which is here.
+ *
+ * ⚠️ **It is the widget's starting point, never a written value.** `color` stays absent until
+ * somebody picks one, so opening the dialog does not repaint a board that predates colours.
+ */
+export const DEFAULT_COLUMN_COLOR = "#9ca3af";
 export const BoardColumn = z.strictObject({
     id: z.string().min(1).max(60).describe("Stable key stored on every task in this column."),
     title: z.string().min(1).max(80).describe("What the column is called on screen."),
@@ -20,6 +32,20 @@ export const BoardColumn = z.strictObject({
         .boolean()
         .default(false)
         .describe("Whether a task in this column counts as finished. More than one column may be."),
+    /**
+     * ⚠️ **The colour belongs to the COLUMN, never to the card** (#725, and #365 took the status dot
+     * off the card on purpose). A card is in a column; drawing the column's colour on it would be the
+     * same fact twice, and the second copy is the one that goes stale.
+     *
+     * A free value rather than a fixed palette (Jack's decision 2026-08-22). It only ever fills a
+     * DOT, so a badly chosen one is hard to see but makes nothing unreadable — which is what makes a
+     * free choice affordable here and would not make it affordable behind text.
+     */
+    color: z
+        .string()
+        .regex(/^#[0-9a-fA-F]{6}$/, "A colour is six hex digits behind a hash, like #6b7280.")
+        .optional()
+        .describe("The dot in front of this column's title, and in front of a linked task that sits in it. Six hex digits behind a hash. Absent means the reader's own default, so an older board is not repainted by this field appearing."),
 });
 // One card, as the board view needs it: everything to draw and sort by, and NOTHING from R2. The
 // body is fetched per task through `node_version_get` when somebody opens one.
@@ -210,7 +236,7 @@ export const BoardAssigneeSearchInput = z.strictObject({
     boardId: IntelId.describe("The board whose people to offer. Only those who can open this board appear, so the same query against two boards can give two different answers."),
     query: z
         .string()
-        .describe("What was typed. Under two characters the answer is empty rather than everybody: a single letter is a listing under a different name."),
+        .describe("What was typed. EMPTY names up to three people who reach this board, so a picker can open with suggestions instead of nothing. One character answers empty rather than everybody: a single letter is a listing under a different name, while an empty query asks for a bounded set this board already knows."),
 });
 // ⚠️ A DIFFERENT question from the one above, and deliberately not board-scoped. This one names
 // people who are ALREADY recorded on a card, so that a circle can carry initials instead of a raw
@@ -223,4 +249,14 @@ export const BoardAssigneeResolveInput = z.strictObject({
         .max(100)
         .describe("The ids to name. Ids that cannot be named are absent from the answer rather than reported, and more than a hundred is refused rather than silently shortened."),
 });
-export const BoardAssigneeList = z.strictObject({ items: z.array(BoardAssignee) });
+export const BoardAssigneeList = z.strictObject({
+    items: z.array(BoardAssignee),
+    /**
+     * ⚠️ **How many are left over, so the cap is visible rather than silent** (#757). Three suggestions
+     * that look like the whole list are worse than three that say "and 4 more": the first teaches the
+     * reader that nobody else exists.
+     *
+     * `0` on a search answer, where the cap is gate's own and this door does not own it.
+     */
+    more: z.number().int().min(0).default(0),
+});

package/dist/contract/node.d.ts

@@ -120,9 +120,31 @@ export declare const PurgeNodePreviewInput: z.ZodObject<{
     nodeId: z.ZodString;
 }, z.core.$strict>;
 export type PurgeNodePreviewInput = z.infer<typeof PurgeNodePreviewInput>;
+/**
+ * ⚠️ **A count is not an answer before a deletion that cannot be undone** (D71, #733). `totalItems`
+ * alone reads as "82 items" for a folder holding somebody's whole memory, and `destructive.md` asks
+ * for the number to be named BEFORE the confirmation — one step more precise is the difference
+ * between a number and something a person can decide on.
+ *
+ * `items` is capped, and the cap is visible rather than silent: `totalItems` keeps counting past it,
+ * so a caller can always say "and 40 more". A list of ten thousand rows would be an answer nobody
+ * reads and a response nobody can render.
+ */
 export declare const PurgeNodePreview: z.ZodObject<{
     inboundLinks: z.ZodNumber;
     totalItems: z.ZodNumber;
+    items: z.ZodArray<z.ZodObject<{
+        id: z.ZodString;
+        kind: z.ZodUnion<readonly [z.ZodEnum<{
+            folder: "folder";
+            document: "document";
+            table: "table";
+            attachment: "attachment";
+            board: "board";
+            task: "task";
+        }>, z.ZodLiteral<"flow">]>;
+        title: z.ZodString;
+    }, z.core.$strict>>;
 }, z.core.$strict>;
 export type PurgeNodePreview = z.infer<typeof PurgeNodePreview>;
 export declare const PurgeNodeResult: z.ZodObject<{

package/dist/contract/node.js

@@ -187,9 +187,27 @@ export const PurgeNodeInput = z.strictObject({
 export const PurgeNodePreviewInput = z.strictObject({
     nodeId: IntelId.describe("Archived node a purge would delete. Answers how many items would go with it and how many documents link to it from outside, and changes nothing. A node that is not archived is refused here for the same reason node_purge refuses it."),
 });
+/**
+ * ⚠️ **A count is not an answer before a deletion that cannot be undone** (D71, #733). `totalItems`
+ * alone reads as "82 items" for a folder holding somebody's whole memory, and `destructive.md` asks
+ * for the number to be named BEFORE the confirmation — one step more precise is the difference
+ * between a number and something a person can decide on.
+ *
+ * `items` is capped, and the cap is visible rather than silent: `totalItems` keeps counting past it,
+ * so a caller can always say "and 40 more". A list of ten thousand rows would be an answer nobody
+ * reads and a response nobody can render.
+ */
 export const PurgeNodePreview = z.strictObject({
     inboundLinks: z.number().int().nonnegative(),
     totalItems: z.number().int().positive(),
+    // ⚠️ `flow` beside the node kinds, because a flow filed in the folder goes with it and is counted
+    // in `totalItems`. Naming everything except flows would leave out the one thing the cascade had to
+    // be widened for (#733).
+    items: z.array(z.strictObject({
+        id: IntelId,
+        kind: z.union([NodeKind, z.literal("flow")]),
+        title: z.string(),
+    })),
 });
 // The title travels back because after this call nothing can look it up any more — not the row, not
 // a version, not the index. A caller that wants to say what it just deleted has this one chance.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@anchrd/intel-contract",
-  "version": "0.26.0",
+  "version": "0.28.0",
   "type": "module",
   "license": "UNLICENSED",
   "repository": {