orbitmap 0.4.4 → 0.5.0

package/README.md

@@ -155,7 +155,7 @@ OrbitMap organises work on several levels. The CLI mirrors them 1:1:
 
 | Command | Description |
 |---------|-------------|
-| `orbitmap tasks` | List your assigned tasks (`--status`, `--priority`, `--orbit`) |
+| `orbitmap tasks` | List tasks across every area you reach and every assignee (`--area`, `--status`, `--priority`, `--orbit`, `--intent`, `--mission`, `--agent`, `--unassigned`, `--limit`, `--all`) |
 | `orbitmap task <id-or-number>` | Show full task details |
 | `orbitmap start [id-or-number]` | Start working on a task (auto-picks next TODO if no ID) |
 | `orbitmap status <id-or-number> <status>` | Update task status (`--force` to move a parent to `done` with unfinished subtasks) |
@@ -169,6 +169,59 @@ OrbitMap organises work on several levels. The CLI mirrors them 1:1:
 
 **Valid statuses:** `backlog`, `todo`, `in_progress`, `in_review`, `review_changes`, `done`, `blocked`
 
+### What a list shows, and what it hides
+
+Every list — `tasks`, `issues`, `ideas`, `vibes`, `docs`, `intents`, `missions` — spans
+**every area your key reaches and every assignee**. It is not scoped to your own work, and it
+is not scoped to the area your directory maps to: that area is the context for *writes* and
+for single-object reads, and the server deliberately ignores it when listing.
+
+Narrowing is explicit, and always visible in the output:
+
+```bash
+orbitmap tasks                      # everything you can reach
+orbitmap tasks --area demo          # one area
+orbitmap tasks --area demo,web      # two areas (comma-separated, no spaces)
+orbitmap tasks --area all           # cancel an ORBITMAP_AREA narrowing for this call
+orbitmap tasks --agent me           # only your own tasks — the pre-9.0.0 default
+orbitmap tasks --agent jakub-agent  # a colleague's
+orbitmap tasks --unassigned         # the free backlog
+orbitmap tasks --intent IN-nahetc   # everything under one intent, in one call
+orbitmap tasks --mission MS-abc123
+orbitmap tasks --status all         # every status, on every list
+```
+
+Lists are paged: **30 rows by default, 100 at most** per page. The page is not the answer —
+`--all` is:
+
+```bash
+orbitmap tasks --limit 100          # one bigger page
+orbitmap tasks --all                # follow every page and print all 143 rows
+```
+
+Under every result the CLI prints what produced it, whether the list was empty, truncated or
+complete:
+
+```
+30 of 143 shown across 7 areas — run with --all for every row.
+Scope: all 7 reachable areas, status todo,in_progress (46 hidden, add --status all), assignee any.
+```
+
+An empty list carries the same line, so "nothing exists" and "you did not ask for it" are
+never the same sentence:
+
+```
+No tasks. Scope: areas demo (1 of 7), status todo,in_progress (46 hidden, add --status all), assignee unassigned.
+```
+
+`--json` carries the whole `meta` block: `total`, `next_cursor`, `per_area`
+(`{slug, shown, total}` per area), `applied_filters`, `scope` and `workspace`, plus each row's
+own `area`, `agent_id` and `assigned_user_id`.
+
+`--area` names *one* area everywhere else (`create`, `log`, `status`, `doc-import`, …) — that
+is the area a write lands in, so a comma-separated `--area` is refused there rather than
+silently taking the first.
+
 ### Referring to objects: `<id-or-number>`
 
 Every command that takes an object reference accepts all three forms interchangeably:
@@ -234,7 +287,7 @@ when there is none — so a rejected transition is re-run with `--log`, not retr
 
 | Command | Description |
 |---------|-------------|
-| `orbitmap docs` | List area documents |
+| `orbitmap docs` | List documents across every area you reach, plus workspace-level ones (`--area`, `--type`, `--search`, `--limit`, `--all`) |
 | `orbitmap doc <id-or-slug>` | Show document (TOC by default, `--full`, `--section`) |
 | `orbitmap doc-import <title>` | Import a markdown file (`--context` to set when-to-use hint) |
 | `orbitmap doc-update <id-or-slug>` | Replace a document from a file |
