@joshuafolkken/kit 1.1005.0 → 1.1035.0

package/prompts/collaboration-workflow/single-source-rules.md

@@ -1,13 +0,0 @@
-## エージェント規則の単一ソースは `CLAUDE.md`（`AGENTS.md` / `GEMINI.md` は導線）
-
-**規則の本体は `CLAUDE.md` にしか無い。** `AGENTS.md` と `GEMINI.md` は「規則は `CLAUDE.md` にある。作業前に全文を読むこと」だけを書いた短い導線文書であり、規則を 1 行も持たない（joshuafolkken/kit#963）。
-
-- **規則の追加・仕様変更・文言修正・節の追加は `CLAUDE.md` に 1 回だけ書く。** 他の 2 本には触れない
-- **導線文書に規則を書き戻さない。** そこに書かれた規則は、次の改訂で更新し忘れる 4 つ目の置き場になる
-- `scripts/document/ai-document-pointers.test.ts` が機械的に守る。導線文書に規則本体が再出現した場合、導線の一文が消えた場合、`CLAUDE.md` が単一ソースであることの記述が消えた場合に落ちる
-
-**なぜこうなったか。** 3 本はほぼ同一の複製で、規則を 1 つ変えるたびに 3 回書いて 3 回レビューする必要があり、しかも 3 本とも常駐上限まで 1KB を切っていた。これは `CLAUDE.md` 自身が「No clones — single-source」で禁じているクローンそのものであり、禁止を書いている文書がその禁止に違反している状態だった。
-
-**他ツールでの検証は行っていない。** Codex / Cursor / Gemini CLI が導線を辿るかは未確認で、現在 Claude しか使っていないという判断による（joshuafolkken/kit#970 の `## Decisions`）。導線を辿らないツールを使い始める時点で、そのツールについて別途扱う。
-
-- このルールは横断ドキュメント（CLAUDE.md「Doc Sync Rules」）のカノニカル参照

package/scripts/build/shim-shell.ts

@@ -1,25 +0,0 @@
-// The two `sh` fragments both unit-suite shims are built from. Single-sourced because a guard's own
-// defects fail **open**: a path that lost its quoting leaves the shim a syntax error that records
-// nothing, and a `printf` that lost its `>>` truncates the record every call — in either case the
-// run is reported clean while the calls keep going out. One spelling, used by every generator, is
-// what keeps that impossible to get wrong in only one of them.
-
-const SINGLE_QUOTE = "'"
-
-// One `sh` word, quoted. A checkout under `/Users/o'brien` is not exotic, and an unquoted path there
-// would close the quote and leave the rest of the line as syntax.
-function quoted(value: string): string {
-	// `sh` has no escape inside single quotes, so an apostrophe is written by closing the quote,
-	// emitting an escaped one, and opening a new quote: `'\''`.
-	return SINGLE_QUOTE + value.replaceAll("'", String.raw`'\''`) + SINGLE_QUOTE
-}
-
-// Append one line of prose to the shared record. `>>` rather than `>`, because every worker of the
-// run writes to the same file and the last one must not erase what the others found.
-function record_line(log_file: string, recorded: string): string {
-	return String.raw`printf '%s\n' "${recorded}" >> ${quoted(log_file)}`
-}
-
-const shim_shell = { quoted, record_line }
-
-export { shim_shell }

package/scripts/claude/skill-meta.ts

@@ -1,37 +0,0 @@
-// Where a skill lives and how its frontmatter is read (joshuafolkken/kit#854, single-sourced for
-// joshuafolkken/kit#1151).
-//
-// The suites that assert a skill ships correctly and the `josh cost` resident breakdown that sizes
-// the skills index both need the same two facts: which directory holds the skills, and what the
-// entry file's frontmatter says. This module is where those live, so the pattern is not written
-// twice — `skill-fixture.ts` is a test fixture and is excluded from the published package, so
-// shipped code cannot read it.
-
-const SKILL_ROOT = '.claude/skills'
-const SKILL_ENTRY_FILE = 'SKILL.md'
-const FRONTMATTER_PATTERN = /^---\n([\S\s]*?)\n---\n/u
-const DESCRIPTION_PATTERN = /^description: (.+)$/mu
-
-function has_frontmatter(content: string): boolean {
-	return FRONTMATTER_PATTERN.test(content)
-}
-
-function frontmatter_of(content: string): string {
-	return FRONTMATTER_PATTERN.exec(content)?.[1] ?? ''
-}
-
-// The description is the trigger for every agent that discovers a skill by reading descriptions
-// rather than by being told a path, so it is read out rather than merely asserted present.
-function description_of(content: string): string {
-	return DESCRIPTION_PATTERN.exec(frontmatter_of(content))?.[1] ?? ''
-}
-
-const skill_meta = {
-	SKILL_ROOT,
-	SKILL_ENTRY_FILE,
-	has_frontmatter,
-	frontmatter_of,
-	description_of,
-}
-
-export { skill_meta }

