@joshuafolkken/kit 1.957.0 → 1.978.0

package/.github/workflows/pr-classification.yml

@@ -15,6 +15,13 @@ on:
 # nothing here needs it: every run reads the pull request's labels as they stand when it runs, not as
 # its event carried them, so whichever suite GitHub counts as newest holds a current verdict.
 
+# The same safe-chain installer pin as ci.yml — the release and its install-safe-chain.sh SHA-256.
+# `pnpm dlx … setup-ci` left only shims, so the install below ran without a scan (joshuafolkken/kit#2765).
+# `josh latest` moves both together, in this file and in ci.yml.
+env:
+  SAFE_CHAIN_INSTALLER_VERSION: 1.5.20
+  SAFE_CHAIN_INSTALLER_SHA256: 0ad25efe15d1fa56105157a454d647223e78eb0c53d1f85e3d10afcd722e7bfd
+
 jobs:
   classification:
     name: Release classification
@@ -63,7 +70,11 @@ jobs:
             ${{ runner.os }}-pnpm-store-
 
       - name: Setup safe-chain
-        run: pnpm dlx @aikidosec/safe-chain@1.5.20 setup-ci
+        run: |
+          installer="$RUNNER_TEMP/install-safe-chain.sh"
+          curl --proto '=https' -fsSL "https://github.com/AikidoSec/safe-chain/releases/download/$SAFE_CHAIN_INSTALLER_VERSION/install-safe-chain.sh" -o "$installer"
+          echo "$SAFE_CHAIN_INSTALLER_SHA256  $installer" | sha256sum -c -
+          sh "$installer" --ci
 
       - name: Install dependencies
         env:

package/CLAUDE.md

@@ -89,7 +89,7 @@ Read from a `.env` file at the project root by the AI scripts, `josh port` and `
 
 ### Dependency overrides (`pnpm-workspace.yaml` / `package.json`)
 
-- **Effective overrides live in `pnpm-workspace.yaml`.** pnpm 11 and 12 ignore `pnpm.overrides` in `package.json` (verified with pnpm 12.6.0). Check both files for existing declarations, but never count the ignored package field as an effective override. **An absent or empty `pnpm.overrides` is not evidence that the project has no overrides.**
+- **Effective overrides live in `pnpm-workspace.yaml`.** pnpm 11 and 12 ignore `pnpm.overrides` in `package.json`. Check both files for existing declarations, but never count the ignored package field as an effective override. **An absent or empty `pnpm.overrides` is not evidence that the project has no overrides.**
 - **NEVER** remove or modify entries in **either** location without explicit user approval.
 - **NEVER** modify the `devEngines` field in `package.json` without explicit user confirmation. It pins the development toolchain (e.g. pnpm version); silently changing it can break CI or other contributors' environments.
 - **The check is a command you run, not a conclusion you reach.** After `pnpm update`, `josh latest`, or any dependency-update command, **load the `dependency-update` skill** and follow its procedure before reporting anything about the pins.
@@ -144,7 +144,7 @@ Before every `git commit` (follow-up commits included), self-review against `pro
 
 ## Doc Sync Rules
 
