document360-writer 0.5.70 → 0.5.72

package/dist/commands/catchup.d.ts

@@ -1,4 +1,4 @@
-import { computeSyncStatus, planPull, applyPull } from 'document360-engine';
+import { computeSyncStatus, planPull, applyPull, planImport, applyImport } from 'document360-engine';
 import type { ReplContext } from '../repl.js';
 import type { SlashCommandResult } from './index.js';
 export type PendingSummary = {
@@ -18,15 +18,15 @@ export declare function parseCatchUpArgs(args: string[]): {
 export declare function buildCatchUpPrompt({ publish }: {
     publish: boolean;
 }): string;
-/** Outcome of the Phase-0 portal reconcile (catch-up pulls portal changes BEFORE the agent writes). */
+/** Outcome of the Phase-0 portal reconcile (catch-up brings the portal fully down BEFORE the agent writes). */
 export type PortalReconcileResult = {
     /** Repo-relative paths whose clean portal edits were pulled into local (lossless — local was unchanged). */
     pulled: string[];
+    /** Repo-relative paths of NEW portal articles imported into local drafts (were untracked-remote). */
+    imported: 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 /pull). */
+    /** Per-article pull/import failures (left for /pull). */
     failed: {
         path: string;
         error: string;
@@ -39,13 +39,16 @@ export type ReconcileDeps = {
     status: typeof computeSyncStatus;
     plan: typeof planPull;
     apply: typeof applyPull;
+    planImport: typeof planImport;
+    applyImport: typeof applyImport;
 };
 /**
- * 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.
+ * Phase 0 of /catch-up — bring the portal FULLY down before the agent works, so "/catch-up" is the one
+ * command a returning user needs (pull + process). Auto-pull clean `remote-ahead` (lossless — local
+ * unchanged) AND import `untracked-remote` (new portal-authored articles → local drafts), the same way
+ * bare /pull does; `conflict` is surfaced + skipped (never overwrite a copy we can't trust). Best-effort:
+ * a status failure returns `{ error }` and catch-up proceeds (the agent's own d360_sync_status still gates).
+ * The hidden feedback category is excluded upstream (computeSyncStatus), so its articles never import here.
  */
 export declare function reconcilePortal(opts: {
     cwd: string;

package/package.json

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