@joshuafolkken/kit 1.1005.0 → 1.1035.0

package/scripts/test/unit-projects.ts

@@ -1,139 +0,0 @@
-import { agent_session_environment } from '#scripts/josh/agent-session-environment'
-import { PILOT_FILES } from './pilot-files'
-import { VITEST_INCLUDE_GLOBS } from './vitest-include-globs'
-
-// The unit suite runs as two Vitest projects so the isolation-safe files can skip per-file worker
-// isolation, which re-evaluates every shared module once per file (joshuafolkken/kit#2170). Measured
-// back to back on the pilot set, isolate:false ran it in 27.5s against 64.7s isolated — a 57% cut,
-// because module evaluation is about half of a run's wall clock.
-//
-// **The two projects partition the suite exactly.** `pure` runs the classifier's isolation-free set;
-// `isolated` runs everything else the main globs match, excluding the pilot files so no file lands in
-// both. Their union is every included file bar the packed-consumer smoke test, and nothing runs
-// twice — which is what keeps the gate's green condition identical to the single-project suite it
-// replaces. `classify-isolation.ts` lists a file as pure only when it mutates no state a sibling in
-// the same worker could observe, so isolate:false changes how the pure files run, never whether they
-// pass.
-
-const TEST_TIMEOUT_MS = 10_000
-
-// Smoke test packs and installs the real tarball — too slow (~60 s setup) for the unit gate. Run
-// before release with: pnpm vitest run --config vitest.harness.config.ts
-const MAIN_EXCLUDE: ReadonlyArray<string> = ['scripts/build/packed-consumer.test.ts']
-
-// **`JOSH_LANE_CHILD` is blanked so the unit suite never inherits the lane it happens to run in**
-// (joshuafolkken/kit#2310). The gate runs inside a dispatched lane child, whose mark and lane cwd would
-// otherwise make every world-consulting rule guard (`pre-gate-cut`, `implementation-cut`, `lane-park`)
-// read a delivery fixture as a real lane-child call and fire on it. A suite that wants to test
-// lane-child behavior sets the mark itself in its own `beforeEach`, exactly as it always has; blank is
-// the "no dispatch mark" a person's session carries, which `marked_issue` reads as absent.
-//
-// **The proxy spellings are blanked for the same reason** (joshuafolkken/kit#2436): a package-manager
-// wrapper writes its loopback proxy and CA into everything `pnpm` spawns, so a suite asserting what a
-// `gh` spawn receives would pass in CI and fail on a machine with the wrapper. A suite about proxies
-// declares the one it is testing in its own `beforeEach`.
-//
-// **The detached ship supervisor's marks are blanked too** (joshuafolkken/kit#2456): the pre-push unit
-// run inherits `JOSH_SHIP_SUPERVISED` and `JOSH_AGENT_PROVIDER` from the supervisor that pushes, so a
-// ship fixture would take the supervised stop path — and try to relaunch a real lane child — only there.
-const PROXY_ENV: Record<string, string> = Object.fromEntries(
-	[...agent_session_environment.PROXY_KEYS, agent_session_environment.PROXY_CERTIFICATE_KEY].map(
-		(key) => [key, ''],
-	),
-)
-
-const ENV: Record<string, string> = {
-	...PROXY_ENV,
-	CLAUDE_CODE_SESSION_ID: 'vitest-session',
-	CODEX_THREAD_ID: '',
-	JOSH_AGENT_PROVIDER: '',
-	JOSH_LANE_CHILD: '',
-	JOSH_SHIP_SUPERVISED: '',
-}
-
-const PURE_PROJECT = 'pure'
-const ISOLATED_PROJECT = 'isolated'
-
-// The state guard runs on the pure project alone. isolate:false is what lets one file see the git
-// branch, working tree or GIT_* variables a sibling left changed, so that is the only run where a leak
-// is a correctness problem rather than a latent one — and the isolated project keeps exactly the guards
-// the single-project suite had. The network guard is armed once at the root instead, since it arms
-// `PATH` before any worker of either project forks.
-const STATE_GUARD: ReadonlyArray<string> = ['./scripts/test/test-state-guard.ts']
-
-// Runs in every worker of both projects, before each test, and silences the real streams for the test
-// body so a fixture's direct `process.stdout` write cannot leak into `pnpm josh test:unit`'s output
-// (joshuafolkken/kit#2296). `setupFiles` rather than `globalSetup` because it must run inside the
-// worker where the test's writes happen, not once in the main process.
-const STDOUT_GUARD: ReadonlyArray<string> = ['./scripts/test/test-stdout-guard.ts']
-
-// Runs in every worker for the same reason: it wraps that worker's own `fetch`, refusing a real
-// Telegram send and recording which test tried (joshuafolkken/kit#2494).
-const TELEGRAM_GUARD: ReadonlyArray<string> = ['./scripts/test/test-telegram-guard.ts']
-
-interface UnitProjectTest {
-	name: string
-	env: Record<string, string>
-	include: ReadonlyArray<string>
-	exclude: ReadonlyArray<string>
-	isolate: boolean
-	testTimeout: number
-	globalSetup: ReadonlyArray<string>
-	setupFiles: ReadonlyArray<string>
-}
-
-interface UnitProject {
-	test: UnitProjectTest
-}
-
-interface UnitProjectSpec {
-	name: string
-	include: ReadonlyArray<string>
-	isolate: boolean
-	exclude?: ReadonlyArray<string>
-	globalSetup?: ReadonlyArray<string>
-}
-
-function unit_project(spec: UnitProjectSpec): UnitProject {
-	return {
-		test: {
-			name: spec.name,
-			env: ENV,
-			include: [...spec.include],
-			exclude: [...(spec.exclude ?? [])],
-			isolate: spec.isolate,
-			testTimeout: TEST_TIMEOUT_MS,
-			globalSetup: [...(spec.globalSetup ?? [])],
-			setupFiles: [...STDOUT_GUARD, ...TELEGRAM_GUARD],
-		},
-	}
-}
-
-const UNIT_PROJECTS: ReadonlyArray<UnitProject> = [
-	unit_project({
-		name: PURE_PROJECT,
-		include: PILOT_FILES,
-		isolate: false,
-		globalSetup: STATE_GUARD,
-	}),
-	unit_project({
-		name: ISOLATED_PROJECT,
-		include: VITEST_INCLUDE_GLOBS,
-		isolate: true,
-		exclude: [...MAIN_EXCLUDE, ...PILOT_FILES],
-	}),
-]
-
-const unit_projects = {
-	ENV,
-	ISOLATED_PROJECT,
-	MAIN_EXCLUDE,
-	PURE_PROJECT,
-	STATE_GUARD,
-	STDOUT_GUARD,
-	TELEGRAM_GUARD,
-	UNIT_PROJECTS,
-}
-
-export type { UnitProject, UnitProjectTest }
-export { unit_projects }

