@joshuafolkken/kit 1.1514.0 → 1.2114.0

package/.github/workflows/publish.yml

@@ -7,9 +7,11 @@ run-name: Publish ${{ github.ref_name }}
 on:
   workflow_dispatch:
 
-# Every job installs through `.github/actions/setup-pnpm`, so the jobs holding the publish rights
-# install behind the same hash-verified safe-chain scan as CI (joshuafolkken/kit#2982). The store
-# cache is off here: a cache entry another run saved never reaches a job with publish credentials.
+# The jobs holding the publish rights install nothing and run no repository code: a compromised
+# dependency would otherwise publish with valid provenance (joshuafolkken/kit#4633). Every install
+# and every `tsx` run happens in `pack`, which holds no credentials, behind the same hash-verified
+# safe-chain scan as CI (joshuafolkken/kit#2982). Its store cache is off: a cache entry another run
+# saved never reaches the tarball the publish jobs receive.
 
 jobs:
   # The package is built once, here, and both registries receive this one tarball: a job that built
@@ -21,20 +23,46 @@ jobs:
     timeout-minutes: 10
     permissions:
       contents: read
+    # One dist-tag for both registries, chosen against npmjs, whose `latest` needs no credentials to
+    # read: both receive the same tarball in the same run, so they move in step. `pack` runs outside
+    # the `package-publish` queue, so the publish jobs re-check `latest` against its choice (see there).
+    outputs:
+      tag: ${{ steps.publish-tag.outputs.tag }}
+      version: ${{ steps.publish-tag.outputs.version }}
     steps:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          persist-credentials: false
 
       - uses: ./.github/actions/setup-node
 
