document360-writer 0.5.17 → 0.5.18

package/dist/commands/catchup.d.ts

@@ -1,3 +1,4 @@
+import { computeSyncStatus, planPull, applyPull } from 'document360-engine';
 import type { ReplContext } from '../repl.js';
 import type { SlashCommandResult } from './index.js';
 export type PendingSummary = {
@@ -17,6 +18,42 @@ export declare function parseCatchUpArgs(args: string[]): {
 export declare function buildCatchUpPrompt({ publish }: {
     publish: boolean;
 }): string;
-/** Classic-REPL `/catch-up`. Always forwards (it's the double-check) — even with no local queue it still
-    runs the sync/gap check to catch code changes the builder didn't hint. */
+/** Outcome of the Phase-0 portal reconcile (catch-up pulls portal changes BEFORE the agent writes). */
+export type PortalReconcileResult = {
+    /** Repo-relative paths whose clean portal edits were pulled into local (lossless — local was unchanged). */
+    pulled: string[];
+    /** Paths changed in BOTH places — left untouched for the user to resolve. */
+    conflicts: string[];
+    /** Titles of NEW portal articles not local yet — surfaced, not imported (import lands with P3/manifest). */
+    untrackedRemote: string[];
+    /** Per-article pull failures (left for /sync pull). */
+    failed: {
+        path: string;
+        error: string;
+    }[];
+    /** Set when the status check itself failed — catch-up still proceeds (the agent re-checks). */
+    error?: string;
+};
+/** Injectable seam (tests). Defaults to the real engine sync primitives. */
+export type ReconcileDeps = {
+    status: typeof computeSyncStatus;
+    plan: typeof planPull;
+    apply: typeof applyPull;
+};
+/**
+ * Phase 0 of /catch-up — reconcile the portal with TODAY's per-article sync, BEFORE the agent works:
+ * auto-pull clean `remote-ahead` (lossless — local unchanged), and surface `conflict` (skipped — never
+ * overwrite) + `untracked-remote` (new portal articles can't be imported yet). Best-effort: a status
+ * failure returns `{ error }` and catch-up proceeds (the agent's own d360_sync_status still gates). The
+ * manifest (portal-aware-sync P1.1) will make the status check cheap once it ships on the environment.
+ */
+export declare function reconcilePortal(opts: {
+    cwd: string;
+    profileName?: string;
+}, deps?: ReconcileDeps): Promise<PortalReconcileResult>;
+/** Human summary of the reconcile, each line tagged for tone (✓ ok · ℹ info · ⚠ warn). Empty when the
+    portal was already in sync (nothing to report). */
+export declare function reconcileSummaryLines(r: PortalReconcileResult): string[];
+/** Classic-REPL `/catch-up`. Reconciles the portal first (Phase 0), then forwards the queued-work prompt
+    (the double-check) — even with no local queue it still runs, to catch code changes the builder didn't hint. */
 export declare function catchupCommand(args: string[], ctx?: ReplContext): Promise<SlashCommandResult>;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "document360-writer",
-  "version": "0.5.17",
+  "version": "0.5.18",
   "description": "Standalone documentation agent CLI. Reads your code, writes your docs. Specialized for Document360 publishing.",
   "type": "module",
   "bin": {