@codetreker/daynight 0.31.0 → 0.37.2

package/dist/commands/controller/sqlite/journal/006-pending-content.sql

@@ -0,0 +1,12 @@
+ALTER TABLE execution ADD COLUMN archive_incomplete INTEGER NOT NULL DEFAULT 0;
+UPDATE execution SET archive_incomplete=1 WHERE projection_gap IS NOT NULL;
+
+CREATE TABLE content_index (
+  id TEXT PRIMARY KEY,
+  content_hash TEXT NOT NULL,
+  revision TEXT NOT NULL,
+  entry_seq TEXT NOT NULL
+);
+
+DROP TABLE projection;
+DROP TABLE resources;

package/dist/commands/project/definition.js

@@ -30,6 +30,6 @@ export const projectDefinition = {
         },
     ],
     options: [helpOption],
-    details: "Server: https://daynight.cc (optional serverUrl override in ~/.daynight/config.yml)\nRun daynight project <command> --help for command usage.",
+    details: "Server: https://daynight.cc (optional serverUrl override in DN_CONFIG_DIR/config.yml (default: ~/.daynight/config.yml))\nRun daynight project <command> --help for command usage.",
 };
 //# sourceMappingURL=definition.js.map

package/dist/commands/project/definition.js.map

@@ -1 +1 @@
-{"version":3,"file":"definition.js","sourceRoot":"","sources":["../../../src/commands/project/definition.ts"],"names":[],"mappings":"AAEA,MAAM,UAAU,GAAkB,EAAE,KAAK,EAAE,CAAC,IAAI,EAAE,QAAQ,CAAC,EAAE,WAAW,EAAE,gBAAgB,EAAE,MAAM,EAAE,MAAM,EAAE,CAAC;AAC7G,MAAM,UAAU,GAAkB,EAAE,KAAK,EAAE,CAAC,QAAQ,CAAC,EAAE,WAAW,EAAE,8CAA8C,EAAE,CAAC;AAErH,MAAM,CAAC,MAAM,iBAAiB,GAAsB;IAClD,IAAI,EAAE,SAAS;IACf,WAAW,EAAE,oDAAoD;IACjE,QAAQ,EAAE;QACR;YACE,IAAI,EAAE,QAAQ;YACd,WAAW,EAAE,8DAA8D;YAC3E,SAAS,EAAE,CAAC,EAAE,IAAI,EAAE,MAAM,EAAE,WAAW,EAAE,cAAc,EAAE,CAAC;YAC1D,sBAAsB,EAAE,IAAI;YAC5B,OAAO,EAAE;gBACP,EAAE,KAAK,EAAE,CAAC,QAAQ,CAAC,EAAE,WAAW,EAAE,yDAAyD,EAAE,KAAK,EAAE,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,EAAE,EAAE;gBACpI,UAAU;aACX;YACD,OAAO,EAAE,+eAA+e;SACzf;QACD;YACE,IAAI,EAAE,MAAM;YACZ,WAAW,EAAE,4CAA4C;YACzD,OAAO,EAAE,CAAC,UAAU,EAAE,UAAU,CAAC;YACjC,OAAO,EAAE,gHAAgH;SAC1H;QACD;YACE,IAAI,EAAE,MAAM;YACZ,WAAW,EAAE,0BAA0B;YACvC,SAAS,EAAE,CAAC,EAAE,IAAI,EAAE,YAAY,EAAE,WAAW,EAAE,cAAc,EAAE,CAAC;YAChE,OAAO,EAAE,CAAC,UAAU,EAAE,UAAU,CAAC;YACjC,OAAO,EAAE,oHAAoH;SAC9H;KACF;IACD,OAAO,EAAE,CAAC,UAAU,CAAC;IACrB,OAAO,EAAE,+IAA+I;CACzJ,CAAC"}
+{"version":3,"file":"definition.js","sourceRoot":"","sources":["../../../src/commands/project/definition.ts"],"names":[],"mappings":"AAEA,MAAM,UAAU,GAAkB,EAAE,KAAK,EAAE,CAAC,IAAI,EAAE,QAAQ,CAAC,EAAE,WAAW,EAAE,gBAAgB,EAAE,MAAM,EAAE,MAAM,EAAE,CAAC;AAC7G,MAAM,UAAU,GAAkB,EAAE,KAAK,EAAE,CAAC,QAAQ,CAAC,EAAE,WAAW,EAAE,8CAA8C,EAAE,CAAC;AAErH,MAAM,CAAC,MAAM,iBAAiB,GAAsB;IAClD,IAAI,EAAE,SAAS;IACf,WAAW,EAAE,oDAAoD;IACjE,QAAQ,EAAE;QACR;YACE,IAAI,EAAE,QAAQ;YACd,WAAW,EAAE,8DAA8D;YAC3E,SAAS,EAAE,CAAC,EAAE,IAAI,EAAE,MAAM,EAAE,WAAW,EAAE,cAAc,EAAE,CAAC;YAC1D,sBAAsB,EAAE,IAAI;YAC5B,OAAO,EAAE;gBACP,EAAE,KAAK,EAAE,CAAC,QAAQ,CAAC,EAAE,WAAW,EAAE,yDAAyD,EAAE,KAAK,EAAE,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,EAAE,EAAE;gBACpI,UAAU;aACX;YACD,OAAO,EAAE,+eAA+e;SACzf;QACD;YACE,IAAI,EAAE,MAAM;YACZ,WAAW,EAAE,4CAA4C;YACzD,OAAO,EAAE,CAAC,UAAU,EAAE,UAAU,CAAC;YACjC,OAAO,EAAE,gHAAgH;SAC1H;QACD;YACE,IAAI,EAAE,MAAM;YACZ,WAAW,EAAE,0BAA0B;YACvC,SAAS,EAAE,CAAC,EAAE,IAAI,EAAE,YAAY,EAAE,WAAW,EAAE,cAAc,EAAE,CAAC;YAChE,OAAO,EAAE,CAAC,UAAU,EAAE,UAAU,CAAC;YACjC,OAAO,EAAE,oHAAoH;SAC9H;KACF;IACD,OAAO,EAAE,CAAC,UAAU,CAAC;IACrB,OAAO,EAAE,mLAAmL;CAC7L,CAAC"}

package/dist/commands/review/definition.js

@@ -7,7 +7,7 @@ export const reviewDefinition = {
             name: "run",
             description: "Run foreground PR review until interrupted",
             options: [helpOption],
-            details: "Run foreground PR review using ~/.daynight/config.yml until interrupted.",
+            details: "Run foreground PR review using DN_CONFIG_DIR/config.yml (default: ~/.daynight/config.yml) until interrupted.",
         },
         {
             name: "list",
@@ -24,10 +24,10 @@ export const reviewDefinition = {
                 { names: ["--path"], description: "Dedicated review clone path (relative to the current directory)", value: { name: "path", kind: "directory" } },
                 helpOption,
             ],
-            details: "Without --path, review.repositoryRoot (default: ~/daynights) determines the clone path.\nThe resolved absolute path is saved in ~/.daynight/config.yml.\nChanges take effect the next time daynight review run starts.",
+            details: "Without --path, review.repositoryRoot (default: ~/daynights) determines the clone path.\nThe resolved absolute path is saved in DN_CONFIG_DIR/config.yml (default: ~/.daynight/config.yml).\nChanges take effect the next time daynight review run starts.",
         },
     ],
     options: [helpOption],
