@skrr-ai/cli 0.1.41 → 0.1.42

package/dist/lib/task-closure.js

@@ -2,6 +2,7 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.closureSnapshotLines = exports.describeAssessor = void 0;
 exports.closureReport = closureReport;
+exports.reopenRequiredLines = reopenRequiredLines;
 const data_provider_1 = require("@skrr-ai/data-provider");
 function isUnavailable(closure) {
     return Boolean(closure && closure.unavailable);
@@ -82,6 +83,22 @@ function closureReport(closure) {
         : 'Closing anyway is allowed — all of this is recorded on resolution.closure.');
     return lines;
 }
+/**
+ * The ways forward when a closed Task refuses a Result (`TASK_REOPEN_REQUIRED`).
+ *
+ * Both writers reach this refusal, `tasks result submit` and `tasks complete`,
+ * so both print from here. The first version sat in `result submit` alone and
+ * offered `tasks complete` as a way around it, which the same refusal stops:
+ * every step named here has to work on a closed Task (OSK-10031).
+ */
+function reopenRequiredLines({ bin, task, command, }) {
+    return [
+        `→ Reopen it: ${bin} tasks move ${task} --status in_progress`,
+        command === 'complete'
+            ? '→ Then run this command again.'
+            : `→ Then submit again, or submit and close in one step: ${bin} tasks complete ${task} --summary "…"`,
+    ];
+}
 /** `met (agent)` vs `met (person)` — shared with the web through data-provider. */
 var data_provider_2 = require("@skrr-ai/data-provider");
 Object.defineProperty(exports, "describeAssessor", { enumerable: true, get: function () { return data_provider_2.describeAssessorKind; } });