@@ -278,7 +331,7 @@ orbitmap doc-share <doc-uuid> <area-uuid> --agents agent1-uuid,agent2-uuid
 
 | Command | Description |
 |---------|-------------|
-| `orbitmap context` | Show agent identity and current area |
+| `orbitmap context` | Session matching material: agent identity, area/workspace, missions and intents with TL;DRs, mission workitems, areas, document metadata |
 | `orbitmap areas` | List all areas assigned to this agent |
 | `orbitmap create-area <name>` | Create a new area (`--desc`, `--slug`, `--workspace-id`) |
 | `orbitmap members <area-id>` | List agents and users in an area (accepts slug) |
@@ -288,16 +341,16 @@ orbitmap doc-share <doc-uuid> <area-uuid> --agents agent1-uuid,agent2-uuid
 
 | Command | Description |
 |---------|-------------|
-| `orbitmap issues` | List open issues |
+| `orbitmap issues` | List open issues across every area you reach (`--area`, `--status`, `--severity`, `--intent`, `--limit`, `--all`) |
 | `orbitmap issue show <id>` | Show issue details (UUID or number) |
 | `orbitmap issue register` | Register a new issue (`--intent` to link it to an intent) |
 | `orbitmap issue status <id> <status>` | Update issue status |
 | `orbitmap issue resolve <id>` | Resolve an issue |
-| `orbitmap ideas` | List ideas |
+| `orbitmap ideas` | List ideas across every area you reach (`--area`, `--status`, `--priority`, `--limit`, `--all`) |
 | `orbitmap idea add` | Add a new idea |
 | `orbitmap idea show <id>` | Show idea details (UUID or number) |
 | `orbitmap idea status <id>` | Update idea status |
-| `orbitmap vibes` | List vibes |
+| `orbitmap vibes` | List vibes across every area you reach (`--area`, `--type`, `--since`, `--limit`, `--all`) |
 | `orbitmap vibe log` | Log a new vibe |
 | `orbitmap vibe show <id>` | Show vibe details |
 | `orbitmap vibe update <id>` | Update a vibe |
@@ -308,10 +361,10 @@ Workspace-level desired outcomes. Tasks and issues hang off an intent; an intent
 
 | Command | Description |
 |---------|-------------|
-| `orbitmap intents` | List intents (shortcut for `intent list`) |
-| `orbitmap intent show <id-or-number>` | Show an intent (UUID or `IN-xxxxxx`) |
+| `orbitmap intents` | List intents — workspace-wide (`--status`, `--mission`, `--limit`, `--all`) |
+| `orbitmap intent show <id-or-number>` | Show an intent (UUID or `IN-xxxxxx`) — embeds the context bundle (`--no-bundle` strips it, `--no-logs` skips the work-log tail, `--slim` is the freshness probe) |
 | `orbitmap intent create <title>` | Create an intent (`--outcome`, `--design`, `--plan`, `--status`, `--orbit`) |
-| `orbitmap intent update <id>` | Update title, outcome, design, plan, or status (`--log <type>:<content>`, repeatable) |
+| `orbitmap intent update <id>` | Update title, outcome, design, plan, or status (`--areas <slug>,<slug>` declares its areas; `--log <type>:<content>`, repeatable) |
 | `orbitmap intent link <id> --type task\|issue --id <uuid>` | Link a task or issue |
 | `orbitmap intent unlink <id> --type task\|issue --id <uuid>` | Unlink a task or issue |
 | `orbitmap intent orbit <id> [orbit-id]` | Set the intent's orbit (`--clear` to remove) |
@@ -335,13 +388,23 @@ orbitmap intent update IN-a1b2c3 --status plan \
 
 `intent create --orbit` is create-then-attach. If the attach step fails the intent is still created — the CLI reports the failure and does not retry.
 
