@anchrd/intel-contract 0.26.0 → 0.27.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.27.0",
   "type": "module",
   "license": "UNLICENSED",
   "repository": {