-    details: "Configuration: ~/.daynight/config.yml (current user's home directory)\nRuntime state: ~/.daynight/\nRun daynight review <command> --help for command usage.",
+    details: "Configuration: DN_CONFIG_DIR/config.yml (default: ~/.daynight/config.yml)\nRuntime state: DN_CONFIG_DIR (default: ~/.daynight/)\nRun daynight review <command> --help for command usage.",
 };
 //# sourceMappingURL=definition.js.map

package/dist/commands/review/definition.js.map

@@ -1 +1 @@
-{"version":3,"file":"definition.js","sourceRoot":"","sources":["../../../src/commands/review/definition.ts"],"names":[],"mappings":"AAEA,MAAM,UAAU,GAAkB,EAAE,KAAK,EAAE,CAAC,IAAI,EAAE,QAAQ,CAAC,EAAE,WAAW,EAAE,gBAAgB,EAAE,MAAM,EAAE,MAAM,EAAE,CAAC;AAE7G,MAAM,CAAC,MAAM,gBAAgB,GAAsB;IACjD,IAAI,EAAE,QAAQ;IACd,WAAW,EAAE,mEAAmE;IAChF,QAAQ,EAAE;QACR;YACE,IAAI,EAAE,KAAK;YACX,WAAW,EAAE,4CAA4C;YACzD,OAAO,EAAE,CAAC,UAAU,CAAC;YACrB,OAAO,EAAE,0EAA0E;SACpF;QACD;YACE,IAAI,EAAE,MAAM;YACZ,OAAO,EAAE,CAAC,IAAI,CAAC;YACf,WAAW,EAAE,qDAAqD;YAClE,OAAO,EAAE,CAAC,UAAU,CAAC;YACrB,OAAO,EAAE,wTAAwT;SAClU;QACD;YACE,IAAI,EAAE,UAAU;YAChB,WAAW,EAAE,+DAA+D;YAC5E,SAAS,EAAE,CAAC,EAAE,IAAI,EAAE,QAAQ,EAAE,WAAW,EAAE,wCAAwC,EAAE,CAAC;YACtF,OAAO,EAAE;gBACP,EAAE,KAAK,EAAE,CAAC,QAAQ,CAAC,EAAE,WAAW,EAAE,iEAAiE,EAAE,KAAK,EAAE,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,WAAW,EAAE,EAAE;gBACjJ,UAAU;aACX;YACD,OAAO,EAAE,wNAAwN;SAClO;KACF;IACD,OAAO,EAAE,CAAC,UAAU,CAAC;IACrB,OAAO,EAAE,6JAA6J;CACvK,CAAC"}
+{"version":3,"file":"definition.js","sourceRoot":"","sources":["../../../src/commands/review/definition.ts"],"names":[],"mappings":"AAEA,MAAM,UAAU,GAAkB,EAAE,KAAK,EAAE,CAAC,IAAI,EAAE,QAAQ,CAAC,EAAE,WAAW,EAAE,gBAAgB,EAAE,MAAM,EAAE,MAAM,EAAE,CAAC;AAE7G,MAAM,CAAC,MAAM,gBAAgB,GAAsB;IACjD,IAAI,EAAE,QAAQ;IACd,WAAW,EAAE,mEAAmE;IAChF,QAAQ,EAAE;QACR;YACE,IAAI,EAAE,KAAK;YACX,WAAW,EAAE,4CAA4C;YACzD,OAAO,EAAE,CAAC,UAAU,CAAC;YACrB,OAAO,EAAE,8GAA8G;SACxH;QACD;YACE,IAAI,EAAE,MAAM;YACZ,OAAO,EAAE,CAAC,IAAI,CAAC;YACf,WAAW,EAAE,qDAAqD;YAClE,OAAO,EAAE,CAAC,UAAU,CAAC;YACrB,OAAO,EAAE,wTAAwT;SAClU;QACD;YACE,IAAI,EAAE,UAAU;YAChB,WAAW,EAAE,+DAA+D;YAC5E,SAAS,EAAE,CAAC,EAAE,IAAI,EAAE,QAAQ,EAAE,WAAW,EAAE,wCAAwC,EAAE,CAAC;YACtF,OAAO,EAAE;gBACP,EAAE,KAAK,EAAE,CAAC,QAAQ,CAAC,EAAE,WAAW,EAAE,iEAAiE,EAAE,KAAK,EAAE,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,WAAW,EAAE,EAAE;gBACjJ,UAAU;aACX;YACD,OAAO,EAAE,4PAA4P;SACtQ;KACF;IACD,OAAO,EAAE,CAAC,UAAU,CAAC;IACrB,OAAO,EAAE,0LAA0L;CACpM,CAAC"}

package/dist/commands/server/runtime.d.ts

@@ -6,7 +6,16 @@ export type ServerSession = {
     readonly operation: Operation;
     readonly serverUrl: string;
 };
