@githolon/dsl 0.119.9 → 0.119.11

package/dart/CHANGELOG.md

@@ -1,3 +1,7 @@
+## 0.70.11
+
+- A pack tidy that fails after a sync no longer shows the application as still preparing: the read index a sync owes is reported under its own read cause, and a SYNC report is custody upkeep alone (CAP-952).
+
 ## 0.70.10
 
 Deliver the shared runtime's owned, bounded pack import continuations and cancellation with the matching kernel protocol, preventing concurrent workspace acquisition from dropping an active import.

package/dart/lib/src/reception/workspace_preparation_report.dart

@@ -55,47 +55,56 @@ final class WorkspacePreparationReport {
     WorkspacePreparationReport? previous,
   }) {
     final kernel = progress.hasKernel() ? progress.kernel : null;
-    final retry =
-        progress.hasRetryAfterMillis() ? progress.retryAfterMillis : null;
+    final retry = progress.hasRetryAfterMillis()
+        ? progress.retryAfterMillis
+        : null;
     final step = progress.satisfiedByRead
         ? WorkspacePreparationStep.complete
         : kernel == null
-            ? switch (progress.cause) {
-                protocol.ReadMaintenanceCause
-                      .READ_MAINTENANCE_CAUSE_DOMAIN_PREPARATION =>
-                  WorkspacePreparationStep.preparingWrites,
-                protocol.ReadMaintenanceCause.READ_MAINTENANCE_CAUSE_OPEN ||
-                protocol
-                    .ReadMaintenanceCause.READ_MAINTENANCE_CAUSE_READ_DEBT ||
-                protocol
-                      .ReadMaintenanceCause.READ_MAINTENANCE_CAUSE_RESIDENCY =>
-                  WorkspacePreparationStep.preparingReads,
-                _ => WorkspacePreparationStep.preparingWorkspace,
-              }
-            : switch (kernel.phase) {
-                protocol.MaintenancePhase.MAINTENANCE_PHASE_READ_DOCUMENTS ||
-                protocol.MaintenancePhase.MAINTENANCE_PHASE_SQLITE_INDEX ||
-                protocol.MaintenancePhase.MAINTENANCE_PHASE_READ_INDEX_CACHE =>
-                  WorkspacePreparationStep.preparingReads,
-                protocol.MaintenancePhase.MAINTENANCE_PHASE_COMMAND_FRONTIER ||
-                protocol.MaintenancePhase.MAINTENANCE_PHASE_COMMAND_ROUTE =>
-                  WorkspacePreparationStep.preparingWrites,
-                protocol.MaintenancePhase.MAINTENANCE_PHASE_GIT_CUSTODY =>
-                  WorkspacePreparationStep.preparingCustody,
-                protocol.MaintenancePhase.MAINTENANCE_PHASE_COMPLETE =>
-                  WorkspacePreparationStep.complete,
-                _ => WorkspacePreparationStep.preparingWorkspace,
-              };
-    // Packing Git custody after writes, or upkeep merely scheduled because this peer's own
-    // writes were admitted, never holds a read or a write: the workspace is ready meanwhile.
-    final upkeep = step == WorkspacePreparationStep.preparingCustody ||
+        ? switch (progress.cause) {
+            protocol
+                .ReadMaintenanceCause
+                .READ_MAINTENANCE_CAUSE_DOMAIN_PREPARATION =>
+              WorkspacePreparationStep.preparingWrites,
+            protocol.ReadMaintenanceCause.READ_MAINTENANCE_CAUSE_OPEN ||
+            protocol.ReadMaintenanceCause.READ_MAINTENANCE_CAUSE_READ_DEBT ||
+            protocol.ReadMaintenanceCause.READ_MAINTENANCE_CAUSE_RESIDENCY =>
+              WorkspacePreparationStep.preparingReads,
+            _ => WorkspacePreparationStep.preparingWorkspace,
+          }
+        : switch (kernel.phase) {
+            protocol.MaintenancePhase.MAINTENANCE_PHASE_READ_DOCUMENTS ||
+            protocol.MaintenancePhase.MAINTENANCE_PHASE_SQLITE_INDEX ||
+            protocol.MaintenancePhase.MAINTENANCE_PHASE_READ_INDEX_CACHE =>
+              WorkspacePreparationStep.preparingReads,
+            protocol.MaintenancePhase.MAINTENANCE_PHASE_COMMAND_FRONTIER ||
+            protocol.MaintenancePhase.MAINTENANCE_PHASE_COMMAND_ROUTE =>
+              WorkspacePreparationStep.preparingWrites,
+            protocol.MaintenancePhase.MAINTENANCE_PHASE_GIT_CUSTODY =>
+              WorkspacePreparationStep.preparingCustody,
+            protocol.MaintenancePhase.MAINTENANCE_PHASE_COMPLETE =>
+              WorkspacePreparationStep.complete,
+            _ => WorkspacePreparationStep.preparingWorkspace,
+          };
+    // Packing Git custody after writes or after a sync, or upkeep merely scheduled because
+    // commits were admitted or received, never holds a read or a write: the workspace is ready
+    // meanwhile. The read index a sync owes is reported under its own read cause, so a report
+    // carrying the SYNC cause is custody upkeep alone. Without SYNC here, one failed pack tidy
+    // after a sync showed the whole application as "still preparing" for its back-off (up to
+    // 30 minutes) while every workspace was up to date (prod web, 13 Oct 2026).
+    final upkeep =
+        step == WorkspacePreparationStep.preparingCustody ||
         (kernel == null &&
-            progress.cause ==
-                protocol.ReadMaintenanceCause
-                    .READ_MAINTENANCE_CAUSE_ADMITTED_OFFER);
+            (progress.cause ==
+                    protocol
+                        .ReadMaintenanceCause
+                        .READ_MAINTENANCE_CAUSE_ADMITTED_OFFER ||
+                progress.cause ==
+                    protocol.ReadMaintenanceCause.READ_MAINTENANCE_CAUSE_SYNC));
     return WorkspacePreparationReport(
       step: step,
-      active: retry == null &&
+      active:
+          retry == null &&
           !upkeep &&
           !progress.stopped &&
           !progress.satisfiedByRead &&
@@ -108,18 +117,18 @@ final class WorkspacePreparationReport {
       gitFrontier: kernel == null
           ? null
           : kernel.hasGitFrontier()
-              ? kernel.gitFrontier
-              : previous?.gitFrontier,
+          ? kernel.gitFrontier
+          : previous?.gitFrontier,
       readFrontier: kernel == null
           ? null
           : kernel.hasReadFrontier()
-              ? kernel.readFrontier
-              : previous?.readFrontier,
+          ? kernel.readFrontier
+          : previous?.readFrontier,
       sqliteFrontier: kernel == null
           ? null
           : kernel.hasSqliteFrontier()
-              ? kernel.sqliteFrontier
-              : previous?.sqliteFrontier,
+          ? kernel.sqliteFrontier
+          : previous?.sqliteFrontier,
     );
   }
 