+**The context bundle.** `intent show` prints a `Context bundle:` block after the intent's own outcome/design/plan and before the work-log tail: the mission handle with its outcome TL;DR, the documents that surround the intent (listed by their `when_to_use`, with the slug to pass to `orbitmap doc`), sibling intent handles, and the intent's own tasks and issues. It is handle tier — TL;DRs and titles, never bodies. `--no-bundle` strips it when you only want the intent itself.
+
+**The freshness probe.** `--slim` replaces the whole body with a ~150-token probe: handle, the outcome/design/plan TL;DRs, declared areas, mission, task counts per status, and the `updated_at` + `last_log_id` pair. Hold that pair from a full fetch; run the probe to see whether the intent moved. Unchanged means your copy is current — do not re-fetch. A work log never touches `updated_at`, so both halves have to be compared. `--slim` wins over `--no-bundle` and `--no-logs`.
+
+```bash
+orbitmap intent show IN-a1b2c3                # intent + context bundle + work-log tail
+orbitmap intent show IN-a1b2c3 --no-bundle    # just the intent and its logs
+orbitmap intent show IN-a1b2c3 --slim         # freshness probe: TL;DRs + updated_at/last_log_id
+```
+
 ### Missions
 
 Time-boxed workspace focus. Only one mission can be `active` at a time.
 
 | Command | Description |
 |---------|-------------|
-| `orbitmap missions` | List missions (shortcut for `mission list`) |
+| `orbitmap missions` | List missions — workspace-wide (`--status`, `--limit`, `--all`) |
 | `orbitmap mission show <id-or-number>` | Show a mission (UUID or `MS-xxxxxx`) |
 | `orbitmap mission create <title>` | Create a mission (`--desc`, `--outcome`, `--end-date`) |
 | `orbitmap mission update <id>` | Update title, description, outcome, or end date (`--log <type>:<content>`, repeatable) |

package/dist/adapters/cloud.d.ts