+      # Read before setup-pnpm puts the safe-chain shims on PATH: safe-chain hides recent versions from
+      # registry metadata and prints a notice to stdout, which corrupts the value (joshuafolkken/kit#3060).
+      - name: Read registry latest
+        id: registry-latest
+        run: |
+          latest=$(cd "$RUNNER_TEMP" && npm view @joshuafolkken/kit dist-tags.latest --registry https://registry.npmjs.org)
+          echo "latest=$latest" >> "$GITHUB_OUTPUT"
+
       - uses: ./.github/actions/setup-pnpm
         with:
           cache: 'false'
 
+      - name: Select publish tag
+        id: publish-tag
+        run: |
+          version=$(node -p "require('./package.json').version")
+          tag=$(pnpm exec tsx scripts/release/publish-tag-cli.ts "$version" "$LATEST")
+          echo "tag=$tag" >> "$GITHUB_OUTPUT"
+          echo "version=$version" >> "$GITHUB_OUTPUT"
+        env:
+          LATEST: ${{ steps.registry-latest.outputs.latest }}
+
       - run: pnpm pack --out "$RUNNER_TEMP/kit.tgz"
 
       # Kept as long as GitHub lets a run be re-run, so re-running a failed publish job still finds
       # the tarball instead of forcing a full re-run that republishes an existing version.
-      - uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
+      - uses: actions/upload-artifact@cf430e030ddbb5b0abf93d22962f4752f3646cd9 # v7.0.2
         with:
           name: kit-package
           path: ${{ runner.temp }}/kit.tgz
@@ -54,40 +82,38 @@ jobs:
       packages: write
     steps:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          persist-credentials: false
 
       - uses: ./.github/actions/setup-node
         with:
           registry-url: 'https://npm.pkg.github.com'
           scope: '@joshuafolkken'
 
-      # Read before setup-pnpm puts the safe-chain shims on PATH: safe-chain hides recent versions from
-      # registry metadata and prints a notice to stdout, which corrupts the value (joshuafolkken/kit#3060).
-      - name: Read registry latest
-        id: registry-latest
-        run: |
-          latest=$(cd "$RUNNER_TEMP" && npm view @joshuafolkken/kit dist-tags.latest --registry https://npm.pkg.github.com)
-          echo "latest=$latest" >> "$GITHUB_OUTPUT"
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-
-      - uses: ./.github/actions/setup-pnpm
-        with:
-          cache: 'false'
-
-      - name: Select GitHub Packages tag
-        id: publish-tag
-        run: |
-          version=$(node -p "require('./package.json').version")
-          tag=$(pnpm exec tsx scripts/release/publish-tag-cli.ts "$version" "$LATEST")
-          echo "tag=$tag" >> "$GITHUB_OUTPUT"
-        env:
-          LATEST: ${{ steps.registry-latest.outputs.latest }}
-
       - uses: actions/download-artifact@9000827ccba6bdab643e8b6fd33ac0654aef8333 # v8.0.2
         with:
           name: kit-package
           path: ${{ runner.temp }}
 
+      # `pack` chose `latest` outside this queue, so another tag's run may have moved npmjs' `latest`
+      # since: publishing then could move it back to an older version (joshuafolkken/kit#2660). The
+      # choice stays valid while npmjs' `latest` is not above this run's version, so an older tag's
+      # run publishing in between does not stop this one; a newer one stops the job before it
+      # publishes, and re-running all jobs chooses again. `sort -V` ranks a prerelease above its
+      # release, which can only stop a valid run, never let a stale one through. `backfill` needs no
+      # check: a later `latest` is never lower than the one `pack` read. The user config is skipped
+      # so the scoped GitHub Packages registry setup-node wrote does not redirect the lookup.
+      - name: Confirm npm latest is not newer
+        if: needs.pack.outputs.tag == 'latest'
+        run: |
+          latest=$(cd "$RUNNER_TEMP" && npm view @joshuafolkken/kit dist-tags.latest --registry https://registry.npmjs.org --userconfig /dev/null)
+          if ! printf '%s\n%s\n' "$latest" "$VERSION" | sort -V -C; then
+            echo "::error::npm latest moved to $latest, above $VERSION, after pack chose the tag; re-run all jobs"
+            exit 1
+          fi
+        env:
+          VERSION: ${{ needs.pack.outputs.version }}
+
       # The tag reaches the command through the environment rather than expanded into it, so a step
       # output is never parsed as shell (joshuafolkken/kit#3084). setup-node's user config carries
       # the GitHub Packages token, so it is kept here.
@@ -95,7 +121,7 @@ jobs:
         run: cd "$RUNNER_TEMP" && npm publish kit.tgz --tag "$PUBLISH_TAG" --registry https://npm.pkg.github.com
         env:
           NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          PUBLISH_TAG: ${{ steps.publish-tag.outputs.tag }}
+          PUBLISH_TAG: ${{ needs.pack.outputs.tag }}
 
   publish-npm:
     needs: pack
@@ -110,40 +136,34 @@ jobs:
       id-token: write
     steps:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          persist-credentials: false
 
       - uses: ./.github/actions/setup-node
         with:
           registry-url: 'https://registry.npmjs.org'
 
-      # Before setup-pnpm, for the same reason as publish-github's lookup (joshuafolkken/kit#3060).
-      - name: Read registry latest
-        id: registry-latest
-        run: |
-          latest=$(cd "$RUNNER_TEMP" && npm view @joshuafolkken/kit dist-tags.latest --registry https://registry.npmjs.org)
-          echo "latest=$latest" >> "$GITHUB_OUTPUT"
-
-      - uses: ./.github/actions/setup-pnpm
-        with:
-          cache: 'false'
-
       - uses: actions/download-artifact@9000827ccba6bdab643e8b6fd33ac0654aef8333 # v8.0.2
         with:
           name: kit-package
           path: ${{ runner.temp }}
 
-      - name: Select npm tag
-        id: publish-tag
+      # The same check as publish-github's, for the same reason.
+      - name: Confirm npm latest is not newer
+        if: needs.pack.outputs.tag == 'latest'
         run: |
-          version=$(node -p "require('./package.json').version")
-          tag=$(pnpm exec tsx scripts/release/publish-tag-cli.ts "$version" "$LATEST")
-          echo "tag=$tag" >> "$GITHUB_OUTPUT"
+          latest=$(cd "$RUNNER_TEMP" && npm view @joshuafolkken/kit dist-tags.latest --registry https://registry.npmjs.org --userconfig /dev/null)
+          if ! printf '%s\n%s\n' "$latest" "$VERSION" | sort -V -C; then
+            echo "::error::npm latest moved to $latest, above $VERSION, after pack chose the tag; re-run all jobs"
+            exit 1
+          fi
         env:
-          LATEST: ${{ steps.registry-latest.outputs.latest }}
+          VERSION: ${{ needs.pack.outputs.version }}
 
       - name: Publish to npm
         run: cd "$RUNNER_TEMP" && npm publish kit.tgz --access public --tag "$PUBLISH_TAG" --registry https://registry.npmjs.org --userconfig /dev/null
         env:
-          PUBLISH_TAG: ${{ steps.publish-tag.outputs.tag }}
+          PUBLISH_TAG: ${{ needs.pack.outputs.tag }}
 
   update-production:
     needs: [publish-github, publish-npm]
@@ -167,6 +187,7 @@ jobs:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
         with:
           fetch-depth: 0
+          persist-credentials: false
 
       - uses: ./.github/actions/setup-node
 

package/.github/workflows/sonar-qube.yml

@@ -40,6 +40,7 @@ jobs:
         if: env.SONAR_TOKEN != ''
         with:
           fetch-depth: 0 # Shallow clones should be disabled for a better relevancy of analysis
+          persist-credentials: false
       # The dependencies are installed before the scan, on a push as well as on a pull request:
       # `tsconfig.sonar.json` extends `@joshuafolkken/kit/tsconfig/base`, which a consumer resolves
       # only from node_modules, so a scan ahead of the install read a config it could not load

package/.prettierignore

@@ -6,6 +6,8 @@
 !.claude/.claude-plugin/
 # Prettier pads every Markdown table column, which grows the skills past their byte budgets (joshuafolkken/kit#3325)
 .claude/**/*.md
+# Generated one-row-per-command table, pinned by its generator's test; padding would multiply its size (#4162)
+docs/josh-command-catalog.md
 
 # Package Managers
 package-lock.json

package/.vscode/settings.json

@@ -16,6 +16,25 @@
 	"files.associations": {
 		"**/tsconfig/*.json": "jsonc"
 	},
+	"files.watcherExclude": {
+		"**/node_modules/**": true,
+		"**/.git/objects/**": true,
+		"**/.git/subtree-cache/**": true,
+		"**/.git/josh/**": true,
+		"**/.josh/observations/**": true,
+		"**/.svelte-kit/**": true,
+		"coverage/**": true,
+		"build/**": true,
+		"dist/**": true
+	},
+	"search.exclude": {
+		"**/node_modules": true,
+		"**/.git/josh": true,
+		"**/.svelte-kit": true,
+		"coverage": true,
+		"build": true,
+		"dist": true
+	},
 	"[markdown]": {
 		"editor.defaultFormatter": "esbenp.prettier-vscode"
 	},

package/.vscode/tasks.json

@@ -7,8 +7,7 @@
 			"command": "pnpm josh run:board",
 			"isBackground": true,
 			"problemMatcher": [],
-			"presentation": { "reveal": "always", "panel": "dedicated", "focus": false },
-			"runOptions": { "runOn": "folderOpen" }
+			"presentation": { "reveal": "always", "panel": "dedicated", "focus": false }
 		}
 	]
 }

package/CLAUDE.md

@@ -1,9 +1,5 @@
 # Claude Code Instructions
 
-## Project
-
-Stack: TypeScript · pnpm · SvelteKit · Vitest · Playwright · TailwindCSS · Drizzle · better-auth · Paraglide · MCP
-
 ## Communication
 
 - **Answer opinion-seeking questions from a neutral standpoint.** A leading question is not a cue to agree — recommend the option you genuinely judge best.
@@ -11,14 +7,14 @@ Stack: TypeScript · pnpm · SvelteKit · Vitest · Playwright · TailwindCSS ·
 - **Cross-package problems → file the upstream Issue, then stop.** A defect in another package (a dependency, or `josh` / kit tooling) is never worked around locally — **weakening a verification gate is a workaround too**. File it (first-party Tier A, third-party Tier C) and stop. `prompts/collaboration-workflow/upstream-interrupt.md`. Your own repository's run tooling is not another package: `upstream-interrupt.md` → "実行中のリポジトリ自身のラン機構の不具合".
 - **Third-party repositories are Tier C.** Decide the party with `pnpm josh repo:party`; every write to a tracker we do not own needs explicit current-turn instruction. `prompts/collaboration-workflow/upstream-interrupt.md`.
 - **No clones — single-source, even across package boundaries.** Duplicate non-trivial logic only after presenting the alternative and getting explicit approval. `prompts/collaboration-workflow/principles.md` → "no-clones".
-- **Design for elegance and simplicity first.** Before adding a hook, guard, rule or abstraction, ask whether fixing the cause makes it unnecessary. `prompts/collaboration-workflow/principles.md` → "elegant-design"; conflicting quality goals → "quality-priority".
+- **Design for elegance and simplicity first.** Before adding a hook, guard, rule or abstraction, ask whether fixing the cause makes it unnecessary. `prompts/collaboration-workflow/principles.md` → "elegant-design"; conflicting quality goals, or a remedy for defects → "quality-priority".
 - **Write concise prose: conditions and actions only.** `prompts/collaboration-workflow/principles.md` → "concise-prose".
 - **Distinguish consultation from execution.** A question or goal statement asks for analysis only — act on an explicit imperative or a workflow keyword. `prompts/collaboration-workflow/principles.md` → "consult-vs-execute".
 - **Route distributed-doc / config changes upstream to kit.** In a consumer repo never edit kit-distributed docs/config; in kit you are the source. `prompts/collaboration-workflow/principles.md` → "upstream-to-kit".
 - **Latest-first, fix forward — pin back only as a last resort.** `prompts/collaboration-workflow/principles.md` → "latest-first".
 - **Output language follows `JOSH_SESSION_LANG`** (default `ja`) for session output and artifact prose; English for Issue/PR titles, code comments, test titles, commit messages and script strings. `prompts/collaboration-workflow/overview.md`.
 - **Durable rules belong in prompts/docs, not local MEMORY.** `prompts/collaboration-workflow/principles.md` → "durable-rules".
-- **Hook-delivered rules** (file edits, shell bodies, turn batching, Issue citation, …): `prompts/collaboration-workflow/rule-delivery.md` → "配送されている規則".
+- **Hook-delivered rules** (file edits, shell bodies, turn batching, …): `prompts/collaboration-workflow/rule-delivery.md` → "配送されている規則".
 
 ### Decision autonomy
 
@@ -32,7 +28,7 @@ Log auto-decisions: an Issue comment in an Issue workflow, else a one-line "Auto
 
 ## Critical Conventions (non-standard — always apply)
 
-Naming, exports, file names and content rules are enforced by `eslint/rules/`; their single source is `prompts/coding-standards.md` → "Conventions". `function` syntax, not arrows (named SvelteKit route handlers may use typed-const arrows); lint does not check it.
+Naming, exports, file names and content rules are enforced by `eslint/rules/`; their single source is `prompts/coding-standards.md` → "Conventions". `function` syntax, not arrows (named SvelteKit route handlers may use typed-const arrows), `func-style`.
 
 ### Quality limits
 
@@ -45,10 +41,10 @@ Before building a feature, run `pnpm josh pkg:scout <keywords>`: `clear` → use
 
 ## Code Change Rules
 
-0. **Work summary + test declaration** — before writing any implementation code, once per Issue: Now / Change / Check, then every change with its test (`prompts/collaboration-workflow/report-format.md` → "作業前サマリはいつ・どう出すか"). **Tests are required for ALL changes** — zero tests without explicit approval is a violation; a runtime change with no test is refused at `pnpm josh git -y` on `required` (`pnpm josh test:declared`).
+0. **Work summary + test declaration** — before writing any implementation code, once per Issue: Now / Change / Check, then every change with its test (`prompts/collaboration-workflow/report-format.md` → "作業前サマリはいつ・どう出すか"). **Tests are required for ALL changes** — zero tests without explicit approval is a violation.
 1. **Refactor first** — `prompts/refactoring.md`; no high/medium refactoring left on new/modified code.
 2. **Tests** — those declared in Step 0 (`prompts/testing-guide.md`).
-3. **Verification gate** — `pnpm josh gate`; while implementing re-run one check (`pnpm josh lint:related` / `pnpm josh cspell:dot` / `pnpm josh test:related`). Add legitimate flagged terms to `cspell.config.yaml`.
+3. **Verification gate** — `pnpm josh gate`, never piped: `| tail` reports a red gate as green, and its last lines carry the verdict (`prompts/collaboration-workflow/output-bounds.md`); while implementing re-run one check (`pnpm josh lint:related` / `pnpm josh cspell:dot` / `pnpm josh test:related`). Add legitimate flagged terms to `cspell.config.yaml`.
 4. **IDE feedback** — zero errors on changed files; never say "it should pass" without running it. Do not modify `eslint.config.js` unless asked.
 
 ## Completion gate (before you tell the user work is done)
@@ -61,10 +57,7 @@ Before every `git commit`, a subagent runs `/code-review` per `prompts/review.md
 
 ## Git Rules
 
-- **No commits** unless explicitly requested. **No merges, branch deletions, force pushes or other shared-state mutations** unless requested in the current turn — except invoking `fullrun` or `backlogrun` authorizes the merge via `pnpm josh followup`; `prrun` does not. `.claude/settings.json` denies these, but the deny is narrower than the rule — never read "the tool let me" as permission.
-- **Never stage or mutate the git index on your own** — only on explicit instruction or via `pnpm josh git`. `prompts/collaboration-workflow/operating-rules.md` → "no-self-staging".
-- **Use `pnpm josh git`; open a PR with `pnpm josh pr`** — `pnpm josh rule:guard` refuses a direct `gh pr create`. GitHub operations are `gh api` (REST) — `prompts/collaboration-workflow/gh-rest.md`.
-- **Run `git status` (and `git stash list`) live** before acting on any tree assumption.
+Commits, the index and shared state (merge, branch delete, force push) only on explicit instruction, through `pnpm josh git` / `pnpm josh pr`; run `git status` live before any tree assumption: `prompts/collaboration-workflow/operating-rules.md` → "git-rules".
 
 ## Collaboration Workflow
 
@@ -80,8 +73,4 @@ Never start a `kickoff` / `halfrun` / `prrun` / `fullrun` / `backlogrun` workflo
 
 #### Mid-workflow stop notification (`confirmation`)
 
-The `Stop` hook sends it when your held run awaits a decision — lead with the reason, end with `Recommended: <choice>`. Send it yourself only when the hook refuses the stop:
-
-```bash
-pnpm josh notify --task-type confirmation --issue-url "<url>" --body=$'<reason>' --recommended "<choice>" --alternative "<other>"
-```
+The `Stop` hook sends it; send it yourself only when the hook refuses the stop: `prompts/collaboration-workflow/rule-delivery.md` → "stop-notify". A lane child stopping for a person → `pnpm josh run:park`, no notify: `backlogrun-park.md` → "park and continue".

package/README.md

@@ -1,8 +1,10 @@
 # @joshuafolkken/kit
 
-**AI assistant setup, plus an optional GitHub workflow.**
+The hand-off kit for Claude Code and Codex.
 
-kit gives Claude Code or Codex your project's rules and checks.
+**Hand it off. Walk away. Come back to done.**
+
+Not "almost done" — tested, checked, finished.
 
 ## The workflow
 

package/SECURITY.md

@@ -25,7 +25,7 @@ The `files` field of `package.json` decides what the published `@joshuafolkken/k
 **Code that runs on your machine and in CI**
 
 - `dist/`, `scripts/` — the `josh` command and the scripts behind it. They read and write files in your repository, run `git`, `gh` and `pnpm`, and call the GitHub API and, when configured, the Telegram API.
-- `.claude/settings.json` — Claude Code hooks that run `pnpm josh …` commands on session start, on each prompt, before and after tool calls and on stop, plus a deny list for staging, committing, merging, force pushes, branch deletions and reads of `.env`, `.env.*` (except the tracked `.env.example` and `.env.test`) and `.dev.vars`. It sets `permissions.defaultMode` to `bypassPermissions`, as the distributed `.vscode/settings.json` does for the VS Code extension — an opt-out default, which Claude Code v2.1.257 and later ignore in a project settings file, described in [`docs/init.md` → "Claude Code permission mode"](https://github.com/joshuafolkken/kit/blob/main/docs/init.md#claude-code-permission-mode). `josh sync` overwrites it.
+- `.claude/settings.json` — Claude Code hooks that run `pnpm josh …` commands on session start, on each prompt, before and after tool calls and on stop, plus a deny list for staging, committing, merging, force pushes, branch deletions and reads of `.env`, `.env.*` (except the tracked `.env.example` and `.env.test`) and `.dev.vars`. The deny list and the `pretool-guard` hook are a guardrail, not a sandbox: another spelling of the same action (a git command inside `bash -c '…'`, a script that opens the file itself) gets through, and an instruction planted in text the agent reads can run with your permissions; the section linked below describes these limits and what keeps them small. It allows `Bash(*)` and ships no `permissions.defaultMode`, which Claude Code v2.1.257 and later ignore in a project settings file; the distributed `.vscode/settings.json` turns the VS Code extension's prompts off — an opt-out default, described in [`docs/init.md` → "Claude Code permission mode"](https://github.com/joshuafolkken/kit/blob/main/docs/init.md#claude-code-permission-mode).
 - `.codex/` — the same hooks for Codex (`hooks.json`) and its project settings (`config.toml`).
 - `.github/` — GitHub Actions workflows (CI, tagging, pull request classification, Dependabot auto-merge, SonarQube and production), composite actions, `dependabot.yml`, the pull request template and the release-notes config. `josh sync` overwrites the distributed workflows; their action references are pinned to commit SHAs. kit's own `publish.yml` ships in the package but is never copied into a project.
 - `lefthook/` — Git hook presets: lint before commit, checks before push.
@@ -36,7 +36,7 @@ The `files` field of `package.json` decides what the published `@joshuafolkken/k
 
 - `CLAUDE.md`, `AGENTS.md`, `GEMINI.md`, `.cursorrules`, `prompts/` — the rules and procedures AI agents follow.
 - `.claude/skills/`, `.claude/.claude-plugin/`, `.claude-plugin/` — the Claude Code skills, shipped as the `kit` plugin and its marketplace entry.
-- `.claude/agents/` — the Claude Code subagent definitions (the `investigator`), shipped beside the skills. It is granted no `Edit` / `Write` tool, but it is granted `Bash`, so its read-only scope is an instruction in its prompt rather than a tool restriction — a dispatched unit can run any shell command the parent session's permissions allow.
+- `.claude/agents/` — the Claude Code subagent definitions (the `investigator` and the `reviewer`), shipped beside the skills. The `investigator` is granted no `Edit` / `Write` tool, but it is granted `Bash`, so its read-only scope is an instruction in its prompt rather than a tool restriction — a dispatched unit can run any shell command the parent session's permissions allow. The `reviewer` is granted `Edit`, `Write` and `Bash` so a review can apply its fixes, and no `Agent` / `Skill` tool, so it cannot launch another agent.
 - `.mcp.json` — the MCP server configuration for the Svelte documentation server. It contains only the public endpoint `https://mcp.svelte.dev/mcp`.
 - `.coderabbit.yaml` — CodeRabbit review settings.
 
@@ -44,7 +44,7 @@ The `files` field of `package.json` decides what the published `@joshuafolkken/k
 
 - `eslint/`, `prettier/`, `tsconfig/`, `cspell/`, `env/`, `ports/`, `playwright.config.ts`, `tsconfig.sonar.json` — shared configuration your project imports or receives.
 - `templates/` — the templates `josh init` and `josh sync` write from.
-- `.vscode/`, `.gitattributes`, `.ncurc.json`, `.prettierignore`, `pnpm-workspace.yaml` — editor, Git and package-manager settings.
+- `.vscode/`, `.gitattributes`, `.prettierignore`, `pnpm-workspace.yaml` — editor, Git and package-manager settings.
 - `CODE_OF_CONDUCT.md`, `SECURITY.md` — community files.
 
 ## Installing safe-chain

package/dist/CLAUDE.md

@@ -1,9 +1,5 @@
 # Claude Code Instructions
 
-## Project
-
-Stack: TypeScript · pnpm · SvelteKit · Vitest · Playwright · TailwindCSS · Drizzle · better-auth · Paraglide · MCP
-
 ## Communication
 
 - **Answer opinion-seeking questions from a neutral standpoint.** A leading question is not a cue to agree — recommend the option you genuinely judge best.
@@ -11,14 +7,14 @@ Stack: TypeScript · pnpm · SvelteKit · Vitest · Playwright · TailwindCSS ·
 - **Cross-package problems → file the upstream Issue, then stop.** A defect in another package (a dependency, or `josh` / kit tooling) is never worked around locally — **weakening a verification gate is a workaround too**. File it (first-party Tier A, third-party Tier C) and stop. `node_modules/@joshuafolkken/kit/prompts/collaboration-workflow/upstream-interrupt.md`. Your own repository's run tooling is not another package: `upstream-interrupt.md` → "実行中のリポジトリ自身のラン機構の不具合".
 - **Third-party repositories are Tier C.** Decide the party with `pnpm josh repo:party`; every write to a tracker we do not own needs explicit current-turn instruction. `node_modules/@joshuafolkken/kit/prompts/collaboration-workflow/upstream-interrupt.md`.
 - **No clones — single-source, even across package boundaries.** Duplicate non-trivial logic only after presenting the alternative and getting explicit approval. `node_modules/@joshuafolkken/kit/prompts/collaboration-workflow/principles.md` → "no-clones".
-- **Design for elegance and simplicity first.** Before adding a hook, guard, rule or abstraction, ask whether fixing the cause makes it unnecessary. `node_modules/@joshuafolkken/kit/prompts/collaboration-workflow/principles.md` → "elegant-design"; conflicting quality goals → "quality-priority".
+- **Design for elegance and simplicity first.** Before adding a hook, guard, rule or abstraction, ask whether fixing the cause makes it unnecessary. `node_modules/@joshuafolkken/kit/prompts/collaboration-workflow/principles.md` → "elegant-design"; conflicting quality goals, or a remedy for defects → "quality-priority".
 - **Write concise prose: conditions and actions only.** `node_modules/@joshuafolkken/kit/prompts/collaboration-workflow/principles.md` → "concise-prose".
 - **Distinguish consultation from execution.** A question or goal statement asks for analysis only — act on an explicit imperative or a workflow keyword. `node_modules/@joshuafolkken/kit/prompts/collaboration-workflow/principles.md` → "consult-vs-execute".
 - **Route distributed-doc / config changes upstream to kit.** In a consumer repo never edit kit-distributed docs/config; in kit you are the source. `node_modules/@joshuafolkken/kit/prompts/collaboration-workflow/principles.md` → "upstream-to-kit".
 - **Latest-first, fix forward — pin back only as a last resort.** `node_modules/@joshuafolkken/kit/prompts/collaboration-workflow/principles.md` → "latest-first".
 - **Output language follows `JOSH_SESSION_LANG`** (default `ja`) for session output and artifact prose; English for Issue/PR titles, code comments, test titles, commit messages and script strings. `node_modules/@joshuafolkken/kit/prompts/collaboration-workflow/overview.md`.
 - **Durable rules belong in prompts/docs, not local MEMORY.** `node_modules/@joshuafolkken/kit/prompts/collaboration-workflow/principles.md` → "durable-rules".
-- **Hook-delivered rules** (file edits, shell bodies, turn batching, Issue citation, …): `node_modules/@joshuafolkken/kit/prompts/collaboration-workflow/rule-delivery.md` → "配送されている規則".
+- **Hook-delivered rules** (file edits, shell bodies, turn batching, …): `node_modules/@joshuafolkken/kit/prompts/collaboration-workflow/rule-delivery.md` → "配送されている規則".
 
 ### Decision autonomy
 
@@ -32,7 +28,7 @@ Log auto-decisions: an Issue comment in an Issue workflow, else a one-line "Auto
 
 ## Critical Conventions (non-standard — always apply)
 
-Naming, exports, file names and content rules are enforced by `node_modules/@joshuafolkken/kit/eslint/rules/`; their single source is `node_modules/@joshuafolkken/kit/prompts/coding-standards.md` → "Conventions". `function` syntax, not arrows (named SvelteKit route handlers may use typed-const arrows); lint does not check it.
+Naming, exports, file names and content rules are enforced by `node_modules/@joshuafolkken/kit/eslint/rules/`; their single source is `node_modules/@joshuafolkken/kit/prompts/coding-standards.md` → "Conventions". `function` syntax, not arrows (named SvelteKit route handlers may use typed-const arrows), `func-style`.
 
 ### Quality limits
 
@@ -45,10 +41,10 @@ Before building a feature, run `pnpm josh pkg:scout <keywords>`: `clear` → use
 
 ## Code Change Rules
 
-0. **Work summary + test declaration** — before writing any implementation code, once per Issue: Now / Change / Check, then every change with its test (`node_modules/@joshuafolkken/kit/prompts/collaboration-workflow/report-format.md` → "作業前サマリはいつ・どう出すか"). **Tests are required for ALL changes** — zero tests without explicit approval is a violation; a runtime change with no test is refused at `pnpm josh git -y` on `required` (`pnpm josh test:declared`).
+0. **Work summary + test declaration** — before writing any implementation code, once per Issue: Now / Change / Check, then every change with its test (`node_modules/@joshuafolkken/kit/prompts/collaboration-workflow/report-format.md` → "作業前サマリはいつ・どう出すか"). **Tests are required for ALL changes** — zero tests without explicit approval is a violation.
 1. **Refactor first** — `node_modules/@joshuafolkken/kit/prompts/refactoring.md`; no high/medium refactoring left on new/modified code.
 2. **Tests** — those declared in Step 0 (`node_modules/@joshuafolkken/kit/prompts/testing-guide.md`).
-3. **Verification gate** — `pnpm josh gate`; while implementing re-run one check (`pnpm josh lint:related` / `pnpm josh cspell:dot` / `pnpm josh test:related`). Add legitimate flagged terms to `cspell.config.yaml`.
+3. **Verification gate** — `pnpm josh gate`, never piped: `| tail` reports a red gate as green, and its last lines carry the verdict (`node_modules/@joshuafolkken/kit/prompts/collaboration-workflow/output-bounds.md`); while implementing re-run one check (`pnpm josh lint:related` / `pnpm josh cspell:dot` / `pnpm josh test:related`). Add legitimate flagged terms to `cspell.config.yaml`.
 4. **IDE feedback** — zero errors on changed files; never say "it should pass" without running it. Do not modify `eslint.config.js` unless asked.
 
 ## Completion gate (before you tell the user work is done)
@@ -61,10 +57,7 @@ Before every `git commit`, a subagent runs `/code-review` per `node_modules/@jos
 
 ## Git Rules
 
-- **No commits** unless explicitly requested. **No merges, branch deletions, force pushes or other shared-state mutations** unless requested in the current turn — except invoking `fullrun` or `backlogrun` authorizes the merge via `pnpm josh followup`; `prrun` does not. `.claude/settings.json` denies these, but the deny is narrower than the rule — never read "the tool let me" as permission.
-- **Never stage or mutate the git index on your own** — only on explicit instruction or via `pnpm josh git`. `node_modules/@joshuafolkken/kit/prompts/collaboration-workflow/operating-rules.md` → "no-self-staging".
-- **Use `pnpm josh git`; open a PR with `pnpm josh pr`** — `pnpm josh rule:guard` refuses a direct `gh pr create`. GitHub operations are `gh api` (REST) — `node_modules/@joshuafolkken/kit/prompts/collaboration-workflow/gh-rest.md`.
-- **Run `git status` (and `git stash list`) live** before acting on any tree assumption.
+Commits, the index and shared state (merge, branch delete, force push) only on explicit instruction, through `pnpm josh git` / `pnpm josh pr`; run `git status` live before any tree assumption: `node_modules/@joshuafolkken/kit/prompts/collaboration-workflow/operating-rules.md` → "git-rules".
 
 ## Collaboration Workflow
 
@@ -80,8 +73,4 @@ Never start a `kickoff` / `halfrun` / `prrun` / `fullrun` / `backlogrun` workflo
 
 #### Mid-workflow stop notification (`confirmation`)
 
-The `Stop` hook sends it when your held run awaits a decision — lead with the reason, end with `Recommended: <choice>`. Send it yourself only when the hook refuses the stop:
-
-```bash
-pnpm josh notify --task-type confirmation --issue-url "<url>" --body=$'<reason>' --recommended "<choice>" --alternative "<other>"
-```
+The `Stop` hook sends it; send it yourself only when the hook refuses the stop: `node_modules/@joshuafolkken/kit/prompts/collaboration-workflow/rule-delivery.md` → "stop-notify". A lane child stopping for a person → `pnpm josh run:park`, no notify: `backlogrun-park.md` → "park and continue".