From fa1dfd0c433e686c60f82d45a526a2a37089df21 Mon Sep 17 00:00:00 2001 From: Paul Bakaus Date: Mon, 17 Aug 2026 22:10:37 -0700 Subject: [PATCH] Tests: note what plugin-e2e validates before and after the generated-output sync Prepared with AI assistance (Claude Code). --- tests/plugin-e2e.test.mjs | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/tests/plugin-e2e.test.mjs b/tests/plugin-e2e.test.mjs index 1f7f286de..e614cce12 100644 --- a/tests/plugin-e2e.test.mjs +++ b/tests/plugin-e2e.test.mjs @@ -18,6 +18,14 @@ * CLI derives a path from the home directory rather than CLAUDE_CONFIG_DIR. * Requires the `claude` CLI on PATH; skips cleanly otherwise. * + * The subtree under test is whatever git holds at ./plugin, which the sync + * workflow regenerates on main (`bun run build:release`). Between the launcher + * swap landing and that sync, ./plugin still ships the Node-era scripts; the + * loader inventory asserted here is unaffected either way (the launcher layout + * was verified against a local `bun run build:release` before the swap + * merged), and tests/hook-build.test.mjs gates its launcher-path assertions on + * the synced output. + * * Run with: bun run test:plugin-e2e */ import { describe, it, before, after } from 'node:test';