@skyramp/mcp 0.3.8 → 0.4.0-rc.1

package/build/utils/scenarioDrafting.d.ts

@@ -1,92 +0,0 @@
-import { DraftedScenario } from "../types/RepositoryAnalysis.js";
-import { WorkspaceAuthType } from "./workspaceAuth.js";
-import type { ScannedEndpoint } from "./repoScanner.js";
-export declare function isRealResource(r: string): boolean;
-type MethodInput = string | {
-    method: string;
-    sourceFile?: string;
-    interactions?: Array<{
-        request?: {
-            body?: Record<string, unknown>;
-        };
-    }>;
-};
-type EndpointInput = {
-    path: string;
-    methods: Array<MethodInput>;
-};
-type EndpointRef = {
-    method: string;
-    path: string;
-    sourceFile?: string;
-};
-type ScenarioDraftOptions = {
-    /** Existing endpoints touched by a security/destructive diff; used only for attack-surface expansion. */
-    changedEndpoints?: Array<EndpointRef>;
-    /** Gate sibling destructive expansion to diffs with auth/permission/admin-key signals. */
-    securityRelevantDiff?: boolean;
-};
-export type ResourceRelationships = Map<string, Set<string>>;
-/**
- * Infer parent→child resource relationships from two signals already present
- * in the endpoint data — no source code scanning required.
- *
- * Signal 1 — path nesting (always available):
- *   /collections/{id}/links  →  links depends on collections
- *
- * Signal 2 — request body FK fields (available when trace data is merged):
- *   POST /orders body: { product_id: "..." }  →  orders depends on products
- *
- * Returns a map of `dependent → Set<parent>`. Only confirmed, real-resource
- * pairs are included. When no signal is found the map is empty, which tells
- * the caller to fall back to heuristic pairing.
- */
-export declare function inferResourceRelationships(endpoints: Array<EndpointInput>): ResourceRelationships;
-export declare function draftScenariosFromEndpoints(endpoints: Array<EndpointInput>, newEndpoints?: Array<EndpointRef>, wsAuthType?: WorkspaceAuthType, options?: ScenarioDraftOptions, removedEndpoints?: Array<EndpointRef>): DraftedScenario[];
-/**
- * Enforce a global cap on drafted scenarios while preserving category diversity.
- *
- * 1. CRITICAL (bug_caught, requirement_conflict) scenarios prioritized first.
- * 2. One scenario per non-empty category guaranteed (breadth).
- * 3. Remaining budget filled by priority tier (HIGH > MEDIUM > LOW).
- * 4. Hard cap at MAX_TOTAL_SCENARIOS — applied to the combined output.
- */
-export declare function capScenarios(scenarios: DraftedScenario[]): DraftedScenario[];
-/**
- * Draft scenarios that directly test each new endpoint in the branch diff.
- *
- * For each new endpoint, method-specific scenarios are produced:
- *   PUT/PATCH  → mutation-recalc integration, boundary-values integration, contract, not-found
- *   POST       → lifecycle integration (create + optional GET), contract, validation error
- *   DELETE     → lifecycle integration (create + delete + 404), contract
- *   GET /{id}  → contract, not-found
- *   GET /coll  → contract + collection-list integration (create-then-GET) or contract-only
- *
- * Additionally, PUT/PATCH/DELETE methods get an auth-boundary scenario
- * (category "security_boundary" → HIGH priority, not CRITICAL) so it
- * lands in ADDITIONAL deterministically instead of depending on LLM
- * supplement. GET is excluded (often public); POST is excluded because
- * the security-boundary supplement tier covers it. Exception: execution
- * endpoints (/execute, /run, /trigger, etc.) include auth-boundary for
- * all non-GET methods (including POST) since they are high-value targets.
- */
-export declare function draftDiffDirectScenarios(newEndpoints: Array<{
-    method: string;
-    path: string;
-}>, resourceGroups: Map<string, {
-    basePath: string;
-    methods: Set<string>;
-    paramPath?: string;
-}>, wsAuthType?: WorkspaceAuthType): DraftedScenario[];
-/**
- * Drafts response-shape verification scenarios for endpoints reached via the
- * importer-hop classification: files that don't declare routes themselves
- * (DTOs, services, models) but are imported by files that do.
- *
- * `byFile` maps each hop-mapped source file to the endpoint paths it reaches;
- * `addedFieldsByFile` maps the same files to property names added in their
- * diff hunks (best-effort — an empty list is fine, the scenario is still
- * drafted, just without field hints).
- */
-export declare function draftResponseShapeScenarios(hopEndpoints: Array<ScannedEndpoint>, byFile: Record<string, string[]>, addedFieldsByFile: Record<string, string[]>): DraftedScenario[];
-export {};