@pome-sh/checks 0.1.2 → 0.1.3

package/CHANGELOG.md

@@ -1,5 +1,23 @@
 # @pome-sh/checks
 
+## 0.1.3
+
+No change to the published surface — `dist/` is byte-identical to 0.1.2, so no
+declaration moved and no consumer's verdict changes. The declaration layer has
+not been touched since 0.1.2 was cut (`38acaf9`), which is the version-bump
+gate doing its job rather than an absence of work.
+
+What this version is for: it is the first release cut by following
+[`RELEASING.md`](../../RELEASING.md) end to end since the `packages-v*` batch
+flow was replaced by version-diff-on-push, and it exists to prove that runbook
+is followable — bump, merge, `release.yml` publishes, pome-cloud pins. The
+consumer half is the part that was actually owed: pome-cloud has been pinned at
+0.1.1 since before 0.1.2 shipped, so F-1157's redaction-survival vocabulary has
+not reached the grader.
+
+Version-only bumps are accepted here rather than carrying an exception list,
+per `cli/CHANGELOG.md` 0.21.7.
+
 ## 0.1.2
 
 Carries F-1157 to the grader. Three things move in `dist/`:

package/dist/_types/twin-github/src/seed.d.ts

@@ -61,9 +61,9 @@ export declare const seedSchema: z.ZodObject<{
                 context: z.ZodDefault<z.ZodString>;
                 state: z.ZodDefault<z.ZodEnum<{
                     error: "error";
+                    success: "success";
                     failure: "failure";
                     pending: "pending";
-                    success: "success";
                 }>>;
                 description: z.ZodDefault<z.ZodString>;
             }, z.core.$strip>>>;

package/dist/_types/twin-linear/src/types.d.ts

@@ -4,7 +4,44 @@ export type LinearWorkflowStateType = "backlog" | "unstarted" | "started" | "com
 export type LinearTokenType = "personal" | "oauth_access" | "oauth_refresh" | "client_credentials";
 export type LinearTokenActorType = "user" | "app";
 export type LinearIssuePriority = 0 | 1 | 2 | 3 | 4;
+/** Linear's `AgentActivityType` enum, member-for-member — the `content` discriminator. */
 export type LinearAgentActivityType = "thought" | "elicitation" | "action" | "response" | "error" | "prompt";
+/** Linear's `AgentActivitySignal` enum, member-for-member (F-1176). */
+export type LinearAgentActivitySignal = "stop" | "continue" | "auth" | "select";
+/**
+ * Linear's `AgentActivityContent` union, member-for-member (F-1176).
+ *
+ * Upstream this is a real GraphQL union discriminated on `type`, whose six
+ * members are `AgentActivity{Thought,Action,Response,Elicitation,Error,Prompt}
+ * Content`. Five of the six carry `body`; `action` carries `action` /
+ * `parameter` / `result` instead, which is why an activity's payload cannot be
+ * flattened back to the `{ type, body }` pair the twin used to accept.
+ *
+ * `bodyData` / `resultData` are upstream's structured companions to the text
+ * fields. The twin does not derive them, but it accepts and stores them rather
+ * than refusing an agent that was written against real Linear and sends them.
+ */
+export type LinearAgentActivityContent = {
+    type: "thought" | "response" | "elicitation";
+    body: string;
+    bodyData?: unknown;
+} | {
+    type: "prompt";
+    body: string;
+    title?: string | null;
+    bodyData?: unknown;
+} | {
+    type: "error";
+    body: string;
+    reasonCode?: string | null;
+    bodyData?: unknown;
+} | {
+    type: "action";
+    action: string;
+    parameter: string;
+    result?: string | null;
+    resultData?: unknown;
+};
 /** Linear's `AgentSessionStatus` enum, member-for-member (F-1172). */
 export type LinearAgentSessionStatus = "pending" | "active" | "awaitingInput" | "complete" | "error" | "stale";
 /** One entry of Linear's `AgentSession.externalUrls` JSON payload. */
@@ -208,10 +245,15 @@ export type LinearAgentSession = {
 };
 export type LinearAgentActivity = {
     id: string;
-    sessionId: string;
-    userId: string | null;
-    type: LinearAgentActivityType;
-    body: string;
+    agentSessionId: string;
+    /**
+     * Non-null, matching Linear's `AgentActivity.user: User!`. The column is
+     * still nullable — its FK is `ON DELETE SET NULL` — so this is enforced at
+     * the read boundary, next to the status check, rather than assumed.
+     */
+    userId: string;
+    content: LinearAgentActivityContent;
+    signal: LinearAgentActivitySignal | null;
     ephemeral: boolean;
     createdAt: string;
     updatedAt: string;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pome-sh/checks",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "Pome's grading vocabulary — the check declarations, seed schemas and default seeds of all five digital twins, plus the check DSL they are written in. Declarations only: no twin server, no database, no routes, no tools.",
   "private": false,
   "type": "module",