@vibecompass/vibecompass 0.17.2 → 0.17.3

package/CHANGELOG.md

@@ -1,5 +1,18 @@
 # Changelog
 
+## 0.17.3 - 2026-10-12
+
+A small sync release: `push` tells you what the hosted dashboard could not
+show. The lane brief stays opt-in (D-368).
+
+- `push` prints the server's projection warnings. The server builds the
+  dashboard in the same step as the push and reports anything it could not
+  build, such as a file whose decision links could not be read
+  (`lineage_extraction_failed`, D-371). `push` now prints each one as a
+  `Note: <code> (<path>): <message>` line after the run, so you learn about it
+  in the terminal instead of only from a dashboard notice. The push itself
+  still succeeded. A push with nothing to report prints no extra lines.
+
 ## 0.17.2 - 2026-10-12
 
 Lockstep release with the app's lineage port: section headings open a fence

package/README.md

@@ -339,6 +339,11 @@ changed canonical project-memory files and the hosted dashboard should catch
 up. Hosted-only projects do not use a local authoritative push; update or
 refresh them through the hosted dashboard/proposal flow.
 
+`push` prints a `Note: <code> (<path>): <message>` line for anything the
+hosted dashboard could not build from your files, such as a file whose decision
+links could not be read. The push itself succeeded; the note names the file so
+you can check it.
+
 ### Where the token lives (D-355)
 
 Hosted commands look for the token in this order:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vibecompass/vibecompass",
-  "version": "0.17.2",
+  "version": "0.17.3",
   "description": "Local-first project-memory core for VibeCompass",
   "type": "module",
   "bin": {

package/src/cli.js

@@ -619,6 +619,10 @@ export async function runCli(argv, io = createDefaultIo(), runtime = {}) {
     if (result.staleProposalIds.length > 0) {
       io.stdout.write(`Stale proposals: ${result.staleProposalIds.join(', ')}\n`);
     }
+    for (const warning of result.warnings) {
+      const where = warning.path ? ` (${warning.path})` : '';
+      io.stdout.write(`Note: ${warning.code}${where}: ${warning.message}\n`);
+    }
     io.stdout.write(`Recorded ${result.manifestPath}\n`);
     io.stdout.write(`${result.message}\n`);
     return 0;

package/src/sync.js

@@ -56,10 +56,32 @@ export async function pushProjectMemory(options = {}, environment = {}) {
     remoteRevisionId: response.remote_revision_id,
     appliedProposalIds: response.applied_proposal_ids ?? [],
     staleProposalIds: response.stale_proposal_ids ?? [],
+    warnings: readProjectionWarnings(response),
     message: `Pushed ${documents.length} canonical document${documents.length === 1 ? '' : 's'} to hosted project memory.`,
   };
 }
 
+/**
+ * The hosted push projects the dashboard read model in the same transaction
+ * (D-239) and reports what it could not project as `projection.warnings`
+ * (`{ code, message, path? }`), such as `lineage_extraction_failed` (D-371).
+ * The push itself succeeded, so these are notes, not errors. A server that
+ * sends no projection block, or an entry without a message, yields nothing.
+ */
+function readProjectionWarnings(response) {
+  const warnings = response?.projection?.warnings;
+  if (!Array.isArray(warnings)) {
+    return [];
+  }
+  return warnings
+    .filter((warning) => warning && typeof warning === 'object' && typeof warning.message === 'string')
+    .map((warning) => ({
+      code: typeof warning.code === 'string' && warning.code ? warning.code : 'projection_warning',
+      message: warning.message,
+      ...(typeof warning.path === 'string' && warning.path ? { path: warning.path } : {}),
+    }));
+}
+
 export async function pullPreviewProjectMemory(options = {}, environment = {}) {
   const context = await loadSyncContext(options, environment);
   const existingManifest = await readJsonIfPresent(context.manifestPath);