@skrr-ai/cli 0.1.14 → 0.1.17

package/dist/lib/tasks.js

@@ -1,9 +1,12 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.RECOGNIZED_TASK_VERDICTS = exports.TASK_WORK_EVENT_KINDS = exports.TASK_PRIORITIES = void 0;
+exports.RECOGNIZED_TASK_VERDICTS = exports.DELIVERABLE_LIFECYCLE_VALUES = exports.EXPECT_FLAG_HELP = exports.TASK_WORK_EVENT_KINDS = exports.TASK_PRIORITIES = void 0;
 exports.releasePinRepairGuard = releasePinRepairGuard;
 exports.taskUpdateMutationGuard = taskUpdateMutationGuard;
 exports.executionIsolationFromWorktreeFlag = executionIsolationFromWorktreeFlag;
+exports.parseExpectation = parseExpectation;
+exports.parseExpectations = parseExpectations;
+exports.parseDeliverableCoordinate = parseDeliverableCoordinate;
 exports.buildTaskCreatePayload = buildTaskCreatePayload;
 exports.boundSessionAgentId = boundSessionAgentId;
 exports.applyDaemonSessionDefaults = applyDaemonSessionDefaults;
@@ -106,8 +109,95 @@ function executionIsolationFromWorktreeFlag(worktree) {
         return undefined;
     return worktree ? 'ephemeral' : 'shared';
 }
+/**
+ * Parse an expectation spec.
+ *
+ * DELEGATES to `@skrr-ai/data-provider`, which owns the grammar and is read by
+ * the API and the web client too. The copy this replaces validated correctly
+ * and then described a syntax it refused — its messages named three different
+ * flags (`--requires`, `--output`, `--accept`) and used `git_ref:origin/main`
+ * as the example, a value the same function rejects. For an agent the refusal
+ * IS the documentation: it hits the error and corrects, so an error naming a
+ * rejected example costs a whole turn and can loop.
+ */
+function parseExpectation(spec) {
+    return (0, data_provider_1.parseExpectationSpec)(spec);
+}
+/** Parse several, failing on the first that cannot be read. */
+function parseExpectations(specs) {
+    if (!specs || specs.length === 0) {
+        return { ok: true, value: [] };
+    }
+    const out = [];
+    for (const spec of specs) {
+        const parsed = (0, data_provider_1.parseExpectationSpec)(spec);
+        if (!parsed.ok) {
+            return parsed;
+        }
+        out.push(parsed.value);
+    }
+    return { ok: true, value: out };
+}
+/**
+ * The one-line help every expectation flag shares, so they cannot disagree.
+ *
+ * The vocabulary is read from the owning package, but DEFENSIVELY: oclif
+ * evaluates a flag `description` when the command class body runs, i.e. at
+ * module load, and several suites mock `@skrr-ai/data-provider` with an
+ * explicit allow-list that predates these exports. Under such a mock the arrays
+ * are `undefined`, and a HELP STRING is never worth failing a module load for —
+ * the fallbacks below are a test-environment courtesy, never the vocabulary
+ * anything is validated against. `parseExpectationSpec` runs at call time
+ * against the real module and remains the only authority.
+ */
+const kindsForHelp = Array.isArray(data_provider_1.TASK_OUTCOME_KINDS)
+    ? data_provider_1.TASK_OUTCOME_KINDS.join(', ')
+    : 'code, page, url, file, message, dataset';
+const presetsForHelp = Array.isArray(data_provider_1.EXPECTATION_PRESETS)
+    ? data_provider_1.EXPECTATION_PRESETS.map((preset) => `@${preset.key}`).join(', ')
+    : '@merged-to-main, @pdf-delivered';
+exports.EXPECT_FLAG_HELP = 'What this task must produce, as <kind>[/<format>][:<target>] or @<preset> — ' +
+    `e.g. 'code:origin/main', 'file/pdf:Drive/Reports', '@merged-to-main'. ` +
+    `Kinds: ${kindsForHelp}. Presets: ${presetsForHelp}. ` +
+    'Anything else is stored as a plain-language expectation a person settles. Repeatable.';
+/**
+ * Parse a deliverable coordinate. Also delegated — `:` and `@` and now `/` all
+ * mean different things, and a second implementation of that grammar is how the
+ * declaring side and the recording side stop agreeing.
+ */
+function parseDeliverableCoordinate(spec) {
+    return (0, data_provider_1.parseDeliverableCoordinate)(spec);
+}
+/** Lifecycle values a caller may assert, for flag validation. */
+exports.DELIVERABLE_LIFECYCLE_VALUES = data_provider_1.DELIVERABLE_LIFECYCLES;
+/**
+ * `--from-json` takes stored API field names, while the interactive flags use
+ * shorter names such as `--project` and `--spawned-by`. Normalize the obvious
+ * camel-case forms before a permissive API route can silently drop them.
+ */
+function normalizeTaskCreateJsonAliases(body) {
+    const normalized = { ...body };
+    const aliases = [
+        ['parent', 'parentId'],
+        ['space', 'spaceId'],
+        ['goal', 'goalId'],
+        ['commitment', 'commitmentId'],
+        ['project', 'projectId'],
+        ['cycle', 'cycleId'],
+        ['spawnedBy', 'spawnedByTaskId'],
+    ];
+    for (const [alias, canonical] of aliases) {
+        if (Object.prototype.hasOwnProperty.call(normalized, canonical))
+            continue;
+        if (!Object.prototype.hasOwnProperty.call(normalized, alias))
+            continue;
+        normalized[canonical] = normalized[alias];
+        delete normalized[alias];
+    }
+    return normalized;
+}
 function buildTaskCreatePayload(body, flags = {}) {
-    const payload = (0, prompt_1.mergeDefined)(body, {
+    const payload = (0, prompt_1.mergeDefined)(normalizeTaskCreateJsonAliases(body), {
         templateId: flags.template,
         title: flags.title,
         description: flags.description,
@@ -123,6 +213,7 @@ function buildTaskCreatePayload(body, flags = {}) {
         assigneeAgentIds: flags['assignee-agent'],
         assigneeUserIds: flags['assignee-user'],
         executionMode: flags['execution-mode'],
+        expectations: flags.expectations,
         startDate: flags['start-date'],
         dueDate: flags['due-date'],
         estimate: flags.estimate,