@anchrd/intel-contract 0.24.0 → 0.25.0

package/dist/contract/board.d.ts

@@ -107,3 +107,28 @@ export declare const BoardTaskUpdateInput: z.ZodObject<{
     idempotencyKey: z.ZodString;
 }, z.core.$strict>;
 export type BoardTaskUpdateInput = z.infer<typeof BoardTaskUpdateInput>;
+export declare const BoardAssignee: z.ZodObject<{
+    id: z.ZodString;
+    name: z.ZodString;
+    email: z.ZodEmail;
+    isMachine: z.ZodBoolean;
+}, z.core.$strict>;
+export type BoardAssignee = z.infer<typeof BoardAssignee>;
+export declare const BoardAssigneeSearchInput: z.ZodObject<{
+    boardId: z.ZodString;
+    query: z.ZodString;
+}, z.core.$strict>;
+export type BoardAssigneeSearchInput = z.infer<typeof BoardAssigneeSearchInput>;
+export declare const BoardAssigneeResolveInput: z.ZodObject<{
+    ids: z.ZodArray<z.ZodString>;
+}, z.core.$strict>;
+export type BoardAssigneeResolveInput = z.infer<typeof BoardAssigneeResolveInput>;
+export declare const BoardAssigneeList: z.ZodObject<{
+    items: z.ZodArray<z.ZodObject<{
+        id: z.ZodString;
+        name: z.ZodString;
+        email: z.ZodEmail;
+        isMachine: z.ZodBoolean;
+    }, z.core.$strict>>;
+}, z.core.$strict>;
+export type BoardAssigneeList = z.infer<typeof BoardAssigneeList>;

package/dist/contract/board.js

@@ -188,3 +188,39 @@ export const BoardTaskUpdateInput = z.strictObject({
         .describe("A node this card waits for. `null` clears the dependency."),
     idempotencyKey: IdempotencyKey,
 });
+// ── Who a card can be given to ────────────────────────────────────────────────────────────────
+// D70 (`~/Dev/anchrd/core/DECISIONS.md`): the people offered here are the ones who can actually open
+// THIS board, never everyone who holds an account. The narrower answer is the point, and it is what
+// makes the door safe to offer to anyone who can see the board.
+//
+// ⚠️ `email` travels because two colleagues share a first name more often than a picker can afford,
+// and a list of indistinguishable "Anton" rows is not a picker. It is no wider than what gate hands
+// any signed-in person at `POST /directory/search`; the narrowing this door adds is WHO appears,
+// not WHAT is said about them.
+//
+// `isMachine` travels for the same reason gate carries it: whoever picks an assignee wants to know
+// whether they are handing the card to a colleague or to an agent.
+export const BoardAssignee = z.strictObject({
+    id: IntelId,
+    name: z.string(),
+    email: z.email(),
+    isMachine: z.boolean(),
+});
+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."),
+});
+// ⚠️ 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
+// id (`#258`). Someone whose access was withdrawn, or whose account was switched off, still has to
+// be nameable: a card that reads as unassigned is a worse answer than the truth.
+export const BoardAssigneeResolveInput = z.strictObject({
+    ids: z
+        .array(IntelId)
+        .min(1)
+        .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) });

package/package.json

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