@skyramp/mcp 0.3.6 → 0.3.7

package/node_modules/playwright/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skyramp/playwright",
-  "version": "1.58.2-skyramp.8.14.5",
+  "version": "1.58.2-skyramp.8.14.6",
   "description": "Skyramp's fork of Playwright with trace recording for UI test generation",
   "publishConfig": {
     "access": "public"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skyramp/mcp",
-  "version": "0.3.6",
+  "version": "0.3.7",
   "main": "build/index.js",
   "exports": {
     ".": "./build/index.js",
@@ -75,7 +75,7 @@
     "fast-glob": "^3.3.3",
     "js-yaml": "^4.1.1",
     "picomatch": "^4.0.5",
-    "playwright": "file:vendor/skyramp-playwright-1.58.2-skyramp.8.14.5.tgz",
+    "playwright": "file:vendor/skyramp-playwright-1.58.2-skyramp.8.14.6.tgz",
     "simple-git": "^3.30.0",
     "ts-is-record": "^3.0.5",
     "typescript": "^5.8.3",

package/build/tools/code-refactor/enhance-state.d.ts

@@ -1,49 +0,0 @@
-/**
- * SKYR-4262 — enforcement for the assertion-enhancement step.
- *
- * `skyramp_enhance_assertions` is prompt-returning: it hands the agent
- * instructions and relies on it to Read + Edit the spec. Nothing verified that
- * the file actually changed, and one production run showed an agent calling the
- * tool for 9 generated specs back-to-back, declaring the assertions adequate
- * without reading a single file, and shipping specs whose named behavior
- * (disabled-state checks) was asserted nowhere.
- *
- * Same enforcement shape as SKYR-4115's pendingReuseVerification: record an
- * obligation when the instructions are handed out, check it at the next tool
- * that touches the same spec, fail open on any state error, and make the
- * clearing action one the agent can always perform:
- *   - edit the spec (any content change clears the debt), or
- *   - document a deliberate no-change decision with a
- *     `// assertions reviewed:` comment in the spec — which is itself an edit,
- *     so the hash check is the only gate and the marker is the documentation.
- */
-/** Snapshot of a spec at the moment enhancement instructions were handed out. */
-export interface EnhanceRecord {
-    /** Absolute path, for basename-collision detection in multi-repo runs. */
-    testFilePath?: string;
-    /** sha256 of the file content at handout time. */
-    sha256?: string;
-    /** Number of `expect(` occurrences at handout time — for the block message. */
-    expectCount?: number;
-}
-/**
- * Record that enhancement instructions were handed out for `testFile`.
- * Best-effort: a missing run state (non-Testbot use) or unreadable file
- * degrades to "no enforcement", never to a failed tool call.
- */
-export declare function recordEnhanceObligation(testFile: string, explicitStateFile?: string): Promise<void>;
-/**
- * Was this spec handed assertion-enhancement instructions it never acted on?
- *
- * Returns an actionable message when the file is byte-identical to its state at
- * handout time, `undefined` otherwise. The debt clears through the file itself:
- * any edit — adding the missing assertions, or documenting a deliberate
- * no-change decision with a `// assertions reviewed: <reason>` comment —
- * changes the hash. Enforcing "the file changed" rather than "the assertions
- * are good" keeps this a checkpoint, not a judge: assertion quality stays where
- * it belongs, in the enhancement instructions and the report.
- *
- * Fails open on every error path: an unreadable state file or spec is not
- * evidence the agent skipped anything.
- */
-export declare function pendingAssertionEnhancement(testFile: string, explicitStateFile?: string): Promise<string | undefined>;

package/build/tools/code-refactor/enhance-state.js

@@ -1,109 +0,0 @@
-import * as path from "path";
-import { createHash } from "crypto";
-import { readFile } from "fs/promises";
-import { logger } from "../../utils/logger.js";
-import { resolveRunStatePath, StateManager, } from "../../utils/AnalysisStateManager.js";
-const REVIEW_MARKER = "// assertions reviewed:";
-async function fileSnapshot(testFile) {
-    try {
-        const content = await readFile(testFile, "utf8");
-        return {
-            content,
-            sha256: createHash("sha256").update(content).digest("hex"),
-            expectCount: (content.match(/\bexpect\s*\(/g) ?? []).length,
-        };
-    }
-    catch {
-        return undefined;
-    }
-}
-/**
- * Record that enhancement instructions were handed out for `testFile`.
- * Best-effort: a missing run state (non-Testbot use) or unreadable file
- * degrades to "no enforcement", never to a failed tool call.
- */
-export async function recordEnhanceObligation(testFile, explicitStateFile) {
-    const stateFile = resolveRunStatePath(explicitStateFile);
-    if (!stateFile)
-        return;
-    const snapshot = await fileSnapshot(testFile);
-    if (!snapshot)
-        return;
-    try {
-        const manager = StateManager.fromStatePath(stateFile);
-        const data = await manager.readData();
-        if (!data)
-            return;
-        const key = path.basename(testFile);
-        await manager.writeData({
-            ...data,
-            enhanceOutcomes: {
-                ...data.enhanceOutcomes,
-                [key]: {
-                    testFilePath: testFile,
-                    sha256: snapshot.sha256,
-                    expectCount: snapshot.expectCount,
-                },
-            },
-        });
-    }
-    catch (err) {
-        logger.warning("Could not record the assertion-enhancement obligation — proceeding", {
-            testFile,
-            error: String(err),
-        });
-    }
-}
-/**
- * Was this spec handed assertion-enhancement instructions it never acted on?
- *
- * Returns an actionable message when the file is byte-identical to its state at
- * handout time, `undefined` otherwise. The debt clears through the file itself:
- * any edit — adding the missing assertions, or documenting a deliberate
- * no-change decision with a `// assertions reviewed: <reason>` comment —
- * changes the hash. Enforcing "the file changed" rather than "the assertions
- * are good" keeps this a checkpoint, not a judge: assertion quality stays where
- * it belongs, in the enhancement instructions and the report.
- *
- * Fails open on every error path: an unreadable state file or spec is not
- * evidence the agent skipped anything.
- */
-export async function pendingAssertionEnhancement(testFile, explicitStateFile) {
-    try {
-        const stateFile = resolveRunStatePath(explicitStateFile);
-        if (!stateFile)
-            return undefined;
-        const data = await StateManager.fromStatePath(stateFile).readData();
-        const record = data?.enhanceOutcomes?.[path.basename(testFile)];
-        if (!record?.sha256)
-            return undefined;
-        // enhanceOutcomes is keyed by basename across the whole run; in a multi-repo
-        // run two specs can share one record. Blocking a tool on another spec's debt
-        // is worse than missing this one, so a mismatch fails open.
-        if (record.testFilePath && record.testFilePath !== testFile)
-            return undefined;
-        const snapshot = await fileSnapshot(testFile);
-        if (!snapshot)
-            return undefined;
-        if (snapshot.sha256 !== record.sha256)
-            return undefined;
-        if (snapshot.content.includes(REVIEW_MARKER))
-            return undefined;
-        const spec = path.basename(testFile);
-        const countNote = record.expectCount !== undefined
-            ? ` It still has the same ${record.expectCount} expect() call${record.expectCount === 1 ? "" : "s"} it was generated with.`
-            : "";
-        return (`skyramp_enhance_assertions handed out instructions for ${spec} and the file has not changed since.${countNote} ` +
-            `Read the file and apply the enhancement instructions — in particular, add expect() assertions for the specific ` +
-            `behavior this test is named for (state checks like toBeDisabled/toBeEnabled/toHaveCount, not just replayed text ` +
-            `assertions). If after actually reading the file you determine no change is needed, document that in the spec with ` +
-            `a \`${REVIEW_MARKER} <what you checked and why it is sufficient>\` comment near the top of the test.`);
-    }
-    catch (err) {
-        logger.warning("Could not check for a pending assertion enhancement — proceeding", {
-            testFile,
-            error: String(err),
-        });
-        return undefined;
-    }
-}