ask-marcel-office-cli 1.5.2 → 2.1.0

package/dist/infra/auth.d.ts

@@ -6,6 +6,7 @@ import type { BrowserAuth, ElevatedFailureReason } from './browser-auth.js';
 type AuthError = {
     type: 'auth_failed';
     message: string;
+    code?: string;
 } | {
     type: 'auth_cancelled';
 };
@@ -15,7 +16,7 @@ type AuthError = {
  * `{ elevated: 'captured' | 'failed', elevatedReason?: ... }` field on
  * the login response so an LLM consumer can predict whether the
  * elevated-dependent commands (chat metadata, historical-version
- * downloads) will work without invoking them. Login-fix round-1 Wave D.
+ * downloads) will work without invoking them.
  */
 type ElevatedOutcome = {
     captured: true;
@@ -24,7 +25,9 @@ type ElevatedOutcome = {
     reason: ElevatedFailureReason | 'unknown_error';
 };
 type AuthManager = {
-    getAccessToken: () => Promise<Result<AccessToken, AuthError>>;
+    getAccessToken: (options?: {
+        force?: boolean;
+    }) => Promise<Result<AccessToken, AuthError>>;
     /**
      * Returns a Graph token issued for an app on Microsoft's ODSP
      * `logicalPermissions` allow-list. Falls through cache → re-capture
@@ -60,7 +63,6 @@ type AuthManager = {
      * Inspect the elevated-capture outcome from the most recent
      * `acquireViaBrowser` invocation. Returns null if no browser-acquired
      * session has happened in this process (cache hit / refresh-only).
-     * Login-fix round-1 Wave D.
      */
     getLastElevatedOutcome: () => ElevatedOutcome | null;
     /**
@@ -69,22 +71,39 @@ type AuthManager = {
      * as `getLastElevatedOutcome`.
      */
     getLastChatsvcaggOutcome: () => ElevatedOutcome | null;
+    /**
+     * Decode-only preflight for whether the *persisted* elevated
+     * (M365ChatClient) token is present and still usable — the token the
+     * historical-version download / convert commands need. Unlike
+     * `getLastElevatedOutcome` (per-process, null in a fresh CLI invocation),
+     * this reads the on-disk cache, so a separate `deep-scan` run can tell
+     * "elevated available" from "run `login` first" without provoking a 403.
+     * Optional: only the real manager implements it; a minimal fake omits it
+     * and callers treat that as unavailable. Never captures or refreshes.
+     */
+    getCachedElevatedInfo?: () => Promise<{
+        available: boolean;
+        expiresInSeconds: number | undefined;
+    }>;
+    /**
+     * Same decode-only preflight as `getCachedElevatedInfo`, for the chatsvcagg /
+     * ic3 Teams-chat substrate tokens. `login`'s four-token status and
+     * `scopes-check` read these; a minimal fake omits them and callers treat that
+     * as unavailable.
+     */
+    getCachedChatsvcaggInfo?: () => Promise<{
+        available: boolean;
+        expiresInSeconds: number | undefined;
+    }>;
+    getCachedIc3Info?: () => Promise<{
+        available: boolean;
+        expiresInSeconds: number | undefined;
+    }>;
 };
-type SystemBrowserAuthFn = () => Promise<Result<{
-    accessToken: AccessToken;
-    refreshToken: string | null;
-    elevatedAccessToken?: AccessToken | null;
-    chatsvcaggAccessToken?: AccessToken | null;
-    ic3AccessToken?: AccessToken | null;
-    chatsvcaggRegion?: string;
-}, {
-    type: string;
-    message: string;
-}>>;
-declare const createAuthManagerFromApi: (browserAuth: BrowserAuth, cachePath: string, browserProfileDir: string, logger: Logger, fs: FileSystem, systemBrowserAuthFn?: SystemBrowserAuthFn, usePlaywrightFallback?: boolean, skipSystemBrowser?: boolean, recaptureSecondaryViaBrowser?: boolean) => AuthManager;
+declare const createAuthManagerFromApi: (browserAuth: BrowserAuth, cachePath: string, browserProfileDir: string, logger: Logger, fs: FileSystem, recaptureSecondaryViaBrowser?: boolean) => AuthManager;
 /**
- * QA-010: probe the token cache for a fresh access token. Handed to the
- * browser capture so its poll loop can short-circuit the multi-minute dance
+ * Probe the token cache for a fresh access token. Handed to the browser
+ * capture so its poll loop can short-circuit the multi-minute dance
  * when a concurrent process refreshes first (AAD rotates SPA refresh tokens,
  * so the loser of the race cannot refresh and falls into the browser leg).
  * Exported for the composition test; pure read, never writes.
@@ -96,10 +115,7 @@ declare const createAuthManager: (deps: {
     logger: Logger;
     fs?: FileSystem;
     browserProfileDir?: string;
-    systemBrowserAuth?: SystemBrowserAuthFn;
-    usePlaywrightFallback?: boolean;
-    skipSystemBrowser?: boolean;
     recaptureSecondaryViaBrowser?: boolean;
 }) => AuthManager;
 export { createAuthManager, createAuthManagerFromApi, createFreshCachedTokenProbe, stderrProgress };
-export type { AuthError, AuthManager, ElevatedOutcome, SystemBrowserAuthFn };
+export type { AuthError, AuthManager, ElevatedOutcome };

package/dist/infra/browser-auth.d.ts

@@ -13,7 +13,7 @@ type BrowserTokenResult = {
  * one retry after wiping the profile; `navigation_failed` is a network
  * issue, not worth retrying).
  *
- * Login-fix round-1: was previously `AccessToken | null`, which conflated
+ * was previously `AccessToken | null`, which conflated
  * "browser launch hung", "navigation broke", and "silent-SSO polling
  * timed out" into a single null and made the error message inaccurate.
  */
@@ -69,7 +69,7 @@ type Ic3TokenResult = {
 /**
  * Combined outcome of capturing all four tokens (Teams basic / M365
  * elevated / chatsvcagg substrate / IC3 substrate) inside one browser
- * session. Login-fix round-2 introduced this for the basic+elevated
+ * session. introduced this for the basic+elevated
  * pair; chatsvcagg was added next; IC3 is the most recent leg, capturing
  * the bearer Teams web uses for unbounded chat-history reads.
  *
@@ -84,7 +84,7 @@ type BothTokensResult = {
     readonly ic3: Ic3TokenResult;
     /**
      * Set when the Teams poll short-circuited because `freshCachedToken`
-     * found a token written by a concurrent process (QA-010). The caller
+     * found a token written by a concurrent process. The caller
      * must NOT persist this result — the cache is already the source of
      * truth, and `refreshToken` is null here (persisting would clobber the
      * winner's rotated refresh token).
@@ -92,7 +92,6 @@ type BothTokensResult = {
     readonly fromCache?: true;
 };
 type BrowserAuth = {
-    acquireToken: (scopes: string[], startUrl: string) => Promise<BrowserTokenResult | null>;
     /**
      * Capture an "elevated" Graph access token by navigating to a
      * different Microsoft web app whose first-party app identity is on
@@ -136,11 +135,11 @@ type BrowserAuth = {
      */
     acquireIc3Token: () => Promise<Ic3TokenResult>;
     /**
-     * Login-fix round-2: capture BOTH tokens inside ONE browser session.
+     * capture BOTH tokens inside ONE browser session.
      * After the Teams response listener intercepts the Teams token,
      * navigate the SAME page to the elevated URL and harvest the
      * M365ChatClient bearer from outgoing request headers. Cookies are
-     * live in memory, so federated SSO chains (e.g. Okta-fronted
+     * live in memory, so federated SSO chains (e.g. third-party-IdP-fronted
      * tenants) work without a second visible sign-in.
      *
      * Returns `teams: null` if no Teams token came back within the full
@@ -149,7 +148,9 @@ type BrowserAuth = {
      * failed inside the same session — caller decides whether to surface
      * the partial success.
      */
-    acquireBothTokens: (scopes: string[], teamsUrl: string) => Promise<BothTokensResult>;
+    acquireBothTokens: (teamsUrl: string, options?: {
+        skipCacheProbe?: boolean;
+    }) => Promise<BothTokensResult>;
     close: () => Promise<void>;
 };
 type ResponseLike = {
@@ -199,7 +200,7 @@ type BrowserAuthConfig = {
     readonly fs: FileSystem;
     readonly trace?: TraceFn;
     /**
-     * QA-010 (login hang): probe for a fresh token that landed in the cache
+     * (login hang): probe for a fresh token that landed in the cache
      * WHILE the browser capture is polling. AAD SPA refresh tokens rotate, so
      * when two processes race, the loser's refresh fails and it falls into the
      * full multi-minute browser dance — while the winner's fresh token sits in
@@ -210,7 +211,7 @@ type BrowserAuthConfig = {
     /**
      * User-visible progress sink (stderr in production). The browser capture
      * can legitimately take minutes (federated SSO, interactive sign-in); these
-     * one-liners are what separates "waiting on the user" from "hung" (QA-010).
+     * one-liners are what separates "waiting on the user" from "hung".
      */
     readonly onProgress?: (line: string) => void;
     readonly profileDir?: string;
@@ -222,19 +223,19 @@ type BrowserAuthConfig = {
     /**
      * Deadline for the SILENT elevated-token recapture flow (no user
      * interaction expected — persistent profile cookies do the SSO).
-     * Defaults to 20s. The audit (v1.0.0 §1.1) flagged that reusing the
+     * Defaults to 20s. The audit () flagged that reusing the
      * 5-minute interactive `pollDeadlineMs` for this silent path made
      * `list-chats` etc. hang for minutes when cookies were stale, blowing
      * the LLM tool-call window. With a tight cap, the flow either yields
      * a token quickly or fails with `auth_failed: elevated token capture
-     * timed out — run `ask-marcel login` to refresh.`
+     * timed out — run `ask-marcel-office login` to refresh.`
      */
     readonly elevatedRecaptureTimeoutMs?: number;
     /**
      * Hard deadline on `launchPersistentContext` + `newPage` for the
      * elevated capture path. Defaults to 15s. Distinct from
      * `elevatedRecaptureTimeoutMs` so the error message can name which
-     * step hung — launch vs polling. Audit login-fix round-1: previously
+     * step hung — launch vs polling. Audit previously
      * unguarded, so a hung Playwright launch (corrupt persistent profile
      * with stale `Singleton*` locks, or a slow browser binary) would
      * block the whole command indefinitely.

package/dist/infra/graph-client.d.ts

@@ -109,11 +109,37 @@ type TokenInfo = {
     /**
      * Seconds remaining until the cached token's `exp` claim — derived from
      * `expiresAt - now`. Negative when the token has already expired. Absent
-     * when the JWT did not carry an `exp` claim. Audit Jane-session §4: lets
-     * an LLM decide pre-emptively to run `ask-marcel login` (re-auth typically
+     * when the JWT did not carry an `exp` claim. lets
+     * an LLM decide pre-emptively to run `ask-marcel-office login` (re-auth typically
      * worth doing under ~5 minutes) without parsing the ISO string itself.
      */
     readonly expiresInSeconds: number | undefined;
+    /**
+     * Whether the *persisted* elevated (M365ChatClient) token — the one the
+     * historical-version download / convert commands need — is present and still
+     * usable, plus its raw seconds-to-expiry (`undefined` when absent). `available`
+     * is `false` when the auth manager cannot introspect it. Lets `deep-scan`
+     * preflight elevated access in a fresh process instead of turning every
+     * version download into a `403`.
+     */
+    readonly elevated: {
+        readonly available: boolean;
+        readonly expiresInSeconds: number | undefined;
+    };
+    /**
+     * The two Teams-chat substrate tokens (chatsvcagg / ic3), same decode-only
+     * `{ available, expiresInSeconds }` shape as `elevated`. `login` reports all four
+     * tiers so a warm session can see every token's runway; both self-heal from the
+     * shared refresh token, so they are informational rather than a preflight gate.
+     */
+    readonly chatsvcagg: {
+        readonly available: boolean;
+        readonly expiresInSeconds: number | undefined;
+    };
+    readonly ic3: {
+        readonly available: boolean;
+        readonly expiresInSeconds: number | undefined;
+    };
 };
 type FetchFn = (url: string, init?: RequestInit) => Promise<Response>;
 declare const createGraphClient: (auth: AuthManager, fetchFn?: FetchFn) => GraphClient;

package/dist/presenter/error-hints.d.ts

@@ -1,7 +1,7 @@
 /**
  * Translate Graph / substrate / CLI / validation errors into actionable hints.
  *
- * Audit Jane-session §2: bare `error: ErrorInvalidIdMalformed: Id is
+ * bare `error: ErrorInvalidIdMalformed: Id is
  * malformed.` had no remedy for the LLM — it had to guess where the bad ID
  * came from. This module is the centralised "what should I do about this"
  * lookup: pattern-match the error code (or, as a fallback, a substring of
@@ -12,14 +12,14 @@
  * `--output text` (as `hint:` / `source:` lines under the existing `error:`
  * line).
  *
- * Audit Jane-session §2 follow-up: the four error-envelope variants are
- *   - `graph`      — public Microsoft Graph API at /v1.0/
- *   - `substrate`  — Microsoft-internal chat substrates (chatsvcagg / IC3).
- *                    Tagged at the infra layer with `substrateHttp{N}_{name}`.
- *   - `cli`        — CLI itself (Commander parser, CLI rewrites of Graph
- *                    errors via `cli_rewrite_*` and `cli_reject_*` codes)
- *   - `validation` — Zod schema validation from use-cases (no `code` — pure
- *                    message-pattern fallback)
+ * the four error-envelope variants are
+ * - `graph` — public Microsoft Graph API at /v1.0/
+ * - `substrate` — Microsoft-internal chat substrates (chatsvcagg / IC3).
+ * Tagged at the infra layer with `substrateHttp{N}_{name}`.
+ * - `cli` — CLI itself (Commander parser, CLI rewrites of Graph
+ * errors via `cli_rewrite_*` and `cli_reject_*` codes)
+ * - `validation` — Zod schema validation from use-cases (no `code` — pure
+ * message-pattern fallback)
  *
  * Rule precedence: specific code matchers run FIRST, then message-pattern
  * fallbacks. The generic-validation rule sits LAST so it never overrides a

package/dist/use-cases/commands/build-command.d.ts

@@ -7,7 +7,7 @@ import { type ODataKey } from './odata-query.js';
  * passthroughs at all). `defaultSelect`, when set and the user did NOT pass
  * `--select`, is injected into the OData query string so default invocations
  * return a slim projection instead of a 50 KB resource. User-supplied
- * `--select` always wins. Audit Jane-session §A: pairs the `list-mail-attachments`
+ * `--select` always wins. pairs the `list-mail-attachments`
  * pattern with the builder layer so the 6 heaviest endpoints stop returning
  * the full Graph resource by default.
  */

package/dist/use-cases/commands/command-types.d.ts

@@ -52,7 +52,7 @@ type CommandOptionMeta = {
 };
 /**
  * A positional argument (i.e. NOT a `--flag`). Used today only for the
- * `docs` lifecycle command (`ask-marcel docs <command>`) but kept as its
+ * `docs` lifecycle command (`ask-marcel-office docs <command>`) but kept as its
  * own field so the manifest never claims a positional is a flag. An LLM
  * consumer reading `help-json` can branch on the presence of
  * `positionalArguments` to know to skip the `--` prefix.
@@ -100,7 +100,7 @@ type CommandMeta = {
     readonly paginationStrategy?: PaginationStrategy;
     /**
      * Graph permission scopes the endpoint requires. The basic Teams web-client
-     * token grants ~30 scopes (run `ask-marcel scopes-check` to see). Commands
+     * token grants ~30 scopes (run `ask-marcel-office scopes-check` to see). Commands
      * with unmet scopes return `403 Forbidden: Missing scope` at the wire. Use
      * this for pre-flight checks rather than failing on-the-wire. Optional —
      * populated only on commands where the audit confirmed a scope-failure
@@ -120,7 +120,7 @@ type CommandMeta = {
      * captured at login from `teams.microsoft.com`) — the Teams chat-content
      * commands. Like `needsElevatedToken`, an LLM should check this before
      * invoking and warm up an interactive `login`; a headless or stale session
-     * times out on these (the non-interactive silent-SSO limitation, QA-011).
+     * times out on these (the non-interactive silent-SSO limitation, ).
      */
     readonly needsSubstrateToken?: true;
     /**
@@ -128,7 +128,7 @@ type CommandMeta = {
      * or `{contentType, size, text}`) and is therefore a valid target for the
      * global `--output-path` flag. Used by the CLI composition to derive the
      * rejection-message whitelist from the manifest rather than hand-keeping it
-     * as a string literal. Audit round-8 Wave E2.
+     * as a string literal. Audit .
      */
     readonly producesBytes?: true;
     /**
@@ -157,7 +157,7 @@ type CommandMeta = {
      * substrate (chatsvcagg / IC3) that is not in the public Graph API and can
      * break on a Teams web-client update — the docstring "Best-effort, may break
      * on Microsoft client updates" warnings now have a structured pair.
-     * Audit Jane-session §6.
+     *
      */
     readonly stability?: 'experimental';
 };

package/dist/use-cases/commands/convert-local-file.d.ts

@@ -29,6 +29,10 @@ declare const schema: z.ZodObject<{
         true: "true";
         false: "false";
     }>>;
+    includeImages: z.ZodOptional<z.ZodEnum<{
+        true: "true";
+        false: "false";
+    }>>;
     maxCells: z.ZodOptional<z.ZodString>;
 }, z.core.$strip>;
 declare const executeLocal: (fs: FileSystem, params: Record<string, string>) => Promise<Result<unknown, GraphError>>;

package/dist/use-cases/commands/create-forward-draft.d.ts

@@ -0,0 +1,12 @@
+import { z } from 'zod';
+import type { Command, CommandMeta } from './command-types.js';
+declare const schema: z.ZodObject<{
+    forwardMessageId: z.ZodString;
+    toRecipients: z.ZodString;
+    ccRecipients: z.ZodOptional<z.ZodString>;
+    bodyContent: z.ZodString;
+    subject: z.ZodOptional<z.ZodString>;
+}, z.core.$strip>;
+declare const execute: Command['execute'];
+declare const meta: CommandMeta;
+export { execute, meta, schema };

package/dist/use-cases/commands/create-reply-draft.d.ts

@@ -0,0 +1,10 @@
+import { z } from 'zod';
+import type { Command, CommandMeta } from './command-types.js';
+declare const schema: z.ZodObject<{
+    replyToMessageId: z.ZodString;
+    bodyContent: z.ZodString;
+    subject: z.ZodOptional<z.ZodString>;
+}, z.core.$strip>;
+declare const execute: Command['execute'];
+declare const meta: CommandMeta;
+export { execute, meta, schema };

package/dist/use-cases/commands/docs.d.ts

@@ -13,7 +13,7 @@ export type DocsError = {
  * `scopesRequired` — everything the LLM only needs once it's already decided
  * to invoke. `stability` is kept (it's a discovery-time concern: LLMs prefer
  * stable siblings when they exist, so they need to see the tag at discovery
- * time, not after a second full-manifest fetch). Audit Jane-session §B/§6.
+ * time, not after a second full-manifest fetch). /§6.
  */
 export type TerseManifestEntry = {
     readonly name: string;

package/dist/use-cases/commands/get-schedule.d.ts

@@ -0,0 +1,11 @@
+import { z } from 'zod';
+import type { Command, CommandMeta } from './command-types.js';
+declare const schema: z.ZodObject<{
+    schedules: z.ZodString;
+    startDateTime: z.ZodPipe<z.ZodString, z.ZodTransform<import("../../domain/iso-datetime.js").IsoDateTime, string>>;
+    endDateTime: z.ZodPipe<z.ZodString, z.ZodTransform<import("../../domain/iso-datetime.js").IsoDateTime, string>>;
+    availabilityViewInterval: z.ZodOptional<z.ZodString>;
+}, z.core.$strip>;
+declare const execute: Command['execute'];
+declare const meta: CommandMeta;
+export { execute, meta, schema };

package/dist/use-cases/commands/graph-scopes.d.ts

@@ -1,5 +1,5 @@
 /**
- * Central Microsoft Graph permission scope map (audit round-8 Wave C).
+ * Central Microsoft Graph permission scope map.
  *
  * Source of truth: Microsoft Graph permissions reference
  * (https://learn.microsoft.com/en-us/graph/permissions-reference). Each

package/dist/use-cases/commands/image-extraction.d.ts

@@ -1,10 +1,11 @@
 import type { Result } from '../../domain/result.js';
 import type { GraphError } from '../../infra/graph-client.js';
+import type { MediaEnvelope } from './media-files.js';
 /**
  * Shared by extract-drive-item-images and extract-mail-attachment-images: pick the
  * extractor for the file's extension and run it, or return a 415 whose tail
  * (`fetchHint`) names the caller's raw-bytes route. Both commands fetch / decode the
  * bytes first, then hand them here, so the dispatch + media envelope live in one place.
  */
-declare const extractImagesFromBytes: (bytes: Uint8Array, name: string, fetchHint: string) => Promise<Result<unknown, GraphError>>;
+declare const extractImagesFromBytes: (bytes: Uint8Array, name: string, fetchHint: string) => Promise<Result<MediaEnvelope, GraphError>>;
 export { extractImagesFromBytes };

package/dist/use-cases/commands/iso-datetime-schema.d.ts

@@ -6,7 +6,7 @@ import { z } from 'zod';
  * compose this into their schemas in place of `z.string().min(1)`; the
  * URL-builder sees the already-resolved canonical ISO form.
  *
- * Audit Jane-session §C: removes the manual ISO arithmetic an LLM had to do
+ * removes the manual ISO arithmetic an LLM had to do
  * to ask "what changed this week" against `list-calendar-view`. Type
  * inference is left to Zod so the calendar commands' shape signatures stay
  * compatible with `buildListCommand`'s `ZodRawShape` constraint.

package/dist/use-cases/commands/login-status.d.ts

@@ -0,0 +1,31 @@
+type RefreshRoute = 'automatic' | 'interactive';
+type TokenTier = {
+    readonly available: boolean;
+    readonly expiresInSeconds: number | undefined;
+};
+type TokenView = {
+    available: boolean;
+    expiresInSeconds?: number;
+    refresh: RefreshRoute;
+    reason?: string;
+};
+type LoginStatus = {
+    status: 'authenticated';
+    tokens: {
+        basic: TokenView;
+        elevated: TokenView;
+        chatsvcagg: TokenView;
+        ic3: TokenView;
+    };
+    hint: string;
+};
+type LoginStatusInput = {
+    readonly basicExpiresInSeconds: number | undefined;
+    readonly elevated: TokenTier;
+    readonly chatsvcagg: TokenTier;
+    readonly ic3: TokenTier;
+    readonly elevatedFailureReason?: string;
+};
+declare const buildLoginStatus: (input: LoginStatusInput) => LoginStatus;
+export { buildLoginStatus };
+export type { LoginStatus, LoginStatusInput };

package/dist/use-cases/commands/login.d.ts

@@ -2,5 +2,7 @@ import { z } from 'zod';
 import type { Result } from '../../domain/result.js';
 import type { AuthManager } from '../../infra/auth.js';
 declare const schema: z.ZodObject<{}, z.core.$strict>;
-declare const execute: (auth: AuthManager) => Promise<Result<string, import("../../infra/auth.js").AuthError>>;
+declare const execute: (auth: AuthManager, options?: {
+    force?: boolean;
+}) => Promise<Result<string, import("../../infra/auth.js").AuthError>>;
 export { execute, schema };

package/dist/use-cases/commands/markdown-pipeline.d.ts

@@ -5,11 +5,11 @@ import { type InlineAttachment } from './inline-image-embedder.js';
  * Orchestrate the four steps that turn a Graph `?format=html` content
  * call into a markdown envelope:
  *
- *   1. getBinary(contentPath)
- *   2. if Graph returned a 302 downloadUrl, follow via fetchUrl (host
- *      allow-list enforced inside fetchUrl, Hardening #3)
- *   3. embedInlineImages over any cid: refs (Hardening #1: image/* only)
- *   4. htmlToMarkdown via turndown
+ * 1. getBinary(contentPath)
+ * 2. if Graph returned a 302 downloadUrl, follow via fetchUrl (host
+ * allow-list enforced inside fetchUrl, Hardening #3)
+ * 3. embedInlineImages over any cid: refs (Hardening #1: image/* only)
+ * 4. htmlToMarkdown via turndown
  *
  * Returns `{ contentType: 'text/markdown', size, text }` on success.
  */

package/dist/use-cases/commands/option-descriptions.d.ts

@@ -2,4 +2,4 @@
  * `--drive-id` description for every generic OneDrive / SharePoint drive-item
  * command. Always points the caller at how to obtain a drive id.
  */
-export declare const DRIVE_ID_DESCRIPTION = "Microsoft Graph drive ID. Use `ask-marcel list-drives` for the personal OneDrive, or `ask-marcel list-sharepoint-site-drives --site-id <id>` for a SharePoint document library.";
+export declare const DRIVE_ID_DESCRIPTION = "Microsoft Graph drive ID. Use `ask-marcel-office list-drives` for the personal OneDrive, or `ask-marcel-office list-sharepoint-site-drives --site-id <id>` for a SharePoint document library.";

package/dist/use-cases/commands/output-path.d.ts

@@ -11,10 +11,10 @@ import type { FileSystem } from '../ports/filesystem.js';
  * Two recognized inline shapes — both produced by `inlineBinary` and
  * `office-to-markdown`:
  *
- *   1. `{ contentType, size, base64 }` — written via `fs.writeBytes`,
- *      with `base64` replaced by `savedTo`.
- *   2. `{ contentType, size, text }`    — written via `fs.writeText`,
- *      with `text` replaced by `savedTo`.
+ * 1. `{ contentType, size, base64 }` — written via `fs.writeBytes`,
+ * with `base64` replaced by `savedTo`.
+ * 2. `{ contentType, size, text }` — written via `fs.writeText`,
+ * with `text` replaced by `savedTo`.
  *
  * Anything else (plain JSON gets, error envelopes, etc.) returns
  * `no_inlined_bytes` so the CLI can surface a clear error rather than

package/dist/use-cases/commands/parse-recipients.d.ts

@@ -0,0 +1,14 @@
+/**
+ * Parse a comma-separated recipient string into Microsoft Graph address
+ * objects. Shared by the mail-draft write commands (create-mail-draft,
+ * update-mail-draft, create-forward-draft) so the split/trim/empty-drop
+ * behaviour stays identical across all three. Whitespace around each address
+ * is trimmed and empty segments (leading, trailing, or doubled commas) are
+ * dropped, so `"a@x.com, , b@x.com,"` yields exactly two recipients.
+ */
+declare const parseRecipients: (csv: string) => Array<{
+    emailAddress: {
+        address: string;
+    };
+}>;
+export { parseRecipients };

package/dist/use-cases/commands/zip-archive-to-markdown.d.ts

@@ -1,5 +1,6 @@
 import type { Result } from '../../domain/result.js';
 import type { GraphError } from '../../infra/graph-client.js';
+import type { MediaEnvelope } from './media-files.js';
 /**
  * Shared "unzip + convert every contained file" core behind
  * `convert-drive-item-zip` (a OneDrive / SharePoint .zip),
@@ -8,7 +9,7 @@ import type { GraphError } from '../../infra/graph-client.js';
  * `bytesToMarkdown` dispatch the markdown commands use; an entry the dispatch
  * can't convert (image, binary, nested archive, scanned PDF) is LISTED with a
  * note instead of failing the whole archive. Notes use the container-neutral
- * NESTED_HINTS (QA-007): entries live INSIDE the zip, so caller-specific
+ * NESTED_HINTS: entries live INSIDE the zip, so caller-specific
  * sibling-command pointers (`extract-drive-item-images`, …) cannot reach them.
  */
 declare const MAX_ENTRIES = 100;
@@ -18,6 +19,7 @@ type FileResult = {
     readonly size?: number;
     readonly text?: string;
     readonly note?: string;
+    readonly images?: MediaEnvelope['media'];
 };
 type ZipArchiveResult = {
     readonly count: number;
@@ -25,6 +27,6 @@ type ZipArchiveResult = {
     readonly totalEntries?: number;
     readonly files: ReadonlyArray<FileResult>;
 };
-declare const convertZipArchive: (bytes: Uint8Array, includeMetadata: boolean) => Promise<Result<ZipArchiveResult, GraphError>>;
+declare const convertZipArchive: (bytes: Uint8Array, includeMetadata: boolean, includeImages?: boolean) => Promise<Result<ZipArchiveResult, GraphError>>;
 export { convertZipArchive, MAX_ENTRIES };
 export type { FileResult, ZipArchiveResult };

package/dist/use-cases/ports/filesystem.d.ts

@@ -19,7 +19,7 @@ export type FileSystem = {
     readonly writeBytes: (path: string, bytes: Uint8Array) => Promise<Result<void, FileSystemError>>;
     /**
      * Restrict a file's permission bits (e.g. 0o600 on the token cache so
-     * other local users cannot read cached secrets — QA-001).
+     * other local users cannot read cached secrets — ).
      */
     readonly chmod: (path: string, mode: number) => Promise<Result<void, FileSystemError>>;
     readonly deleteIfExists: (path: string) => Promise<Result<void, FileSystemError>>;