@skyramp/mcp 0.4.1 → 0.4.2-rc.2

package/build/types/ExternalTestExecution.d.ts

@@ -1,67 +0,0 @@
-/**
- * Neutral result shape for `skyramp_run_existing_tests` — a repo's OWN
- * (external, user-authored) test suite, run at PR time to CONFIRM which failures
- * a change actually causes. Framework-agnostic: the Playwright adapter (and
- * future pytest/jest adapters) all normalize into these types so the
- * maintenance pipeline and report consume one shape.
- */
-/** `error` (fixture/collection/timeout) is kept distinct from `fail`
- *  (assertion) end-to-end — see external-exec plan item 6. */
-export type ExternalTestStatus = "pass" | "fail" | "error" | "skipped";
-export interface ExternalTestResult {
-    /** Human-readable identity, e.g. `<file> › <describe…> › <title>`. */
-    testId: string;
-    /** Spec file the test lives in. */
-    file: string;
-    status: ExternalTestStatus;
-    /** Failure/error text (ANSI-stripped). Present only for fail/error. */
-    message?: string;
-    durationMs: number;
-}
-export interface ExternalRunSummary {
-    /** Tests that produced a real verdict (pass + fail + error); skipped excluded. */
-    ran: number;
-    failed: number;
-    errored: number;
-    skipped: number;
-    /** True when the candidate set was cut by maxTests/timeout — reported honestly. */
-    truncated: boolean;
-}
-/** Structured env-health diagnostics for logging (populated by the framework adapter). */
-export interface ExternalRunDiagnostics {
-    /** All top-level Playwright run-level error messages (ANSI-stripped, first line each). */
-    runLevelErrors: string[];
-    /** A global-setup/teardown (infra) spec reported fail/error — the environment genuinely
-     *  did not come up (distinct from a product-test failure). */
-    infraSpecFailed: boolean;
-    /** A run-level error is the `--max-failures` "stopped early" bail — benign for env-health
-     *  (it means a test failed and the bounded run stopped, NOT that the env is unhealthy). */
-    maxFailuresBail: boolean;
-}
-export interface ParsedExternalRun {
-    results: ExternalTestResult[];
-    summary: ExternalRunSummary;
-    /** False when a wall of red is environmental (setup/collection failure), not a
-     *  PR signal — consumers must NOT treat results as confirmed failures. */
-    environmentHealthy: boolean;
-    healthDetail?: string;
-    /** Structured diagnostics for logging (optional; set by the Playwright adapter). */
-    diagnostics?: ExternalRunDiagnostics;
-    /** True when the run was skipped because the repo has no runnable external suite
-     *  (no Playwright service / no `testRunCommand`) — i.e. no external tests to
-     *  run. Distinct from a green zero-test run: consumers must treat this as "not
-     *  executed", never "passed". */
-    skipped?: boolean;
-    /** Why the run was skipped (present only when `skipped`). */
-    skipReason?: string;
-}
-/** One persisted run of the external suite, appended to
- *  UnifiedAnalysisState.externalTestResults so drift analysis / the report can
- *  fold in CONFIRMED failures instead of guesses. */
-export interface ExternalTestRunRecord extends ParsedExternalRun {
-    mode: "confirm" | "verify";
-    /** ISO timestamp when the run completed. */
-    ranAt: string;
-    /** owner/repo this run targeted (multi-repo runs); absent → primary. */
-    repository?: string;
-}

package/build/types/ExternalTestExecution.js

@@ -1,8 +0,0 @@
-/**
- * Neutral result shape for `skyramp_run_existing_tests` — a repo's OWN
- * (external, user-authored) test suite, run at PR time to CONFIRM which failures
- * a change actually causes. Framework-agnostic: the Playwright adapter (and
- * future pytest/jest adapters) all normalize into these types so the
- * maintenance pipeline and report consume one shape.
- */
-export {};

package/build/workspace/testSuites.d.ts

@@ -1,20 +0,0 @@
-import type { Service } from "./workspace.js";
-/**
- * A single test suite (one runtimeDetails.testSuites[] entry) flattened to one
- * uniform shape, carrying its owning serviceName so routing/aggregation can label
- * results per suite, and a framework resolved against the service's.
- */
-export interface NormalizedSuite {
-    serviceName: string;
-    framework?: string;
-    testRunCommand: string;
-    testEnv?: Record<string, string>;
-    /** Repo-relative globs this suite owns, for selector→suite routing. */
-    pathGlobs?: string[];
-}
-/**
- * Normalizes a service's runtimeDetails.testSuites into a flat list of suites
- * (SKYR-4002), each carrying its owning serviceName and a framework that falls
- * back to the service's. Returns [] when the service records no testSuites.
- */
-export declare function resolveSuites(service: Service): NormalizedSuite[];

package/build/workspace/testSuites.js

@@ -1,17 +0,0 @@
-/**
- * Normalizes a service's runtimeDetails.testSuites into a flat list of suites
- * (SKYR-4002), each carrying its owning serviceName and a framework that falls
- * back to the service's. Returns [] when the service records no testSuites.
- */
-export function resolveSuites(service) {
-    const suites = service.runtimeDetails?.testSuites;
-    if (!suites)
-        return [];
-    return suites.map((suite) => ({
-        serviceName: service.serviceName,
-        framework: suite.framework ?? service.framework,
-        testRunCommand: suite.testRunCommand,
-        testEnv: suite.testEnv,
-        pathGlobs: suite.pathGlobs,
-    }));
-}