ask-marcel-office-cli 2.1.0 → 2.3.0

package/dist/composition/build-deps.d.ts

@@ -11,6 +11,14 @@ export type BuildDepsConfig = {
     readonly fs?: FileSystem;
     readonly processRunner?: ProcessRunner;
     readonly createAuth?: typeof createAuthManager;
+    /**
+     * Whether this is an interactive session (a real TTY with a human present).
+     * Defaults to `process.stdin.isTTY`. When true, the command-path auth keeps
+     * the first-run auto-launched sign-in browser for the basic token; when false
+     * (a headless / piped agent run) that rung fails fast instead of hanging on
+     * the interactive-login poll. Injectable so tests pin the behavior.
+     */
+    readonly interactive?: boolean;
 };
 /**
  * Builds an AuthManager configured for an interactive `login` run — unlike

package/dist/composition/mcp.d.ts

@@ -0,0 +1,20 @@
+import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
+import type { AuthManager } from '../infra/auth.js';
+import type { GraphClient } from '../infra/graph-client.js';
+import type { FileSystem } from '../use-cases/ports/filesystem.js';
+import type { LoginAuthFactory } from './build-deps.js';
+type BuildMcpServerDeps = {
+    readonly auth: AuthManager;
+    readonly graph: GraphClient;
+    readonly fs: FileSystem;
+    readonly version?: string;
+    /**
+     * Builds the AuthManager for an interactive `login` run (it may recapture
+     * secondary tokens via the browser, unlike the command-path `auth`). Mirrors
+     * `cli.ts`: when omitted (tests), the login tool falls back to `auth`.
+     */
+    readonly makeLoginAuth?: LoginAuthFactory;
+};
+declare const buildMcpServer: (deps: BuildMcpServerDeps) => McpServer;
+export { buildMcpServer };
+export type { BuildMcpServerDeps };

package/dist/composition/run-registry-command.d.ts

@@ -0,0 +1,43 @@
+import type { GraphClient } from '../infra/graph-client.js';
+import type { ErrorSource } from '../presenter/error-hints.js';
+import type { RenderSurface, SizeHintContext } from '../presenter/render-to-string.js';
+import type { Command } from '../use-cases/commands/command-types.js';
+import type { OutputDirError, OutputPathError } from '../use-cases/commands/output-path.js';
+import type { Result } from '../domain/result.js';
+import type { FileSystem } from '../use-cases/ports/filesystem.js';
+/**
+ * The facts the oversized-response banner needs to name a remedy this caller
+ * can actually use. Derived from the manifest, so a new command gets an honest
+ * banner for free. See `SizeHintContext` in the presenter for the why.
+ */
+declare const buildSizeHintContext: (commandName: string, command: Command, surface: RenderSurface) => SizeHintContext;
+declare const formatOutputPathError: (error: OutputPathError, commandName: string, surface: RenderSurface) => string;
+declare const formatOutputDirError: (error: OutputDirError, commandName: string) => string;
+export type RunRegistryCommandDeps = {
+    readonly graph: GraphClient;
+    readonly fs: FileSystem;
+};
+export type RunRegistryCommandRequest = {
+    /** Canonical registry name — drives the manifest-derived error messages. */
+    readonly name: string;
+    readonly command: Command;
+    /** Raw params, keyed by the canonical camelCase option keys. */
+    readonly params: Record<string, string>;
+    readonly outputPath?: string;
+    readonly outputDir?: string;
+    /** Which front end asked. Decides whether a remedy may mention a shell. */
+    readonly surface: RenderSurface;
+};
+/**
+ * `source` / `code` / `retryAfterSeconds` are optional on purpose: the
+ * --output-path and --output-dir rejections carry none of them, and stamping a
+ * source they never had would change the shipped error envelope.
+ */
+export type RunRegistryCommandFailure = {
+    readonly message: string;
+    readonly code?: string;
+    readonly source?: ErrorSource;
+    readonly retryAfterSeconds?: number;
+};
+export declare const runRegistryCommand: (deps: RunRegistryCommandDeps, request: RunRegistryCommandRequest) => Promise<Result<unknown, RunRegistryCommandFailure>>;
+export { buildSizeHintContext, formatOutputDirError, formatOutputPathError };

package/dist/domain/tenant-id.d.ts

@@ -0,0 +1,9 @@
+import type { Result } from './result.js';
+export type TenantId = string & {
+    readonly __brand: 'TenantId';
+};
+export type TenantIdError = {
+    type: 'invalid_tenant_id';
+};
+export declare const tenantId: (raw: string) => Result<TenantId, TenantIdError>;
+export declare const tenantIdUnsafe: (raw: string) => TenantId;

package/dist/domain/utilities/spo-tenant.d.ts

@@ -0,0 +1,20 @@
+/**
+ * Maps a SharePoint / OneDrive host to the tenant domain that owns it, so a
+ * sharing URL alone is enough to discover which tenant to ask for a guest token.
+ *
+ * A tenant's SharePoint hostname is derived from its initial `*.onmicrosoft.com`
+ * domain: `contoso.onmicrosoft.com` serves `contoso.sharepoint.com` for sites and
+ * `contoso-my.sharepoint.com` for personal OneDrive. Reversing that gives a
+ * domain the Entra OIDC discovery endpoint resolves to a tenant id, with no
+ * credentials and no prior knowledge of the tenant.
+ *
+ * Returns null for anything that is not a tenant SharePoint host — including
+ * `1drv.ms`, Microsoft's CONSUMER short-link host, which belongs to no Entra
+ * tenant. A null answer means "no guest token applies here", which leaves the
+ * caller on its home token: the current behaviour, not a failure.
+ *
+ * Verified against a real partner tenant 2026-07-16. This mapping is a
+ * convention rather than a guarantee, so callers must treat a failed discovery
+ * as "cannot cross to this tenant" and surface it, never as a crash.
+ */
+export declare const spoHostToTenantDomain: (host: string) => string | null;