mirror of
https://github.com/garrytan/gstack.git
synced 2026-10-03 01:46:55 +02:00
* refactor(resolvers): split review.ts into MECE resolver modules (pure move) Move every function from scripts/resolvers/review.ts, unchanged, into: - review-dashboard.ts: review dashboard, plan-file review report - plan-gates.ts: approval check, exit-plan-mode gate, plan-file discovery, plan-completion audit/gate (ship + review), plan verification exec - spec-review.ts: both spec review loops, benefits-from, anti-shortcut clause - outside-voice-steps.ts: Codex second opinion, adversarial step, Codex plan review, Codex doc review, disabled-outside record - review-scope.ts: scope drift, cross-review dedup, shared-code reuse review.ts is deleted; index.ts imports the new modules. gen-skill-docs output is byte-identical for every host (--host all). Test imports and source-path references are re-pointed; the two source-text report/gate tests in gen-skill-docs.test.ts become behavioral renders across every consuming skill and host. All 46 touchfile entries that named review.ts now name all five modules, guarded by a recorded selection golden. * test(browse): black-box auth matrix for every server route and both surfaces Drives buildFetchHandler fetchLocal/fetchTunnel with no token, wrong token, root token, scoped token and the SSE cookie for all 33 routes, plus unmatched paths and wrong methods. Denials assert today's exact status, body and content type; allowed credentials assert the handler was reached. Written against the unchanged if-chain server so the W3 route-table refactor must keep it green. * refactor(shard-engine): move scripts/test-strict-output.ts to scripts/lib/shard-engine.ts The shared shard engine grows from the existing strict-output module (runShardChild, killProcessGroup, signal forwarding, strict classifier). scripts/test-strict-output.ts stays as a re-export so existing importers, mock.module paths and the strict-output/run-shard-child tests are unchanged. The engine inherits the global touchfile entry; the free runner's CLI-routing fixture copies the new module. * refactor(resolvers): decompose the three >150-line review resolvers (output-neutral) Split generateAdversarialStep, generateCodexPlanReview and generatePlanCompletionAuditInner into per-section helpers whose template literals are copied verbatim, so every function in the new modules is at or under 150 lines. gen-skill-docs output is byte-identical for every host (--host all, compared against96764e80with a fixed --link-root). * refactor(resolvers): one outside-voice failure policy (deliberate prose unification) outsideVoiceFailurePolicy(ctx, opts) in outside-voice.ts now renders the auth / timeout / empty-response bullets for all four call sites that hand-typed them (Codex second opinion, adversarial step, Codex plan review, design outside voices). Options are explicit per site (timeoutMinutes, onTimeout, stderrOnEmpty, fallback, escape) with no defaults. Deliberate generated-prose changes (every host): - office-hours: 'Fall back to <native> subagent.' becomes 'Fall back to the <native> subagent below.' - plan-devex-review: the plain 'Auth failure (stderr contains ...)' bullets become the canonical bold bullets; auth also triggers on 'API key'; 'auth failed' becomes 'authentication failed'. - review/ship adversarial: 'exceeded 9 minutes and was terminated' becomes 'timed out after 9 minutes and was terminated'; the timeout is still MISSING COVERAGE. - design outside voices: unchanged. Adds ratchet (d) (test/outside-voice-failure-policy.test.ts) with a reasoned allowlist for /codex's own CLI errors, the MISSING COVERAGE retention test, refreshed codex/factory ship goldens, and outside-voice.ts in every touchfile entry of review.ts and design.ts (selection golden extended). * test(pty): fake PTY session driver with an injectable clock through the runner launch seam The three plan-skill runners take an optional PtyDriver (launch, now, monotonic, sleep); omitted, they use the real launcher and clocks exactly as before. test/helpers/pty/fake-session.ts feeds scripted frames through that seam, and claude-pty-runner.runners.unit.test.ts runs observation, counting and floor for success, deadline timeout, permission prompt and plan-ready outcomes with no CLI or real timers. These cases must stay green unchanged through the W4 split and the runPtySession extraction. Touchfiles: every entry that lists claude-pty-runner.ts or pty-screen.ts now also lists test/helpers/pty/**. * refactor(shard-engine): run both lanes on the shared engine; lane policy injected Engine (scripts/lib/shard-engine.ts) gains the W2 primitives: per-shard tmp/Chromium sandbox + async cleanup backstop, log-path allocation and full-stream log capture, one duration-seed reader/writer with a lane predicate, LanePolicy (seed predicate + zero-execution verdict), strictShardStatus, and the shared CLI flag loop. runShardChild takes an optional companion (signal/settle) and waits a bounded 250ms to reap a wall-killed child. Free lane stops spawning shards itself: runFreeShard uses runShardChild with trackShardBrowser as the companion (win32 path unchanged: no process group, no negative-pid kill). Its sync state-dir removal stays lane policy. Paid lane uses the sandbox, log, seed, verdict and flag primitives; the hollow-shard guard applies PAID_LANE_POLICY. Lane outcomes are unchanged (free keeps >= 0 seeds and file-count zero-exec rule; paid keeps > 0 seeds, warning under selection and passed-empty under EVALS_ALL). paid-free-boundary's closure assertion now names the engine module, where the strict classifier lives. * test(shard-engine): engine unit tests, fixture-corpus equivalence, per-lane CLI parity - test/shard-engine.test.ts: failing/unhandled/module-load output fails both lanes, per-lane zero-execution and seed rules, whole-group kill on a wall timeout (both lanes), mocked-win32 path with no negative-pid kill, companion settle order, log capture, sandbox isolation, flag loop. - test/shard-engine-equivalence.test.ts + test/fixtures/shard-equivalence: seven outcome fixtures plus one real shard, run through both lanes and compared with classifications recorded from the base runners (96764e80). - test/shard-cli-parity.test.ts + test/fixtures/shard-cli-parity: flag set, defaults, validation errors and the Unknown argument error per lane match the base runners. * refactor(shard-engine): decompose runFreeShard and runPaidShard to <= 150 lines Output-neutral extraction under the fixture-corpus equivalence and runner tests: captureFreeStream, explainFreeVerdict and logFreeRecovery (free); paidShardCommand, settleShardSpool, settleBootstrapRetention and printLogTail (paid). The bootstrap scope-creation block that bootstrap-retention.test.ts evaluates stays verbatim. * refactor(pty): split claude-pty-runner.ts into test/helpers/pty/* behind a barrel Pure move: every line of the former 5,047-line runner lands verbatim in one module (four private helpers gain `export` for cross-module use): binary, screen (absorbs test/helpers/pty-screen.ts, which now re-exports it), launch, session (PtyDriver), judge, classify, auq, plan-native, boundaries, runners/{observation,counting,floor}. claude-pty-runner.ts re-exports the original public surface by name; pty/ modules import siblings directly. Tests that read the runner's source text: - rewritten as behavioral: the unit test's model-pin tripwire (fake CLI argv: fallback chain, --model before extraArgs, hermetic --strict-mcp-config), pty-skill-seeding-wiring (runners through the fake driver; launcher through a fake CLI reporting CLAUDE_CONFIG_DIR). The "three wrappers forward model" grep is replaced by the runners' fake-driver launch assertions. - pty-screen-session / pty-screen-supervision: stop copying runner source; they mock.module the real pty/screen.ts (and the fixture cleanup) instead. - re-pointed to the owning module (they execute a sliced runner body with injected boundaries; no seam exists for those boundaries yet): eng-seeded-completion-ai, plan-floor-permission, plan-create-prepublication, plan-count-completion; hermetic-wiring's source guard now reads pty/launch.ts and scans every pty/ module for raw process.env spreads. - plan-count-timeout and pty-output-wake mock the viewport at pty/screen.ts. * test(ratchet-c): enforcing module/function size ratchet and moved-code touchfile coverage Ratchet (c) ships enforcing: test/helpers/module-size.ts counts file and top-level function lengths by brace matching over masked source (strings, comments, regex literals and template text masked; ${} expressions kept), covering function declarations, arrow functions assigned to consts and route-table handler properties, with no parser dependency. Its self-test uses template literals and code-fence braces copied from scripts/resolvers/review.ts and design.ts. test/fixtures/module-size-ratchet.json binds scripts/lib/shard-engine.ts (<= 800 lines, <= 150 per function) and records the residual runner sizes (free 2352, paid 1921) as non-growth caps; allowlist entries are keyed on file plus matched text and need a reason. Failure output lists file:line, the rule, Fix: and the allowlist path. touchfiles.test.ts gains the moved-code superset check over test/fixtures/touchfile-move-goldens/ (W2 golden recorded at96764e80: test-strict-output.ts and test-paid-shards.ts global, test-free-shards.ts none). * refactor(browse): declared route table replaces the buildFetchHandler if-chain The ~1,300-line if-chain in buildFetchHandler becomes a route table: each entry declares method, path, auth kind and surfaces, and one auth gate in browse/src/routes/table.ts returns the per-kind denial (root-bearer, scoped, root-or-sse-cookie: 401 Unauthorized; root-token: 403 Root token required; extension-origin: 403 Forbidden). Unmatched requests take the declared fallthrough (root-bearer check, then plain-text 404). Handlers move to browse/src/routes/{core,pairing,pty,tokens,tunnel,activity,commands,files, inspector}.ts and receive a RouteContext with auth checks as functions instead of closing over factory locals. Dispatch order is unchanged: tunnel filter, beforeRoute overlay, gate, handler. TUNNEL_PATHS stays a literal in server.ts. Behavior-preserving: the black-box auth matrix from the previous commit passes unchanged. /memory and /inspector/events are declared root-bearer because the blanket check always ran before their SSE-cookie branch. Source-text route tests are rewritten as behavioral tests through buildFetchHandler or a route's real handler with a stub RouteContext (browse/test/route-test-harness.ts). Checks with no runtime seam are re-pointed to the route modules: Surface type, /inspector/events SSE helper, sanitizeReplacer imports, /pty-inject-scan sidecar-client import, and the ngrok config lookup and startTunnel wiring that stay in server.ts. * test(browse): stubbed-handler auth matrix and route inventory for the route table Every ROUTES entry runs through the real dispatcher and gate with stub handlers on each declared surface and six credentials; denials assert the exact status and body each auth kind returned at96764e8, admitted credentials assert the handler ran (with the gate's TokenInfo for scoped routes). Also pins the reviewed route inventory (method, path, auth kind, surfaces), that every entry declares auth and surfaces, that the table's tunnel paths equal the TUNNEL_PATHS literal with GET /connect admitted, the unmatched fallthrough, and that the root token is rejected on every tunnel route through buildFetchHandler. * test(browse): ratchet (b) keeps route dispatch inside the route table Scans browse/src/server.ts and browse/src/routes/*.ts for pathname comparisons; only the table matcher and the tunnel-surface filter are allowed, listed with reasons in browse/test/fixtures/route-dispatch-allowlist.json (keyed on file plus line text). Also checks every entry declares auth and surfaces and that gstack registers no beforeRoute overlay itself. Self-tests plant a violation and assert the file:line, Fix: and allowlist path in the message, that a shifted line stays allowlisted, and that a reasonless entry is rejected. * test: touchfile superset check for modules moved out of browse/src/server.ts Records the paid evals selected by touching browse/src/server.ts at96764e80(17 E2E, 1 LLM judge) and asserts every browse/src/routes/*.ts module selects a superset. The test reads every golden in test/fixtures/moved-module-selection/ so other moved-code goldens can sit beside it. * test(shard-engine): give non-timeout corpus fixtures CI headroom; keep the POSIX golden off the Windows lane Only the wall-timeout fixture keeps a 3s wall; the rest get 60s so a loaded host cannot turn a pass into a timeout. Base and branch runners still agree on every classification under the new walls. The Windows exclusion entry moves the free runner's ratchet (c) residual cap to 2356 lines. * refactor(pty): one runPtySession loop drives observation, counting and floor test/helpers/pty/session.ts owns launch -> start -> (poll -> tick)* -> timeout and the failure contract the three runners each hand-rolled: the run's own error wins over capture and close errors, close always runs, owned fixture cleanup runs last (also when launch fails). Each runner now supplies a PtySessionPlan: its boot/command step, poll cadence (2s observation/floor sleep; counting's output wake + 250ms coalesce), tick policy (permission handling, native identity, terminal rules stay per runner because they differ) and capture hooks. The runner bodies are decomposed into top-level steps so no function exceeds 150 lines; behavior is unchanged and the fake-driver cases from the first W4 commit pass unmodified. The counting capture step and the native completion-summary predicate are now named functions (countingCapture, isNativeCompletionSummary), so plan-create-prepublication and plan-count-completion call them directly instead of executing sliced source. The two harnesses that still execute a sliced runner body with injected boundaries (eng-seeded-completion-ai, plan-floor-permission) pass the PtyDriver seam instead of overriding Date/Bun.sleep. * test(ratchet-c): register route modules, review resolver modules and server.ts residual cap * refactor(pty): decompose launchClaudePty and engNumberedFindingAUQ under 150 lines launchClaudePty (349 lines) becomes launch preparation (args, hermetic child env, owned state roots), recorder creation, spawn, the trust-dialog watcher, close, and the session handle over one PtyProcess state object. The failure order is unchanged: abort the viewport, dispose any recorders created so far, dispose the viewport, rethrow. The --model / --strict-mcp-config ordering and seedSkills wiring stay pinned by the behavioral fake-CLI tests. engNumberedFindingAUQ (345 lines) keeps its guards and dispatch; each self-contained issue family (declared cache, library retry hooks, cache owner, injected singleton, shared writers, injected export) moves verbatim into its own function. Every pty/ module is now <= 800 lines and every top-level function <= 150 lines. * test(pty): split claude-pty-runner.unit.test.ts along the pty/ module seams The 188 unit tests move verbatim into claude-pty-runner.{screen,classify, auq,launch,plan-native,boundaries}.unit.test.ts (test names unchanged; each file imports only what it uses from the barrel). The five files that no longer read a SKILL.md template join the test-of-test ratchet baseline with a reason. * test(touchfiles): moved PTY modules keep their paid-eval selection test/fixtures/touchfile-selection/w4-pty.json records, at96764e8, the paid evals selected by touching test/helpers/claude-pty-runner.ts (20) and test/helpers/pty-screen.ts (20). touchfiles.test.ts now asserts every .ts file under test/helpers/pty/ (and pty/screen.ts for both sources) selects a superset, reading every golden in that directory so later moves can add one; a planted-violation case pins the report and its Fix line. * fix(browse): unexchanged pair setup keys no longer authenticate bearer requests validateToken accepted a gsk_setup_ key as a bearer on /command, /batch and /file (found while building the W3 auth matrix). A setup key now only authenticates the /connect exchange. * W1: one state-root owner (lib/state-root.ts + bin/gstack-state-root.sh), gstack-paths --explain and fail-stop, parity tests * W1: guarded migration of every executable state-root site; uninstall deletes only ~/.gstack Bins, careful/freeze hooks, setup, upgrade migrations, browse/src, design, ios-qa daemon, lib and scripts resolve the state root through bin/gstack-state-root.sh (bash) or lib/state-root.ts (TS). Bins source the twin and stop with a reinstall message when it is missing; hooks source it and never spawn gstack-paths. browse/src/config.ts and lib/cso/state.ts delegate to resolveStateRoot. Analytics writers and readers move together so the usage log stays one file. gstack-uninstall deletes state only at ~/.gstack, refuses (exit 2) when it resolves to /, $HOME or an ancestor, the checkout or the git root, and leaves any other resolved root in place with the removal command. Fixtures that copy single bins now copy the twin. * W1: privacy keys and trust-policy deny tiers merge across state roots; gstack-config reporting; test hermeticity readConfigKey / gstack_read_config_key return the most restrictive telemetry, memorable_recall, codex_reviews and update_check across the resolved root and ~/.gstack; other keys read the resolved root only. gstack-config set reports an overriding root with the exact override command, list shows the winning root and a root-variable disagreement line. gstack-gbrain-repo-policy get merges deny/read-only tiers. gstack-egress reads through readConfigKey. test-setup.ts strips inherited GSTACK_STATE_ROOT/GSTACK_STATE_DIR and redirects the legacy root. * W1: shared hook logging helper (hosts/claude/hooks/hook-log.ts) One hook-errors.log writer: root from resolveStateRoot, 0600 on every append, opt-in rate limit used only by memorable-user-prompt. The five hooks route through it. * W1: docs/state-root.md and README troubleshooting pointer Precedence table, a real --explain example, the move-your-state recipe, merged privacy keys, the uninstall rule, the resolver-failure fix, and the plugin-mode note (evidence gate: no official plugin distribution). * W1b: template and resolver prose resolve state through guarded gstack-paths; ratchet (a) Every gstack-paths eval in templates and resolvers carries the fail-stop guard; executable ~/.gstack paths in bash blocks (context recovery preamble, eureka log, analytics, project artifacts, upgrade snooze, setup-gbrain lock, retro snapshots, ship consent marker) use $GSTACK_STATE_ROOT, and the writer prose that pairs with them points at the printed PROJECT_DIR / RETRO_FILE. ship drops export GSTACK_STATE_ROOT. SKILL.md regenerated (claude + codex), ship goldens re-pinned, parity and context-budget caps raised to the measured sizes with notes. test/state-root-ratchet.test.ts enforces the rule with a reasoned allowlist; W1 touchfile entries plus a superset golden. * refactor: apply W1 state-root edits in W2/W3/W5-owned files; one moved-code touchfile golden for all workstreams * test: fold the moved-code touchfile golden into touchfiles.test.ts; fix integration fixture closure and caps * v1.91.11.0: CHANGELOG, TODOS, docs and conventions for the refactor wave * test: re-measure plan-ceo/design-consultation caps and ship goldens after the guarded plan-discovery and spec-review blocks; add the state-root twin to the workflow-boundaries fixture * fix(windows): migrations resolve their directory with either path separator; state-root parity compares under the HOME Git Bash actually sees * fix(review,ship): state plan-check timing after smoke expiry and test_stub Skip semantics (review workflow judge clarity) * test(qa-eval): webhook fix eval asks for the fix loop's post-repair probes; eight-scenario coverage stays in the report-only case and the harness recheck * test(qa-eval): re-pin the webhook prompt contract to the fix-loop stage; R29 coverage omissions stay bound by the report-only case * fix(review,ship): plan checks publish a checkpoint before each probe; only the smoke expiry stop is skipped * fix(qa): carry #2999's checkpoint receipt link, report-template line and full-revision placeholder (identical hunks) * test(qa-callers): disable git auto maintenance in the caller fixture Git 2.47+ runs auto maintenance detached after commit; on the CI runner's git 2.55 it rewrote .git/objects fan-out directories while the write observer was running, which surfaced as unauthorized mutations. Same gc.auto=0 / maintenance.auto=false guard the shared-libs fixture already uses. * test(plan-mode-no-op): require prose evidence for the prose-fallback members so a spinner-frame judge verdict cannot end the run as asked * test(ship-docsync): carry #2999's seeded-attempt docsync harness (identical files) The doc-sync fault cases replayed attempt 1 before reaching their gate and ran out of their 285s budget. The fixture now seeds attempt 1 and the parent starts at the gate under test. Taken byte-identical from origin/capy/audit-fix-wave (fb526898,e6ac813d,6ce10ff7,d0c53577,77cce3be). Local: stale-before, recovery and late-result 6/6 PASS (97-164s); the whole file 12/12 PASS.
528 lines
23 KiB
TypeScript
528 lines
23 KiB
TypeScript
/**
|
||
* Browser-skills Phase 2a — gate-tier E2E for /scrape and /skillify.
|
||
*
|
||
* Five scenarios cover the productivity loop and the contracts locked
|
||
* during the v1.19.0.0 plan review:
|
||
*
|
||
* D1 — /skillify provenance guard (scenario 4)
|
||
* D2 — synthesis input slice (covered indirectly by scenario 3 — the
|
||
* committed SKILL.md must not contain conversation prose)
|
||
* D3 — atomic write discipline (scenarios 3 and 5)
|
||
*
|
||
* 1. scrape-match-path — /scrape with intent matching bundled
|
||
* hackernews-frontpage routes via $B skill run, no prototype.
|
||
* 2. scrape-prototype-path — /scrape against a local file:// fixture
|
||
* (no matching skill) drives $B primitives, returns JSON, suggests
|
||
* /skillify.
|
||
* 3. skillify-happy-path — /scrape then /skillify in one session.
|
||
* Skill written to ~/.gstack/browser-skills/<name>/ with full
|
||
* file tree, $B skill test passes.
|
||
* 4. skillify-provenance-refusal — cold /skillify with no prior
|
||
* /scrape refuses with the D1 message; nothing on disk.
|
||
* 5. skillify-approval-reject — /scrape then /skillify but reject in
|
||
* the approval gate; temp dir is removed, nothing at final path.
|
||
*
|
||
* The three skillify keys run gate-tier; the two scrape keys are periodic
|
||
* (/scrape is Aside-first and its fallback no longer prescribes the match +
|
||
* prototype flow they assert — see E2E_TIERS). ~$0.50–$1.50 each.
|
||
* Set EVALS=1 to enable. Set EVALS_MODEL to override (default frontier Claude).
|
||
*/
|
||
|
||
import { describe, test, expect, beforeAll, afterAll } from 'bun:test';
|
||
import { JUDGE_MS, CAPTURE_MS, CAPTURE_LONG_MS } from './helpers/eval-budgets';
|
||
import { runSkillTest } from './helpers/session-runner';
|
||
import {
|
||
ROOT, browseBin, runId,
|
||
describeIfSelected, testConcurrentIfSelected,
|
||
setupBrowseShims, copyDirSync, logCost, recordE2E,
|
||
createEvalCollector, finalizeEvalCollector,
|
||
} from './helpers/e2e-helpers';
|
||
import { extractSkillBody } from './helpers/skill-fixture';
|
||
import { spawnSync } from 'child_process';
|
||
import * as fs from 'fs';
|
||
import * as path from 'path';
|
||
import * as os from 'os';
|
||
|
||
const evalCollector = createEvalCollector('e2e-skillify');
|
||
|
||
// ─── Shared workdir setup ───────────────────────────────────────
|
||
|
||
interface Workdir {
|
||
workDir: string;
|
||
gstackHome: string;
|
||
skillsDir: string;
|
||
}
|
||
|
||
/**
|
||
* Build a working directory that has:
|
||
* - The /scrape and /skillify skills installed under .claude/skills/
|
||
* - The browse binary symlinked + find-browse shim (via setupBrowseShims)
|
||
* - bin/ scripts referenced by the preamble
|
||
* - A scoped GSTACK_HOME under the workdir so on-disk artifacts are
|
||
* contained and assertable
|
||
* - A CLAUDE.md routing block instructing Skill-tool invocation
|
||
*
|
||
* `installSkills` lets each test pick the minimum surface (e.g., the
|
||
* provenance-refusal scenario doesn't need /scrape).
|
||
*/
|
||
function setupSkillifyWorkdir(suffix: string, installSkills: string[] = ['scrape', 'skillify']): Workdir {
|
||
const workDir = fs.mkdtempSync(path.join(os.tmpdir(), `skill-e2e-skillify-${suffix}-`));
|
||
const gstackHome = path.join(workDir, '.gstack-home');
|
||
fs.mkdirSync(gstackHome, { recursive: true });
|
||
|
||
const run = (cmd: string, args: string[]) =>
|
||
spawnSync(cmd, args, { cwd: workDir, stdio: 'pipe', timeout: 5000 });
|
||
run('git', ['init', '-b', 'main']);
|
||
run('git', ['config', 'user.email', 'test@test.com']);
|
||
run('git', ['config', 'user.name', 'Test']);
|
||
fs.writeFileSync(path.join(workDir, 'README.md'), '# test\n');
|
||
run('git', ['add', '.']);
|
||
run('git', ['commit', '-m', 'initial']);
|
||
|
||
setupBrowseShims(workDir);
|
||
|
||
// Install requested skills. The tests exercise the full /scrape + /skillify
|
||
// flows (all 11 skillify steps, D1-D3 contracts), so keep the whole
|
||
// skill-specific body — but drop the ~780-line shared preamble the tests
|
||
// never touch (CLAUDE.md: "E2E test fixtures: extract, don't copy").
|
||
const skillsDir = path.join(workDir, '.claude', 'skills');
|
||
for (const skill of installSkills) {
|
||
const destDir = path.join(skillsDir, skill);
|
||
fs.mkdirSync(destDir, { recursive: true });
|
||
fs.writeFileSync(path.join(destDir, 'SKILL.md'), extractSkillBody(path.join(ROOT, skill)));
|
||
}
|
||
|
||
// bin/ scripts — preamble references several of these.
|
||
const binDir = path.join(workDir, 'bin');
|
||
fs.mkdirSync(binDir, { recursive: true });
|
||
for (const script of [
|
||
'gstack-timeline-log', 'gstack-slug', 'gstack-config', 'gstack-state-root.sh',
|
||
'gstack-update-check', 'gstack-repo-mode',
|
||
'gstack-learnings-log', 'gstack-learnings-search',
|
||
]) {
|
||
const src = path.join(ROOT, 'bin', script);
|
||
if (fs.existsSync(src)) {
|
||
fs.copyFileSync(src, path.join(binDir, script));
|
||
fs.chmodSync(path.join(binDir, script), 0o755);
|
||
}
|
||
}
|
||
|
||
fs.writeFileSync(path.join(workDir, 'CLAUDE.md'), `# Project Instructions
|
||
|
||
## Skill routing
|
||
|
||
When the user's request matches an available skill, ALWAYS invoke it via
|
||
the Skill tool as your FIRST action.
|
||
|
||
Key routing rules:
|
||
- /scrape, "scrape", "get data from", "extract from" → invoke scrape
|
||
- /skillify, "skillify", "codify this scrape" → invoke skillify
|
||
|
||
Environment:
|
||
- GSTACK_HOME="${gstackHome}" for all gstack bin scripts.
|
||
- bin scripts are at ./bin/ relative to this directory.
|
||
- Browse binary is at ${browseBin} — assign to $B (e.g., \`B=${browseBin}\`).
|
||
`);
|
||
|
||
return { workDir, gstackHome, skillsDir };
|
||
}
|
||
|
||
/**
|
||
* Install the bundled hackernews-frontpage browser-skill into the workdir's
|
||
* project-tier (so $B skill list finds it for match-path tests). The skill
|
||
* has to live under <workdir>/.gstack/browser-skills/ for the project-tier
|
||
* lookup to find it (gstack's bundled tier resolves from the install dir,
|
||
* which the test workdir doesn't have).
|
||
*/
|
||
function installBundledHackernewsSkill(workDir: string) {
|
||
const src = path.join(ROOT, 'browser-skills', 'hackernews-frontpage');
|
||
const dst = path.join(workDir, '.gstack', 'browser-skills', 'hackernews-frontpage');
|
||
copyDirSync(src, dst);
|
||
}
|
||
|
||
/** Helper: every Bash invocation's command string from the agent. */
|
||
function bashCommands(result: { toolCalls: Array<{ tool: string; input: any }> }): string[] {
|
||
return result.toolCalls
|
||
.filter((tc) => tc.tool === 'Bash')
|
||
.map((tc) => String(tc.input?.command ?? ''))
|
||
.filter(Boolean);
|
||
}
|
||
|
||
/** Helper: the union of agent text + every tool input/output for matching. */
|
||
function fullSurface(result: any): string {
|
||
const parts: string[] = [];
|
||
if (result.output) parts.push(String(result.output));
|
||
for (const tc of result.toolCalls || []) {
|
||
parts.push(JSON.stringify(tc.input || {}));
|
||
if (tc.output) parts.push(String(tc.output));
|
||
}
|
||
for (const entry of result.transcript || []) {
|
||
try { parts.push(JSON.stringify(entry)); } catch { /* skip */ }
|
||
}
|
||
return parts.join('\n');
|
||
}
|
||
|
||
// ─── Test fixtures ──────────────────────────────────────────────
|
||
|
||
/**
|
||
* Tiny HTML fixture for the prototype-path test. Stable structure with three
|
||
* "items" the agent should be able to extract via $B html + parse.
|
||
*/
|
||
const PROTOTYPE_FIXTURE_HTML = `<!doctype html>
|
||
<html><body>
|
||
<h1>Test Items</h1>
|
||
<ul id="items">
|
||
<li class="item"><a href="/a">First Title</a><span class="score">42</span></li>
|
||
<li class="item"><a href="/b">Second Title</a><span class="score">17</span></li>
|
||
<li class="item"><a href="/c">Third Title</a><span class="score">8</span></li>
|
||
</ul>
|
||
</body></html>
|
||
`;
|
||
|
||
// ─── Live-fire suite ────────────────────────────────────────────
|
||
|
||
describeIfSelected('Browser-skills Phase 2a E2E (/scrape + /skillify)', [
|
||
'scrape-match-path',
|
||
'scrape-prototype-path',
|
||
'skillify-happy-path',
|
||
'skillify-provenance-refusal',
|
||
'skillify-approval-reject',
|
||
], () => {
|
||
afterAll(() => { finalizeEvalCollector(evalCollector); });
|
||
|
||
// ── 1. /scrape match path: bundled hackernews-frontpage matches ──────
|
||
testConcurrentIfSelected('scrape-match-path', async () => {
|
||
const { workDir, gstackHome } = setupSkillifyWorkdir('match', ['scrape']);
|
||
installBundledHackernewsSkill(workDir);
|
||
|
||
const result = await runSkillTest({
|
||
prompt: `Run /scrape latest hacker news stories. Invoke /scrape via the Skill tool.
|
||
You MUST follow the skill's match-phase logic:
|
||
1. Run \`$B skill list\` to see what browser-skills are available
|
||
2. Recognize that "latest hacker news stories" matches the bundled
|
||
hackernews-frontpage skill's triggers
|
||
3. Run \`$B skill run hackernews-frontpage\` and emit the JSON
|
||
Do NOT enter the prototype phase. Do NOT use AskUserQuestion.`,
|
||
workingDirectory: workDir,
|
||
env: { GSTACK_HOME: gstackHome },
|
||
maxTurns: 12,
|
||
allowedTools: ['Skill', 'Bash', 'Read'],
|
||
timeout: JUDGE_MS,
|
||
testName: 'scrape-match-path',
|
||
runId,
|
||
});
|
||
|
||
logCost('scrape-match-path', result);
|
||
|
||
const cmds = bashCommands(result);
|
||
const listedSkills = cmds.some(c => /\bskill\s+list\b/.test(c));
|
||
const ranBundledSkill = cmds.some(c => /\bskill\s+run\s+hackernews-frontpage\b/.test(c));
|
||
const exitOk = ['success', 'error_max_turns'].includes(result.exitReason);
|
||
|
||
recordE2E(evalCollector, 'scrape match-path routes to bundled skill', 'Phase 2a E2E', result, {
|
||
passed: exitOk && listedSkills && ranBundledSkill,
|
||
});
|
||
|
||
expect(exitOk).toBe(true);
|
||
expect(listedSkills).toBe(true);
|
||
expect(ranBundledSkill).toBe(true);
|
||
try { fs.rmSync(workDir, { recursive: true, force: true }); } catch {}
|
||
}, CAPTURE_MS);
|
||
|
||
// ── 2. /scrape prototype path: drive $B primitives against fixture ────
|
||
testConcurrentIfSelected('scrape-prototype-path', async () => {
|
||
const { workDir, gstackHome } = setupSkillifyWorkdir('prototype', ['scrape']);
|
||
|
||
// Stage a local HTML fixture the agent can goto via file://
|
||
const fixturePath = path.join(workDir, 'fixture.html');
|
||
fs.writeFileSync(fixturePath, PROTOTYPE_FIXTURE_HTML);
|
||
const fileUrl = `file://${fixturePath}`;
|
||
|
||
const result = await runSkillTest({
|
||
prompt: `Run /scrape titles and scores from ${fileUrl}.
|
||
Invoke /scrape via the Skill tool. Follow the skill's prototype-phase logic:
|
||
1. \`$B skill list\` finds NO matching skill
|
||
2. Drive: \`$B goto ${fileUrl}\` then \`$B html\` (or \`$B text\`)
|
||
3. Parse the items (each has a title and a score)
|
||
4. Emit JSON of the form {"items": [{"title": "...", "score": N}, ...], "count": N}
|
||
5. Suggest /skillify in one line
|
||
Do NOT use AskUserQuestion.`,
|
||
workingDirectory: workDir,
|
||
env: { GSTACK_HOME: gstackHome },
|
||
maxTurns: 18,
|
||
allowedTools: ['Skill', 'Bash', 'Read'],
|
||
timeout: CAPTURE_MS,
|
||
testName: 'scrape-prototype-path',
|
||
runId,
|
||
});
|
||
|
||
logCost('scrape-prototype-path', result);
|
||
|
||
const cmds = bashCommands(result);
|
||
const wentToFixture = cmds.some(c => c.includes(fileUrl));
|
||
const fetchedHtml = cmds.some(c => /\bgoto\b|\bhtml\b|\btext\b/.test(c));
|
||
const surface = fullSurface(result);
|
||
const mentionsSkillify = /skillify/i.test(surface);
|
||
// Accept JSON shape variants — the prompt asks for `"items": [...]` but
|
||
// the model sometimes emits equivalent containers (`"results"`, `"data"`,
|
||
// `"hits"`) or skips the wrapper entirely and emits a bare array of
|
||
// objects with title+score keys. All of these satisfy the underlying
|
||
// intent: "the agent produced parseable structured output naming the
|
||
// scraped items". We assert the shape, not a literal key name.
|
||
const hasJsonItems =
|
||
/"(items|results|data|hits|entries)"\s*:\s*\[/i.test(surface) ||
|
||
/'(items|results|data|hits|entries)'\s*:/i.test(surface) ||
|
||
// Bare array of {title, score} objects (no outer wrapper key)
|
||
/\[\s*\{[^}]*\btitle\b[^}]*\bscore\b/.test(surface);
|
||
const exitOk = ['success', 'error_max_turns'].includes(result.exitReason);
|
||
|
||
recordE2E(evalCollector, 'scrape prototype-path drives $B + emits JSON + nudges skillify', 'Phase 2a E2E', result, {
|
||
passed: exitOk && wentToFixture && fetchedHtml && hasJsonItems && mentionsSkillify,
|
||
});
|
||
|
||
expect(exitOk).toBe(true);
|
||
expect(wentToFixture).toBe(true);
|
||
expect(fetchedHtml).toBe(true);
|
||
expect(hasJsonItems).toBe(true);
|
||
expect(mentionsSkillify).toBe(true);
|
||
try { fs.rmSync(workDir, { recursive: true, force: true }); } catch {}
|
||
}, CAPTURE_MS);
|
||
|
||
// ── 3. /skillify happy path: scrape then skillify in one session ─────
|
||
testConcurrentIfSelected('skillify-happy-path', async () => {
|
||
const { workDir, gstackHome } = setupSkillifyWorkdir('happy', ['scrape', 'skillify']);
|
||
const fixturePath = path.join(workDir, 'fixture.html');
|
||
fs.writeFileSync(fixturePath, PROTOTYPE_FIXTURE_HTML);
|
||
const fileUrl = `file://${fixturePath}`;
|
||
|
||
const childHome = path.join(workDir, 'home');
|
||
fs.mkdirSync(childHome, { recursive: true });
|
||
|
||
const result = await runSkillTest({
|
||
prompt: `Two steps in this session:
|
||
|
||
1. Run /scrape titles and scores from ${fileUrl} via the Skill tool.
|
||
Drive the prototype path; return JSON with items[].
|
||
|
||
2. Run /skillify via the Skill tool. Follow ALL 11 steps including:
|
||
- D1 provenance guard (you have a recent /scrape, proceed)
|
||
- D2 synthesis: include ONLY the final-attempt $B calls (goto + html)
|
||
- D3 atomic write: stage to temp dir, run test, then commit on approval
|
||
- When AskUserQuestion fires, choose the recommended option (A)
|
||
for both the name/tier question AND the approval gate.
|
||
|
||
Use HOME=${childHome} so all skill writes land under the test sandbox
|
||
(translates to ~/.gstack/browser-skills/<name>/ via $HOME).
|
||
|
||
Do NOT halt for clarification.`,
|
||
workingDirectory: workDir,
|
||
env: {
|
||
GSTACK_HOME: gstackHome,
|
||
// Fresh subdir, NEVER the cwd: with HOME == cwd, claude resolves
|
||
// <cwd>/.claude/skills as the PERSONAL skills dir and the seeded
|
||
// project-tier skills stop registering — this test's Skill() calls
|
||
// silently errored ("Unknown skill") and only passed via the agent
|
||
// self-recovering by Reading SKILL.md manually. Same fix as the
|
||
// provenance-refusal test below.
|
||
HOME: childHome, // /skillify writes to $HOME/.gstack/browser-skills/
|
||
},
|
||
maxTurns: 40,
|
||
allowedTools: ['Skill', 'Bash', 'Read', 'Write'],
|
||
timeout: CAPTURE_LONG_MS,
|
||
testName: 'skillify-happy-path',
|
||
runId,
|
||
});
|
||
|
||
logCost('skillify-happy-path', result);
|
||
|
||
// The skill lands under $HOME/.gstack/browser-skills/<name>/ (= childHome);
|
||
// sweep the cwd tier too in case the skill's write path resolves cwd-relative.
|
||
const skillRoots = [childHome, workDir].map((r) => path.join(r, '.gstack', 'browser-skills'));
|
||
const writtenSkills = skillRoots.flatMap((root) => (fs.existsSync(root)
|
||
? fs.readdirSync(root)
|
||
.filter(d => !d.startsWith('.') && d !== 'hackernews-frontpage')
|
||
.map((d) => path.join(root, d))
|
||
: []));
|
||
const skillDir = writtenSkills[0] ?? '';
|
||
const hasAllFiles = !!skillDir
|
||
&& fs.existsSync(path.join(skillDir, 'SKILL.md'))
|
||
&& fs.existsSync(path.join(skillDir, 'script.ts'))
|
||
&& fs.existsSync(path.join(skillDir, 'script.test.ts'))
|
||
&& fs.existsSync(path.join(skillDir, '_lib', 'browse-client.ts'))
|
||
&& fs.existsSync(path.join(skillDir, 'fixtures'));
|
||
|
||
// D2 enforcement: the SKILL.md prose body MUST NOT contain conversation
|
||
// fragments. Cheap heuristic: it shouldn't have "I" or "Let me" or other
|
||
// first-person/agent-narration markers.
|
||
let prosesClean = false;
|
||
if (hasAllFiles) {
|
||
const skillMd = fs.readFileSync(path.join(skillDir, 'SKILL.md'), 'utf-8');
|
||
const body = skillMd.split(/\n---\n/)[1] || '';
|
||
prosesClean = !/^I /m.test(body)
|
||
&& !/Let me /i.test(body)
|
||
&& !/^I'll /m.test(body);
|
||
}
|
||
|
||
const exitOk = ['success', 'error_max_turns'].includes(result.exitReason);
|
||
|
||
recordE2E(evalCollector, 'skillify happy path writes well-formed skill on disk', 'Phase 2a E2E', result, {
|
||
passed: exitOk && hasAllFiles && prosesClean,
|
||
});
|
||
|
||
expect(exitOk).toBe(true);
|
||
expect(writtenSkills.length).toBeGreaterThan(0);
|
||
expect(hasAllFiles).toBe(true);
|
||
expect(prosesClean).toBe(true);
|
||
try { fs.rmSync(workDir, { recursive: true, force: true }); } catch {}
|
||
}, CAPTURE_LONG_MS);
|
||
|
||
// ── 4. /skillify provenance refusal: D1 contract ─────────────────────
|
||
testConcurrentIfSelected('skillify-provenance-refusal', async () => {
|
||
const { workDir, gstackHome } = setupSkillifyWorkdir('refusal', ['skillify']);
|
||
// Child HOME must be a FRESH dir, never workDir itself: with HOME == cwd,
|
||
// claude resolves <cwd>/.claude/skills as the PERSONAL skills dir and the
|
||
// project-tier skills seeded there never register — the Skill tool then
|
||
// errors "Unknown skill: skillify" (observed on claude 2.1.237). A
|
||
// sibling home/ dir keeps the override's intent (any ~/.gstack write from
|
||
// the child lands inside the assertable sandbox, not the operator's real
|
||
// home) without colliding with project-skill discovery.
|
||
const childHome = path.join(workDir, 'home');
|
||
fs.mkdirSync(childHome, { recursive: true });
|
||
|
||
const result = await runSkillTest({
|
||
prompt: `Run /skillify via the Skill tool. There has been NO prior /scrape
|
||
in this conversation. Follow the skill's Step 1 (D1 provenance guard) literally:
|
||
walk back through agent turns, find no /scrape result, refuse with the exact
|
||
message the skill specifies, and stop. Do NOT synthesize anything. Do NOT
|
||
write any files.`,
|
||
workingDirectory: workDir,
|
||
env: {
|
||
GSTACK_HOME: gstackHome,
|
||
HOME: childHome,
|
||
},
|
||
maxTurns: 8,
|
||
allowedTools: ['Skill', 'Bash', 'Read'],
|
||
timeout: JUDGE_MS,
|
||
testName: 'skillify-provenance-refusal',
|
||
runId,
|
||
});
|
||
|
||
logCost('skillify-provenance-refusal', result);
|
||
|
||
// Tripwire: the Skill tool must actually LOAD skillify. A not-loaded
|
||
// skill (tool error "Unknown skill: skillify", or the agent narrating
|
||
// "not registered" and improvising a refusal) must never pass as a D1
|
||
// refusal. Neither phrase appears in the skillify fixture or the prompt,
|
||
// so a hit can only come from a real load failure.
|
||
const surface = fullSurface(result);
|
||
const skillLoadFailed = /unknown skill|not registered/i.test(surface);
|
||
|
||
// The refusal must be in the AGENT'S OWN words. When the Skill tool
|
||
// loads skillify, the SKILL.md body — which contains the exact refusal
|
||
// message — is injected into the transcript as a user message, so
|
||
// matching the full surface would pass vacuously. Match only assistant
|
||
// text blocks + the final result.
|
||
const agentText = [
|
||
result.output,
|
||
...result.transcript
|
||
.filter((e: any) => e?.type === 'assistant')
|
||
.flatMap((e: any) => ((e.message?.content ?? []) as any[])
|
||
.filter((c: any) => c?.type === 'text')
|
||
.map((c: any) => String(c.text ?? ''))),
|
||
].join('\n');
|
||
const refusalText = /no recent \/?scrape result|run \/scrape.*first|no prior \/?scrape/i.test(agentText);
|
||
|
||
// Critical: nothing on disk. No staged dir, no committed skill. Tier
|
||
// paths resolve under $HOME/.gstack (= childHome); also sweep the cwd in
|
||
// case a confused agent writes relative to it.
|
||
const diskRoots = [childHome, workDir];
|
||
const noSkillsWritten = diskRoots.every((root) => {
|
||
const skillsRoot = path.join(root, '.gstack', 'browser-skills');
|
||
return !fs.existsSync(skillsRoot)
|
||
|| fs.readdirSync(skillsRoot).filter(d => !d.startsWith('.')).length === 0;
|
||
});
|
||
const noStaging = diskRoots.every((root) => {
|
||
const stagingRoot = path.join(root, '.gstack', '.tmp');
|
||
return !fs.existsSync(stagingRoot)
|
||
|| fs.readdirSync(stagingRoot).filter(d => d.startsWith('skillify-')).length === 0;
|
||
});
|
||
|
||
const exitOk = ['success', 'error_max_turns'].includes(result.exitReason);
|
||
|
||
recordE2E(evalCollector, 'skillify D1 refusal — no on-disk write', 'Phase 2a E2E', result, {
|
||
passed: exitOk && !skillLoadFailed && refusalText && noSkillsWritten && noStaging,
|
||
});
|
||
|
||
expect(exitOk).toBe(true);
|
||
expect(skillLoadFailed).toBe(false);
|
||
expect(refusalText).toBe(true);
|
||
expect(noSkillsWritten).toBe(true);
|
||
expect(noStaging).toBe(true);
|
||
try { fs.rmSync(workDir, { recursive: true, force: true }); } catch {}
|
||
}, JUDGE_MS);
|
||
|
||
// ── 5. /skillify approval-gate reject: D3 cleanup ────────────────────
|
||
testConcurrentIfSelected('skillify-approval-reject', async () => {
|
||
const { workDir, gstackHome } = setupSkillifyWorkdir('reject', ['scrape', 'skillify']);
|
||
const fixturePath = path.join(workDir, 'fixture.html');
|
||
fs.writeFileSync(fixturePath, PROTOTYPE_FIXTURE_HTML);
|
||
const fileUrl = `file://${fixturePath}`;
|
||
|
||
const childHome = path.join(workDir, 'home');
|
||
fs.mkdirSync(childHome, { recursive: true });
|
||
|
||
const result = await runSkillTest({
|
||
prompt: `Two steps:
|
||
|
||
1. Run /scrape titles and scores from ${fileUrl} via the Skill tool.
|
||
|
||
2. Run /skillify via the Skill tool. Follow steps 1-9. When the approval
|
||
gate AskUserQuestion fires (Step 9), choose option C (Discard) instead
|
||
of A (Commit). The D3 contract says the temp dir must be removed and
|
||
nothing should land at the final tier path.
|
||
|
||
Use HOME=${childHome}. Do NOT commit the skill.`,
|
||
workingDirectory: workDir,
|
||
env: {
|
||
GSTACK_HOME: gstackHome,
|
||
// Fresh subdir, never the cwd — see the happy-path comment.
|
||
HOME: childHome,
|
||
},
|
||
maxTurns: 35,
|
||
allowedTools: ['Skill', 'Bash', 'Read', 'Write'],
|
||
timeout: CAPTURE_LONG_MS,
|
||
testName: 'skillify-approval-reject',
|
||
runId,
|
||
});
|
||
|
||
logCost('skillify-approval-reject', result);
|
||
|
||
// D3 contract: nothing at the final tier path; staging dir is gone.
|
||
// Sweep BOTH roots: $HOME/.gstack (= childHome) and cwd-relative .gstack.
|
||
const negativeRoots = [childHome, workDir];
|
||
const writtenSkills = negativeRoots.flatMap((root) => {
|
||
const skillsRoot = path.join(root, '.gstack', 'browser-skills');
|
||
return fs.existsSync(skillsRoot)
|
||
? fs.readdirSync(skillsRoot).filter(d => !d.startsWith('.'))
|
||
: [];
|
||
});
|
||
const stagingLeftovers = negativeRoots.flatMap((root) => {
|
||
const stagingRoot = path.join(root, '.gstack', '.tmp');
|
||
return fs.existsSync(stagingRoot)
|
||
? fs.readdirSync(stagingRoot).filter(d => d.startsWith('skillify-'))
|
||
: [];
|
||
});
|
||
|
||
const exitOk = ['success', 'error_max_turns'].includes(result.exitReason);
|
||
|
||
recordE2E(evalCollector, 'skillify approval-reject leaves no on-disk artifact', 'Phase 2a E2E', result, {
|
||
passed: exitOk && writtenSkills.length === 0 && stagingLeftovers.length === 0,
|
||
});
|
||
|
||
expect(exitOk).toBe(true);
|
||
expect(writtenSkills.length).toBe(0);
|
||
expect(stagingLeftovers.length).toBe(0);
|
||
try { fs.rmSync(workDir, { recursive: true, force: true }); } catch {}
|
||
}, CAPTURE_LONG_MS);
|
||
});
|