@cardstack/boxel-cli 0.3.0-unstable.58 → 0.3.0-unstable.87

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cardstack/boxel-cli",
-  "version": "0.3.0-unstable.58",
+  "version": "0.3.0-unstable.87",
   "license": "MIT",
   "description": "CLI tools for Boxel workspace management",
   "main": "./dist/index.js",
@@ -58,8 +58,8 @@
     "ts-node": "^10.9.1",
     "vite": "^6.3.2",
     "vitest": "^2.1.9",
-    "@cardstack/local-types": "0.0.0",
     "@cardstack/postgres": "0.0.0",
+    "@cardstack/local-types": "0.0.0",
     "@cardstack/runtime-common": "1.0.0"
   },
   "publishConfig": {

package/src/commands/realm/sync.ts

@@ -51,6 +51,11 @@ class RealmSyncer extends RealmSyncBase {
   remoteDeletedFiles: string[] = [];
   localDeletedFiles: string[] = [];
   skippedConflicts: string[] = [];
+  // Top-level message from a failed /_atomic batch (e.g. "Atomic upload
+  // failed: 500 Internal Server Error"). Surfaced in `SyncResult.error`
+  // so callers don't have to scrape stderr to learn why the batch
+  // failed.
+  uploadFatalMessage?: string;
 
   constructor(
     private syncOptions: BiSyncOptions,
@@ -320,7 +325,24 @@ class RealmSyncer extends RealmSyncBase {
       this.pushedFiles.push(...result.succeeded);
       if (result.error) {
         this.hasError = true;
-        console.error(result.error.message);
+        // Fold the per-file titles into the surfaced message so
+        // SyncResult.error carries the server's JSON:API error
+        // payload (e.g. "Write Error"), not just the HTTP status
+        // line. Distinct titles only — repeated identical titles
+        // (the common case for a top-level write failure) would
+        // otherwise produce noisy duplicates. The summary line is
+        // re-echoed by registerSyncCommand at the end of the run
+        // via `Error: ${result.error}`, so we no longer also emit
+        // the standalone status line inline — that would duplicate
+        // it in CLI output. The per-file loop stays because it
+        // carries path-level detail the summary aggregates away.
+        let titles = Array.from(
+          new Set(result.error.perFile.map((e) => e.title)),
+        );
+        this.uploadFatalMessage =
+          titles.length > 0
+            ? `${result.error.message} (${titles.join('; ')})`
+            : result.error.message;
         for (const entry of result.error.perFile) {
           console.error(`  ${entry.path}: ${entry.title}`);
         }
@@ -679,7 +701,11 @@ function buildSyncErrorMessage(syncer: RealmSyncer): string {
     `${syncer.skippedConflicts.length} conflicts skipped`,
   ].join(', ');
 
-  return `Sync completed with errors. ${summary}.`;
+  let base = `Sync completed with errors. ${summary}.`;
+  if (syncer.uploadFatalMessage) {
+    return `${base} ${syncer.uploadFatalMessage}`;
+  }
+  return base;
 }
 function emptyResult(partial: Pick<SyncResult, 'error'>): SyncResult {
   return {