@amistio/cli 0.1.56 → 0.1.57

package/README.md

@@ -101,7 +101,7 @@ Runner setup and local-tool execution use bounded failure controls. During Git w
 
 The environment doctor blocks work before local AI/tool execution when `git`, `node`, Corepack, the package manager, required package scripts, dependencies, setup allowlist, Docker, or the requested execution profile is not ready. Foreground, background, and startup-service runners accept `--execution-profile`; use `--setup-package-manager-install` with `hostWorktreeWithSetup` when the runner may run the fixed package-manager install step in the execution worktree. Work and Runner surfaces receive sanitized profile/readiness metadata only; raw host paths, command lines, environment values, and secrets are not uploaded. Watch mode also performs a Git PATH preflight before auto-sync or work claiming. If the runner reports that Git is not available to the runner PATH, install Git or restart the foreground, background, or startup-service runner from an environment where `git --version` works. On macOS, service and GUI-launched runner environments may not inherit the same PATH as an interactive shell, so restart or reinstall the service after changing PATH.
 
-Runner watch mode defaults to bounded parallel claim lanes, capped at 4. `--max-concurrent-work <count>` lowers or explicitly sets the advertised lane count; use `--max-concurrent-work 1` only when you intentionally want serial execution. The server enforces one active lease per runner lane, honors the advertised capacity, and keeps equivalent implementation scopes serialized through Git worktree locks; use separate lanes for independent work, not multiple attempts at the same ADR scope. Before local tool execution, the runner records a bounded user-level active claim with work item, lane, lease, implementation scope, and worktree key, then releases it on completion or failure; if another local lane already owns the same work or worktree, the runner skips execution and releases the server claim when possible.
+Runner watch mode defaults to bounded parallel claim lanes, capped at 8. `--max-concurrent-work <count>` lowers or explicitly sets the advertised lane count; use `--max-concurrent-work 1` only when you intentionally want serial execution. The server enforces one active lease per runner lane, honors the advertised capacity, and keeps equivalent implementation scopes serialized through Git worktree locks; use separate lanes for independent work, not multiple attempts at the same ADR scope. Before local tool execution, the runner records a bounded user-level active claim with work item, lane, lease, implementation scope, and worktree key, then releases it on completion or failure; if another local lane already owns the same work or worktree, the runner skips execution and releases the server claim when possible.
 
 Watch mode prints a completed-work success once per work item, keeps fresh completion visible briefly, and returns old completed work to the ready state when no queued, running, blocked, failed, review, or runner-readiness action needs attention.
 

package/dist/index.js

@@ -9,6 +9,7 @@ import { Command } from "commander";
 
 // ../shared/src/schemas.ts
 import { z } from "zod";
+var runnerMaxConcurrentWorkLimit = 8;
 var isoDateTimeSchema = z.string().datetime({ offset: true });
 var itemTypeSchema = z.enum([
   "account",
@@ -948,8 +949,8 @@ var runnerHeartbeatItemSchema = baseItemSchema.extend({
   supportedExecutionEnvironmentProfiles: z.array(runnerExecutionEnvironmentProfileSchema).optional(),
   currentExecutionEnvironmentProfile: runnerExecutionEnvironmentProfileSchema.optional(),
   environmentReadiness: runnerEnvironmentReadinessSchema.optional(),
-  maxConcurrentWork: z.number().int().min(1).max(4).optional(),
-  activeClaimLaneIds: z.array(runnerClaimLaneIdSchema).max(4).optional(),
+  maxConcurrentWork: z.number().int().min(1).max(runnerMaxConcurrentWorkLimit).optional(),
+  activeClaimLaneIds: z.array(runnerClaimLaneIdSchema).max(runnerMaxConcurrentWorkLimit).optional(),
   currentWorkItemId: z.string().min(1).optional(),
   currentImplementationScopeId: z.string().min(1).optional(),
   currentWorktreeKey: z.string().min(1).optional(),
@@ -11221,7 +11222,7 @@ var DEFAULT_MAX_PREFLIGHT_ATTEMPTS = 3;
 var DEFAULT_TOOL_TIMEOUT_SECONDS = 30 * 60;
 var RUNNER_WORK_LEASE_SECONDS = 300;
 var RUNNER_WORK_LEASE_RENEWAL_MS = 12e4;
-var MAX_CONCURRENT_RUNNER_WORK = 4;
+var MAX_CONCURRENT_RUNNER_WORK = runnerMaxConcurrentWorkLimit;
 var runnerSupportedWorkKinds = ["brainGeneration", "implementation", "promptBatch", "planRevision", "assistantQuestion", "impactPreview", "issueDiagnosis", "securityPostureScan", "appEvaluationScan", "brainConsolidationScan", "projectContextRefresh", "implementationVerification", "testQualityScan", "implementationTestGate"];
 program.name("amistio").description("Amistio project brain CLI").version(CLI_VERSION);
 program.command("init").description("Create Amistio control-plane folders for a new project").option("--root <path>", "Repository root", defaultRoot).action(async (options) => {
@@ -13512,7 +13513,8 @@ async function submitImplementationFinalizationEntry(apiClient, entry, options =
         ...entry.telemetry,
         message: message2,
         blockerReason: message2,
-        releaseClaim: true
+        releaseClaim: true,
+        releaseReason: "implementationTestGatePending"
       }).catch((releaseError) => {
         console.error(`Could not release implementation work ${entry.workItemId} while waiting for its test gate: ${truncateLogExcerpt(errorMessage7(releaseError))}`);
       });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@amistio/cli",
-  "version": "0.1.56",
+  "version": "0.1.57",
   "type": "module",
   "repository": {
     "type": "git",