package/dart/lib/src/runner/node-entry.mjs

@@ -23834,7 +23834,7 @@ var ReadMaintenanceDesk = class {
       const failures = demand.failures + 1;
       this.#pending.delete(workspace);
       const retryMillis = Math.min(30 * 60 * 1e3, 1e3 * 2 ** Math.min(failures - 1, 10));
-      slowQuantumObserver?.(`[nomos-kernel-perf] ${JSON.stringify({
+      (slowQuantumObserver ?? ((line) => console.warn(line)))(`[nomos-kernel-perf] ${JSON.stringify({
         op: "peer_maintenance_failure",
         failed: true,
         workspace,
@@ -25893,7 +25893,7 @@ function delayUntilDue(follow, nowUnixMillis) {
 
 // ../src/runtime/runtime_identity.ts
 init_define_NOMOS_KERNEL_RELEASE();
-var PEER_RUNTIME_IDENTITY = "0.119.9" ? `@githolon/runtime@${"0.119.9"}` : "@githolon/runtime@unbundled";
+var PEER_RUNTIME_IDENTITY = "0.119.11" ? `@githolon/runtime@${"0.119.11"}` : "@githolon/runtime@unbundled";
 
 // ../src/runtime/replica_follow_desk.ts
 init_define_NOMOS_KERNEL_RELEASE();

package/dart/pubspec.yaml

@@ -7,7 +7,7 @@ repository: https://github.com/Captain-App/nomos2
 description: >-
   Nomos 2 Dart client — generated domain values, intent payloads and application
   lifecycle types over the typed Nomos kernel protocol and USDA custody model.
-version: 0.70.10
+version: 0.70.11
 
 environment:
   sdk: ^3.5.0

package/dart/test/workspace_preparation_upkeep_test.dart

@@ -37,12 +37,14 @@ void main() {
         ),
       ),
     );
-    expect(reads.active, isTrue,
-        reason: 'a read index still being built is real preparation');
+    expect(
+      reads.active,
+      isTrue,
+      reason: 'a read index still being built is real preparation',
+    );
   });
 
-  test('upkeep backing off after a failure is not a sync problem (CAP-693)',
-      () {
+  test('upkeep backing off after a failure is not a sync problem (CAP-693)', () {
     // A shallow device's Git upkeep was refused by the kernel; the status turned orange though
     // every read and write still worked.
     final failingUpkeep = WorkspacePreparationReport.fromMaintenance(
@@ -63,7 +65,39 @@ void main() {
         retryAfterMillis: 4000,
       ),
     );
-    expect(failingReads.retrying, isTrue,
-        reason: 'preparation a read waits on still shows');
+    expect(
+      failingReads.retrying,
+      isTrue,
+      reason: 'preparation a read waits on still shows',
+    );
   });
+
+  test(
+    'a pack tidy that fails after a sync is upkeep backing off, not a sync problem (CAP-952)',
+    () {
+      // Prod web, 13 Oct 2026: the kernel refused a repack after an incoming sync ("repack header
+      // …: object could not be found"). The sync icon stayed amber on "Still preparing" for the
+      // back-off while all 34 workspaces were up to date.
+      final failingAfterSync = WorkspacePreparationReport.fromMaintenance(
+        protocol.ReadMaintenanceProgress(
+          workspace: 'estate',
+          cause: protocol.ReadMaintenanceCause.READ_MAINTENANCE_CAUSE_SYNC,
+          retryAfterMillis: 1800000,
+        ),
+      );
+      expect(failingAfterSync.retrying, isFalse);
+      expect(failingAfterSync.upkeepRetrying, isTrue);
+      expect(failingAfterSync.active, isFalse);
+
+      // The read index a sync owes travels under its own read cause and still counts.
+      final indexAfterSync = WorkspacePreparationReport.fromMaintenance(
+        protocol.ReadMaintenanceProgress(
+          workspace: 'estate',
+          cause: protocol.ReadMaintenanceCause.READ_MAINTENANCE_CAUSE_RESIDENCY,
+          retryAfterMillis: 1000,
+        ),
+      );
+      expect(indexAfterSync.retrying, isTrue);
+    },
+  );
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@githolon/dsl",
-  "version": "0.119.9",
+  "version": "0.119.11",
   "type": "module",
   "sideEffects": false,
   "description": "Nomos 2 domain-authoring DSL: aggregates + directives in TS, executed and encoded to the Rust kernel's wire shapes.",
@@ -82,7 +82,7 @@
     "test": "vitest run"
   },
   "dependencies": {
-    "@githolon/runtime": "^0.119.9",
+    "@githolon/runtime": "^0.119.11",
     "@bufbuild/protobuf": "^2.13.0",
     "@bufbuild/protoc-gen-es": "^2.13.0",
     "esbuild": "0.24.2",

package/src/compile_package_main.ts

@@ -2591,8 +2591,8 @@ const NOMOS_TYPES_DEP = "^0.15.2";
 // 0.48.x: session-bound clients (XClient.bind/NomosClientInterface/DomainClientSessionMismatch/
 //         DomainNotInstalledForSession, engine.follow, pendingConflicts lanes) — the generated client
 //         REQUIRES this surface. 0.48.1 fixes NomosSession.watchPendingConflicts delegation.
-const NOMOS_CLIENT_DEP = "^0.70.10";
-const NOMOS_FLUTTER_DEP = "^0.69.0";
+const NOMOS_CLIENT_DEP = "^0.70.11";
+const NOMOS_FLUTTER_DEP = "^0.69.1";
 // DRIFT TRIPWIRE: pubspec_pins.test.ts asserts these equal the CURRENT versions in the Dart and Flutter
 // package pubspecs — a release without this bump fails the suite, so tenants never
 // land back in dependency_overrides (the exact co2 report this closes, third occurrence).