@skrr-ai/cli 0.1.10 → 0.1.12

package/dist/commands/goals/revisions.js

@@ -4,6 +4,20 @@ const core_1 = require("@oclif/core");
 const data_provider_1 = require("@skrr-ai/data-provider");
 const base_command_1 = require("../../base-command");
 const format_1 = require("../../lib/format");
+/**
+ * The one class of goal change this log does not contain.
+ *
+ * `PATCH /api/goals/:goalId/planner-config` writes the goal through
+ * `Goal.findOneAndUpdate` directly rather than `GoalModel.updateGoal`, which is
+ * where `RevisionService` is called from — so arming, re-timing or disarming the
+ * auto-planner (and any `maxActiveTasks` change made through that route) leaves
+ * no revision. "Who turned the planner on for this goal, and when" is the audit
+ * question a shared goal actually raises, and the table answers it with silence.
+ *
+ * Naming the gap is the honest thing the CLI can do; closing it is a server
+ * change. DELETE THIS FOOTER once the planner-config route records a revision.
+ */
+const PLANNER_GAP_NOTE = 'Note: auto-planner changes made with `goals planner-config` are not recorded as revisions.';
 class GoalsRevisions extends base_command_1.BaseCommand {
     static description = 'List revisions for a goal';
     static examples = [
@@ -33,6 +47,7 @@ class GoalsRevisions extends base_command_1.BaseCommand {
         const items = result?.data ?? [];
         if (items.length === 0) {
             this.log('No revisions.');
+            this.log(PLANNER_GAP_NOTE);
             return;
         }
         const rows = items.map((rev) => ({
@@ -49,6 +64,8 @@ class GoalsRevisions extends base_command_1.BaseCommand {
             { key: 'changes', header: 'FIELDS' },
             { key: 'when', header: 'AT' },
         ], (line) => this.log(line));
+        this.log('');
+        this.log(PLANNER_GAP_NOTE);
     }
 }
 exports.default = GoalsRevisions;

package/dist/commands/goals/show.d.ts

@@ -1,4 +1,12 @@
 import { BaseCommand } from '../../base-command';
+/**
+ * The completion row, labelled by what it counts.
+ *
+ * `null`/absent is rendered `-` rather than `0%`: the server returns null when a
+ * goal has NO linked tasks, and printing 0% there says "nothing is done" about a
+ * denominator that does not exist.
+ */
+export declare function taskCompletionLine(completionPercent: unknown): string;
 export default class GoalsShow extends BaseCommand {
     static description: string;
     static examples: string[];
@@ -9,4 +17,13 @@ export default class GoalsShow extends BaseCommand {
         json: import("@oclif/core/lib/interfaces").BooleanFlag<boolean>;
     };
     run(): Promise<void>;
+    /**
+     * The goal's key results, best-effort.
+     *
+     * A second request, and a failure here must not take the goal down with it —
+     * `goals show` answering "here is your goal, minus its key results" is far
+     * better than answering nothing. `null` distinguishes "could not read" from
+     * "there are none", so neither view claims an empty OKR.
+     */
+    private readKeyResults;
 }

package/dist/commands/goals/show.js

@@ -1,9 +1,37 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
+exports.taskCompletionLine = taskCompletionLine;
 const core_1 = require("@oclif/core");
 const data_provider_1 = require("@skrr-ai/data-provider");
 const base_command_1 = require("../../base-command");
+const format_1 = require("../../lib/format");
 const web_url_1 = require("../../lib/web-url");
+const planner_config_1 = require("./planner-config");
+/**
+ * What `_completionPercent` actually measures.
+ *
+ * `GoalEnrichment.enrichGoalCompletion` computes it as done ÷ total over the
+ * goal's LINKED TASKS. Key-result progress is a parallel axis that never enters
+ * it. Rendering that number under the bare label `Progress:` on an OKR goal made
+ * it read as "the goal is half achieved" when it meant "1 of the 2 tasks I
+ * linked is closed" — dogfooded on a goal whose two key results were at 25% and
+ * 40% while the goal reported 0%.
+ *
+ * So the label names its own denominator, and the key results are printed
+ * beside it rather than left to a second command nobody knows to run.
+ */
+const TASK_COMPLETION_NOTE = 'share of linked tasks closed — key results are a separate axis';
+/**
+ * The completion row, labelled by what it counts.
+ *
+ * `null`/absent is rendered `-` rather than `0%`: the server returns null when a
+ * goal has NO linked tasks, and printing 0% there says "nothing is done" about a
+ * denominator that does not exist.
+ */
+function taskCompletionLine(completionPercent) {
+    const value = typeof completionPercent === 'number' ? `${Math.round(completionPercent)}%` : '-';
+    return `Tasks done:  ${value}  (${TASK_COMPLETION_NOTE})`;
+}
 class GoalsShow extends base_command_1.BaseCommand {
     static description = 'Show details for a single goal';
     static examples = [
@@ -28,11 +56,14 @@ class GoalsShow extends base_command_1.BaseCommand {
         }
         const g = goal;
         const url = (0, web_url_1.goalUrlFrom)(this.cliConfig.baseURL, g);
+        const planner = (0, planner_config_1.goalPlannerView)(g);
+        const keyResults = await this.readKeyResults(args.id);
         if (flags.json) {
-            this.log(JSON.stringify({ ...g, url }, null, 2));
+            // Additive: the server's own fields are passed through untouched, with
+            // the derived planner reading and the goal's key results beside them.
+            this.log(JSON.stringify({ ...g, url, planner, keyResults }, null, 2));
             return;
         }
-        const progress = g._completionPercent;
         this.log(`ID:          ${g.id ?? g._id ?? '-'}`);
         this.log(`Title:       ${g.title ?? '-'}`);
         if (url)
@@ -47,12 +78,68 @@ class GoalsShow extends base_command_1.BaseCommand {
         this.log(`Target date: ${g.targetDate ? String(g.targetDate).slice(0, 10) : '-'}`);
         this.log(`DRI:         ${g._driName ?? g.driUserId ?? g.driAgentId ?? '-'}`);
         this.log(`Owner Agent: ${g.ownerAgentId ?? '-'}`);
-        this.log(`Progress:    ${typeof progress === 'number' ? `${Math.round(progress)}%` : '-'}`);
+        this.log(taskCompletionLine(g._completionPercent));
+        // The single most consequential piece of state on a goal — a recurring
+        // automation that creates tasks, and optionally starts agents on them —
+        // was readable only through `--json` field names you had to know in
+        // advance, or by WRITING to `planner-config`.
+        this.log('');
+        this.log('Planner:');
+        for (const line of (0, planner_config_1.renderGoalPlannerLines)(planner)) {
+            this.log(line);
+        }
+        this.log('');
+        if (keyResults === null) {
+            this.log('Key results: (not readable — see the warning above)');
+        }
+        else if (keyResults.length === 0) {
+            this.log('Key results: none');
+            this.log(`  Add one with \`${this.config.bin} goals key-results create ${args.id} --title ...\``);
+        }
+        else {
+            this.log('Key results:');
+            (0, format_1.renderTable)(keyResults
+                .slice()
+                .sort((a, b) => (a.order ?? 0) - (b.order ?? 0))
+                .map((kr) => {
+                const value = (0, data_provider_1.resolveKeyResultProgress)(kr);
+                return {
+                    progress: typeof value === 'number' ? `${Math.round(value)}%` : '-',
+                    status: String(kr.status ?? '-'),
+                    mode: String(kr.progressMode ?? '-'),
+                    title: String(kr.title ?? '-'),
+                };
+            }), [
+                { key: 'progress', header: 'PROGRESS' },
+                { key: 'status', header: 'STATUS' },
+                { key: 'mode', header: 'MODE' },
+                { key: 'title', header: 'TITLE', maxWidth: 48 },
+            ], (line) => this.log(`  ${line}`));
+        }
         if (g.description) {
             this.log('');
             this.log('Description:');
             this.log(`  ${g.description}`);
         }
     }
+    /**
+     * The goal's key results, best-effort.
+     *
+     * A second request, and a failure here must not take the goal down with it —
+     * `goals show` answering "here is your goal, minus its key results" is far
+     * better than answering nothing. `null` distinguishes "could not read" from
+     * "there are none", so neither view claims an empty OKR.
+     */
+    async readKeyResults(goalId) {
+        try {
+            const response = await data_provider_1.dataService.listKeyResults(goalId);
+            return response?.data ?? [];
+        }
+        catch (err) {
+            this.warn(`Could not read this goal's key results: ${err.message}. ` +
+                `Try \`${this.config.bin} goals key-results list ${goalId}\`.`);
+            return null;
+        }
+    }
 }
 exports.default = GoalsShow;

package/dist/commands/login.js

@@ -4,7 +4,10 @@ const core_1 = require("@oclif/core");
 const data_provider_1 = require("@skrr-ai/data-provider");
 const auth_core_1 = require("@skrr-ai/auth-core");
 const base_command_1 = require("../base-command");
+const daemonHandoff_1 = require("../lib/daemonHandoff");
+const daemon_setup_1 = require("../lib/daemon-setup");
 const config_1 = require("../lib/config");
+const keychain_1 = require("../lib/keychain");
 const login_1 = require("../lib/login");
 const api_fetch_1 = require("../lib/api-fetch");
 const auth_storage_1 = require("../lib/auth-storage");
@@ -116,6 +119,21 @@ class Login extends base_command_1.BaseCommand {
             const previousBaseURL = existing.baseURL;
             const nextBaseURL = (0, config_1.canonicalizeKnownBaseURL)(requestedBaseUrl);
             if (previousBaseURL && previousBaseURL !== nextBaseURL) {
+                // Say what is about to be lost. `--base-url` on the default profile
+                // silently REPOINTS it, so a session on the other deployment — and
+                // every space, task and board reachable through it — becomes
+                // unreachable until another interactive login. The `--profile` help
+                // advertises profiles as exactly this isolation ("signing into one does
+                // not sign you out of another"), so a reader has good reason to expect
+                // the flag to be additive rather than a move.
+                //
+                // A warning rather than a prompt: `cliLogin` completes without a
+                // terminal through the daemon broker, which is the case that matters
+                // most on a headless box, and a confirmation would break it.
+                const profile = (0, keychain_1.getActiveProfile)();
+                this.warn(`Pointing profile "${profile}" at ${(0, config_1.describeDeployment)(nextBaseURL)}. ` +
+                    `Its ${(0, config_1.describeDeployment)(previousBaseURL)} session will be replaced — ` +
+                    `sign in with \`--profile <name>\` instead to keep both.`);
                 undoBaseURL = () => {
                     // Re-read rather than reusing `existing`: the flow may have persisted
                     // other fields (cliId, migration markers) before failing, and this
@@ -157,6 +175,41 @@ class Login extends base_command_1.BaseCommand {
                 this.log('');
                 this.log(`Signed in via ${result.flow} on ${(0, config_1.describeDeployment)(this.cliConfig.baseURL)}. ` +
                     `Run \`${this.config.bin} whoami\` to confirm your identity.`);
+                // One login covers the machine: hand the local daemon a credential of its
+                // own. Best-effort by construction — the login above has already SUCCEEDED,
+                // and a failure here must not fail it or discard what the user just earned.
+                // It degrades to exactly the old behaviour, with a hint naming the command
+                // that finishes the job.
+                let handoff = await (0, daemonHandoff_1.handOffToLocalDaemon)(process.env, { loginFlow: result.flow });
+                // Nothing to hand a credential TO. This is the first moment we can fix
+                // that correctly — installing the daemon binds it to a deployment and a
+                // profile, and until this login there was no session to take them from.
+                // Keyed off `reason` rather than the sentence in `detail`, which is
+                // written for a person and expected to be reworded.
+                if (handoff.reason === 'no-binary' || handoff.reason === 'no-service') {
+                    const setup = await (0, daemon_setup_1.offerDaemonSetup)({
+                        binaryPresent: handoff.reason === 'no-service',
+                        log: (line) => this.log(line),
+                    });
+                    if (setup.status === 'installed') {
+                        // Re-run rather than duplicating the mint here: it is the same act
+                        // it always was, and now it has somewhere to land.
+                        handoff = await (0, daemonHandoff_1.handOffToLocalDaemon)(process.env, { loginFlow: result.flow });
+                    }
+                    else if (setup.status === 'failed') {
+                        this.log(`Could not set up the runtime: ${setup.detail}.`);
+                    }
+                    else {
+                        this.log(`This machine is not set up — ${setup.detail}.`);
+                    }
+                }
+                if (handoff.status === 'delivered') {
+                    this.log(`The local daemon was signed in too — ${handoff.detail}.`);
+                }
+                else if (handoff.status === 'failed') {
+                    this.log(`The local daemon was not signed in (${handoff.detail}). ` +
+                        `Run \`${this.config.bin} daemon login\` to finish.`);
+                }
             }
             catch (err) {
                 // Everything structured in login.ts throws Error; surface the

package/dist/commands/spaces/create.js

@@ -1,6 +1,7 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 const core_1 = require("@oclif/core");
+const data_provider_1 = require("@skrr-ai/data-provider");
 const outbox_1 = require("../../lib/outbox");
 const api_fetch_1 = require("../../lib/api-fetch");
 const base_command_1 = require("../../base-command");
@@ -24,7 +25,7 @@ class SpacesCreate extends base_command_1.BaseCommand {
         }),
         title: core_1.Flags.string({ description: 'Space title (required unless set via --from-json)' }),
         description: core_1.Flags.string({ description: 'Space description' }),
-        status: core_1.Flags.string({ description: 'Space status' }),
+        status: core_1.Flags.string({ description: 'Space status', options: [...data_provider_1.SPACE_STATUSES] }),
         color: core_1.Flags.string({ description: 'Space color (hex, e.g. #4f46e5)' }),
         'lead-agent': core_1.Flags.string({ description: 'Space Leader agent ID' }),
         'target-date': core_1.Flags.string({ description: 'Target date (ISO string)' }),

package/dist/commands/spaces/index.js

@@ -117,7 +117,15 @@ class Spaces extends base_command_1.BaseCommand {
             this.log(JSON.stringify({ object: 'space_guide', data: PERSPECTIVES }, null, 2));
             return;
         }
-        this.log('Space perspectives:');
+        // Every perspective below needs a `<space-id>`, and this screen used to
+        // start at the first of them — so `skrr spaces`, the natural way to orient
+        // yourself in the domain, printed ~14 commands a reader had no way to run
+        // and never named the two that unblock them. The entry point to a domain
+        // has to answer "how do I get one of these" before "what can I do with
+        // one".
+        this.log('Get a space id:  skrr spaces list        Make one:  skrr spaces create --title "..."');
+        this.log('');
+        this.log('Space perspectives (each takes a <space-id>):');
         this.log('');
         for (const item of PERSPECTIVES) {
             this.log(`${item.perspective.padEnd(12)} ${item.purpose}`);

package/dist/commands/spaces/list.d.ts

@@ -1,4 +1,22 @@
 import { BaseCommand } from '../../base-command';
+/**
+ * What an empty `--q` result is allowed to claim.
+ *
+ * `No spaces matching "space scratch".` is a confident assertion that nothing
+ * matched, and for the sense a person means it is FALSE: both words are in the
+ * title of a space they own and created a minute earlier. The server ORs one
+ * escaped regex built from the whole query across title/description/identifier,
+ * so the query is a substring and word order is load-bearing — a fact the
+ * message hid, leaving "it does not exist" as the only available reading.
+ *
+ * So the message reports what was actually run and hands back the two moves
+ * that recover: shorten to one distinctive word, or list everything. It says
+ * "matched" (what this query did) rather than "matching" (what exists).
+ *
+ * Pure and exported so the wording is testable without an oclif runtime — the
+ * convention `describeResourceNotFound` follows in `base-command`.
+ */
+export declare function noSpacesMatchedMessage(q: string, bin?: string): string;
 export default class SpacesList extends BaseCommand {
     static description: string;
     static examples: string[];

package/dist/commands/spaces/list.js

@@ -1,10 +1,34 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
+exports.noSpacesMatchedMessage = noSpacesMatchedMessage;
 const core_1 = require("@oclif/core");
 const data_provider_1 = require("@skrr-ai/data-provider");
 const base_command_1 = require("../../base-command");
 const web_url_1 = require("../../lib/web-url");
 const format_1 = require("../../lib/format");
+/**
+ * What an empty `--q` result is allowed to claim.
+ *
+ * `No spaces matching "space scratch".` is a confident assertion that nothing
+ * matched, and for the sense a person means it is FALSE: both words are in the
+ * title of a space they own and created a minute earlier. The server ORs one
+ * escaped regex built from the whole query across title/description/identifier,
+ * so the query is a substring and word order is load-bearing — a fact the
+ * message hid, leaving "it does not exist" as the only available reading.
+ *
+ * So the message reports what was actually run and hands back the two moves
+ * that recover: shorten to one distinctive word, or list everything. It says
+ * "matched" (what this query did) rather than "matching" (what exists).
+ *
+ * Pure and exported so the wording is testable without an oclif runtime — the
+ * convention `describeResourceNotFound` follows in `base-command`.
+ */
+function noSpacesMatchedMessage(q, bin = 'skrr') {
+    return (`No spaces matched ${JSON.stringify(q)}.\n` +
+        '  → `--q` is a case-insensitive SUBSTRING match over title, description and identifier, ' +
+        'not a tokenized search, so word order matters.\n' +
+        `  → retry with one distinctive word, or list them all with \`${bin} spaces list\`.`);
+}
 class SpacesList extends base_command_1.BaseCommand {
     static description = 'List spaces';
     static examples = [
@@ -17,14 +41,32 @@ class SpacesList extends base_command_1.BaseCommand {
     ];
     static flags = {
         json: core_1.Flags.boolean({ description: 'Output as JSON' }),
-        status: core_1.Flags.string({ description: 'Filter by space status' }),
+        // Enumerated so a typo is refused by the flag parser naming the choices.
+        // Undeclared, `--status bogus_status` exited 0 with zero results — which is
+        // exactly what a real status with no spaces looks like, so a typo and an
+        // empty set were indistinguishable and nothing named a valid value.
+        status: core_1.Flags.string({
+            description: 'Filter by space status',
+            options: [...data_provider_1.SPACE_STATUSES],
+        }),
         label: core_1.Flags.string({
             description: 'Filter by label ID (repeatable). Multiple labels AND together — a space must carry all of them.',
             multiple: true,
         }),
         'include-archived': core_1.Flags.boolean({ description: 'Include archived spaces' }),
         q: core_1.Flags.string({
-            description: 'Free-text search over title, description, or space ref (case-insensitive)',
+            // NOT "free-text search". The server ORs ONE escaped regex built from the
+            // whole string across title/description/identifier
+            // (`api/models/Space.js` → `listSpaces`), so `--q` is a `LIKE %q%`.
+            // "Free-text search" made a promise the floor does not keep: it reads as
+            // "type the words you remember, in any order", and `--q "space scratch"`
+            // then answers "no spaces" for a space titled "… scratch space".
+            //
+            // A Meilisearch-backed deployment narrows through the index instead and
+            // IS tokenized and typo-tolerant — but the CLI cannot tell which path ran,
+            // so the help describes the guaranteed floor rather than the better case.
+            description: 'Match title, description, or identifier (case-insensitive). Substring, not tokenized — ' +
+                'word order matters, so prefer one distinctive word.',
         }),
         limit: core_1.Flags.integer({ description: 'Max results', default: 50 }),
         cursor: core_1.Flags.string({ description: 'Pagination cursor from a previous page' }),
@@ -53,12 +95,12 @@ class SpacesList extends base_command_1.BaseCommand {
         const r = response;
         const items = r?.data ?? [];
         if (items.length === 0) {
-            this.log(flags.q ? `No spaces matching ${JSON.stringify(flags.q)}.` : 'No spaces.');
+            this.log(flags.q ? noSpacesMatchedMessage(flags.q, this.config.bin) : 'No spaces.');
             return;
         }
         const rows = items.map((s) => ({
             id: String(s.id ?? s._id ?? '-'),
-            ref: String(s.identifier ?? '-'),
+            identifier: String(s.identifier ?? '-'),
             title: String(s.title ?? '-'),
             status: String(s.status ?? '-'),
             goals: String(Array.isArray(s.goalIds) ? s.goalIds.length : 0),
@@ -66,9 +108,17 @@ class SpacesList extends base_command_1.BaseCommand {
             lead: String(s.leadAgentId ?? '-'),
         }));
         (0, format_1.renderTable)(rows, [
-            // REF leads for the same reason it does on tasks: it is the short
-            // thing a person types back into another command.
-            { key: 'ref', header: 'REF' },
+            // Leads for the same reason it does on tasks: it is the short thing a
+            // person types back into another command.
+            //
+            // Headed `IDENTIFIER`, not `REF`, because `identifier` is the ONLY name
+            // this value has anywhere else — it is the wire field, the storage
+            // field, and what `@skrr-ai/data-provider` calls it. The column used to
+            // say `REF` and the detail view `Ref:`, so all three human surfaces
+            // named a key that does not exist in `--json`; a script author read
+            // `ref` off every row, got nothing, and concluded `--json` was dropping
+            // a field the table plainly had. (OSK S4 dogfood finding)
+            { key: 'identifier', header: 'IDENTIFIER' },
             { key: 'title', header: 'TITLE', maxWidth: 50 },
             { key: 'status', header: 'STATUS' },
             { key: 'goals', header: 'GOALS' },

package/dist/commands/spaces/show.js

@@ -43,7 +43,10 @@ class SpacesShow extends base_command_1.BaseCommand {
         }
         const ancestors = Array.isArray(s.ancestorSpaceIds) ? s.ancestorSpaceIds : [];
         this.log(`ID:          ${s.id ?? s._id ?? '-'}`);
-        this.log(`Ref:         ${s.identifier ?? '-'}`);
+        // `Identifier`, not `Ref` — the label has to be the key a reader can then
+        // find in `--json`, where this value is `identifier` and no `ref` exists.
+        // Matches the `IDENTIFIER` column in `spaces list`.
+        this.log(`Identifier:  ${s.identifier ?? '-'}`);
         this.log(`Title:       ${s.title ?? '-'}`);
         if (url)
             this.log(`URL:         ${url}`);

package/dist/commands/spaces/summary.d.ts

@@ -1,4 +1,8 @@
 import { BaseCommand } from '../../base-command';
+/** Exported for `summary.spec.ts`. `0` is a fact worth printing here — "blocked 0" is the answer, not a blank. */
+export declare function num(value: unknown): string;
+/** `label n · label n`, dropping pairs the payload did not carry at all. */
+export declare function pairs(source: Record<string, unknown> | undefined, keys: [string, string][]): string;
 export default class SpacesSummary extends BaseCommand {
     static description: string;
     static args: {

package/dist/commands/spaces/summary.js

@@ -1,9 +1,22 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
+exports.num = num;
+exports.pairs = pairs;
 const core_1 = require("@oclif/core");
 const data_provider_1 = require("@skrr-ai/data-provider");
 const base_command_1 = require("../../base-command");
 const space_output_1 = require("../../lib/space-output");
+/** Exported for `summary.spec.ts`. `0` is a fact worth printing here — "blocked 0" is the answer, not a blank. */
+function num(value) {
+    return typeof value === 'number' ? String(value) : '-';
+}
+/** `label n · label n`, dropping pairs the payload did not carry at all. */
+function pairs(source, keys) {
+    return keys
+        .filter(([key]) => source?.[key] !== undefined)
+        .map(([key, label]) => `${label} ${num(source?.[key])}`)
+        .join(' · ');
+}
 class SpacesSummary extends base_command_1.BaseCommand {
     static description = 'Show the aggregated summary for a space';
     static args = {
@@ -23,7 +36,70 @@ class SpacesSummary extends base_command_1.BaseCommand {
         const output = result && typeof result === 'object'
             ? (0, space_output_1.withSpacePerspectiveUrl)(this.cliConfig.baseURL, args.id, 'dashboard', result)
             : result;
-        this.log(JSON.stringify(output, null, 2));
+        // This printed the raw payload regardless of `--json`, which differed only
+        // by its own `generatedAt` timestamp — so the flag advertised a mode the
+        // command did not have, and the FIRST perspective `skrr spaces` points a
+        // human at (the dashboard row) was a wall of JSON.
+        if (flags.json) {
+            this.log(JSON.stringify(output, null, 2));
+            return;
+        }
+        const o = (output ?? {});
+        const tasks = o.tasks;
+        const byPriority = tasks?.openByPriority;
+        this.log(`Space:    ${o.spaceId ?? args.id}`);
+        if (o.url)
+            this.log(`Web:      ${o.url}`);
+        this.log('');
+        if (tasks) {
+            const pct = typeof tasks.percentage === 'number' ? ` (${tasks.percentage}%)` : '';
+            this.log(`Tasks     ${num(tasks.total)} total · ${num(tasks.done)} done${pct} · ${num(tasks.open)} open`);
+            const flow = pairs(tasks, [
+                ['inProgress', 'in progress'],
+                ['running', 'running'],
+                ['blocked', 'blocked'],
+                ['failed', 'failed'],
+            ]);
+            if (flow)
+                this.log(`          ${flow}`);
+            const timing = pairs(tasks, [
+                ['dueToday', 'due today'],
+                ['dueSoon', 'due soon'],
+                ['stale', 'stale'],
+                ['unassigned', 'unassigned'],
+            ]);
+            if (timing)
+                this.log(`          ${timing}`);
+            const priority = pairs(byPriority, [
+                ['critical', 'critical'],
+                ['high', 'high'],
+                ['medium', 'medium'],
+                ['low', 'low'],
+            ]);
+            if (priority)
+                this.log(`          open by priority: ${priority}`);
+        }
+        for (const [key, label] of [
+            ['goals', 'Goals    '],
+            ['conversations', 'Chats    '],
+        ]) {
+            const section = o[key];
+            if (section?.total !== undefined)
+                this.log(`${label} ${num(section.total)}`);
+        }
+        // Agents carries `activeIds`, not a total — counting the array is the
+        // answer to "how many agents are working here", and an empty one is a real
+        // answer rather than a missing section.
+        const agents = o.agents;
+        if (Array.isArray(agents?.activeIds))
+            this.log(`Agents    ${agents.activeIds.length} active`);
+        // The per-status breakdown is in the payload and deliberately not a
+        // section: it restates `byStatus` counts the lines above already summarise,
+        // and nine near-zero rows would bury the four numbers that matter.
+        this.log('');
+        this.log('Full breakdown (byStatus, per-section detail): --json');
+        if (o.next_command)
+            this.log(`Next: ${o.next_command}`);
     }
 }
 exports.default = SpacesSummary;

package/dist/commands/spaces/update.d.ts

@@ -16,6 +16,10 @@ export default class SpacesUpdate extends BaseCommand {
         'target-date': import("@oclif/core/lib/interfaces").OptionFlag<string | undefined, import("@oclif/core/lib/interfaces").CustomOptions>;
         goal: import("@oclif/core/lib/interfaces").OptionFlag<string[] | undefined, import("@oclif/core/lib/interfaces").CustomOptions>;
         'inherit-access': import("@oclif/core/lib/interfaces").BooleanFlag<boolean>;
+        'estimate-scale': import("@oclif/core/lib/interfaces").OptionFlag<string | undefined, import("@oclif/core/lib/interfaces").CustomOptions>;
+        'estimate-migration': import("@oclif/core/lib/interfaces").OptionFlag<string | undefined, import("@oclif/core/lib/interfaces").CustomOptions>;
+        'default-estimate': import("@oclif/core/lib/interfaces").OptionFlag<number | undefined, import("@oclif/core/lib/interfaces").CustomOptions>;
+        'use-default-estimate': import("@oclif/core/lib/interfaces").BooleanFlag<boolean>;
         'worktree-isolation': import("@oclif/core/lib/interfaces").OptionFlag<string | undefined, import("@oclif/core/lib/interfaces").CustomOptions>;
     };
     run(): Promise<void>;

package/dist/commands/spaces/update.js

@@ -13,6 +13,7 @@ class SpacesUpdate extends base_command_1.BaseCommand {
         '<%= config.bin %> spaces update <space-id> --lead-agent <agent-id>',
         '<%= config.bin %> spaces update <space-id> --no-inherit-access',
         '<%= config.bin %> spaces update <space-id> --from-json patch.json',
+        '<%= config.bin %> spaces update <space-id> --estimate-scale fibonacci --estimate-migration migrate',
     ];
     static args = {
         id: core_1.Args.string({ description: 'Space ID', required: true, ignoreStdin: true }),
@@ -24,7 +25,7 @@ class SpacesUpdate extends base_command_1.BaseCommand {
         }),
         title: core_1.Flags.string({ description: 'New title' }),
         description: core_1.Flags.string({ description: 'New description' }),
-        status: core_1.Flags.string({ description: 'New status' }),
+        status: core_1.Flags.string({ description: 'New status', options: [...data_provider_1.SPACE_STATUSES] }),
         color: core_1.Flags.string({ description: 'New color (hex)' }),
         'lead-agent': core_1.Flags.string({ description: 'New Space Leader agent ID' }),
         'target-date': core_1.Flags.string({ description: 'New target date (ISO string)' }),
@@ -37,6 +38,38 @@ class SpacesUpdate extends base_command_1.BaseCommand {
             allowNo: true,
             description: 'Whether this subspace inherits members/permissions from its parent chain. Use --no-inherit-access to make it private. (To change the parent itself, use `spaces move`.)',
         }),
+        // `tasks create --estimate` resolves its scale up the ancestor chain, and
+        // with nothing set it resolves to `none`, which admits no value — so the
+        // estimate is dropped. That was reachable only from the web UI, which made
+        // the CLI's own estimate flag conditionally inert with no way to satisfy
+        // its prerequisite. `PATCH /api/spaces/:id` has accepted these three fields
+        // all along.
+        'estimate-scale': core_1.Flags.string({
+            description: 'Estimate scale for this space and its descendants. Allowed values per scale: ' +
+                Object.entries(data_provider_1.ESTIMATE_SCALE_VALUES)
+                    .map(([scale, values]) => `${scale} ${values.length ? values.join('/') : '(none)'}`)
+                    .join(', '),
+            options: [...data_provider_1.ESTIMATE_SCALES],
+        }),
+        // The server makes this MANDATORY on a scale change (deliberately — so no
+        // destructive interpretation is inferred) and answers a missing one with
+        // ESTIMATE_SCALE_MIGRATION_REQUIRED. Surfacing it as its own flag is the
+        // difference between a documented choice and a 400 the caller has to
+        // reverse-engineer.
+        'estimate-migration': core_1.Flags.string({
+            description: 'What happens to estimates that already exist when the scale changes. Required whenever ' +
+                '--estimate-scale changes the EFFECTIVE scale. `migrate` maps each estimate onto the ' +
+                'nearest value in the new scale; `clear` DELETES every estimate in this space and its ' +
+                'descendants. Changing to `none` accepts only `clear`, since there is nothing to map into.',
+            options: [...data_provider_1.ESTIMATE_SCALE_MIGRATION_MODES],
+        }),
+        'default-estimate': core_1.Flags.integer({
+            description: 'Estimate applied to unestimated tasks when --use-default-estimate is on. Must be a value the scale allows',
+        }),
+        'use-default-estimate': core_1.Flags.boolean({
+            allowNo: true,
+            description: 'Whether rollups treat an unestimated task as --default-estimate',
+        }),
         'worktree-isolation': core_1.Flags.string({
             options: ['shared', 'ephemeral'],
             description: "Space default for how this space's autonomous task runs use git worktrees. " +
@@ -63,6 +96,10 @@ class SpacesUpdate extends base_command_1.BaseCommand {
             leadAgentId: flags['lead-agent'],
             targetDate: flags['target-date'],
             inheritAccess: flags['inherit-access'],
+            estimateScale: flags['estimate-scale'],
+            estimateScaleMigration: flags['estimate-migration'],
+            defaultEstimate: flags['default-estimate'],
+            useDefaultEstimateForUnestimated: flags['use-default-estimate'],
         });
         // Worktree-isolation default lives on the space's deliveryPolicy subdoc,
         // which the API replaces wholesale on update. Merge into the policy the user