interface CompleteCommandOptions { silent?: boolean; skipValidation?: boolean; yes?: boolean; /** Close without a passing reports/verify.json (stored as metadata.closeReason). */ reason?: string; /** Batch-close every active increment whose tasks are all done or skipped. */ all?: boolean; } /** * CLI command to complete one or more active increments * * This is used by: * 1. Manual user invocation: specweave complete [more-ids...] * 2. Auto mode stop hook: specweave complete --silent --yes * * Features: * - Short-ID resolution: "0589" → "0589-cli-complete-improvements" * - Batch mode: "specweave complete 0573 0562 0571" * - Per-ID error isolation: one failure doesn't stop others * * @param incrementId - First increment ID (required) * @param moreIds - Additional increment IDs (variadic) * @param options - Command options (silent, skipValidation, yes) * @since v4.0 - Auto mode stop hook integration * @since v4.1 - Short-ID resolution and batch mode */ export declare function completeCommand(incrementId: string | undefined, moreIds?: string[], options?: CompleteCommandOptions): Promise; /** * `complete` never commits, so say how when the closed increment has * uncommitted changes. Only inside a git work tree. The pathspec keeps other * staged work out of the commit; run Git in the increment project when invoked elsewhere. */ export declare function commitHint(projectRoot: string, incrementId: string, cwd?: string): string | undefined; export {}; //# sourceMappingURL=complete.d.ts.map