npm - @planu/cli - Versions diffs - 3.9.7 → 3.9.9 - Mend

@@ -1,53 +0,0 @@
-// tools/update-registry.ts — Handler for the update_registry MCP tool
-// Allows users to add custom framework entries to the local registry.
-import { saveCustomEntry } from '../engine/registry/core.js';
-/**
- * Handle update_registry tool invocations.
- * Saves a custom registry entry to data/global/registry-custom.json.
- * Custom entries override base entries with the same framework ID.
- */
-export async function handleUpdateRegistry(args) {
-    const entry = {
-        framework: args.framework,
-        displayName: args.displayName,
-        ecosystem: args.ecosystem,
-        frameworkVersion: args.frameworkVersion,
-        lastUpdated: new Date().toISOString().split('T')[0] ?? new Date().toISOString(),
-        customEntry: true,
-        correctPatterns: args.correctPatterns.map((p) => ({
-            pattern: p.pattern,
-            example: p.example,
-            since: p.since,
-        })),
-        deprecatedPatterns: (args.deprecatedPatterns ?? []).map((p) => ({
-            pattern: p.pattern,
-            replacedBy: p.replacedBy,
-            severity: p.severity,
-        })),
-        commonMistakes: (args.commonMistakes ?? []).map((p) => ({
-            pattern: p.pattern,
-            example: p.example,
-            replacedBy: p.replacedBy,
-            severity: p.severity,
-        })),
-    };
-    await saveCustomEntry(entry);
-    const lines = [
-        `## Registry actualizado`,
-        '',
-        `Framework **${entry.displayName}** (\`${entry.framework}\`) guardado en el registry custom.`,
-        '',
-        `- Ecosystem: ${entry.ecosystem}`,
-        `- Version de referencia: ${entry.frameworkVersion}`,
-        `- Patrones correctos: ${entry.correctPatterns.length}`,
-        `- Patrones obsoletos: ${entry.deprecatedPatterns.length}`,
-        `- Errores comunes: ${entry.commonMistakes.length}`,
-        '',
-        'La entrada se aplicara en la proxima llamada a `check_spec_accuracy`.',
-        'Las entradas custom tienen prioridad sobre las entradas base del registry.',
-    ];
-    return {
-        content: [{ type: 'text', text: lines.join('\n') }],
-    };
-}
-//# sourceMappingURL=update-registry.js.map