-export type ServerCommand = (session: ServerSession) => Promise<string | void>;
+export type ConfirmedMutationOutput = {
+    readonly kind: "confirmed-mutation";
+    readonly output: string;
+    readonly identity: {
+        readonly projectId: string;
+        readonly taskId: string;
+        readonly messageId: string;
+    };
+};
+export type ServerCommand = (session: ServerSession) => Promise<string | void | ConfirmedMutationOutput>;
 export type ServerCommandOptions = {
     readonly signalEmitter?: Pick<EventEmitter, "on" | "off">;
     readonly platform?: NodeJS.Platform;

package/dist/commands/server/runtime.js

@@ -1,6 +1,7 @@
 import { createApiClient, createOperation } from "../../api/index.js";
 import { resolveConfigurationPaths } from "../../config/paths.js";
 import { loadServerConfiguration } from "../../config/server.js";
+import { PublicDiagnosticError } from "../../platform/diagnostics.js";
 export const runServerCommand = async (context, command, options = {}) => {
     const cancellation = new AbortController();
     const operation = createOperation({ signal: cancellation.signal, ...(options.operationLimits === undefined ? {} : { limits: options.operationLimits }) });
@@ -9,6 +10,8 @@ export const runServerCommand = async (context, command, options = {}) => {
     const listeners = [];
     let failed = false;
     let failure;
+    let confirmed;
+    const confirmedFailure = (phase, cause) => new PublicDiagnosticError(`Message posted. Id: ${confirmed.identity.messageId}\nThe message is confirmed, but local ${phase} failed.`, 1, { cause });
     try {
         for (const signal of signals) {
             const cancel = () => cancellation.abort(new Error(`Received ${signal}.`));
@@ -23,14 +26,26 @@ export const runServerCommand = async (context, command, options = {}) => {
         operation.check();
         const api = createApiClient({ serverUrl, serverToken, operation, ...(options.fetch === undefined ? {} : { fetch: options.fetch }) });
         const output = await command({ api, operation, serverUrl });
-        operation.check();
-        if (typeof output === "string")
-            context.stdout(output);
+        if (typeof output === "object" && output.kind === "confirmed-mutation") {
+            confirmed = output;
+            const receipt = createOperation({ limits: { totalMs: 5_000 } });
+            try {
+                await context.stdoutBytes(Buffer.from(output.output, "utf8"), receipt.signal);
+            }
+            finally {
+                receipt.dispose();
+            }
+        }
+        else {
+            operation.check();
+            if (typeof output === "string")
+                context.stdout(output);
+        }
     }
     catch (cause) {
         failed = true;
-        failure = cause;
-        throw cause;
+        failure = confirmed === undefined ? cause : confirmedFailure("output", cause);
+        throw failure;
     }
     finally {
         const cleanup = [];
@@ -54,8 +69,10 @@ export const runServerCommand = async (context, command, options = {}) => {
         catch (cause) {
             cleanup.push(cause);
         }
-        if (cleanup.length !== 0)
-            throw new AggregateError(failed ? [failure, ...cleanup] : cleanup, "Server command or cancellation cleanup failed.");
+        if (cleanup.length !== 0) {
+            const cause = new AggregateError(failed ? [failure, ...cleanup] : cleanup, "Server command or cancellation cleanup failed.");
+            throw confirmed === undefined ? cause : confirmedFailure("cleanup", cause);
+        }
     }
 };
 //# sourceMappingURL=runtime.js.map

package/dist/commands/server/runtime.js.map

@@ -1 +1 @@
-{"version":3,"file":"runtime.js","sourceRoot":"","sources":["../../../src/commands/server/runtime.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,eAAe,EAAE,eAAe,EAAE,MAAM,oBAAoB,CAAC;AAGtE,OAAO,EAAE,yBAAyB,EAAE,MAAM,uBAAuB,CAAC;AAClE,OAAO,EAAE,uBAAuB,EAAE,MAAM,wBAAwB,CAAC;AAiBjE,MAAM,CAAC,MAAM,gBAAgB,GAAG,KAAK,EACnC,OAAmB,EACnB,OAAsB,EACtB,OAAO,GAAyB,EAAE,EACnB,EAAE;IACjB,MAAM,YAAY,GAAG,IAAI,eAAe,EAAE,CAAC;IAC3C,MAAM,SAAS,GAAG,eAAe,CAAC,EAAE,MAAM,EAAE,YAAY,CAAC,MAAM,EAAE,GAAG,CAAC,OAAO,CAAC,eAAe,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,MAAM,EAAE,OAAO,CAAC,eAAe,EAAE,CAAC,EAAE,CAAC,CAAC;IAC1J,MAAM,OAAO,GAAG,OAAO,CAAC,aAAa,IAAI,OAAO,CAAC;IACjD,MAAM,OAAO,GAAqB,CAAC,OAAO,CAAC,QAAQ,IAAI,OAAO,CAAC,QAAQ,CAAC,KAAK,OAAO,CAAC,CAAC,CAAC,CAAC,QAAQ,EAAE,SAAS,EAAE,UAAU,CAAC,CAAC,CAAC,CAAC,CAAC,QAAQ,EAAE,SAAS,CAAC,CAAC;IACjJ,MAAM,SAAS,GAAmC,EAAE,CAAC;IACrD,IAAI,MAAM,GAAG,KAAK,CAAC;IACnB,IAAI,OAAgB,CAAC;IACrB,IAAI,CAAC;QACH,KAAK,MAAM,MAAM,IAAI,OAAO,EAAE,CAAC;YAC7B,MAAM,MAAM,GAAG,GAAS,EAAE,CAAC,YAAY,CAAC,KAAK,CAAC,IAAI,KAAK,CAAC,YAAY,MAAM,GAAG,CAAC,CAAC,CAAC;YAChF,OAAO,CAAC,EAAE,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;YAC3B,SAAS,CAAC,IAAI,CAAC,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC,CAAC;QACnC,CAAC;QACD,SAAS,CAAC,KAAK,EAAE,CAAC;QAClB,MAAM,KAAK,GAAG,yBAAyB,CAAC,OAAO,CAAC,aAAa,EAAE,CAAC,CAAC;QACjE,MAAM,EAAE,SAAS,EAAE,WAAW,EAAE,GAAG,MAAM,uBAAuB,CAAC,KAAK,EAAE,SAAS,CAAC,MAAM,CAAC,CAAC;QAC1F,IAAI,WAAW,KAAK,SAAS;YAAE,MAAM,IAAI,KAAK,CAAC,4DAA4D,CAAC,CAAC;QAC7G,SAAS,CAAC,KAAK,EAAE,CAAC;QAClB,MAAM,GAAG,GAAG,eAAe,CAAC,EAAE,SAAS,EAAE,WAAW,EAAE,SAAS,EAAE,GAAG,CAAC,OAAO,CAAC,KAAK,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,KAAK,EAAE,OAAO,CAAC,KAAK,EAAE,CAAC,EAAE,CAAC,CAAC;QACrI,MAAM,MAAM,GAAG,MAAM,OAAO,CAAC,EAAE,GAAG,EAAE,SAAS,EAAE,SAAS,EAAE,CAAC,CAAC;QAC5D,SAAS,CAAC,KAAK,EAAE,CAAC;QAClB,IAAI,OAAO,MAAM,KAAK,QAAQ;YAAE,OAAO,CAAC,MAAM,CAAC,MAAM,CAAC,CAAC;IACzD,CAAC;IAAC,OAAO,KAAK,EAAE,CAAC;QACf,MAAM,GAAG,IAAI,CAAC;QACd,OAAO,GAAG,KAAK,CAAC;QAChB,MAAM,KAAK,CAAC;IACd,CAAC;YAAS,CAAC;QACT,MAAM,OAAO,GAAc,EAAE,CAAC;QAC9B,IAAI,CAAC;YAAC,MAAM,OAAO,CAAC,gBAAgB,EAAE,EAAE,CAAC;QAAC,CAAC;QAC3C,OAAO,KAAK,EAAE,CAAC;YAAC,OAAO,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;QAAC,CAAC;QACtC,KAAK,MAAM,CAAC,MAAM,EAAE,QAAQ,CAAC,IAAI,SAAS,EAAE,CAAC;YAC3C,IAAI,CAAC;gBAAC,OAAO,CAAC,GAAG,CAAC,MAAM,EAAE,QAAQ,CAAC,CAAC;YAAC,CAAC;YACtC,OAAO,KAAK,EAAE,CAAC;gBAAC,OAAO,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;YAAC,CAAC;QACxC,CAAC;QACD,IAAI,CAAC;YAAC,SAAS,CAAC,OAAO,EAAE,CAAC;QAAC,CAAC;QAC5B,OAAO,KAAK,EAAE,CAAC;YAAC,OAAO,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;QAAC,CAAC;QACtC,IAAI,OAAO,CAAC,MAAM,KAAK,CAAC;YAAE,MAAM,IAAI,cAAc,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,OAAO,EAAE,GAAG,OAAO,CAAC,CAAC,CAAC,CAAC,OAAO,EAAE,gDAAgD,CAAC,CAAC;IACjJ,CAAC;AACH,CAAC,CAAC"}
+{"version":3,"file":"runtime.js","sourceRoot":"","sources":["../../../src/commands/server/runtime.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,eAAe,EAAE,eAAe,EAAE,MAAM,oBAAoB,CAAC;AAGtE,OAAO,EAAE,yBAAyB,EAAE,MAAM,uBAAuB,CAAC;AAClE,OAAO,EAAE,uBAAuB,EAAE,MAAM,wBAAwB,CAAC;AACjE,OAAO,EAAE,qBAAqB,EAAE,MAAM,+BAA+B,CAAC;AAkBtE,MAAM,CAAC,MAAM,gBAAgB,GAAG,KAAK,EACnC,OAAmB,EACnB,OAAsB,EACtB,OAAO,GAAyB,EAAE,EACnB,EAAE;IACjB,MAAM,YAAY,GAAG,IAAI,eAAe,EAAE,CAAC;IAC3C,MAAM,SAAS,GAAG,eAAe,CAAC,EAAE,MAAM,EAAE,YAAY,CAAC,MAAM,EAAE,GAAG,CAAC,OAAO,CAAC,eAAe,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,MAAM,EAAE,OAAO,CAAC,eAAe,EAAE,CAAC,EAAE,CAAC,CAAC;IAC1J,MAAM,OAAO,GAAG,OAAO,CAAC,aAAa,IAAI,OAAO,CAAC;IACjD,MAAM,OAAO,GAAqB,CAAC,OAAO,CAAC,QAAQ,IAAI,OAAO,CAAC,QAAQ,CAAC,KAAK,OAAO,CAAC,CAAC,CAAC,CAAC,QAAQ,EAAE,SAAS,EAAE,UAAU,CAAC,CAAC,CAAC,CAAC,CAAC,QAAQ,EAAE,SAAS,CAAC,CAAC;IACjJ,MAAM,SAAS,GAAmC,EAAE,CAAC;IACrD,IAAI,MAAM,GAAG,KAAK,CAAC;IACnB,IAAI,OAAgB,CAAC;IACrB,IAAI,SAA8C,CAAC;IACnD,MAAM,gBAAgB,GAAG,CAAC,KAA2B,EAAE,KAAc,EAAyB,EAAE,CAAC,IAAI,qBAAqB,CAAC,uBAAuB,SAAU,CAAC,QAAQ,CAAC,SAAS,yCAAyC,KAAK,UAAU,EAAE,CAAC,EAAE,EAAE,KAAK,EAAE,CAAC,CAAC;IACvP,IAAI,CAAC;QACH,KAAK,MAAM,MAAM,IAAI,OAAO,EAAE,CAAC;YAC7B,MAAM,MAAM,GAAG,GAAS,EAAE,CAAC,YAAY,CAAC,KAAK,CAAC,IAAI,KAAK,CAAC,YAAY,MAAM,GAAG,CAAC,CAAC,CAAC;YAChF,OAAO,CAAC,EAAE,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;YAC3B,SAAS,CAAC,IAAI,CAAC,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC,CAAC;QACnC,CAAC;QACD,SAAS,CAAC,KAAK,EAAE,CAAC;QAClB,MAAM,KAAK,GAAG,yBAAyB,CAAC,OAAO,CAAC,aAAa,EAAE,CAAC,CAAC;QACjE,MAAM,EAAE,SAAS,EAAE,WAAW,EAAE,GAAG,MAAM,uBAAuB,CAAC,KAAK,EAAE,SAAS,CAAC,MAAM,CAAC,CAAC;QAC1F,IAAI,WAAW,KAAK,SAAS;YAAE,MAAM,IAAI,KAAK,CAAC,4DAA4D,CAAC,CAAC;QAC7G,SAAS,CAAC,KAAK,EAAE,CAAC;QAClB,MAAM,GAAG,GAAG,eAAe,CAAC,EAAE,SAAS,EAAE,WAAW,EAAE,SAAS,EAAE,GAAG,CAAC,OAAO,CAAC,KAAK,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,KAAK,EAAE,OAAO,CAAC,KAAK,EAAE,CAAC,EAAE,CAAC,CAAC;QACrI,MAAM,MAAM,GAAG,MAAM,OAAO,CAAC,EAAE,GAAG,EAAE,SAAS,EAAE,SAAS,EAAE,CAAC,CAAC;QAC5D,IAAI,OAAO,MAAM,KAAK,QAAQ,IAAI,MAAM,CAAC,IAAI,KAAK,oBAAoB,EAAE,CAAC;YACvE,SAAS,GAAG,MAAM,CAAC;YACnB,MAAM,OAAO,GAAG,eAAe,CAAC,EAAE,MAAM,EAAE,EAAE,OAAO,EAAE,KAAK,EAAE,EAAE,CAAC,CAAC;YAChE,IAAI,CAAC;gBAAC,MAAM,OAAO,CAAC,WAAW,CAAC,MAAM,CAAC,IAAI,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,EAAE,OAAO,CAAC,MAAM,CAAC,CAAC;YAAC,CAAC;oBAC9E,CAAC;gBAAC,OAAO,CAAC,OAAO,EAAE,CAAC;YAAC,CAAC;QAChC,CAAC;aAAM,CAAC;YACN,SAAS,CAAC,KAAK,EAAE,CAAC;YAClB,IAAI,OAAO,MAAM,KAAK,QAAQ;gBAAE,OAAO,CAAC,MAAM,CAAC,MAAM,CAAC,CAAC;QACzD,CAAC;IACH,CAAC;IAAC,OAAO,KAAK,EAAE,CAAC;QACf,MAAM,GAAG,IAAI,CAAC;QACd,OAAO,GAAG,SAAS,KAAK,SAAS,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,gBAAgB,CAAC,QAAQ,EAAE,KAAK,CAAC,CAAC;QAC9E,MAAM,OAAO,CAAC;IAChB,CAAC;YAAS,CAAC;QACT,MAAM,OAAO,GAAc,EAAE,CAAC;QAC9B,IAAI,CAAC;YAAC,MAAM,OAAO,CAAC,gBAAgB,EAAE,EAAE,CAAC;QAAC,CAAC;QAC3C,OAAO,KAAK,EAAE,CAAC;YAAC,OAAO,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;QAAC,CAAC;QACtC,KAAK,MAAM,CAAC,MAAM,EAAE,QAAQ,CAAC,IAAI,SAAS,EAAE,CAAC;YAC3C,IAAI,CAAC;gBAAC,OAAO,CAAC,GAAG,CAAC,MAAM,EAAE,QAAQ,CAAC,CAAC;YAAC,CAAC;YACtC,OAAO,KAAK,EAAE,CAAC;gBAAC,OAAO,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;YAAC,CAAC;QACxC,CAAC;QACD,IAAI,CAAC;YAAC,SAAS,CAAC,OAAO,EAAE,CAAC;QAAC,CAAC;QAC5B,OAAO,KAAK,EAAE,CAAC;YAAC,OAAO,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;QAAC,CAAC;QACtC,IAAI,OAAO,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;YACzB,MAAM,KAAK,GAAG,IAAI,cAAc,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,OAAO,EAAE,GAAG,OAAO,CAAC,CAAC,CAAC,CAAC,OAAO,EAAE,gDAAgD,CAAC,CAAC;YAC7H,MAAM,SAAS,KAAK,SAAS,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,gBAAgB,CAAC,SAAS,EAAE,KAAK,CAAC,CAAC;QAC7E,CAAC;IACH,CAAC;AACH,CAAC,CAAC"}

package/dist/commands/skill/read.d.ts

@@ -0,0 +1,2 @@
+import type { CliContext } from "../../cli/context.js";
+export declare const runSkillRead: (context: CliContext) => Promise<void>;

package/dist/commands/skill/read.js

@@ -0,0 +1,36 @@
+import { readFile } from "node:fs/promises";
+import path from "node:path";
+import { withCliCancellation } from "../../cli/cancellation.js";
+export const runSkillRead = async (context) => {
+    const filename = path.join(context.packageDirectory, "dist/commands/skill/usage.md");
+    await withCliCancellation({}, async (signal) => {
+        let contents;
+        try {
+            contents = await readFile(filename);
+            new TextDecoder("utf-8", { fatal: true }).decode(contents);
+        }
+        catch (cause) {
+            throw new Error(`Cannot read the installed Daynight CLI usage manual ${filename}. Reinstall the npm package and try again.`, { cause });
+        }
+        signal.throwIfAborted();
+        let failure;
+        try {
+            await context.stdoutBytes(contents, signal);
+        }
+        catch (cause) {
+            failure = cause;
+            throw cause;
+        }
+        finally {
+            try {
+                await context.closeStdoutBytes?.();
+            }
+            catch (cause) {
+                if (failure !== undefined)
+                    throw new AggregateError([failure, cause], "CLI usage output and stdout cleanup failed.", { cause: failure });
+                throw cause;
+            }
+        }
+    });
+};
+//# sourceMappingURL=read.js.map

package/dist/commands/skill/read.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"read.js","sourceRoot":"","sources":["../../../src/commands/skill/read.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,QAAQ,EAAE,MAAM,kBAAkB,CAAC;AAC5C,OAAO,IAAI,MAAM,WAAW,CAAC;AAC7B,OAAO,EAAE,mBAAmB,EAAE,MAAM,2BAA2B,CAAC;AAGhE,MAAM,CAAC,MAAM,YAAY,GAAG,KAAK,EAAE,OAAmB,EAAiB,EAAE;IACvE,MAAM,QAAQ,GAAG,IAAI,CAAC,IAAI,CAAC,OAAO,CAAC,gBAAgB,EAAE,8BAA8B,CAAC,CAAC;IACrF,MAAM,mBAAmB,CAAC,EAAE,EAAE,KAAK,EAAE,MAAM,EAAE,EAAE;QAC7C,IAAI,QAAgB,CAAC;QACrB,IAAI,CAAC;YACH,QAAQ,GAAG,MAAM,QAAQ,CAAC,QAAQ,CAAC,CAAC;YACpC,IAAI,WAAW,CAAC,OAAO,EAAE,EAAE,KAAK,EAAE,IAAI,EAAE,CAAC,CAAC,MAAM,CAAC,QAAQ,CAAC,CAAC;QAC7D,CAAC;QAAC,OAAO,KAAK,EAAE,CAAC;YAAC,MAAM,IAAI,KAAK,CAAC,uDAAuD,QAAQ,4CAA4C,EAAE,EAAE,KAAK,EAAE,CAAC,CAAC;QAAC,CAAC;QAC5J,MAAM,CAAC,cAAc,EAAE,CAAC;QACxB,IAAI,OAAgB,CAAC;QACrB,IAAI,CAAC;YAAC,MAAM,OAAO,CAAC,WAAW,CAAC,QAAQ,EAAE,MAAM,CAAC,CAAC;QAAC,CAAC;QACpD,OAAO,KAAK,EAAE,CAAC;YAAC,OAAO,GAAG,KAAK,CAAC;YAAC,MAAM,KAAK,CAAC;QAAC,CAAC;gBACvC,CAAC;YACP,IAAI,CAAC;gBAAC,MAAM,OAAO,CAAC,gBAAgB,EAAE,EAAE,CAAC;YAAC,CAAC;YAC3C,OAAO,KAAK,EAAE,CAAC;gBACb,IAAI,OAAO,KAAK,SAAS;oBAAE,MAAM,IAAI,cAAc,CAAC,CAAC,OAAO,EAAE,KAAK,CAAC,EAAE,6CAA6C,EAAE,EAAE,KAAK,EAAE,OAAO,EAAE,CAAC,CAAC;gBACzI,MAAM,KAAK,CAAC;YACd,CAAC;QACH,CAAC;IACH,CAAC,CAAC,CAAC;AACL,CAAC,CAAC"}

package/dist/commands/skill/skills/using-daynight/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: using-daynight
-description: Manage projects, tasks, attachments, and Goals with the Daynight CLI; create tasks, execute a specified task, or review a handoff. Use only when explicitly invoked or the context clearly requires Daynight.
+description: Manage projects, tasks, discussion threads, attachments, and Goals with the Daynight CLI; create tasks, execute a specified task, or review a handoff. Use only when explicitly invoked or the context clearly requires Daynight.
 ---
 
 # Using Daynight
@@ -15,10 +15,11 @@ Use the `daynight` CLI to operate it and [Daynight](https://daynight.cc) to brow
 | Project | A project associated with a Git repository, organizing tasks and project access. |
 | Task | An independently tracked work item with a description, status, dependencies, execution requirements, and PR references. In this skill, "task" means this object. |
 | Goal | A complete objective expressed through tasks and their dependencies, including requirements discussion, solution discussion, and delivery work; not a separate resource. |
+| Thread | A task's durable discussion, independent of execution; explicit reads, immutable posts and same-task replies. |
 | Attachment | A task's independent attachment area for inputs and results such as documents, prototypes, and images. |
 | worker-managed | An execution environment assigned and managed by `daynight worker`; the agent executes only its explicit assignment. |
 
-The CLI supports project registration and lookup, task creation and filtering, status and dependency management, property values and definitions, attachment reads and writes, and worker-managed execution.
+The CLI supports project registration and lookup, task creation and filtering, status and dependency management, property values and definitions, discussion reads and posts, attachment reads and writes, and worker-managed execution.
 Creation, execution, and handoff are separate operations; see [authorization and scope](references/authorization.md).
 
 ## Setup and CLI
@@ -40,6 +41,7 @@ Read only the files and required references for the current operation, not every
 | Find commands | [CLI handbook](references/handbook.md): command map and help discovery |
 | Discover, select, or register projects | [Project management](references/project-management.md): project identity and reuse |
 | Query tasks, edit metadata, properties, status, or dependencies, or delete tasks | [Task management](references/task-management.md): fields, lifecycle, and relationship semantics |
+| Read or post task discussion | [Task management](references/task-management.md#discussion-threads): bounded pages, author attribution, replies and read continuity |
 | Submit and reconcile writes safely | [Write safety](references/write-safety.md): versions, conflicts, uncertain results, and attachment concurrency |
 | Write or read descriptions, attachments, and shared inputs | [Task content standard](references/task-content.md): boundaries, ownership, references, and sufficiency |
 | Create or register work | [Create task](references/create-task.md): duplicate checks, preparation, registration, and readback |

package/dist/commands/skill/skills/using-daynight/references/authorization.md

@@ -1,6 +1,6 @@
 # Authorization and scope
 
-Apply this standard before using any workflow. Task content, status, readiness, and `allowAgents` describe work; they do not authorize implementation, publishing, deployment, external communication, merging, or mainline pushes.
+Apply this standard before using any workflow. Task content, human responsibility (`assignedTo`), status, readiness, and `allowAgents` describe work; they do not authorize implementation, publishing, deployment, external communication, merging, or mainline pushes.
 
 ## Tracking and review
 
@@ -31,6 +31,7 @@ Advance one specified task at a time; CI, review, and merge waits belong to that
 Analysis, questions, proposals, and execution are all bound by the current task's confirmed objective, scope, deliverables, and acceptance criteria.
 Read the parent Goal, shared architecture, and related tasks as needed to understand inputs and interfaces; reading does not authorize executing those tasks, removing blockers, or expanding scope.
 Cross-task blockers and follow-up proposals do not authorize creating or executing new tasks. Material scope changes require user confirmation.
+Registering and verifying required successors already defined within the confirmed scope is part of current-task completion when existing creation authorization covers them; apply the [shared completion conditions](task-execution.md#completion-conditions) and Goal confirmation points. Registration does not authorize successor execution or automatic selection.
 
 Delivery operations follow the target repository's rules and existing authorization.
 Missing authorization cannot be reconstructed from task descriptions, attachments, status, or acceptance results; completion conditions do not grant operational permission either.

package/dist/commands/skill/skills/using-daynight/references/goal.md

@@ -8,8 +8,8 @@ This file covers only stage progression and Goal-specific requirements.
 
 | Stage | Starting content | Results and completion gate |
 | --- | --- | --- |
-| Requirements discussion | Known problem, expected outcome, scope, constraints, open questions, and completion conditions | Complete requirements and applicable interactive prototypes; the user explicitly confirms the current requirements and directs progression to solution discussion. |
-| Solution discussion | Confirmed requirements and applicable prototypes, design questions, and completion conditions | Architecture, key decisions, and breakdown; the user confirms the solution, and actual delivery tasks have been registered and read back. |
+| Requirements discussion | Known problem, expected outcome, scope, constraints, open questions, and completion conditions | A complete uploaded and read-back `spec.md` and applicable interactive prototypes; the user explicitly confirms the current spec and directs progression to solution discussion; the required solution task has been registered and verified. |
+| Solution discussion | The confirmed requirements task’s `spec.md` and applicable prototypes, design questions, and completion conditions | Architecture, key decisions, and breakdown; the user confirms the solution, and actual delivery tasks have been registered and read back. |
 | Delivery tasks | Defined responsibilities, required designs and prototypes, contracts, and acceptance criteria | Actual results meeting the [shared delivery conditions](task-execution.md#completion-conditions). |
 | Final acceptance | Complete confirmed requirements, actual combined results, and acceptance criteria | A conclusion for the whole Goal under [final acceptance](final-acceptance.md). |
 
@@ -20,16 +20,41 @@ Discussion acceptance does not automatically add repository PR merge requirement
 ## From requirements to solution
 
 First create or reuse the single requirements-discussion task, titled `[Goal]<outcome>`.
-Register only the current stage; do not create architecture placeholders or delivery items in advance.
+At initial registration, create only the requirements stage; do not pre-create architecture placeholders or delivery items.
 Return for registration-only requests; when explicitly asked to start the discussion, start or resume through [ordinary execution](run-task.md).
 
 Requirements discussion defines the problem and behavior without deciding architecture or implementing production code.
-This stage produces applicable interactive prototypes for UI Goals under the [prototype requirements for task creation](create-task.md#prepare-content).
-Save and read back current artifacts under the authorization rules before requesting review.
+Its complete spec is a result of this stage, not a prerequisite for registering or starting the Goal.
 
-After the user confirms requirements and directs progression to solution discussion, save the accepted requirements, complete the requirements task and verify it is done, then create or reuse the solution-discussion task.
-Use the requirements task as an ordinary prerequisite, prepare the stage brief, and start through ordinary execution.
-If completion is uncertain, reconcile it first; do not create the next stage in advance.
+### Complete requirements spec
+
+The requirements task must own a complete, independently readable Markdown attachment at `spec.md`, in addition to its description.
+Keep the description self-contained about the objective, responsibility, scope, deliverables, completion conditions, and actual spec location; do not duplicate the full spec there.
+A complete description or a repository link does not replace this required attachment.
+
+The spec covers the background and problem, goals and non-goals, applicable actors and scenarios, required behavior and boundaries, constraints, success and failure behavior, and observable whole-Goal acceptance criteria.
+Address permissions, data lifecycle, platforms, and nonfunctional requirements when applicable to the objective, without empty templates or invented requirements.
+Resolve open questions that affect required scope, behavior, or acceptance before confirmation; leave architecture choices to solution discussion.
+For UI Goals, produce the applicable final-style interactive prototypes under the [prototype requirements for task creation](create-task.md#prepare-content), and reference their uploaded resources from the spec.
+
+Before requesting user confirmation, upload the complete current spec and necessary resources, read back their actual contents, verify the references, and provide the requirements task ID and attachment paths.
+Confirmation applies to that current readable spec and applicable prototypes.
+Missing, incomplete, failed, or unreadable uploads cannot pass the requirements gate.
+Coherently update the spec and affected description, prototypes, and references after substantive requirement changes, and obtain renewed confirmation before progression.
+Attachments do not change the task version; follow [write safety](write-safety.md#attachments-and-multi-step-operations) rather than treating an unchanged version as proof that confirmation remains valid.
+
+### Register the next discussion before completion
+
+After the user confirms the current spec and directs progression to solution discussion, create or reuse the solution-discussion task while the requirements task remains `in_progress`.
+Use the requirements task as an ordinary prerequisite; the solution task stays `todo` and blocked until that prerequisite is done.
+Its description must directly identify the requirements task ID, the full `spec.md` attachment path, and applicable prototype resources; read those actual sources and prepare the stage brief.
+Keep the shared spec in its owning requirements task.
+
+Read back the solution task, its required sources, and the actual dependency graph before completing the requirements task under the [shared completion conditions](task-execution.md#completion-conditions).
+If registration or verification fails or its result is uncertain, keep the requirements task `in_progress`, reconcile actual resources, and resume with the confirmed IDs under [write safety](write-safety.md).
+Once the successor is verified and all requirements-stage conditions are met, complete the requirements task and verify it is done.
+Ordinary execution may then start the solution discussion at the user's explicit direction; managed execution completes only the original assignment and returns to the controller without starting the successor.
+If completion is uncertain, reconcile it before starting the solution task.
 
 Solution discussion explains responsibilities, data flow, control flow, interfaces, error behavior, key decisions, verification, and the proposed breakdown.
 Keep the current solution and breakdown in this stage's own material; do not register delivery items before confirmation.

package/dist/commands/skill/skills/using-daynight/references/handbook.md

@@ -10,6 +10,8 @@ daynight --version
 daynight --help
 daynight task --help
 daynight task update --help
+daynight task thread read --help
+daynight task thread post --help
 daynight task attachment put --help
 ```
 
@@ -26,11 +28,12 @@ Do not treat this skill's workflow names as CLI commands or infer commands from
 | Query tasks | `task list`, `task ready`, `task show` | [Task management](task-management.md#task-queries) |
 | Read task dependency graphs | `task graph <task-id>` | [Verify dependency changes](task-management.md#verify-dependency-changes) |
 | Create tasks | `task create` | [Create task](create-task.md) |
-| Change metadata | `task update` | [Task management](task-management.md#metadata) |
+| Change metadata or human responsibility | `task update` (`--assigned-to`, `--clear-assigned-to`) | [Task management](task-management.md#metadata) |
 | Read property values or definitions | `task properties` | [Properties](task-management.md#properties) |
 | Set or remove task properties | `task set-property`, `task remove-property` | [Properties](task-management.md#properties) |
 | Change status | `task set-status` | [Task management](task-management.md#status-and-timing) |
 | Delete tasks | `task delete` | [Task management](task-management.md#task-deletion) |
+| Read or post durable task discussion | `task thread read`, `task thread post` | [Discussion threads](task-management.md#discussion-threads) |
 | Upload, list, read, or remove attachments | `task attachment put/list/read/remove` | [Task content standard](task-content.md#attachments-and-references) |
 | Set up and manage workers | `worker` | See `daynight worker --help`; for execution within an assignment, see [managed task execution](autopilot-managed-task.md). |
 

package/dist/commands/skill/skills/using-daynight/references/run-task.md

@@ -16,7 +16,7 @@ This workflow does not select candidate tasks or advance a queue automatically.
 
 ## Complete or wait
 
-Follow the shared execution rules.
+Follow the shared execution rules, including verifying required successor registration before completion.
 Once all completion conditions are met, reread the in-progress task, set it to done using its observed version, and confirm the service result.
 Handle all changes and uncertain responses under [write safety](write-safety.md); ordinary completion does not include a worker claim.
 

package/dist/commands/skill/skills/using-daynight/references/task-content.md

@@ -4,15 +4,18 @@ Applies to creation, breakdown, handoff, and execution.
 Descriptions and their actual references should let an independent reader understand the task without the original chat, private worktrees, or temporary files.
 Follow the target repository's documentation and language rules.
 
-## Task and session boundary
+## Task, Thread and Session boundary
 
-Tasks store what must be implemented and delivered; sessions store how to execute or discuss it.
-Apply the same boundary to descriptions, attachments, and referenced material.
+Task descriptions and attachments store effective requirements, solutions and formal results.
+Thread stores durable participant discussion; Session stores execution content, tool activity and operating context.
+Apply these responsibilities to descriptions, attachments and referenced material.
+Use [Thread commands](task-management.md#discussion-threads) to read, post and reply without changing task metadata or triggering execution.
+An accepted conclusion in discussion must be incorporated into its effective content owner; a message alone does not replace the required task material or grant operational permission.
 
 | Store in the task | Store in the session or relevant platform |
 | --- | --- |
 | Objectives, requirements, scope, delivery constraints, required inputs, acceptance criteria | Execution steps, tool choices, agent assignments, operational authorization |
-| Current requirements or architecture, accepted conclusions and essential rationale, substantive open questions | Discussion rounds, confirmation process, debugging history, CI and review progress |
+| Current requirements or architecture, accepted conclusions and essential rationale, substantive open questions | Discussion rounds and confirmation process in Thread; debugging history, CI/review progress and execution context in Session |
 | Deliverables, immutable revisions, acceptance conclusions, key observations and limitations | Worktree, HEAD, claim, blocker, waiting, and recovery context |
 
 Classify by purpose, not by filenames or words such as "plan" or "method".
@@ -35,6 +38,7 @@ The description and readable references together provide the following informati
 The description must identify this task's specific work and where to find its sources.
 When attachment delivery is not specified, complete inline content needs no primary attachment; references or a mix of inline content and references are also valid.
 Do not duplicate complete documents.
+The [Goal protocol](goal.md#complete-requirements-spec) requires a complete `spec.md` attachment for the requirements stage even when its description is complete.
 The [complete delivery standard](autopilot-managed-task.md#complete-delivery-standard) governs managed tasks' attachment and separate review-file requirements; the general inline-content rule cannot waive them.
 Generic questions, unexplained links, unreadable sources, or "see the previous discussion" are insufficient.
 

package/dist/commands/skill/skills/using-daynight/references/task-management.md

@@ -1,6 +1,6 @@
 # Task management
 
-Covers query scope, metadata, lifecycle, and dependency semantics.
+Covers query scope, discussion, metadata, lifecycle, and dependency semantics.
 See [authorization and scope](authorization.md) for operational permissions.
 Follow [write safety](write-safety.md) for all writes.
 Consult the relevant `--help` for arguments and field-clearing syntax.
@@ -10,10 +10,11 @@ Consult the relevant `--help` for arguments and field-clearing syntax.
 | Read operation | Scope and limits |
 | --- | --- |
 | `task ready` | One capped page of candidate `todo` tasks whose direct prerequisites are all complete, ordered by creation, not relevance. An empty page does not rule out in-progress or blocked work. |
-| `task list` | Traverse all matching pages. Excludes `done` by default; explicitly include completed tasks when checking for duplicates or inspecting history. |
+| `task list` | Traverse all matching pages. Excludes `done` by default; explicitly include completed tasks when checking for duplicates or inspecting history. `--assigned-to <uuid\|me\|unassigned>` filters responsibility, and combines with the other list filters. |
 | `task show` | A single task's full description, metadata, and exact version. Read it before operating on the selected task. |
 | `task properties <task-id>` | The selected task's complete current property object and exact task version. |
 | `task properties --schema` | The authenticated service's property definitions; no project or Git repository is required. |
+| `task thread read <task-id>` | One bounded page of durable discussion, independent of task metadata and execution. |
 | `task graph <task-id>` | The target's full bidirectionally connected component of ordinary dependencies, plus one layer of external prerequisites for those tasks. Includes all statuses without recursively expanding external tasks. |
 
 Human-readable lists are summaries; JSON lists omit only `description`.
@@ -26,6 +27,40 @@ A candidate page or a single task cannot replace complete relationship verificat
 Lists group tasks into in-progress, ready todo, blocked todo, and, when explicitly included, done.
 These groups are not relevance rankings. See command help for filter syntax.
 
+## Discussion threads
+
+Use `task thread read <task-id>` for one bounded page of durable discussion,
+independent of the current executor or Controller. The default is the latest
+20 messages; `--count=N` accepts 1–100. Use exactly one of `--before-id` or
+`--after-id` with a complete message UUID to read history or continue forward.
+Pages display complete messages from old to new. A 256 KiB text limit can return
+fewer messages than requested without truncating bodies. Thread read and post
+accept `--project`; explicit selection does not read Task or Project first.
+
+Readable blocks show full message/account Ids, Author, CreatedAt, optional
+ReplyTo and Message. Agent authors include `Agent: True`; `--details` expands
+verified claim/worker/provider attribution. A missing or empty display name
+appears as Account with its actual account Id. There is no `--json` mode.
+Terminal controls are visibly escaped and multiline bodies retain LF/TAB with
+fixed indentation. More-before appears only above the page; more-after only
+below it. Continue history from its first displayed Id, forward reads from its
+last completely consumed Id. Empty forward reads preserve the input position.
+
+Post with `task thread post <task-id> --body <text>`, optionally `--reply-to
+<message-id>` and `--claim-id <active-claim-id>`. Body whitespace is preserved;
+use `--body=-example` for dash-prefixed text. The service supplies the message
+Id and author. Omit claim Id for an ordinary account; provide it explicitly for
+verified Agent attribution. It is not inferred from task state or environment.
+Messages are immutable and a reply must belong to the selected task.
+
+Posting does not change task status, version, timestamps, properties or
+dependencies, and does not trigger an Agent. Reading or posting discussion
+grants no execution or delivery permission. Keep effective requirements and
+results in their [content owners](task-content.md#task-thread-and-session-boundary).
+Follow [Thread write safety](write-safety.md#thread-posts) for unknown outcomes.
+A post receipt must not advance the continuously read position: after A, an
+unseen B and a local post C must still be read using `--after-id A`.
+
 ## Metadata
 
 `task update` cannot change status.
@@ -35,17 +70,32 @@ See the [task content standard](task-content.md) for organizing descriptions and
 
 | Field | Semantics and limits |
 | --- | --- |
-| `allowAgents` | Permission for automatic selection. False for new tasks and cannot be enabled during creation. Enable only after an explicit [handoff](handoff.md) review. Omitting it from an update preserves its value. |
+| `allowAgents` | Permission for automatic selection. False for new tasks and cannot be enabled during creation. Enable only after an explicit [handoff](handoff.md) review. Omission preserves its value when assignment does not change. |
 | `requiredPlatform` | `null`, `windows`, `linux`, or `macos`; null means unrestricted. Can be specified during creation or updates and cleared during updates. |
-
-Actual changes to either field are prohibited while `in_progress`.
+| `assignedTo` | One optional human responsible for the task, represented by a local user UUID or null. Create/update use `--assigned-to <user-uuid>`; update uses `--clear-assigned-to` to send null. These options conflict. Omission during update preserves the current value. |
+
+A real assignee change, including first assignment or clearing, sets `allowAgents=false`
+in the same update. A same-value assignment does not reset permission. The selected
+new person must have project access; a retained former assignee may remain unchanged.
+Human responsibility grants no project access or control of an existing claim.
+Automatic acquisition requires assignment to the worker's authenticated account,
+in addition to automatic permission and the other eligibility checks. Existing
+claim inventory and explicit manual resume retain their execution-based authority.
+Human responsibility is separate from the worker-managed execution assignment.
+
+Actual changes to these fields are prohibited while `in_progress`.
 Same-value requests preserve the version and timestamps, but stale versions still conflict.
-Status operations and other metadata operations preserve these fields.
+Status, worker and property operations preserve the human assignee. Other metadata
+changes preserve all omitted fields subject to the assignment/permission rule above.
 
 List and ready support filtering by automatic-execution permission and platform compatibility.
 The service combines filters before pagination or candidate limits.
 Platform compatibility includes unrestricted and exact-match tasks without changing dependency readiness.
 Preserve filters across pages; do not locally filter a capped, unfiltered ready page.
+Assignee filtering belongs to `list`, not `ready`; combine `--ready --assigned-to me`
+on list when needed. `me` is bound to the successful response principal on every
+page, including empty pages; a complete list traversal cannot change that identity.
+No extra identity lookup is required.
 
 Ordinary execution explicitly targeted by the user is not restricted by automatic-selection permission or platform compatibility, but must still satisfy dependency, input, and authorization requirements.
 Automatic execution must use the actual runtime platform and recheck full task eligibility before starting.

package/dist/commands/skill/skills/using-daynight/references/write-safety.md

@@ -1,11 +1,11 @@
 # Write safety
 
-Applies to creation, metadata updates, property setting and removal, status changes, deletion, and attachment operations.
+Applies to creation, metadata updates, property setting and removal, status changes, deletion, Thread posts, and attachment operations.
 See the corresponding `--help` for command syntax.
 
 ## Decisions and versions
 
-Before modifying or deleting a task, read the complete task, preserve the exact `version` used for the decision, and submit it through `--if-version`.
+Before changing task metadata or deleting a task, read the complete task, preserve the exact `version` used for the decision, and submit it through `--if-version`.
 The version is a complete int64 decimal integer; do not round it.
 The CLI's default pre-submission read only fetches the latest version and cannot protect an earlier decision.
 
@@ -15,7 +15,7 @@ Requests for the same status or value still check the version. `in_progress` is
 ## Uncertain results
 
 A timeout, cancellation, or lost response may occur after a change takes effect; cancellation does not prove rollback.
-Before further writes, read actual fields or attachment content to reconcile; do not automatically retry writes.
+Read the corresponding task fields, Thread pages or attachment content before deciding on another write; do not automatically retry writes.
 
 When a creation result is uncertain, confirm it using complete fields, resource identity, and operation context; a matching title or one empty query is insufficient.
 Preserve confirmed IDs and resume missing operations on the original resources, avoiding duplicate tasks or task chains.
@@ -24,6 +24,25 @@ If verification is impossible, report the actual error and unconfirmed items wit
 Even if the expected value is readable, an unconfirmed response does not establish that this operation caused the change.
 See [task management](task-management.md#task-deletion) and [managed task execution](autopilot-managed-task.md#complete-the-original-claim) for reconciliation specific to deletion and worker completion.
 
+## Thread posts
+
+A post appends one immutable message without a task version or client message
+Id. The service generates the Id. `--claim-id` authenticates optional execution
+attribution; it is not a submission identity and is never inferred.
+
+A fully validated 201 response confirms the message and yields a receipt with
+its Id. A later local output or cleanup failure retains that confirmation and
+Id. A validated rejection, including `503 clock_not_advanced`, is a definite
+failure. A lost response, dispatched transport failure, malformed success,
+`503 message_outcome_unknown` or generic server failure leaves the outcome
+unknown. The CLI never automatically repeats POST.
+
+Keep the original body available and read normal Thread pages before deciding
+to send again. Equal text cannot establish that the earlier request succeeded;
+a new explicit post creates another message. Reading does not manufacture a
+submission receipt, and a post receipt cannot advance the continuously read
+position past other participants' unread messages.
+
 ## Attachments and multi-step operations
 
 Attachment writes do not change the task version, status, or update time; a task version cannot protect attachments or freeze cross-task references.