@anchrd/intel-contract 0.23.0 → 0.24.0

package/dist/contract/board.d.ts

@@ -1,4 +1,14 @@
 import { z } from "zod";
+/**
+ * The id of the archive column, on every board (D68, #674).
+ *
+ * ⚠️ **It is derived, never stored.** A card sits in it because `nodes.archived_at` is set, and
+ * `board_tasks.status` keeps naming the working column it came from — that is what lets a card
+ * pulled back out land where it was. A configured column may not claim this id; `board_update`
+ * refuses it, because two columns with one id means every card in them lands in whichever the view
+ * draws first.
+ */
+export declare const ARCHIVE_COLUMN_ID = "archived";
 export declare const BoardColumn: z.ZodObject<{
     id: z.ZodString;
     title: z.ZodString;
@@ -14,6 +24,7 @@ export declare const BoardTask: z.ZodObject<{
     startDate: z.ZodNullable<z.ZodISODateTime>;
     dueDate: z.ZodNullable<z.ZodISODateTime>;
     dependsOn: z.ZodNullable<z.ZodString>;
+    parentTaskId: z.ZodNullable<z.ZodString>;
     position: z.ZodNumber;
     archivedAt: z.ZodNullable<z.ZodISODateTime>;
 }, z.core.$strict>;
@@ -43,6 +54,7 @@ export declare const BoardView: z.ZodObject<{
         title: z.ZodString;
         terminal: z.ZodDefault<z.ZodBoolean>;
     }, z.core.$strict>>;
+    archiveVisible: z.ZodBoolean;
     tasks: z.ZodArray<z.ZodObject<{
         id: z.ZodString;
         title: z.ZodString;
@@ -52,6 +64,7 @@ export declare const BoardView: z.ZodObject<{
         startDate: z.ZodNullable<z.ZodISODateTime>;
         dueDate: z.ZodNullable<z.ZodISODateTime>;
         dependsOn: z.ZodNullable<z.ZodString>;
+        parentTaskId: z.ZodNullable<z.ZodString>;
         position: z.ZodNumber;
         archivedAt: z.ZodNullable<z.ZodISODateTime>;
     }, z.core.$strict>>;
@@ -64,6 +77,7 @@ export declare const BoardUpdateInput: z.ZodObject<{
         title: z.ZodString;
         terminal: z.ZodDefault<z.ZodBoolean>;
     }, z.core.$strict>>;
+    archiveVisible: z.ZodOptional<z.ZodBoolean>;
     idempotencyKey: z.ZodString;
 }, z.core.$strict>;
 export type BoardUpdateInput = z.infer<typeof BoardUpdateInput>;
@@ -76,6 +90,7 @@ export declare const BoardTaskCreateInput: z.ZodObject<{
     startDate: z.ZodDefault<z.ZodNullable<z.ZodISODateTime>>;
     dueDate: z.ZodDefault<z.ZodNullable<z.ZodISODateTime>>;
     dependsOn: z.ZodDefault<z.ZodNullable<z.ZodString>>;
+    parentTaskId: z.ZodDefault<z.ZodNullable<z.ZodString>>;
     idempotencyKey: z.ZodString;
 }, z.core.$strict>;
 export type BoardTaskCreateInput = z.infer<typeof BoardTaskCreateInput>;

package/dist/contract/board.js

@@ -3,6 +3,16 @@ import { IdempotencyKey, IntelId, IsoDateTime } from "./contract.js";
 // One column of a board. `terminal` is what "done" means here — a rule about the column rather than
 // a magic status name, so an installation may call it "Shipped" or "Abgerechnet" without anything
 // downstream having to know the word.
+/**
+ * The id of the archive column, on every board (D68, #674).
+ *
+ * ⚠️ **It is derived, never stored.** A card sits in it because `nodes.archived_at` is set, and
+ * `board_tasks.status` keeps naming the working column it came from — that is what lets a card
+ * pulled back out land where it was. A configured column may not claim this id; `board_update`
+ * refuses it, because two columns with one id means every card in them lands in whichever the view
+ * draws first.
+ */
+export const ARCHIVE_COLUMN_ID = "archived";
 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."),
@@ -26,6 +36,18 @@ export const BoardTask = z.strictObject({
     startDate: IsoDateTime.nullable(),
     dueDate: IsoDateTime.nullable(),
     dependsOn: IntelId.nullable(),
+    /**
+     * The task this one sits under, or `null` when it sits directly on the board.
+     *
+     * ⚠️ **The hierarchy is the node tree** (`nodes.parent_id`), not a second column here — a task
+     * under a task IS the tree Intel already has, which is why the cycle guard that refuses moving a
+     * node into its own descendant covers this for free.
+     *
+     * ⚠️ **Under a filter this may name a task that is not in the same answer.** `board_get` returns
+     * what matches; a subtask can match while its parent does not. A reader that assumes the parent
+     * is present will lose the row — treat an unknown parent as top level.
+     */
+    parentTaskId: IntelId.nullable(),
     position: z.number(),
     archivedAt: IsoDateTime.nullable(),
 });
@@ -59,6 +81,14 @@ export const BoardView = z.strictObject({
     boardId: IntelId,
     title: z.string().min(1).max(240),
     columns: z.array(BoardColumn),
+    /**
+     * Whether the archive column is drawn (D68, #674).
+     *
+     * ⚠️ It travels even when it is `false`, because the settings dialog needs to draw the switch in
+     * both positions — and because "the column is not in `columns`" has two possible reasons, hidden
+     * and not-yet-supported, which a reader cannot tell apart from the list alone.
+     */
+    archiveVisible: z.boolean(),
     tasks: z.array(BoardTask),
 });
 export const BoardUpdateInput = z.strictObject({
@@ -66,7 +96,13 @@ export const BoardUpdateInput = z.strictObject({
     columns: z
         .array(BoardColumn)
         .min(1)
-        .describe("The complete new column list, in order. Columns are replaced, not merged."),
+        .describe(`The complete new column list, in order. Columns are replaced, not merged. The archive column (\`${ARCHIVE_COLUMN_ID}\`) is not part of this list and cannot be named in it — it is on every board and is only shown or hidden.`),
+    // ⚠️ Shown or hidden, never removed. The archive is the same place on every board; a shelf that
+    // could be dragged between the working columns would be a shelf pretending to be a stage.
+    archiveVisible: z
+        .boolean()
+        .optional()
+        .describe("Whether the archive column is drawn. Omit to leave it as it is."),
     idempotencyKey: IdempotencyKey,
 });
 export const BoardTaskCreateInput = z.strictObject({
@@ -100,6 +136,12 @@ export const BoardTaskCreateInput = z.strictObject({
     dependsOn: IntelId.nullable()
         .default(null)
         .describe("A node this task waits for. Any node, not only another task."),
+    // ⚠️ Creating a subtask is ONE call; moving an existing task under another is `node_update`
+    // with a new `parentId`. Two paths for "where a task sits" would mean two cycle guards, and the
+    // one on the node path is the one that already exists.
+    parentTaskId: IntelId.nullable()
+        .default(null)
+        .describe("The task this one belongs under. It must be on the same board. Omit for a card that sits directly on the board."),
     idempotencyKey: IdempotencyKey,
 });
 // ⚠️ Moving a card IS this call: `status` and `position` together. There is deliberately no
@@ -117,7 +159,12 @@ export const BoardTaskUpdateInput = z.strictObject({
         .max(240)
         .optional()
         .describe("Refused on purpose: a card's title lives on the node. Rename it with node_update."),
-    status: z.string().min(1).max(60).optional().describe("The column to move it to."),
+    status: z
+        .string()
+        .min(1)
+        .max(60)
+        .optional()
+        .describe(`The column to move it to. \`${ARCHIVE_COLUMN_ID}\` is not an ordinary column: it archives the card through the same path as \`node_archive\`, with the same refusals — a card that still has live subtasks is refused. Moving it to any other column while it is archived brings it back.`),
     position: z
         .number()
         .optional()

package/package.json

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