-**`CLAUDE.md` is the single source for every agent rule.** `AGENTS.md` and `GEMINI.md` carry no rules — a rule addition, spec change or wording fix is written **once**, here (joshuafolkken/kit#963). The structural test [scripts/document/ai-document-pointers.test.ts](https://github.com/joshuafolkken/kit/blob/main/scripts/document/ai-document-pointers.test.ts) fails if a rule body reappears in either, or if a pointer loses the sentence that sends an agent here.
+**`CLAUDE.md` is the single source for every agent rule.** `AGENTS.md` and `GEMINI.md` carry no rules — a rule addition, spec change or wording fix is written **once**, here (joshuafolkken/kit#963).
 
 **docs/ must stay in sync with the package.** When `josh bump` changes the version, review `docs/` and update any section describing changed behavior (new/renamed commands, `josh init` / `josh sync` behavior, new config files) before committing.
 
@@ -166,7 +166,7 @@ Before every `git commit` (follow-up commits included), self-review against `pro
 
 `kickoff`, `fullrun`, `halfrun` and `backlogrun` are the Issue-driven shorthand commands. **Their procedures are not resident** — they live in the `workflow-commands` skill. **What stays here is decided by one question: must the rule fire on a turn where no skill was loaded?** Explicit invocation, the mid-workflow stop notification, the `overrides` / `devEngines` prohibitions, the UI-verification gate and the three `epic:*` rules below all do; everything a run reaches only after reading the skill is routed to, never restated (`SKILL.md` → "What stays resident, and what is read from here").
 
-**Read the skill before running any part of a command — including the first `gh` call.** Acting from the table below alone is not enough: the table says which command was typed, not how to run it.
+**Read the skill before running any part of a command — including the first `gh` call.**
 
 | Typed keyword            | What it does                                                                                                                                                          | Read first                                                       |
 | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- |

package/README.md

@@ -1,10 +1,10 @@
 # @joshuafolkken/kit
 
-A development toolkit that sets up a repository for AI-assisted work with one command. `josh init` gives an AI assistant (Claude Code, Codex, Gemini, Cursor) the project's rules, and the `josh` CLI runs the checks and the Git / GitHub Issue workflow the same way in every project. You stop copying config between repositories and re-explaining conventions to the assistant. For the problems kit exists to solve, see [why.md](./docs/why.md) (Japanese).
+A development toolkit for AI-assisted work. `josh init` gives an AI assistant (Claude Code, Codex, Gemini, Cursor) the project's rules, formatting and checks in one command. With `kickoff`, `fullrun` and `backlogrun`, the agent then takes a GitHub Issue through plan → implement → verify → PR → merge, the same way in every project. Why kit exists: [why.md](./docs/why.md) (Japanese).
 
 ## What your project gets
 
-kit does not branch by language. It asks one question — does the project use Node tooling? — and picks a [profile](./docs/init.md#project-profiles):
+kit picks a [profile](./docs/init.md#project-profiles) from one question — does the project use Node tooling?
 
 | Your project                             | Profile  | What you get                                                      |
 | ---------------------------------------- | -------- | ----------------------------------------------------------------- |
@@ -12,54 +12,58 @@ kit does not branch by language. It asks one question — does the project use N
 | HTML / CSS (browser JavaScript included) | `static` | Formatting (Prettier), AI assistant files, Git / VS Code settings |
 | Another language (Python, Rust, Go, …)   | `static` | AI assistant files and Git / VS Code settings only                |
 
-kit adds no linter or test runner for languages other than JavaScript and TypeScript; in a `static` project, `josh` skips each check that has nothing to run and says why.
+In a `static` project, `josh` skips each check that has nothing to run and says why.
 
 ## Quick start
 
-In your project directory:
+Requires [Node.js](https://nodejs.org/) 22.19.0+ and [pnpm](https://pnpm.io/) for every profile ([getting-started.md](./docs/getting-started.md)); the [gh CLI](https://cli.github.com/) for `josh version` and the Issue workflow is required by `josh start` and optional otherwise. Run in your project directory.
+
+### The project is already on GitHub, or will not use GitHub
 
 ```bash
-pnpm add -D --allow-build=esbuild @joshuafolkken/kit
-pnpm exec josh init
-pnpm install
-pnpm josh format
+pnpm --allow-build=esbuild dlx @joshuafolkken/kit init
 pnpm josh gate
 ```
 
-`josh init` is the entry without GitHub. To start a new project on the GitHub Issue workflow (`kickoff`), run `pnpm exec josh start` instead of `josh init` — it also creates the Git repository, the GitHub repository and the labels ([init.md → `josh init` or `josh start`](./docs/init.md#josh-init-or-josh-start)).
+### The project has no GitHub repository yet, and will use the Issue workflow
+
+```bash
+pnpm add -D --allow-build=esbuild --allow-build=unrs-resolver @joshuafolkken/kit
+pnpm exec josh start
+```
 
-It needs [Node.js](https://nodejs.org/) 22.19.0 or later with [pnpm](https://pnpm.io/), even for a `static` project; [getting-started.md](./docs/getting-started.md) installs both. The global `josh` command ([cli.md](./docs/cli.md)) and the [gh CLI](https://cli.github.com/) for `josh version` and the GitHub Issue workflow are optional.
+`josh start` also runs `git init` when needed and creates and pushes the GitHub repository. Details: [init.md → `josh init` or `josh start`](./docs/init.md#josh-init-or-josh-start).
 
 ## Documentation
 
 **Get started**
 
-- [getting-started.md](./docs/getting-started.md) — first install for an `index.html` site or a non-Node project (`static`)
-- [package.md](./docs/package.md) — add kit to a Node project (`node`)
+- [getting-started.md](./docs/getting-started.md) — first install for a `static` project
+- [package.md](./docs/package.md) — add kit to a Node project
 - [tutorial.md](./docs/tutorial.md) — your first change with an agent, from Issue to merge
-- [how-to.md](./docs/how-to.md) — step-by-step guides by task: update, release, run Issues, fix a failing gate
+- [how-to.md](./docs/how-to.md) — guides by task
 - [overview.md](./docs/overview.md) — what kit sets up and how it works
 
 **Commands and configuration**
 
-- [cli.md](./docs/cli.md) — install the global `josh` command
+- [cli.md](./docs/cli.md) — the global `josh` command
 - [josh-commands.md](./docs/josh-commands.md) — every `josh` command ([catalog](./docs/josh-command-catalog.md))
-- [init.md](./docs/init.md) — what `josh init` creates, per profile
-- [sync.md](./docs/sync.md) — what `josh sync` updates after an upgrade
-- [manual-config.md](./docs/manual-config.md) — use the presets without `josh init`
-- [package-api.md](./docs/package-api.md) — the config presets and libraries the package exports
+- [init.md](./docs/init.md) — what `josh init` creates
+- [sync.md](./docs/sync.md) — what `josh sync` updates
+- [manual-config.md](./docs/manual-config.md) — the presets without `josh init`
+- [package-api.md](./docs/package-api.md) — the package's exports
 
 **AI workflow and operations**
 
-- [scripts-ai.md](./docs/scripts-ai.md) — Telegram notifications and the Issue workflow commands
+- [scripts-ai.md](./docs/scripts-ai.md) — Issue workflow commands and Telegram notifications
 - [cloud-session.md](./docs/cloud-session.md) — running in an agent container
-- [eval.md](./docs/eval.md) — measuring whether the agent rules are followed
+- [eval.md](./docs/eval.md) — measuring rule adherence
 - [troubleshooting.md](./docs/troubleshooting.md) — install and auth errors
 - [authentication.md](./docs/authentication.md) — existing GitHub Packages installs only
 
 ## Contributing
 
-Community standards live in [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md); security reports go through [SECURITY.md](./SECURITY.md). Development conventions are in [CLAUDE.md](./CLAUDE.md); releases are in [publishing.md](./docs/publishing.md), and maintainer records in [docs/maintainers/](./docs/maintainers/).
+Conventions are in [CLAUDE.md](./CLAUDE.md), releases in [publishing.md](./docs/publishing.md). See [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md) and [SECURITY.md](./SECURITY.md); maintainer records are in [docs/maintainers/](./docs/maintainers/).
 
 ## License
 

package/dist/CLAUDE.md

@@ -89,7 +89,7 @@ Read from a `.env` file at the project root by the AI scripts, `josh port` and `
 
 ### Dependency overrides (`pnpm-workspace.yaml` / `package.json`)
 
-- **Effective overrides live in `pnpm-workspace.yaml`.** pnpm 11 and 12 ignore `pnpm.overrides` in `package.json` (verified with pnpm 12.6.0). Check both files for existing declarations, but never count the ignored package field as an effective override. **An absent or empty `pnpm.overrides` is not evidence that the project has no overrides.**
+- **Effective overrides live in `pnpm-workspace.yaml`.** pnpm 11 and 12 ignore `pnpm.overrides` in `package.json`. Check both files for existing declarations, but never count the ignored package field as an effective override. **An absent or empty `pnpm.overrides` is not evidence that the project has no overrides.**
 - **NEVER** remove or modify entries in **either** location without explicit user approval.
 - **NEVER** modify the `devEngines` field in `package.json` without explicit user confirmation. It pins the development toolchain (e.g. pnpm version); silently changing it can break CI or other contributors' environments.
 - **The check is a command you run, not a conclusion you reach.** After `pnpm update`, `josh latest`, or any dependency-update command, **load the `dependency-update` skill** and follow its procedure before reporting anything about the pins.
@@ -144,7 +144,7 @@ Before every `git commit` (follow-up commits included), self-review against `nod
 
 ## Doc Sync Rules
 
-**`CLAUDE.md` is the single source for every agent rule.** `AGENTS.md` and `GEMINI.md` carry no rules — a rule addition, spec change or wording fix is written **once**, here (joshuafolkken/kit#963). The structural test [scripts/document/ai-document-pointers.test.ts](https://github.com/joshuafolkken/kit/blob/main/scripts/document/ai-document-pointers.test.ts) fails if a rule body reappears in either, or if a pointer loses the sentence that sends an agent here.
+**`CLAUDE.md` is the single source for every agent rule.** `AGENTS.md` and `GEMINI.md` carry no rules — a rule addition, spec change or wording fix is written **once**, here (joshuafolkken/kit#963).
 
 **docs/ must stay in sync with the package.** When `josh bump` changes the version, review `https://github.com/joshuafolkken/kit/tree/main/docs/` and update any section describing changed behavior (new/renamed commands, `josh init` / `josh sync` behavior, new config files) before committing.
 
@@ -166,7 +166,7 @@ Before every `git commit` (follow-up commits included), self-review against `nod
 
 `kickoff`, `fullrun`, `halfrun` and `backlogrun` are the Issue-driven shorthand commands. **Their procedures are not resident** — they live in the `workflow-commands` skill. **What stays here is decided by one question: must the rule fire on a turn where no skill was loaded?** Explicit invocation, the mid-workflow stop notification, the `overrides` / `devEngines` prohibitions, the UI-verification gate and the three `epic:*` rules below all do; everything a run reaches only after reading the skill is routed to, never restated (`SKILL.md` → "What stays resident, and what is read from here").
 
-**Read the skill before running any part of a command — including the first `gh` call.** Acting from the table below alone is not enough: the table says which command was typed, not how to run it.
+**Read the skill before running any part of a command — including the first `gh` call.**
 
 | Typed keyword            | What it does                                                                                                                                                          | Read first                                                       |
 | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- |

package/dist/hooks/batch-guard.js

@@ -9,10 +9,10 @@ import {
   load_environment_file,
   notice_refusal_path,
   refusal_path
-} from "./chunk-244WYOEO.js";
-import "./chunk-XSL4SRMA.js";
-import "./chunk-LDQDZYHX.js";
-import "./chunk-BELI5XSS.js";
+} from "./chunk-NXL3SBXY.js";
+import "./chunk-2K52BRWV.js";
+import "./chunk-KQG4776P.js";
+import "./chunk-ZPLXLJ7O.js";
 import "./chunk-WPALEIRX.js";
 import "./chunk-RKUAD3I6.js";
 export {

package/dist/hooks/{chunk-XSL4SRMA.js → chunk-2K52BRWV.js}

@@ -1,13 +1,13 @@
 import {
   lane_child_marker
-} from "./chunk-LDQDZYHX.js";
+} from "./chunk-KQG4776P.js";
 import {
   time_bundle_call,
   time_format,
   time_round_trips,
   time_spans,
   time_transcript_line
-} from "./chunk-BELI5XSS.js";
+} from "./chunk-ZPLXLJ7O.js";
 
 // scripts/lane/lane-guard-policy.ts
 var DEFAULT_MODE = "refuse";

package/dist/hooks/{chunk-M6K7EQDO.js → chunk-BNGGEY3Z.js}

@@ -1,6 +1,7 @@
 import {
   ALREADY_DONE_LABEL,
   BREAKING_CHANGE_LABEL,
+  BUGFIX_LABEL,
   BUG_LABEL,
   CONTEXT_CUT_THRESHOLD,
   ENHANCEMENT_LABEL,
@@ -9,6 +10,7 @@ import {
   NEEDS_DECISION_LABEL,
   NEEDS_HUMAN_REVIEW_LABEL,
   RECENT_REQUEST_WINDOW,
+  RELEASE_CLASSIFICATION_NAMES,
   agent_role_profile,
   agent_session_environment,
   bash_triggers,
@@ -35,31 +37,31 @@ import {
   run_watcher_guard,
   shell_segments,
   tail_commands
-} from "./chunk-IJPBTDTB.js";
+} from "./chunk-Q7LE77CO.js";
 import {
   find_local_bin_upwards
 } from "./chunk-3V37IID6.js";
 import {
   batch_outcome
-} from "./chunk-244WYOEO.js";
+} from "./chunk-NXL3SBXY.js";
 import {
   investigation_refusal
-} from "./chunk-KOCK5FXQ.js";
+} from "./chunk-BVMSPG3M.js";
 import {
   duplicate_read_outcome
-} from "./chunk-GNOITLRR.js";
+} from "./chunk-ZYYSBNR6.js";
 import {
   investigation_reads
-} from "./chunk-HJXQZ7V4.js";
+} from "./chunk-F6OM6SIG.js";
 import {
   lane_guard_policy,
   time_batch_guard
-} from "./chunk-XSL4SRMA.js";
+} from "./chunk-2K52BRWV.js";
 import {
   hook_decision,
   lane_child_marker,
   run_issue_number
-} from "./chunk-LDQDZYHX.js";
+} from "./chunk-KQG4776P.js";
 import {
   PLATFORM_TEMP_ROOT,
   cost_attribute,
@@ -71,7 +73,7 @@ import {
   stamp_file,
   time_density_hook,
   time_shell
-} from "./chunk-BELI5XSS.js";
+} from "./chunk-ZPLXLJ7O.js";
 
 // scripts/hooks/pretool-guard.ts
 import { text } from "node:stream/consumers";
@@ -1016,24 +1018,37 @@ function current_state() {
     directory: process.cwd(),
     source: process.env,
     carried: run_cut.carried_cut_sync,
+    held_issue: run_cut.held_issue_sync,
     // **Read through the short reuse window** (joshuafolkken/kit#2385). The row now fires per
     // threshold crossing rather than once per run, so this predicate is a candidate on every edit;
     // the window collapses one turn's burst of edits to a single whole-transcript price.
     verdict: () => implementation_cut_verdict.reused_verdict(() => cost_cli.session_verdict())
   };
 }
-function uncut_lane_child_issue(state) {
+function lane_child_issue(state) {
   if (!lane_child_marker.is_child_of(state.directory, state.source)) return void 0;
-  const issue = lane_paths.lane_issue_of(state.directory, { ...state.source });
+  return lane_paths.lane_issue_of(state.directory, { ...state.source });
+}
+function held_run_issue(state) {
+  if (lane_paths.lane_issue_of(state.directory, { ...state.source }) !== void 0) return void 0;
+  return state.held_issue();
+}
+function uncut_run_issue(state) {
+  const issue = lane_child_issue(state) ?? held_run_issue(state);
   if (issue === void 0) return void 0;
   return state.carried()?.issue === issue ? void 0 : issue;
 }
+function warrants_the_cut(state) {
+  const verdict = state.verdict();
+  if (lane_child_issue(state) === void 0) return verdict === cost_verdict.OVER_VERDICT;
+  return verdict !== cost_verdict.UNDER_VERDICT;
+}
 function is_over_threshold_edit(call, state = current_state()) {
-  if (!is_edit_tool(call.name) || uncut_lane_child_issue(state) === void 0) return false;
-  return state.verdict() !== cost_verdict.UNDER_VERDICT;
+  if (!is_edit_tool(call.name) || uncut_run_issue(state) === void 0) return false;
+  return warrants_the_cut(state);
 }
 var THRESHOLD_TEXT = `${cost_format.format_tokens(CONTEXT_CUT_THRESHOLD)}-token`;
-var IMPLEMENTATION_CUT_REASON = `\u26D4 implementation-phase cut: this checkout is a lane dispatched for this issue and its recent-context cost has crossed the shared ${THRESHOLD_TEXT} threshold mid-implementation, so the thinking accumulated so far is now re-read on every later request. Take the cut before this edit. First write a handoff file with the Write tool \u2014 the user\u2019s instruction verbatim, what you have completed, what remains, and what you deliberately did not touch \u2014 and pass it as \`--handoff <path>\`, so the fresh process resumes on the original instruction rather than the working tree alone (joshuafolkken/kit#2354); a resume that finds no instruction is refused \`incomplete\` rather than continuing blind. \`pnpm josh run:cut --impl <N> --handoff <path>\` ends this process and relaunches a fresh one that resumes back into implementation (\`resume-impl\`), dropping the accumulated context rather than carrying it \u2014 joshuafolkken/kit#1933 built the boundary and joshuafolkken/kit#2310 measured it firing 0 times because the verdict was only ever read at session entry, where the context has not yet grown. The verdict is \`pnpm josh cost --cut\`'s exactly \u2014 the same per-request billed-input statistic against the same threshold, never a second measurement. Issue \`pnpm josh run:cut --impl <N> --handoff <path>\` now and read the verdict: on \`cut\`, **end the turn immediately** \u2014 the fresh process owns the run and continues implementing, so it must not be waited for; on \`not-a-lane\`, \`unready\`, \`busy\`, \`failed\` or \`unknown\`, this process carries the run on and the edit is simply the next call. Never relaunch a second process after \`busy\`. This fired because the dispatch mark names this lane; a person working here carries no mark and sees no refusal, so there is no human-or-child judgement left to make. The procedure is \`.claude/skills/workflow-commands/pre-gate-cut.md\`. Reissue this edit once the cut has answered \u2014 an edit reissued right after this refusal passes, so \`busy\` / \`failed\` cannot wedge the run edit after edit; this fires again on the next threshold crossing rather than once per run.`;
+var IMPLEMENTATION_CUT_REASON = `\u26D4 implementation-phase cut: this checkout is a lane dispatched for this issue, or a run holds it for this issue (joshuafolkken/kit#2760), and its recent-context cost has crossed the shared ${THRESHOLD_TEXT} threshold mid-implementation, so the thinking accumulated so far is now re-read on every later request. Take the cut before this edit. First write a handoff file with the Write tool \u2014 the user\u2019s instruction verbatim, what you have completed, what remains, and what you deliberately did not touch \u2014 and pass it as \`--handoff <path>\`, so the fresh process resumes on the original instruction rather than the working tree alone (joshuafolkken/kit#2354); a resume that finds no instruction is refused \`incomplete\` rather than continuing blind. \`pnpm josh run:cut --impl <N> --handoff <path>\` ends this process and relaunches a fresh one that resumes back into implementation (\`resume-impl\`), dropping the accumulated context rather than carrying it \u2014 joshuafolkken/kit#1933 built the boundary and joshuafolkken/kit#2310 measured it firing 0 times because the verdict was only ever read at session entry, where the context has not yet grown. The verdict is \`pnpm josh cost --cut\`'s exactly \u2014 the same per-request billed-input statistic against the same threshold, never a second measurement. Issue \`pnpm josh run:cut --impl <N> --handoff <path>\` now and read the verdict: on \`cut\`, **end the turn immediately** \u2014 in a lane the fresh process owns the run and continues implementing, so it must not be waited for; outside a lane nothing is relaunched, so first send the \`confirmation\` Telegram naming the resume command \`fullrun #<N>\` and keep the hold; on \`not-a-lane\`, \`unready\`, \`busy\`, \`failed\` or \`unknown\`, this process carries the run on and the edit is simply the next call. Never relaunch a second process after \`busy\`. This fired because the dispatch mark names this lane or the run hold names this issue; a person working here carries no mark and holds no run, so sees no refusal, so there is no human-or-child judgement left to make. The procedure is \`.claude/skills/workflow-commands/pre-gate-cut.md\`. Reissue this edit once the cut has answered \u2014 an edit reissued right after this refusal passes, so \`busy\` / \`failed\` cannot wedge the run edit after edit; this fires again on the next threshold crossing rather than once per run.`;
 var REISSUE_WINDOW_MS = 9e4;
 function is_reissued_refusal(now_ms, delivered_at_ms) {
   return now_ms - delivered_at_ms < REISSUE_WINDOW_MS;
@@ -1057,7 +1072,7 @@ var implementation_cut = {
   is_over_threshold_edit,
   is_reissued_refusal,
   takes_the_impl_cut,
-  uncut_lane_child_issue
+  uncut_run_issue
 };
 
 // scripts/rules/issue-bug-label.ts
@@ -1951,12 +1966,12 @@ function uncut_lane_issue(state) {
   if (state.marked_issue !== issue) return void 0;
   return state.carried()?.issue === issue ? void 0 : issue;
 }
-function warrants_the_cut(verdict) {
+function warrants_the_cut2(verdict) {
   return verdict !== cost_verdict.UNDER_VERDICT;
 }
 function is_uncut_gate(command, state = current_state2()) {
   if (!runs_the_gate(command) || uncut_lane_issue(state) === void 0) return false;
-  return warrants_the_cut(state.context_verdict());
+  return warrants_the_cut2(state.context_verdict());
 }
 var PRE_GATE_CUT_REASON = "\u26D4 pre-gate cut: this checkout is a lane dispatched for this issue and the gate is the boundary to cut at, so take the cut before running it. `pnpm josh run:cut <N>` ends this process and relaunches a fresh one that resumes from the gate, dropping the thinking built up while implementing rather than carrying it on every later request \u2014 joshuafolkken/kit#1839 measured 176K of 204K output riding across that boundary, and joshuafolkken/kit#1864 measured the step itself firing 0 times in 6 lane children while it was carried as prose. Issue `pnpm josh run:cut <N>` now, and read the verdict: on `cut`, **end the turn immediately** \u2014 the fresh process owns the run from there and must not be waited for; on `not-a-lane`, `unready`, `busy`, `failed` or `unknown`, this process carries the run on and the gate is simply the next call. Never relaunch a second process after `busy`. This fired because the dispatch mark names this lane; a person working here carries no mark and sees no refusal, so there is no human-or-child judgement left to make. The procedure is `.claude/skills/workflow-commands/pre-gate-cut.md`. Reissue the gate once the cut has answered \u2014 this fires once per run, so it cannot repeat on the call in hand.";
 function reaches_the_pre_gate_boundary(call, _turn, run2) {
@@ -3577,16 +3592,7 @@ import { readFileSync as readFileSync6 } from "node:fs";
 import { fileURLToPath as fileURLToPath2 } from "node:url";
 import { execaSync } from "execa";
 import { z as z8 } from "zod";
-var BUGFIX = "bugfix";
-var BREAKING = "breaking-change";
-var CLASSIFICATION_LABELS2 = [
-  BREAKING,
-  "enhancement",
-  BUGFIX,
-  "other-change",
-  "ignore-for-release"
-];
-var CLASSIFICATION_SET = new Set(CLASSIFICATION_LABELS2);
+var CLASSIFICATION_SET = new Set(RELEASE_CLASSIFICATION_NAMES);
 var ISSUE_BUG_LABEL = "bug";
 var DECLARATION = /^- リリース分類: (.+)$/gmu;
 var LEGACY_LABELS = /* @__PURE__ */ new Set(["semver-major", "semver-minor"]);
@@ -3605,14 +3611,14 @@ function classification_error(labels, author) {
     return `Choose exactly one release classification; found: ${selected.join(", ")}`;
   }
   if (selected.length === 1 || author.endsWith("[bot]")) return void 0;
-  return `Choose one release classification: ${CLASSIFICATION_LABELS2.join(", ")}`;
+  return `Choose one release classification: ${RELEASE_CLASSIFICATION_NAMES.join(", ")}`;
 }
 function is_classification(value) {
   return CLASSIFICATION_SET.has(value);
 }
 function release_candidates(candidates) {
-  if (!candidates.includes(BREAKING)) return candidates;
-  return candidates.filter((candidate) => candidate !== "enhancement");
+  if (!candidates.includes(BREAKING_CHANGE_LABEL)) return candidates;
+  return candidates.filter((candidate) => candidate !== ENHANCEMENT_LABEL);
 }
 function issue_candidates(issue_json) {
   const issue = z8.object({ labels: z8.array(LABEL), body: z8.string().nullable() }).parse(JSON.parse(issue_json));
@@ -3621,8 +3627,8 @@ function issue_candidates(issue_json) {
   const candidates = [...release_candidates([...names, ...declared].filter(is_classification))];
   const unknown = declared.filter((value) => !is_classification(value));
   if (unknown.length > 0) throw new Error(`Unknown release classification: ${unknown.join(", ")}`);
-  if (names.includes(ISSUE_BUG_LABEL) && !candidates.includes(BREAKING)) {
-    candidates.push(BUGFIX);
+  if (names.includes(ISSUE_BUG_LABEL) && !candidates.includes(BREAKING_CHANGE_LABEL)) {
+    candidates.push(BUGFIX_LABEL);
   }
   return candidates;
 }
@@ -3632,7 +3638,7 @@ function select_issue_classification(issue_json) {
   const [label] = selected;
   if (label === void 0 || selected.length > 1) {
     throw new Error(
-      `Choose one release classification before opening the PR: ${CLASSIFICATION_LABELS2.join(", ")}; found: ${selected.join(", ") || "none"}. Add "- \u30EA\u30EA\u30FC\u30B9\u5206\u985E: <label>" to the Issue body.`
+      `Choose one release classification before opening the PR: ${RELEASE_CLASSIFICATION_NAMES.join(", ")}; found: ${selected.join(", ") || "none"}. Add "- \u30EA\u30EA\u30FC\u30B9\u5206\u985E: <label>" to the Issue body.`
     );
   }
   return label;

package/dist/hooks/{chunk-KOCK5FXQ.js → chunk-BVMSPG3M.js}

@@ -1,12 +1,12 @@
 import {
   investigation_reads
-} from "./chunk-HJXQZ7V4.js";
+} from "./chunk-F6OM6SIG.js";
 import {
   lane_guard_policy
-} from "./chunk-XSL4SRMA.js";
+} from "./chunk-2K52BRWV.js";
 import {
   hook_decision
-} from "./chunk-LDQDZYHX.js";
+} from "./chunk-KQG4776P.js";
 
 // scripts/delegation/investigation-guard.ts
 import { text } from "node:stream/consumers";

package/dist/hooks/{chunk-3ON7HOYB.js → chunk-CRGJTD6E.js}

@@ -5,7 +5,7 @@ import {
 import {
   ESLINT_EDIT_CACHE_FLAGS,
   time_density_hook
-} from "./chunk-BELI5XSS.js";
+} from "./chunk-ZPLXLJ7O.js";
 
 // scripts/hooks/format-edited-file.ts
 import { existsSync as existsSync2 } from "node:fs";

package/dist/hooks/{chunk-HJXQZ7V4.js → chunk-F6OM6SIG.js}

@@ -1,16 +1,16 @@
 import {
   time_batch_guard
-} from "./chunk-XSL4SRMA.js";
+} from "./chunk-2K52BRWV.js";
 import {
   hook_decision
-} from "./chunk-LDQDZYHX.js";
+} from "./chunk-KQG4776P.js";
 import {
   cost_blocks,
   cost_transcript,
   time_bundle_call,
   time_shell,
   time_spans
-} from "./chunk-BELI5XSS.js";
+} from "./chunk-ZPLXLJ7O.js";
 
 // scripts/delegation/investigation-reads.ts
 import path from "node:path";

package/dist/hooks/{chunk-LDQDZYHX.js → chunk-KQG4776P.js}

@@ -3,7 +3,7 @@ import {
   stamp_file,
   time_density_hook,
   time_hook_transcript
-} from "./chunk-BELI5XSS.js";
+} from "./chunk-ZPLXLJ7O.js";
 import {
   josh_environment_file
 } from "./chunk-WPALEIRX.js";

package/dist/hooks/{chunk-244WYOEO.js → chunk-NXL3SBXY.js}

@@ -1,10 +1,10 @@
 import {
   lane_guard_policy,
   time_batch_guard
-} from "./chunk-XSL4SRMA.js";
+} from "./chunk-2K52BRWV.js";
 import {
   hook_decision
-} from "./chunk-LDQDZYHX.js";
+} from "./chunk-KQG4776P.js";
 
 // scripts/hooks/batch-guard.ts
 import { text } from "node:stream/consumers";