package/scripts/test/vitest-include-globs.ts

@@ -1,12 +0,0 @@
-const VITEST_INCLUDE_GLOBS: ReadonlyArray<string> = [
-	'*.test.ts',
-	'scripts/**/*.test.ts',
-	'scripts-ai/**/*.test.ts',
-	'env/**/*.test.ts',
-	'eslint/**/*.test.ts',
-	'ports/**/*.test.ts',
-	'prettier/**/*.test.ts',
-	'templates/**/*.test.ts',
-]
-
-export { VITEST_INCLUDE_GLOBS }

package/scripts/time-runtime/time-batch-guard-fixtures.ts

@@ -1,66 +0,0 @@
-import type { GuardedCall } from './time-batch-guard'
-
-// The calls, labels and transcript builder the batch-guard suite is written from, lifted out of
-// `time-batch-guard.test.ts` so the suite stays under its line limit as kit#2311 adds the read-fold
-// cases (joshuafolkken/kit#2311). Fixtures rather than tests, so they carry no `describe`; the one
-// test file that reads them imports the names it already used.
-
-const NEVER_REFUSED = 0
-const FRESH_PATH = 'scripts/fresh.ts'
-// A path-shaped word that appears only inside quotes (joshuafolkken/kit#1611).
-const QUOTED_PATTERN = 'scripts/time'
-const FRESH_CALL: GuardedCall = { name: 'Read', input: { file_path: FRESH_PATH } }
-// The two calls both predicate tables name, and their labels, so neither the fixture nor the wording is
-// written twice.
-const EDIT_LABEL = 'an edit'
-const SED_LABEL = 'an in-place sed'
-const FILE_READ_LABEL = 'a file read'
-const EDIT_TOOL = 'Edit'
-// Named the way this harness names it. Neither spelling of the delegation tool is in the bundleable
-// set, so the case reads the same under `Task`.
-const DELEGATION_TOOL = 'Agent'
-const WRITE_TOOL = 'Write'
-const WRITE_LABEL = 'a whole-file write'
-const EDIT_CALL: GuardedCall = { name: EDIT_TOOL, input: { file_path: FRESH_PATH } }
-const IN_PLACE_SED_CALL: GuardedCall = {
-	name: 'Bash',
-	input: { command: `sed -i '' s/a/b/ ${FRESH_PATH}` },
-}
-const SHELL_READ_CALL: GuardedCall = { name: 'Bash', input: { command: `cat ${FRESH_PATH}` } }
-const JOSH_CALL: GuardedCall = { name: 'Bash', input: { command: 'pnpm josh gate' } }
-const CHAINED_SED_CALL: GuardedCall = {
-	name: 'Bash',
-	input: { command: `cat notes.md && sed -i '' s/a/b/ ${FRESH_PATH}` },
-}
-const REDIRECTION_CALL: GuardedCall = {
-	name: 'Bash',
-	input: { command: "jq '.x' a.json > b.json" },
-}
-const WRITE_CALL: GuardedCall = { name: WRITE_TOOL, input: { file_path: FRESH_PATH } }
-
-// The turns of one run, joined the way Claude Code writes them: one line per content block.
-function transcript(...groups: Array<Array<string>>): string {
-	return groups.flat().join('\n')
-}
-
-export {
-	CHAINED_SED_CALL,
-	DELEGATION_TOOL,
-	EDIT_CALL,
-	EDIT_LABEL,
-	EDIT_TOOL,
-	FILE_READ_LABEL,
-	FRESH_CALL,
-	FRESH_PATH,
-	IN_PLACE_SED_CALL,
-	JOSH_CALL,
-	NEVER_REFUSED,
-	QUOTED_PATTERN,
-	REDIRECTION_CALL,
-	SED_LABEL,
-	SHELL_READ_CALL,
-	WRITE_CALL,
-	WRITE_LABEL,
-	WRITE_TOOL,
-	transcript,
-}

package/scripts-ai/completion-gate.ts

@@ -1,13 +0,0 @@
-const GATE_LINT = 'pnpm run lint'
-const GATE_CHECK_CI = 'pnpm josh check:svelte:ci'
-const GATE_CSPELL = 'pnpm josh cspell:dot'
-const GATE_TEST_UNIT = 'pnpm josh test:unit'
-
-const COMPLETION_GATE_STEPS: ReadonlyArray<string> = [
-	GATE_LINT,
-	GATE_CHECK_CI,
-	GATE_CSPELL,
-	GATE_TEST_UNIT,
-]
-
-export { COMPLETION_GATE_STEPS, GATE_LINT, GATE_CHECK_CI, GATE_CSPELL, GATE_TEST_UNIT }

package/scripts-ai/environment-loader.ts

@@ -1,9 +0,0 @@
-function load_optional_environment(): void {
-	try {
-		process.loadEnvFile('.env')
-	} catch {
-		// .env is optional
-	}
-}
-
-export { load_optional_environment }