@amistio/cli 0.1.28 → 0.1.29

package/README.md

@@ -60,6 +60,8 @@ Watch mode prints a completed-work success once per work item, keeps fresh compl
 
 Known validation failures such as `unsafe_context_path` are printed with attention-needed next steps. For project-context refresh path-safety failures, deploy the latest web/API fix, update and restart the runner when applicable, retry the refresh, and capture only bounded non-secret output if it repeats.
 
+App-evaluation result finalization rejections print safe validation paths and preserve the local finalization evidence without exposing raw source or secrets. If a structured app-evaluation result is rejected, update and restart the runner, confirm the web/API deployment is current, and retry the evaluation before acting on cleanup or implementation recommendations.
+
 When brain generation or plan revision output is parsed but the Amistio API is temporarily unavailable during finalization, the runner keeps a safe pending result envelope in user-level Amistio config and replays it before claiming more work. The envelope uses a stable idempotency key and does not store raw tool stdout, provider sessions, credentials, or arbitrary local paths.
 
 For headless startup after login on supported user-level service managers:

package/dist/index.js

@@ -2222,9 +2222,11 @@ function computeProjectNextAction(input) {
   if (failedPlanRevision) {
     return failedWorkAction(failedPlanRevision, "planRevisionFailed", "Plan revision failed", failedPlanRevision.lastStatusMessage ?? "Review the conversation and request another revision if needed.");
   }
-  const blockedWork = latestWorkItem(input.workItems.filter((item) => item.status === "blocked" || item.status === "changesRequested"));
+  const blockedWorkItems = input.workItems.filter((item) => item.status === "blocked" || item.status === "changesRequested");
+  const blockedWork = latestWorkItem(blockedWorkItems);
   if (blockedWork) {
-    return workAction(blockedWork, "workBlocked", "user", "danger", "Work is blocked", blockedWork.lastStatusMessage ?? "Review the blocked work item before the runner can continue.");
+    const message = workStatusReason(blockedWork, "Review the blocked work item before the runner can continue.");
+    return workAction(blockedWork, "workBlocked", "user", "danger", "Work is blocked", blockedWorkItems.length > 1 ? `Latest blocked work ${blockedWork.workItemId}: ${message}` : message);
   }
   const failedWork = latestWorkItem(input.workItems.filter((item) => item.status === "failed"));
   if (failedWork) {
@@ -2337,6 +2339,9 @@ function failedWorkAction(workItem, kind, fallbackTitle, fallbackMessage) {
   }
   return workAction(workItem, kind, "user", "danger", fallbackTitle, fallbackMessage);
 }
+function workStatusReason(workItem, fallbackMessage) {
+  return workItem.blockerReason ?? workItem.sourceFailureSummary ?? workItem.lastStatusMessage ?? fallbackMessage;
+}
 function workAction(workItem, kind, actor, tone, title, message, detail) {
   return {
     kind,
@@ -5938,6 +5943,8 @@ function createAppEvaluationScanPrompt(workItem, context) {
     "- When lifecycle metadata disagrees across indexes, frontmatter, feature specs, ADRs, and implementation evidence, cite the conflict and propose a metadata correction or verification step instead of archival/removal.",
     "- Check missing memory or workflow updates when repeated lessons or operational rules are visible.",
     "- Check release readiness, UX, accessibility, performance, reliability, and security-posture follow-through at a summary level.",
+    "- Prefer repository-documented verification commands over ad hoc package-script inference.",
+    "- For this Amistio monorepo, if plain Corepack pnpm fails before scripts with spawnSync pnpm ENOENT, retry the documented command corepack pnpm --config.verify-deps-before-run=false verify before declaring whole-app verification blocked.",
     "",
     "## Data Safety",
     "",
@@ -9154,7 +9161,7 @@ function startWorkLeaseRenewal({ apiClient, projectId, repositoryLinkId, runnerI
 }
 async function recordFinalizationFailure({ apiClient, durationMs, error, isolationTelemetry, projectId, repositoryLinkId, runnerId, sessionContext, toolConfig, toolName, workItem }) {
   const detail = truncateLogExcerpt(errorDetail(error));
-  const message = `${toolName} completed, but Amistio could not finalize the result.`;
+  const message = `${toolName} completed, but Amistio could not finalize the result. ${safeFinalizationFailureSummary(error)}`;
   const settlements = await Promise.allSettled([
     apiClient.sendRunnerHeartbeat(projectId, runnerId, repositoryLinkId, "online", runnerHeartbeatMetadata(toolConfig)),
     markToolSessionBlocked(apiClient, projectId, sessionContext.toolSession, errorMessage3(error)),
@@ -9194,6 +9201,12 @@ async function recordFinalizationFailure({ apiClient, durationMs, error, isolati
   console.error(detail);
   return { status: "failed", exitCode: 1, message };
 }
+function safeFinalizationFailureSummary(error) {
+  if (error instanceof AmistioApiError) {
+    return truncateLogExcerpt(error.message);
+  }
+  return "Review the runner log for the finalization error.";
+}
 function workItemIsolationTelemetry(workItem, isolation) {
   const implementationScopeId = isolation?.implementationScopeId ?? workItem.implementationScopeId;
   const executionBranch = isolation?.branch ?? workItem.executionBranch;