@@ -12,13 +12,25 @@ export declare class CloudAdapter implements WorkspaceAdapter {
      * both or neither may be set.
      */
     private readonly workspace?;
+    /**
+     * The areas the caller EXPLICITLY narrowed a LIST to (`--area a,b`, `ORBITMAP_AREA=a,b`),
+     * already resolved by the one area ladder. Sent as the `area_id` query parameter.
+     *
+     * It is deliberately NOT {@link CloudAdapter.area}. Since API 9.0.0 the `X-Orbitmap-Area`
+     * header no longer narrows a list — the CLI sends it on every call made from an
+     * area-mapped directory, so honouring it there would leave `orbitmap tasks` answering with
+     * one area's work, which is the bug IN-nahetc exists to fix. The header stays the context
+     * for writes and single-entity reads; `area_id` is the only narrowing, and only an
+     * explicit `--area` fills it.
+     */
+    private readonly areaFilter;
     /**
      * Task reference → uuid, for the lifetime of this adapter. A command that touches the same
      * task twice (`dep add TS-a TS-b` resolves two, `status` then reads back) pays for one
      * `/tasks/by-number/{n}` lookup per distinct reference, not per call site.
      */
     private readonly taskIdCache;
-    constructor(apiKey: string, area?: string, apiUrl?: string, workspace?: string);
+    constructor(apiKey: string, area?: string, apiUrl?: string, workspace?: string, areaFilter?: string[]);
     private request;
     /**
      * Add the client half of the story to the workspace-context errors the server can raise.
@@ -49,11 +61,39 @@ export declare class CloudAdapter implements WorkspaceAdapter {
      * No request is made.
      */
     getWorkspaceId(): string | undefined;
+    /**
+     * The `area_id` query value for a LIST: what the caller explicitly asked for, falling back
+     * to the areas the ladder resolved from `--area` / `ORBITMAP_AREA`.
+     *
+     * Comma-joined, exactly as the API's own parser expects
+     * (`BaseAgentApiController::splitAreaRefs`). `undefined` — never an empty string — when
+     * nothing narrows, so the request carries no `area_id` at all and the answer spans every
+     * area the key reaches.
+     */
+    private listAreaParam;
+    /** `limit` / `cursor`, the two paging params every list shares. */
+    private pagingParams;
+    /**
+     * `GET /tasks` — every area the key reaches and every assignee, unless a filter says
+     * otherwise (API 9.0.0).
+     *
+     * `areaId` accepts one ref or several; several are comma-joined, which is the only way to
+     * narrow to two areas without two calls. `agentId` (`me`, a slug or a uuid), `unassigned`
+     * and `all` are the owner scope — `all` now names the default rather than escaping one.
+     * `intentId` / `missionId` take a uuid, `IN-xxxxxx`/`MS-xxxxxx` or the bare code.
+     */
     getTasks(options?: {
         status?: string;
         priority?: string;
-        areaId?: string;
+        areaId?: string | string[];
         orbit?: string;
+        intentId?: string;
+        missionId?: string;
+        agentId?: string;
+        unassigned?: boolean;
+        all?: boolean;
+        limit?: string | number;
+        cursor?: string;
     }): Promise<unknown>;
     /**
      * Resolve any task reference — uuid, `TS-uw9yh5` or the bare code — to the uuid the task
@@ -63,7 +103,18 @@ export declare class CloudAdapter implements WorkspaceAdapter {
     private taskId;
     getTask(taskId: string): Promise<unknown>;
     getTaskByNumber(taskNumber: string): Promise<unknown>;
-    startTask(taskId?: string): Promise<unknown>;
+    /**
+     * `POST /tasks/{id}/start`, or `POST /tasks/start` to let the server auto-pick.
+     *
+     * `confirmReassign` is the USER's answer to a 409 `REASSIGN_CONFIRMATION_REQUIRED`
+     * travelling back: it reassigns a task that belongs to another agent and starts it in one
+     * call. It is never sent on its own initiative — see `askToTakeOver` in
+     * `src/commands/start.ts`. Auto-confirming would turn "ask before taking someone else's
+     * work" into theatre.
+     */
+    startTask(taskId?: string, options?: {
+        confirmReassign?: boolean;
+    }): Promise<unknown>;
     updateTaskStatus(taskId: string, status?: string, deliveryStatus?: string | null, _force?: boolean): Promise<unknown>;
     createSubtasks(parentId: string, subtasks: Array<{
         title: string;
@@ -112,7 +163,10 @@ export declare class CloudAdapter implements WorkspaceAdapter {
     getDocuments(options?: {
         type?: string;
         search?: string;
-        areaId?: string;
+        areaId?: string | string[];
+        status?: string;
+        limit?: string | number;
+        cursor?: string;
     }): Promise<unknown>;
     getDocument(idOrSlug: string, mode?: 'inline' | 'file', options?: {
         full?: boolean;
@@ -221,7 +275,10 @@ export declare class CloudAdapter implements WorkspaceAdapter {
     listIssues(options?: {
         status?: string;
         severity?: string;
-        limit?: string;
+        areaId?: string | string[];
+        intentId?: string;
+        limit?: string | number;
+        cursor?: string;
     }): Promise<unknown>;
     /**
      * `GET /issues/{id_or_number}` — the single issue-read route. It accepts a uuid, a bare
@@ -247,7 +304,9 @@ export declare class CloudAdapter implements WorkspaceAdapter {
     listVibes(options?: {
         type?: string;
         since?: string;
-        limit?: string;
+        areaId?: string | string[];
+        limit?: string | number;
+        cursor?: string;
     }): Promise<unknown>;
     getVibe(id: string): Promise<unknown>;
     updateVibe(id: string, data: {
@@ -259,7 +318,9 @@ export declare class CloudAdapter implements WorkspaceAdapter {
     listIdeas(options?: {
         status?: string;
         priority?: string;
-        limit?: string;
+        areaId?: string | string[];
+        limit?: string | number;
+        cursor?: string;
     }): Promise<unknown>;
     /**
      * `GET /ideas/{id_or_number}` — accepts a uuid, a bare code or `ID-xxxxxx`; the server
@@ -313,9 +374,15 @@ export declare class CloudAdapter implements WorkspaceAdapter {
     }): Promise<unknown>;
     listIntents(options?: {
         status?: string;
-        limit?: string;
+        missionId?: string;
+        limit?: string | number;
+        cursor?: string;
+    }): Promise<unknown>;
+    getIntent(idOrNumber: string, options?: {
+        logs?: boolean;
+        bundle?: boolean;
+        slim?: boolean;
     }): Promise<unknown>;
-    getIntent(idOrNumber: string): Promise<unknown>;
     createIntent(data: {
         name: string;
         outcome?: string;
@@ -330,6 +397,7 @@ export declare class CloudAdapter implements WorkspaceAdapter {
         design?: string;
         plan?: string;
         status?: string;
+        area_ids?: string[];
         logs?: WorkLogEntry[];
     }): Promise<unknown>;
     linkIntentItem(idOrNumber: string, data: {
@@ -343,7 +411,8 @@ export declare class CloudAdapter implements WorkspaceAdapter {
     setIntentOrbit(idOrNumber: string, orbitId: string | null): Promise<unknown>;
     listMissions(options?: {
         status?: string;
-        limit?: string;
+        limit?: string | number;
+        cursor?: string;
     }): Promise<unknown>;
     getMission(idOrNumber: string): Promise<unknown>;
     createMission(data: {
@@ -391,6 +460,12 @@ export interface CreateClientOptions {
      * when the caller has it so the ladder runs once per command.
      */
     workspace?: string;
+    /**
+     * The areas the caller EXPLICITLY narrowed to, already produced by the same ladder — the
+     * `area_id` list filter. See {@link CloudAdapter.areaFilter} for why this is not
+     * {@link CreateClientOptions.area}.
+     */
+    areas?: string[];
     /** Global config the caller already loaded, to avoid a second read of the same file. */
     config?: OrbitMapConfig;
 }

package/dist/adapters/cloud.js

@@ -1,6 +1,6 @@
 import { createReadStream, statSync } from 'node:fs';
 import { basename, extname } from 'node:path';
-import { AREA_CONTEXT_REQUIRED, AREA_WORKSPACE_MISMATCH, OrbitMapAPIError, WORKSPACE_CONTEXT_REQUIRED, } from '../errors.js';
+import { AREA_CONTEXT_REQUIRED, OrbitMapAPIError, WORKSPACE_CONTEXT_REQUIRED, } from '../errors.js';
 import { loadConfig, resolveAuth, DEFAULT_API_URL } from '../config.js';
 import { areaContextHint, ORBITMAP_DIR, resolveArea, resolveWorkspaceId, } from '../workspace-resolve.js';
 import { isObjectNumber, resolveTaskRef, stripPrefix } from '../id-resolve.js';
@@ -15,16 +15,29 @@ export class CloudAdapter {
      * both or neither may be set.
      */
     workspace;
+    /**
+     * The areas the caller EXPLICITLY narrowed a LIST to (`--area a,b`, `ORBITMAP_AREA=a,b`),
+     * already resolved by the one area ladder. Sent as the `area_id` query parameter.
+     *
+     * It is deliberately NOT {@link CloudAdapter.area}. Since API 9.0.0 the `X-Orbitmap-Area`
+     * header no longer narrows a list — the CLI sends it on every call made from an
+     * area-mapped directory, so honouring it there would leave `orbitmap tasks` answering with
+     * one area's work, which is the bug IN-nahetc exists to fix. The header stays the context
+     * for writes and single-entity reads; `area_id` is the only narrowing, and only an
+     * explicit `--area` fills it.
+     */
+    areaFilter;
     /**
      * Task reference → uuid, for the lifetime of this adapter. A command that touches the same
      * task twice (`dep add TS-a TS-b` resolves two, `status` then reads back) pays for one
      * `/tasks/by-number/{n}` lookup per distinct reference, not per call site.
      */
     taskIdCache = new Map();
-    constructor(apiKey, area, apiUrl, workspace) {
+    constructor(apiKey, area, apiUrl, workspace, areaFilter) {
         this.apiKey = apiKey;
         this.area = area;
         this.workspace = workspace;
+        this.areaFilter = areaFilter ?? [];
         this.baseUrl = (apiUrl ?? DEFAULT_API_URL).replace(/\/$/, '');
     }
     async request(method, path, options) {
@@ -120,8 +133,11 @@ export class CloudAdapter {
     explainContextError(error) {
         // Dispatch on the canonical code, not the wire code: the API is renaming `PROJECT_*` to
         // `AREA_*` and both spellings must land here (see ERROR_CODE_ALIASES in errors.ts).
+        // `AREA_WORKSPACE_MISMATCH` (422) used to be handled here too. API 9.0.0 REMOVED it:
+        // the workspace ceiling refuses a foreign `X-Orbitmap-Workspace` with 403 ACCESS_DENIED
+        // before the area and the workspace are ever compared, so the code is unreachable and
+        // the dual-read is gone.
         if (error.canonicalCode !== WORKSPACE_CONTEXT_REQUIRED &&
-            error.canonicalCode !== AREA_WORKSPACE_MISMATCH &&
             error.canonicalCode !== AREA_CONTEXT_REQUIRED) {
             return error;
         }
@@ -173,14 +189,55 @@ export class CloudAdapter {
     getWorkspaceId() {
         return this.workspace;
     }
+    /**
+     * The `area_id` query value for a LIST: what the caller explicitly asked for, falling back
+     * to the areas the ladder resolved from `--area` / `ORBITMAP_AREA`.
+     *
+     * Comma-joined, exactly as the API's own parser expects
+     * (`BaseAgentApiController::splitAreaRefs`). `undefined` — never an empty string — when
+     * nothing narrows, so the request carries no `area_id` at all and the answer spans every
+     * area the key reaches.
+     */
+    listAreaParam(areaId) {
+        const explicit = Array.isArray(areaId) ? areaId : areaId ? [areaId] : [];
+        const refs = explicit.length > 0 ? explicit : this.areaFilter;
+        const joined = refs
+            .flatMap((ref) => ref.split(','))
+            .map((ref) => ref.trim())
+            .filter((ref) => ref !== '')
+            .join(',');
+        return joined === '' ? undefined : joined;
+    }
+    /** `limit` / `cursor`, the two paging params every list shares. */
+    pagingParams(options) {
+        return {
+            limit: options?.limit === undefined ? undefined : String(options.limit),
+            cursor: options?.cursor,
+        };
+    }
     // ── Tasks ──
+    /**
+     * `GET /tasks` — every area the key reaches and every assignee, unless a filter says
+     * otherwise (API 9.0.0).
+     *
+     * `areaId` accepts one ref or several; several are comma-joined, which is the only way to
+     * narrow to two areas without two calls. `agentId` (`me`, a slug or a uuid), `unassigned`
+     * and `all` are the owner scope — `all` now names the default rather than escaping one.
+     * `intentId` / `missionId` take a uuid, `IN-xxxxxx`/`MS-xxxxxx` or the bare code.
+     */
     async getTasks(options) {
         return this.request('GET', '/tasks', {
             params: {
                 status: options?.status,
                 priority: options?.priority,
-                area_id: options?.areaId,
+                area_id: this.listAreaParam(options?.areaId),
                 orbit_id: options?.orbit,
+                intent_id: options?.intentId,
+                mission_id: options?.missionId,
+                agent_id: options?.agentId,
+                unassigned: options?.unassigned ? '1' : undefined,
+                all: options?.all ? '1' : undefined,
+                ...this.pagingParams(options),
             },
         });
     }
@@ -217,11 +274,21 @@ export class CloudAdapter {
     async getTaskByNumber(taskNumber) {
         return this.request('GET', `/tasks/by-number/${taskNumber}`);
     }
-    async startTask(taskId) {
+    /**
+     * `POST /tasks/{id}/start`, or `POST /tasks/start` to let the server auto-pick.
+     *
+     * `confirmReassign` is the USER's answer to a 409 `REASSIGN_CONFIRMATION_REQUIRED`
+     * travelling back: it reassigns a task that belongs to another agent and starts it in one
+     * call. It is never sent on its own initiative — see `askToTakeOver` in
+     * `src/commands/start.ts`. Auto-confirming would turn "ask before taking someone else's
+     * work" into theatre.
+     */
+    async startTask(taskId, options) {
+        const body = options?.confirmReassign ? { confirm_reassign: true } : undefined;
         if (taskId) {
-            return this.request('POST', `/tasks/${await this.taskId(taskId)}/start`);
+            return this.request('POST', `/tasks/${await this.taskId(taskId)}/start`, { body });
         }
-        return this.request('POST', '/tasks/start');
+        return this.request('POST', '/tasks/start', { body });
     }
     async updateTaskStatus(taskId, status, deliveryStatus, 
     // `force` (spec §6.2) is deliberately ignored in cloud mode: the API already allows
@@ -315,7 +382,9 @@ export class CloudAdapter {
             params: {
                 type: options?.type,
                 search: options?.search,
-                area_id: options?.areaId,
+                status: options?.status,
+                area_id: this.listAreaParam(options?.areaId),
+                ...this.pagingParams(options),
             },
         });
     }
@@ -468,7 +537,9 @@ export class CloudAdapter {
             params: {
                 status: options?.status,
                 severity: options?.severity,
-                limit: options?.limit,
+                area_id: this.listAreaParam(options?.areaId),
+                intent_id: options?.intentId,
+                ...this.pagingParams(options),
             },
         });
     }
@@ -498,7 +569,8 @@ export class CloudAdapter {
             params: {
                 type: options?.type,
                 since: options?.since,
-                limit: options?.limit,
+                area_id: this.listAreaParam(options?.areaId),
+                ...this.pagingParams(options),
             },
         });
     }
@@ -511,7 +583,12 @@ export class CloudAdapter {
     // ── Ideas ──
     async listIdeas(options) {
         return this.request('GET', '/ideas', {
-            params: { status: options?.status, priority: options?.priority, limit: options?.limit },
+            params: {
+                status: options?.status,
+                priority: options?.priority,
+                area_id: this.listAreaParam(options?.areaId),
+                ...this.pagingParams(options),
+            },
         });
     }
     /**
@@ -577,11 +654,26 @@ export class CloudAdapter {
     // ── Intents ──
     async listIntents(options) {
         return this.request('GET', '/intents', {
-            params: { status: options?.status, limit: options?.limit },
+            params: {
+                status: options?.status,
+                mission_id: options?.missionId,
+                ...this.pagingParams(options),
+            },
         });
     }
-    async getIntent(idOrNumber) {
-        return this.request('GET', `/intents/${idOrNumber}`);
+    async getIntent(idOrNumber, options) {
+        return this.request('GET', `/intents/${idOrNumber}`, {
+            params: {
+                // `?logs=0` (API 10.0.0) skips the embedded work-log tail. The default —
+                // no parameter at all — keeps the body the endpoint always returned.
+                logs: options?.logs === false ? '0' : undefined,
+                // `?bundle=0` (API 10.1.0) strips the context bundle show embeds by default.
+                bundle: options?.bundle === false ? '0' : undefined,
+                // `?slim=1` (API 10.1.0) answers the freshness probe instead of the full
+                // body; server-side it wins over every other parameter.
+                slim: options?.slim ? '1' : undefined,
+            },
+        });
     }
     async createIntent(data) {
         return this.request('POST', '/intents', { body: data });
@@ -606,7 +698,10 @@ export class CloudAdapter {
     // ── Missions ──
     async listMissions(options) {
         return this.request('GET', '/missions', {
-            params: { status: options?.status, limit: options?.limit },
+            params: {
+                status: options?.status,
+                ...this.pagingParams(options),
+            },
         });
     }
     async getMission(idOrNumber) {
@@ -654,8 +749,14 @@ export { CloudAdapter as OrbitMapClient };
 export async function createClient(explicitArea, options = {}) {
     const config = options.config ?? (await loadConfig());
     const auth = await resolveAuth({ config });
-    const area = explicitArea ?? options.area ?? resolveArea({ config }).area;
+    // The ladder is walked once when the caller already did it (`createAdapter` always has),
+    // and only re-walked here for the historical `createClient(area)` entry point. `--area a,b`
+    // names a LIST filter and no context area, so the raw flag can no longer be used as the
+    // header value — it goes through `resolveArea`, which splits the two apart.
+    const resolved = options.area !== undefined || options.areas !== undefined
+        ? { area: options.area, areas: options.areas ?? [] }
+        : resolveArea({ config, ...(explicitArea !== undefined ? { area: explicitArea } : {}) });
     const workspace = options.workspace ?? resolveWorkspaceId({ config }).workspace;
-    return new CloudAdapter(auth.apiKey, area, auth.apiUrl, workspace);
+    return new CloudAdapter(auth.apiKey, resolved.area, auth.apiUrl, workspace, resolved.areas);
 }
 //# sourceMappingURL=cloud.js.map