package/scripts/document/document-scan.ts

@@ -1,108 +0,0 @@
-// Pulling machine-checkable references out of the distributed documents, so a few structural scans
-// can replace the ~140 per-phrase marker suites the documents used to carry (joshuafolkken/kit#1923).
-// Every function here is a pure string extractor: it takes document text and returns the references
-// it names, which is what lets the scans that call it be checked on a synthetic string with a
-// deliberately broken reference in it.
-
-// A command reference, only inside a code span. `` `pnpm josh gate` `` and `` `josh review:brief` ``
-// are the copy-and-paste form; the leading backtick keeps prose like "josh will decide" out, which
-// would otherwise read "will" as a command name.
-const COMMAND_PATTERN = /`(?:pnpm )?josh ([a-z][a-z0-9:-]+)/gu
-
-// A label the documents operate on — applied (`labels[]=…`), removed (`…/labels/<name>`) or created
-// (`labels -f name=…`). Prose that merely names a label is not scanned; a mistyped name only breaks
-// where a command carries it.
-const LABEL_PATTERN = /(?:labels\[\]=|\/labels\/|labels -f name=)([a-z][a-z0-9:_-]*)/gu
-
-// A section reference: a markdown file in a code span, an arrow, and the cited heading in straight or
-// Japanese quotes — `` `backlogrun-progress.md` → "The hand-off" ``.
-const SECTION_PATTERN = /`([\w./-]+\.md)`\s*→\s*["「]([^"」]+)["」]/gu
-
-// A relative markdown link target, with an optional `#anchor`. External `https://…` links carry no
-// `.md`, so the pattern never matches them.
-const LINK_PATTERN = /\]\(([\w./-]+\.md)(?:#[\w-]+)?\)/gu
-
-// Filenames that appear in the documents as illustrations of the reference form itself, never as real
-// targets — the doc-section explanation cites `` `path.md` → "Heading" `` and `` `X.md` → "Heading" ``.
-const PLACEHOLDER_FILES: ReadonlySet<string> = new Set(['x.md', 'foo.md', 'file.md', 'path.md'])
-
-function matches(text: string, pattern: RegExp): Array<RegExpMatchArray> {
-	return [...text.matchAll(pattern)]
-}
-
-// A trailing colon is a placeholder for the sub-command that follows — `` `josh epic:` `` stands for
-// `epic:audit`, `epic:next` and the rest — so it names no command of its own.
-function command_references(text: string): Array<string> {
-	return matches(text, COMMAND_PATTERN)
-		.map((match) => match[1] ?? '')
-		.filter((name) => !name.endsWith(':'))
-}
-
-// A `<placeholder>` inside a command, and `depth:<n>` after the char class stops at `<`, both leave a
-// token that is not a real label. Real labels never end in a colon and never carry angle brackets.
-function is_real_label(token: string): boolean {
-	return token.length > 0 && !token.endsWith(':') && !token.includes('<')
-}
-
-function label_references(text: string): Array<string> {
-	return matches(text, LABEL_PATTERN)
-		.map((match) => match[1] ?? '')
-		.filter((token) => is_real_label(token))
-}
-
-function base_name(path: string): string {
-	return path.split('/').at(-1) ?? path
-}
-
-function is_placeholder_file(name: string): boolean {
-	return name.includes('<') || PLACEHOLDER_FILES.has(base_name(name).toLowerCase())
-}
-
-interface SectionReference {
-	file: string
-	heading: string
-}
-
-function section_references(text: string): Array<SectionReference> {
-	return matches(text, SECTION_PATTERN)
-		.map(([, file, heading]) => ({ file: file ?? '', heading: heading ?? '' }))
-		.filter((reference) => !is_placeholder_file(reference.file))
-}
-
-function link_targets(text: string): Array<string> {
-	return matches(text, LINK_PATTERN)
-		.map((match) => match[1] ?? '')
-		.filter((file) => !is_placeholder_file(file))
-}
-
-// A cited heading and the heading it names are compared with backticks dropped and whitespace
-// collapsed, because a reference wraps at the column the prose wraps at — sometimes across a
-// blockquote `> ` continuation — while the heading it points at is one unbroken line.
-function normalize_reference(heading: string): string {
-	return heading
-		.replaceAll('`', '')
-		.split(/\s+/u)
-		.filter((word) => word !== '>')
-		.join(' ')
-}
-
-// The two forms a heading can be cited by: with its leading number (`2b. Delegating…`) and without
-// (`Delegating…`), since a document's own numbering is a prefix a reference may or may not carry.
-function reference_forms(title: string): Array<string> {
-	const normalized = normalize_reference(title)
-
-	return [normalized, normalized.replace(/^\d+[a-z]?\. /u, '')]
-}
-
-const document_scan = {
-	command_references,
-	is_placeholder_file,
-	label_references,
-	link_targets,
-	normalize_reference,
-	reference_forms,
-	section_references,
-}
-
-export type { SectionReference }
-export { document_scan }

package/scripts/document/generate-catalog.ts

@@ -1,69 +0,0 @@
-import { writeFileSync } from 'node:fs'
-import { fileURLToPath } from 'node:url'
-import {
-	ALIASES,
-	CATEGORY_ORDER,
-	COMMAND_MAP,
-	type CommandCategory,
-	type CommandEntry,
-} from '#scripts/josh/josh-command-map'
-
-const CATALOG_FILE = fileURLToPath(new URL('../../docs/josh-command-catalog.md', import.meta.url))
-
-const PREAMBLE = `# josh CLI — Command Catalog
-
-Auto-generated — do not edit.
-Run \`tsx scripts/document/generate-catalog.ts\` to regenerate.
-
-`
-
-function aliases_for(command_name: string): ReadonlyArray<string> {
-	return Object.entries(ALIASES)
-		.filter(([, target]) => target === command_name)
-		.map(([alias]) => alias)
-		.toSorted((x, y) => x.localeCompare(y))
-}
-
-function format_alias_heading(name: string, aliases: ReadonlyArray<string>): string {
-	if (aliases.length === 0) return `### \`josh ${name}\``
-	const alias_spans = aliases.map((al) => `\`josh ${al}\``).join(' · ')
-
-	return `### \`josh ${name}\` · ${alias_spans}`
-}
-
-function format_command_entry(name: string, entry: CommandEntry): string {
-	const [synopsis, audience, side_effects] = entry.reference
-	const aliases = aliases_for(name)
-	const kit_note = entry.is_kit_only === true ? ' · **kit only**' : ''
-	const heading = format_alias_heading(name, aliases)
-	const meta = `> **Audience:** ${audience} · **Side effects:** ${side_effects.join(', ')}${kit_note}`
-	const synopsis_line = synopsis ? `\`${synopsis}\`` : '_No arguments._'
-
-	return [heading, '', meta, '', synopsis_line, '', entry.description].join('\n')
-}
-
-function entries_for_category(category: CommandCategory): Array<[string, CommandEntry]> {
-	return Object.entries(COMMAND_MAP)
-		.filter(([, entry]) => entry.category === category)
-		.toSorted(([name_a], [name_b]) => name_a.localeCompare(name_b))
-}
-
-function generate_category_section(category: CommandCategory): string {
-	const entries = entries_for_category(category)
-	if (entries.length === 0) return ''
-	const command_blocks = entries.map(([name, entry]) => format_command_entry(name, entry))
-
-	return `## ${category}\n\n${command_blocks.join('\n\n---\n\n')}\n\n`
-}
-
-function generate_catalog(): string {
-	const content = PREAMBLE + CATEGORY_ORDER.map((cat) => generate_category_section(cat)).join('')
-
-	return `${content.trimEnd()}\n`
-}
-
-if (process.argv[1] === fileURLToPath(import.meta.url)) {
-	writeFileSync(CATALOG_FILE, generate_catalog())
-}
-
-export { CATALOG_FILE, generate_catalog }

package/scripts/document/retired-phrases.ts

@@ -1,143 +0,0 @@
-// Phrases retracted from the distributed documents, kept so a clone or a reverted decision cannot
-// creep back unnoticed (joshuafolkken/kit#1923). This is the small negative table that replaced the
-// ~140 scattered `not.toContain` assertions the per-rule marker suites carried: each phrase is
-// checked absent from the whole document corpus at once by `document-markers.test.ts`.
-//
-// Whitespace is collapsed on both sides before the comparison, so a phrase that the formatter would
-// wrap across a line break is still caught. A phrase here must stay genuinely gone everywhere; if one
-// is ever a legitimate part of a new document, remove its row rather than scoping it.
-const RETIRED_PHRASES: ReadonlyArray<string> = [
-	'"Implemented <title>:',
-	'"dev": "vite dev --port $(josh port dev)',
-	'"dev": "vite dev --port $(pnpm josh port dev)',
-	'"preview": "wrangler dev --port $(josh port preview)',
-	'"preview": "wrangler dev --port $(pnpm josh port preview)',
-	'"preview:stop": "kill-port $(josh port preview)',
-	'"preview:stop": "kill-port $(pnpm josh port preview)',
-	'### セッション対話の言語（`JOSH_SESSION_LANG`）',
-	'**2 つ目を作ってはならない。**',
-	'**2 件目以降で `--exclude` を省略してはならない。**',
-	'**EPIC 作成へ落ちてはならない。**',
-	'**`#N` が宣言された順序に載っていなくても構わない。**',
-	'**`--ordered` は必須であって好みの問題ではない。**',
-	'**`-u` は省略できない。**',
-	'**■ Overview (plain language — always first)**',
-	'**書き換えられた lock ファイルは最初の子と一緒に入る。**',
-	'--- 技術詳細 ---',
-	'2 件以上に分割したら常に epic を作る。件数の閾値も、実行順序の有無による分岐も無い',
-	'3-6 line work summary',
-	'3–6 line work summary',
-	'Artifact languages are unaffected',
-	'Ask the user to run `pnpm josh test` and share the output',
-	'CI only runs the suite it can find, so specs stay under',
-	'CI status check indicates a managed config file was updated',
-	"Cross-package problems → interrupt with a new Issue, don't patch locally.",
-	'EPIC 全体で 1 回の質問',
-	'Fix in place and re-run `/code-review` at the level `pnpm josh review:level` prints on `git diff main`',
-	'Implement + PR',
-	'Invoking `halfrun` authorizes commit, push, and PR creation',
-	'Issue / PR / Telegram の言語は英語のまま変更なし',
-	'Issue plan comments MUST be written in English',
-	'Issue 本文に「`halfrun` で実行すること」と書いても強制力が無く',
-	'Neither toolkit carries `shot` yet',
-	'No toolkit ships that command yet',
-	'Plan comments MUST be in English',
-	'Poll at the polling interval; ask',
-	'Post the agreed plan in English',
-	'Post the plan in English',
-	'Print the headings exactly as written',
-	'Re-run after applying fixes until **no high or medium findings remain**.',
-	'The recommended default when in doubt is the root-cause interrupt',
-	'The user runs `pnpm josh test` and shares the full output',
-	String.raw`Today that\n> is every consumer`,
-	'Typing `halfrun` approved implementing and merging',
-	'Verify **every** rule below. These are non-standard, so call out any violation.',
-	'What still waits for a person, today',
-	'`into owner/repo#N` は正しい書式である',
-	'`queue` との違いはひとつだけである',
-	'about 60 characters in Japanese, 15 words in English',
-	'artifact languages (Issue / PR / Telegram = English) are unchanged',
-	'ask them to run **`pnpm josh test`** locally',
-	'blocker を見る前に',
-	'chain-rule decision table in \\',
-	'code-reviewer',
-	'compose an implementation summary in English',
-	'exactly what it was) → `pnpm josh git -y` →',
-	'exists in neither toolkit yet',
-	'fix them in place and re-run `/code-review` at the level `pnpm josh review:level` prints. Nothing is committed yet',
-	'fresh-context',
-	'fresh-context subagent',
-	'gh issue list --label review-round2-skipped',
-	'including commit, push, PR creation',
-	'is a separate deliverable',
-	"it asks only after a child that ran in the parent's own context",
-	'its own `pnpm josh gate` join',
-	'join it, and `pnpm josh git -y`; on `skip`',
-	'kit exports that rule for consumers and does not apply it to itself',
-	'operating-rules.md` → "Auto-merge',
-	'park したことで人が必要になる',
-	'park しない',
-	'park は依存として表現できない場合に限る',
-	'post the final review markdown as a PR comment',
-	'queue #101',
-	'runs the same pipeline through PR creation',
-	'sleep the polling interval and go back to step 1',
-	'stay in English regardless of `JOSH_SESSION_LANG`',
-	'stop before merge',
-	'stop with the PR OPEN',
-	'the artifact language stays English',
-	'the completed PR diff',
-	"the threshold is the same number the epic's own measurement produced",
-	'through PR creation',
-	'until the user confirms E2E passed',
-	'while the PR is still OPEN',
-	'→ `pnpm josh git -y` → the follow-up filing',
-	'→ join → `pnpm josh git -y`,',
-	'■ これからやること',
-	'この停止は残す',
-	'これが無いと、判断が返ったのに子が永久に止まる',
-	'これは advisory であり、アトミックではない',
-	'これは分割ではない',
-	'これは意図した差である',
-	'そのたびに人が口頭で起票先を指示していた',
-	'どちらを取るか迷う場合は、**根本対応（割り込み Issue）を既定とする**',
-	'コミット後かつ `pnpm josh followup` 実行前',
-	'マップが答えるのは「チェックアウトがどこにあるか」であって',
-	'ラウンドごとのコミットや CI 再実行も発生しない',
-	'ラベルはリポジトリごとに一度作る',
-	'レビュー自体はコミットの前のままで',
-	'今こうなっている: <1文',
-	'位置の判断は対象 EPIC が既に採ってきた基準に従う',
-	'候補画像からの採用決定など',
-	'入口ごとに条件が違う状態は欠陥である',
-	'入口だけがこの記法から取り残されていた',
-	'勝手に clone することは人の作業機の配置を勝手に決めることである',
-	'子 1 件の `fullrun` は分単位。これより短くしても API 消費が増えるだけ',
-	'子が 13 件なら stash も 13 個になる',
-	'子を実装するリポジトリではない',
-	'実行手順の正典は本節であり',
-	'常駐判定の問いは',
-	'成果物が存在した時点で入れる',
-	'成果物の良し悪しは機械では測れない',
-	'成果物は常に英語',
-	'打ち忘れた回の Issue はどの EPIC にも属さない',
-	'排他はリポジトリ単位であり、それを適用するのは `epic:next` である',
-	'推薦は信号が弱ければ何もしないが',
-	'新規 EPIC を作る前に、`#N` が既に EPIC の子でないかを確かめる',
-	'日本語で 60 字程度',
-	'昇格が他人の Issue を容れ物へ書き換える構造変更であり',
-	'最後の行が最も重要である',
-	'検討した 3 案のうち',
-	'片方だけでは後から辿れない',
-	'理由は綴りである',
-	'省略可能な確認ではない',
-	'矛盾を抱えた計画に対して一括決定を行っても、決定ごと作り直しになる',
-	'確認という歯止めを外す以上、上限を付ける',
-	'禁じられているのは裸の',
-	'自分で外せる印は印として機能せず',
-	'自動投稿される Issue コメント文面は英語で記載する',
-	'読み取りにこそ付け忘れやすく、付け忘れは黙って通る',
-	'閉じていない blocker を宣言している候補を除外する',
-]
-
-export { RETIRED_PHRASES }

package/scripts/document/review-agent-type.ts

@@ -1,46 +0,0 @@
-import { read_unwrapped } from './ai-document-fixture'
-
-// The `/code-review` subagent's agent type is named once, in `chain-rule.md` step 1, so a run stops
-// guessing a name like `code-reviewer` and receiving `Agent type not found` (joshuafolkken/kit#2297).
-// This reads that name back and checks it is a real Claude Code agent type rather than a plausible
-// invention.
-
-const CHAIN_RULE = '.claude/skills/workflow-commands/chain-rule.md'
-
-// The built-in Claude Code agent types the `Agent` tool resolves. `general-purpose` is the one the
-// review uses — it carries every tool, so it can load the review skill and, with `--fix`, apply
-// findings. The set is the source of truth the document test measures the named type against; there is
-// no runtime registry to derive it from, so it is enumerated here.
-const KNOWN_AGENT_TYPES: ReadonlySet<string> = new Set([
-	'general-purpose',
-	'Explore',
-	'Plan',
-	'claude',
-	'claude-code-guide',
-	'statusline-setup',
-])
-
-// The type named as `` `<name>` agent type ``, read from the unwrapped document so a reflow that moved
-// the words to a new line does not hide it.
-const AGENT_TYPE_PATTERN = /`([\w-]+)` agent type/u
-
-function named_agent_type(text: string = read_unwrapped(CHAIN_RULE)): string | undefined {
-	return AGENT_TYPE_PATTERN.exec(text)?.[1]
-}
-
-// Whether the document names an agent type and that type is a real one. A missing name and an invented
-// name are both failures — the first leaves the run guessing, the second is the guess made canonical.
-function names_known_type(text: string = read_unwrapped(CHAIN_RULE)): boolean {
-	const named = named_agent_type(text)
-
-	return named !== undefined && KNOWN_AGENT_TYPES.has(named)
-}
-
-const review_agent_type = {
-	CHAIN_RULE,
-	KNOWN_AGENT_TYPES,
-	named_agent_type,
-	names_known_type,
-}
-
-export { review_agent_type }

package/scripts/document/single-source.ts

@@ -1,73 +0,0 @@
-// The single-source check a document-rule test runs to keep one piece of prose in one place
-// (joshuafolkken/kit#2188). Epic #2166 trims the entry read by turning prose a reader interprets into
-// commands and reference-only pointers; that only holds if the body moved to its command's help does
-// not get pasted back into the prose. This is the framework a later child pins each such move with —
-// give it the body marker and the file allowed to carry it, and it names every other document that
-// still carries the body.
-//
-// **It is a pure function of the corpus, so the reader is injected.** Reading the repository is the
-// test's job (`ai-document-fixture.read_repo_file`); this module takes a `read` and answers from what
-// it returns, so the same logic verifies synthetic inputs in its own test and the real corpus in a
-// document-rule suite.
-
-const SINGLE = 1
-
-interface SingleSourceRule {
-	// The prose fragment that must live in exactly one place.
-	marker: string
-	// The one document allowed to carry it; every reference elsewhere points here rather than copying.
-	canonical: string
-}
-
-type ReadDocument = (document_path: string) => string
-
-// Prose is re-wrapped by the formatter, so a marker that spans a line break would miss on a reflow
-// that changed nothing. Collapsing whitespace on both sides pins the words rather than the column,
-// exactly as `read_unwrapped` does for the marker suites.
-function collapsed(text: string): string {
-	return text.replaceAll(/\s+/gu, ' ')
-}
-
-function carries(text: string, marker: string): boolean {
-	return collapsed(text).includes(collapsed(marker))
-}
-
-// Every document whose text carries the marker, canonical included — the primitive the two checks
-// below read from.
-function carriers(
-	marker: string,
-	documents: ReadonlyArray<string>,
-	read: ReadDocument,
-): Array<string> {
-	return documents.filter((document_path) => carries(read(document_path), marker))
-}
-
-// The documents that carry the body but are not its canonical home — a non-empty result is the
-// violation a single-source suite asserts against.
-function violations(
-	rule: SingleSourceRule,
-	documents: ReadonlyArray<string>,
-	read: ReadDocument,
-): Array<string> {
-	return carriers(rule.marker, documents, read).filter(
-		(document_path) => document_path !== rule.canonical,
-	)
-}
-
-// True only when the canonical carries the body and nothing else does. A body missing from its
-// canonical home is as wrong as one copied elsewhere — a pointer left with nothing to point at — so
-// both halves are checked here rather than only the copies.
-function is_single_sourced(
-	rule: SingleSourceRule,
-	documents: ReadonlyArray<string>,
-	read: ReadDocument,
-): boolean {
-	const found = carriers(rule.marker, documents, read)
-
-	return found.length === SINGLE && found[0] === rule.canonical
-}
-
-const single_source = { carriers, is_single_sourced, violations }
-
-export type { ReadDocument, SingleSourceRule }
-export { single_source }

package/scripts/git/git-fixture-workspace.ts

@@ -1,88 +0,0 @@
-import { mkdtempSync } from 'node:fs'
-import { rm } from 'node:fs/promises'
-import { tmpdir } from 'node:os'
-import path from 'node:path'
-import { execa } from 'execa'
-import { git_location_environment } from './git-location-environment'
-
-// The scaffolding a test needs to drive **real git** in a throwaway repository
-// (joshuafolkken/kit#1533).
-//
-// Two suites need it — `lane-change-base.test.ts` builds a lane topology, `rename-changed-paths.test.ts`
-// builds a branch that renames a file away — and neither can use a mocked git, because what each one
-// asserts is a property of git itself rather than of an argument list this repository assembles.
-//
-// **It is one module rather than one copy per suite because this scaffolding has already had to be
-// hardened once.** joshuafolkken/kit#1530 found these fixtures committing into the repository the
-// suite was running in: under a git hook, `GIT_DIR` and `GIT_INDEX_FILE` beat `cwd` outright, and
-// `git config user.email` wrote the fixture's identity into a `--local` config that every linked work
-// tree shares. Both halves of that fix live below. A second copy would take the next such hardening
-// in one place and silently keep the old behavior in the other — the clone `CLAUDE.md` prohibits.
-
-// `restore_environment` is declared as "present, possibly undefined" rather than optional:
-// `exactOptionalPropertyTypes` is on, so an optional property cannot be *assigned* `undefined`, and
-// every suite here starts from a literal that has not opened a workspace yet.
-interface FixtureWorkspace {
-	workspace: string
-	previous_cwd: string
-	restore_environment: (() => void) | undefined
-}
-
-const MAIN_BRANCH = '--initial-branch=main'
-
-// The name commits are authored under, exported because a suite asserts it: proving the identity
-// reached the commit is half of proving it was never written into a config file.
-const AUTHOR_NAME = 'Kit Fixture'
-
-// **The identity rides on `-c` rather than being written with `git config`** (joshuafolkken/kit#1530).
-// A `--local` write outlives the test and is shared by every work tree of the repository it lands in;
-// an option is scoped to the one command.
-const IDENTITY_OPTIONS: ReadonlyArray<string> = [
-	'-c',
-	'user.email=fixture@example.test',
-	'-c',
-	`user.name=${AUTHOR_NAME}`,
-	'-c',
-	'commit.gpgsign=false',
-]
-
-// **The environment is cleared rather than inherited** (joshuafolkken/kit#1530). Run from a git hook,
-// this process holds `GIT_DIR` and `GIT_INDEX_FILE` pointing at the repository being pushed, and both
-// beat `cwd` — so every command here would act on that repository instead of on the fixture.
-async function git(cwd: string, arguments_: ReadonlyArray<string>): Promise<string> {
-	const { stdout } = await execa('git', [...IDENTITY_OPTIONS, ...arguments_], {
-		cwd,
-		env: git_location_environment.location_free_environment(),
-		extendEnv: true,
-	})
-
-	return stdout.trimEnd()
-}
-
-// Cleared for this process too, not only for the children `git` spawns: a suite's assertions drive
-// `git_command`, which spawns git with no environment of its own and so inherits this one.
-function open_workspace(prefix: string): FixtureWorkspace {
-	return {
-		restore_environment: git_location_environment.clear_git_location_variables(),
-		previous_cwd: process.cwd(),
-		workspace: mkdtempSync(path.join(tmpdir(), prefix)),
-	}
-}
-
-async function close_workspace(fixture: FixtureWorkspace): Promise<void> {
-	process.chdir(fixture.previous_cwd)
-	fixture.restore_environment?.()
-	await rm(fixture.workspace, { force: true, recursive: true })
-}
-
-const git_fixture_workspace = {
-	AUTHOR_NAME,
-	close_workspace,
-	git,
-	IDENTITY_OPTIONS,
-	MAIN_BRANCH,
-	open_workspace,
-}
-
-export type { FixtureWorkspace }
-export { git_fixture_workspace }