@formigio/fazemos-cli 0.10.4 → 0.10.6

package/dist/index.js

@@ -4292,7 +4292,11 @@ step
 });
 step
     .command('revise')
-    .description('Request revision on a submitted step. Sends the step back to "in_progress" with feedback. The assignee can then resubmit. The step\'s review cycle counter increments; if max cycles are reached, the step auto-approves.')
+    .description('Request revision on a submitted step. Sends the step back to "in_progress" with feedback. ' +
+    'The assignee can then resubmit. The step\'s review cycle counter increments. ' +
+    'If the review cycle limit is reached, the step transitions to \'failed\'. ' +
+    'Use \'fazemos pl step reset-review-cycles <instanceId> <stepId> --feedback "<text>"\' ' +
+    'to reset the counter with new guidance and retry.')
     .argument('<instanceId>', 'Pipeline instance ID')
     .argument('<stepId>', 'Step instance ID')
     .requiredOption('--reason <text>', 'Revision feedback explaining what needs to change')
@@ -4303,6 +4307,11 @@ step
         });
         console.log(chalk.green(`Revision requested: ${data.step?.step_name || stepId}`));
         console.log(`  Status: ${data.step?.status}`);
+        if (data.step?.status === 'failed' && data.step?.metadata?.error_class === 'max_review_cycles_reached') {
+            console.log(chalk.yellow(`  Review cycle limit reached. Step has been marked as failed.`));
+            console.log(`  To retry with new guidance:`);
+            console.log(`    fazemos pl step reset-review-cycles ${instanceId} ${data.step?.id || stepId} --feedback "<new guidance>"`);
+        }
     }
     catch (err) {
         console.error(chalk.red(err.message));
@@ -4434,6 +4443,51 @@ step
         process.exit(1);
     }
 });
+step
+    .command('reset-review-cycles')
+    .description('Reset a step\'s review cycle counter to 0 with mandatory feedback. ' +
+    'Only valid when the step is in \'failed\' status with error_class \'max_review_cycles_reached\'. ' +
+    'The step transitions back to \'in_progress\' and the feedback is stored for the assignee\'s next attempt. ' +
+    'Requires owner or admin role. ' +
+    'Use "pl step show <instanceId> <stepId>" to check step status and error class.')
+    .argument('<instanceId>', 'Pipeline instance ID')
+    .argument('<stepId>', 'Step instance ID')
+    .requiredOption('-f, --feedback <text>', 'New guidance for the assignee\'s next attempt. Cannot be empty.')
+    .action(async (instanceId, stepId, opts) => {
+    try {
+        const feedback = opts.feedback?.trim();
+        if (!feedback) {
+            console.error(chalk.red('Error: --feedback is required and cannot be empty.'));
+            process.exit(1);
+        }
+        const data = await api('POST', `/api/pipeline-instances/${instanceId}/steps/${stepId}/reset-review-cycles`, {
+            feedback,
+        });
+        const stepName = data.step?.step_name || stepId;
+        const status = data.step?.status || 'unknown';
+        const previousCount = data.reset_metadata?.previous_cycle_count ?? '?';
+        const feedbackRecorded = feedback.length > 120 ? feedback.slice(0, 120) + '...' : feedback;
+        console.log(chalk.green(`Step reset (review cycles): "${stepName}" (${status})`));
+        console.log(`  Cycles reset: ${previousCount} → 0`);
+        console.log(`  Feedback recorded: "${feedbackRecorded}"`);
+        console.log(chalk.yellow(`  Note: Manual dispatch may be needed until I16 ships. Run: fazemos execute ...`));
+    }
+    catch (err) {
+        if (err.code === 'INVALID_STATE') {
+            const currentStatus = err.details?.current_status || 'unknown';
+            console.error(chalk.red(`Error: Step is not in a failed state with max_review_cycles_reached error class.`));
+            console.error(`Current status: ${currentStatus}`);
+            console.error(`Use this command only after a step has failed due to review cycle exhaustion.`);
+        }
+        else if (err.code === 'FORBIDDEN' || err.status === 403) {
+            console.error(chalk.red(`Error: Only owners and admins can reset review cycles.`));
+        }
+        else {
+            console.error(chalk.red(err.message));
+        }
+        process.exit(1);
+    }
+});
 // ── Queue ──────────────────────────────────────────────────
 const queue = program.command('queue').alias('q').description('Work queue commands');
 queue
@@ -7233,12 +7287,16 @@ docs
         handleScopedError(err);
     }
 });
-// Only auto-parse when invoked as the entry point (i.e. `node dist/index.js ...`
-// or `npx tsx src/index.ts ...`). When imported as a module — by tests using
-// `vi.mock` to intercept `api()` and asserting on `program.parseAsync(...)` —
-// skip auto-parse so the test controls invocation.
-const isMainModule = import.meta.url === `file://${process.argv[1]}`;
-if (isMainModule)
+// Skip auto-parse only when running under Vitest (which sets process.env.VITEST).
+// Tests import `program` and drive it via `program.parseAsync(...)` after mocking
+// `./api.js`. In every other context — direct invocation, npx tsx, OR the bin
+// shim that does `import('../dist/index.js')` — auto-parse must run, otherwise
+// the CLI produces no output.
+//
+// Earlier `import.meta.url === file://${process.argv[1]}` check was wrong: the
+// bin shim's argv[1] is the shim path, not the dist/index.js path, so the guard
+// returned false and silently skipped parse.
+if (!process.env.VITEST)
     program.parse();
 export { program };
 //# sourceMappingURL=index.js.map