@@ -1,125 +0,0 @@
-import type { ToolResult } from '../../types/index.js';
-import type { FormatGateOutput } from '../../types/spec/inputs.js';
-import type { Spec } from '../../types/spec/core.js';
-import type { EscalateResult } from '../../types/escalator.js';
-/**
- * The reason why the validate gate blocked a `done` transition.
- * Each reason maps to a specific fix-hint shown to the LLM.
- */
-export type ValidateGateBlockReason = 'validate_score_below_threshold' | 'validate_gate_no_criteria' | 'validate_gate_crash' | 'validate_gate_timeout' | 'validate_gate_unreachable';
-/**
- * Return type for `runValidateGate`.
- *
- * - `blocked: true`  → caller MUST block the transition and surface the reason.
- * - `blocked: false, forced: false` → validate passed with a real score.
- * - `blocked: false, forced: true`  → forceStatus bypass; audit-logged by caller.
- */
-export type ValidateGateResult = {
-    blocked: true;
-    score: number | null;
-    reason: ValidateGateBlockReason;
-    errorMessage?: string;
-} | {
-    blocked: false;
-    score: number;
-    forced: false;
-} | {
-    blocked: false;
-    score: number | null;
-    forced: true;
-    forcedReason: string;
-};
-/**
- * SPEC-721 / SPEC-222 Trigger 1: Run validate engine before marking done.
- *
- * Fail-CLOSED: timeout, crash, or null score → blocked (not allowed through).
- * The only escape hatch is `forceStatus=true` with a `forceStatusReason` ≥100 chars.
- *
- * The timeout lives inside this function (Promise.race) so we own the reason string.
- * Callers must NOT wrap this with `withToolTimeout` — doing so would silently convert
- * timeout into `blocked: false` (the exact bypass this spec closes).
- *
- * @param spec            The spec being transitioned.
- * @param projectPath     Project root for the validate engine.
- * @param forceStatus     Whether the LLM explicitly wants to bypass the gate.
- * @param forceStatusReason  Why — required and ≥100 chars when forceStatus=true.
- * @param budgetMs        Max milliseconds to wait for validate. Default: 9000.
- */
-export declare function runValidateGate(spec: Spec, projectPath: string, forceStatus: boolean, forceStatusReason: string | undefined, budgetMs?: number): Promise<ValidateGateResult>;
-/**
- * Checks the DoD gate before transitioning to 'done'.
- * Returns an error ToolResult if blocked (unless force=true), null if passed.
- */
-export declare function checkDodGate(spec: Spec, specId: string, projectId: string, projectPath: string | undefined, _force: boolean): Promise<ToolResult | null>;
-/**
- * SPEC-335: Security gate — blocks 'done' transition if critical CVEs are found.
- * Only runs when projectPath is available. Never throws — best-effort.
- * Returns an error ToolResult if blocked, null if passed or skipped.
- *
- * Exported for testing; callers should prefer checkDoneGates for the full gate suite.
- */
-export declare function checkSecurityGate(projectPath: string | undefined, specId: string, force?: boolean): Promise<ToolResult | null>;
-/** Return value for checkDoneGates — separates blocking errors from force-bypass warnings. */
-export interface DoneGateResult {
-    /** Non-null means gate blocked — caller MUST return this as an error response. */
-    blocked: ToolResult | null;
-    /**
-     * Non-null when force=true bypassed failing DoD items.
-     * Caller should surface this as a warning in the success response.
-     */
-    forcedBypassWarning: string | null;
-}
-/**
- * SPEC-725: Check the validation-report artifact gate before marking done.
- * If a validation-report.json exists and payload.passed === false, block transition.
- * If the artifact is absent, allow (backward compat).
- * Never throws — always best-effort.
- */
-export declare function checkValidationReportGate(specId: string, projectId: string, force: boolean | undefined): Promise<ToolResult | null>;
-/**
- * SPEC-335: Combined done-gates runner — DoD + security.
- * When force=true, gates are not blocking but failing items are recorded in
- * the project's force-bypass-log.json for traceability (guard: done ≠ implemented).
- */
-export declare function checkDoneGates(spec: Spec, specId: string, projectId: string, projectPath: string | undefined, force: boolean | undefined): Promise<DoneGateResult>;
-export interface ComplianceGateResult {
-    skipped: boolean;
-    score: number | null;
-    issues: string[];
-    blocked: boolean;
-}
-/**
- * SPEC-447: Runs the compliance check when transitioning to 'review'.
- * Never blocks the transition if the compliance engine is unavailable or fails.
- */
-export declare function checkComplianceGate(specId: string, projectId: string, projectPath: string | undefined): Promise<ComplianceGateResult>;
-/** SPEC-642: Block done if QA gate has not run and passed. */
-export declare function checkQaGate(specId: string, projectPath: string | undefined, force: boolean): Promise<ToolResult | null>;
-/**
- * SPEC-716 / SPEC-780: Format gate for transition to 'approved'.
- *
- * - newStatus !== 'approved' → returns `{ blockResult: null, qualityWarnings: [] }` (gate inert)
- * - validateSpecFormat returns valid → `{ blockResult: null, qualityWarnings: [] }`
- * - validateSpecFormat returns invalid AND `forceApprove !== true` → `{ blockResult: <SPEC_FORMAT_INVALID>, qualityWarnings: [] }` (block, legacy behavior)
- * - validateSpecFormat returns invalid AND `forceApprove === true` → `{ blockResult: null, qualityWarnings: <serialized errors> }` (proceed; warnings written to spec frontmatter by caller, mirroring SPEC-769 readiness gate)
- *
- * Best-effort: never throws — gate is skipped on unexpected errors.
- */
-export declare function checkApprovedFormatGate(spec: Spec, newStatus: string, forceApprove?: boolean | undefined): Promise<FormatGateOutput>;
-/**
- * Run the validate gate wrapped in withEscalation for bounded retries.
- *
- * On budget exhaustion, returns an escalation sentinel with decision='retry'|'abort'.
- * The caller is responsible for surfacing the decision as interactiveQuestions.
- *
- * @param spec            - The spec being transitioned.
- * @param projectPath     - Project root for the validate engine.
- * @param projectId       - Project ID for retry counter persistence.
- * @param specId          - Spec ID for retry counter keying.
- * @param frontmatterSha  - Frontmatter SHA for retry counter keying.
- * @param forceStatus     - Whether to bypass the gate.
- * @param forceStatusReason - Required when forceStatus=true.
- * @param budgetMs        - Max milliseconds for validate.
- */
-export declare function runValidateGateWithEscalation(spec: Spec, projectPath: string, projectId: string, specId: string, frontmatterSha: string, forceStatus: boolean, forceStatusReason: string | undefined, budgetMs?: number): Promise<EscalateResult<ValidateGateResult>>;
-//# sourceMappingURL=dod-gates.d.ts.map

@planu/cli 3.9.7 → 3.9.9