ask-marcel-office-cli 1.4.0 → 1.5.0

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

@@ -1,4 +1,5 @@
 import type { AuthManager } from '../infra/auth.js';
+import { createAuthManager } from '../infra/auth.js';
 import type { GraphClient } from '../infra/graph-client.js';
 import type { FileSystem } from '../use-cases/ports/filesystem.js';
 import type { Logger } from '../use-cases/ports/logger.js';
@@ -9,12 +10,24 @@ export type BuildDepsConfig = {
     readonly home?: string;
     readonly fs?: FileSystem;
     readonly processRunner?: ProcessRunner;
+    readonly createAuth?: typeof createAuthManager;
 };
+/**
+ * Builds an AuthManager configured for an interactive `login` run. The login
+ * command varies the browser strategy at runtime (`--use-extension`), so the
+ * composition root hands the CLI a factory rather than a single pre-built
+ * manager — keeping the concrete `createAuthManager` wiring (cache path, env)
+ * out of `cli.ts` and the action testable with an injected fake.
+ */
+export type LoginAuthFactory = (opts: {
+    readonly useExtension: boolean;
+}) => AuthManager;
 export type BuiltDeps = Readonly<{
     logger: Logger;
     auth: AuthManager;
     graph: GraphClient;
     processRunner: ProcessRunner;
     fs: FileSystem;
+    makeLoginAuth: LoginAuthFactory;
 }>;
 export declare const buildDeps: (config?: BuildDepsConfig) => BuiltDeps;

package/dist/composition/cli.d.ts

@@ -4,6 +4,7 @@ import type { GraphClient } from '../infra/graph-client.js';
 import type { FileSystem } from '../use-cases/ports/filesystem.js';
 import type { Logger } from '../use-cases/ports/logger.js';
 import type { ProcessRunner } from '../use-cases/ports/process-runner.js';
+import type { LoginAuthFactory } from './build-deps.js';
 type BuildCliDeps = {
     readonly auth: AuthManager;
     readonly graph: GraphClient;
@@ -13,6 +14,13 @@ type BuildCliDeps = {
     readonly version?: string;
     readonly packageManager?: 'npm' | 'bun';
     readonly onCommandError?: () => void;
+    /**
+     * Builds the AuthManager for an interactive `login` run from the `--use-extension`
+     * flag. Supplied by the composition root (`build-deps.ts`); when omitted (tests),
+     * the login action falls back to the injected `auth`, so a single fake drives both
+     * `login.execute` and `getLastElevatedOutcome`.
+     */
+    readonly makeLoginAuth?: LoginAuthFactory;
 };
 declare const buildCli: (deps: BuildCliDeps) => Command;
 export { buildCli };

package/dist/domain/iso-datetime.d.ts

@@ -5,7 +5,7 @@ import type { Result } from './result.js';
  * built from a calendar-window parameter accepts this type so an unvalidated
  * `string` can't slip through.
  *
- * Audit Hervé-session §C: the previous calendar commands accepted any
+ * Audit Jane-session §C: the previous calendar commands accepted any
  * `z.string().min(1)`, so the LLM had to compute "last week" → ISO by hand.
  * `parseIsoDateTime` turns "7d" / "monday" / "today" / "2026-04-01" / a strict
  * ISO timestamp into the canonical ISO form, so the URL builders stay

package/dist/domain/utilities/archive-status.d.ts

@@ -0,0 +1,18 @@
+/**
+ * Archive detection for Microsoft Graph `site` resources. A site collection can
+ * be archived two ways the CLI must recognise:
+ *   1. Graph returns the site with `siteCollection.archivalDetails.archiveStatus`
+ *      set (the documented v1.0 mechanism for admin-archived team sites).
+ *   2. Graph fails the metadata call itself — auto-archived OneDrives (unlicensed
+ *      ≥93 days) come back as `423 resourceLocked` ("Access to this site has been
+ *      blocked"), the same signal `list-accessible-drives` already treats as an
+ *      unreachable, drop-silently site.
+ */
+declare const archiveStatusOf: (resource: unknown) => string | undefined;
+declare const isArchivedSite: (resource: unknown) => boolean;
+declare const errorIndicatesArchived: (e: {
+    readonly status?: number;
+    readonly code?: string;
+    readonly message?: string;
+}) => boolean;
+export { archiveStatusOf, errorIndicatesArchived, isArchivedSite };

package/dist/domain/utilities/site-url-classifier.d.ts

@@ -0,0 +1,15 @@
+/**
+ * Classify a SharePoint `webUrl` the Microsoft Search index returns but which is
+ * NOT a navigable site collection — fetching it 404s. Three families show up:
+ *   1. SharePoint Add-in (app) webs — isolated `<tenant>-<hex>.sharepoint.com`
+ *      hosts. Add-ins are deprecated; the site redirects to
+ *      `/_layouts/15/AddinDeprecationAnnoucement.aspx`.
+ *   2. SharePoint Embedded containers — `/contentstorage/...`, backing storage
+ *      for apps (Loop / Designer / Copilot), never a navigable site collection.
+ *   3. System pages — any `/_layouts/...` URL is a page, not a site root.
+ *
+ * Detection is by URL shape alone (no Graph call), so these are dropped from the
+ * site listing before the per-site archive probe even runs.
+ */
+declare const isNonNavigableSiteUrl: (webUrl: string) => boolean;
+export { isNonNavigableSiteUrl };