@joshuafolkken/kit 1.887.0 → 1.929.0

package/.claude/skills/workflow-commands/backlogrun-progress.md

@@ -213,7 +213,7 @@ single non-numeric line as the verdict.
    `lane:await` watches local process presence and exits when any named child confirms-complete,
    waking the parent at the actual completion rather than at the next heartbeat interval. **The
    re-confirm delay and poll interval are the command's, not the agent's** — pass only the issue
-   numbers.
+   numbers. Without that wake (Codex), hand off instead — "A parent without a completion callback".
 
    **A `lane:await` wake is a confirmed-gone process, so classify the ending at once — do not wait out
    the silent-unit window** (joshuafolkken/kit#2277). `lane:await` exits only after the child's process
@@ -375,6 +375,11 @@ the check could not answer, and take `over`'s branch at that child.
 only moment where **this** child's work is all written down: the PR is merged, the working tree is clean
 on the default branch, and the epic's state on GitHub is complete.
 
+### A parent without a completion callback hands off at its first dispatch
+
+**A finished command never re-invokes a Codex parent, so after a dispatch `run:step` prints the `--cut`
+below the cut cap, `wait` at it** (joshuafolkken/kit#2653): dispatch the wave, run it, end the turn.
+
 ### The lane child reuses this measurement mid-implementation
 
 **The same `pnpm josh cost --over` measurement bounds a lane child's context _during_ implementation, not
@@ -534,20 +539,16 @@ to untangle**: `epic:next` detects it and exits with an error.
 ### The parent keeps no clock of its own — the watcher's exit is the wake
 
 **After hand-off, the supervisor's driver owns the mechanical clock.** `backlog:drive` polls lane
-completion and the backlog inside the detached process, without waking an AI parent. The historical
-parent-turn instructions below apply only while an AI session is handling a returned judgment branch;
-they do not schedule the supervisor's normal loop. `run:progress --wait` remains the source of human
-heartbeat lines, and `run:report` remains the final report source.
+completion and the backlog inside the detached process, without waking an AI parent; the parent-turn
+instructions below apply only to a returned judgment branch. `run:progress --wait` stays the heartbeat
+source and `run:report` the final report.
 
-**The numbers above are floors between asks, not a timer the parent sets.** A parent that sets one spends
-a turn per tick at the point its context is largest — the exact cost `run:progress` was built to remove.
-The watcher took the *reporting* out of the parent; the parent must not go on keeping the clock anyway,
-or the two run side by side and the run pays for both.
+**The numbers above are floors between asks, not a timer the parent sets** — one tick per turn, at the
+largest context, is the cost `run:progress` removed.
 
 The driver checks lane completion every five seconds and makes a new backlog offer no sooner than one
-minute after the previous offer, except after collecting a child. These waits cost no AI turns.
-The progress watcher keeps reporting on its own interval; a judgment session may still receive its
-exit as a prompt to act. The bounds above continue to apply to both processes.
+minute after the previous offer, except after collecting a child — waits that cost no AI turns. The
+watcher reports on its own interval, and a judgment session may take its exit as a prompt to act.
 
 #### The wake exists only while something is in flight
 

package/.claude/skills/workflow-commands/backlogrun-steps.md

@@ -535,7 +535,8 @@ ordinary way.
 **So every cut is taken at a merge, which is what lets a resumed session state its own `--active`**: a
 woken session picks the run up seconds after the merge the cut was taken at. The one shape that puts a
 cut inside a watch — the backlog answering `exhausted` while this run's own children are still
-merging — is the same, because the woken session has just merged a child.
+merging — is the same, because the woken session has just merged a child. A Codex parent's cut is the one
+taken at a dispatch instead (`backlogrun-progress.md` → "A parent without a completion callback").
 
 **The 8-hour whole-run bound is untouched and still outranks all of this** — it is measured from the
 record's `started_at` across every cut, so a run cannot watch its way past it in 30-minute pieces.

package/.claude/skills/workflow-commands/fullrun-steps.md

@@ -7,6 +7,8 @@ the run is at, and the sections below carry that step in full.
 
 ## The `fullrun #N` step list
 
+Use `pnpm josh issue:lint` `labels:`; see `prompts/collaboration-workflow/issue-template.md`.
+
 **Add `in-progress` the moment `run:hold` answered `hold`** (create if missing:
 `gh api repos/{owner}/{repo}/labels -f name=in-progress -f color=0075ca -f description="Work is
 actively in progress" --silent 2>/dev/null || true`, then `gh api
@@ -49,8 +51,8 @@ completion notification, then merges; if blockers are found it exits non-zero
 `kickoff new` + `fullrun #N` in one run. Steps: (1) Derive an English title, or use the provided one.
 **(1a) Run `pnpm josh issue:scout "<title>" [--body "<summary>"]` before creating the Issue** — a
 candidate that covers the same work stops the run rather than filing a second Issue (`SKILL.md` → §2e).
-(2) Create Issue: `gh api repos/{owner}/{repo}/issues -f title="<title>" -f 'labels[]=depth:<n>' -f
-body="<body>"` (body per `prompts/collaboration-workflow/issue-template.md`). Capture `<N>`. (3) Add
+(2) Create Issue: `gh api repos/{owner}/{repo}/issues -f title="<title>" -f 'labels[]=depth:<n>' -F
+body=@<body-file>` (per `prompts/collaboration-workflow/issue-template.md`). Capture `<N>`. (3) Add
 `in-progress` (as above). (4) Post the agreed plan in the session language: fill the body if blank,
 otherwise add a comment. (5) If the working tree already has staged or modified files,
 `git stash push -m "fullrun new: pre-existing changes"` first. (6) `git switch main && git pull`. (7)

package/.claude/skills/workflow-commands/halfrun.md

@@ -1,5 +1,7 @@
 # `halfrun` — the manifest (implement + verify, stop before commit)
 
+When this run files a new Issue, run `pnpm josh issue:lint <body-file>` and apply every label in its `labels:` answer at creation; `prompts/collaboration-workflow/issue-template.md` is the single source for this classification. Keep the existing `depth` and `route` labels.
+
 `halfrun` sits between `kickoff` (plan only) and `fullrun` (full execution with auto-merge). It
 implements the change and runs the full verification gate, then **stops before commit** — nothing is
 committed, pushed, or opened as a PR — so the user manually verifies the change (typically by exercising
@@ -52,7 +54,7 @@ back with fixes, treat each as a new round: implement, re-run `pnpm josh gate`,
 `halfrun new` or `halfrun new "<title>"`: `kickoff new` + `halfrun #<N>` (no Issue exists yet). Steps
 mirror `fullrun new` (1)–(8): derive an English title (or use the provided one) → **run `pnpm josh
 issue:scout "<title>" [--body "<summary>"]` before creating the Issue** (`SKILL.md` → §2e) → create the
-Issue (`gh api repos/{owner}/{repo}/issues -f title="<title>" -f 'labels[]=depth:<n>' -f body="<body>"`,
+Issue (`gh api repos/{owner}/{repo}/issues -f title="<title>" -f 'labels[]=depth:<n>' -F body=@<body-file>`,
 body per `prompts/collaboration-workflow/issue-template.md`) → add `in-progress` → post the agreed plan → stash
 any pre-existing changes with `git stash push -m "halfrun new: pre-existing changes"`, popped by
 message with `pnpm josh stash:pop "halfrun new: pre-existing changes"`, never a positional `git stash pop` →

package/.claude/skills/workflow-commands/kickoff.md

@@ -47,13 +47,13 @@ split is found.
   title. **(1a) Run `pnpm josh issue:scout "<title>" [--body "<summary>"]` before creating the Issue** —
   a candidate that covers the same work stops the run rather than filing a second Issue (`SKILL.md` →
   §2e). (2) Create Issue: `gh api repos/{owner}/{repo}/issues -f title="<title>" -f 'labels[]=depth:<n>'
-  -f body="<body>"` (body per `prompts/collaboration-workflow/issue-template.md`). Capture `<N>`. (3)
+  -F body=@<body-file>` (body per `prompts/collaboration-workflow/issue-template.md`). Capture `<N>`. (3)
   Post the plan in the session language, using the same body/comment logic as `kickoff #<N>`. (4) Send
   Telegram notification. (5) **Stop** — do not implement. **Multi-issue split path**: (1) For each
   independent deliverable, derive a focused English title, **run `pnpm josh issue:scout "<sub-title>"`
   on it** (`SKILL.md` → §2e), and create a separate Issue with the `route:split` label: `gh api
   repos/{owner}/{repo}/issues -f title="<sub-title>" -f 'labels[]=route:split' -f 'labels[]=depth:<n>'
-  -f body="<body>"`. Capture each Issue number. **When the split is filed into a repository other than
+  -F body=@<body-file>`. Capture each Issue number. **When the split is filed into a repository other than
   the one this session is running in**, every child body gets the `## Origin` backlink described in the
   cross-package rule the AI documents keep resident, the epic body carries the same link as prose or a
   plain bullet (never as a checkbox row, which would disable its auto-close), and the originating Issue
@@ -66,7 +66,7 @@ split is found.
   josh epic:check <E>`. Only where `josh` is unavailable, fall back to the manual procedure: ensure the
   label exists (`gh api repos/{owner}/{repo}/labels -f name=epic -f color=5319e7 -f description="Tracks
   a batch of child issues from one split" --silent 2>/dev/null || true`), then create the epic with `gh
-  api repos/{owner}/{repo}/issues -f title="<epic-title>" -f 'labels[]=epic' -f body="<body>"`. Its body
+  api repos/{owner}/{repo}/issues -f title="<epic-title>" -f 'labels[]=epic' -F body=@<body-file>`. Its body
   follows the epic format in `prompts/collaboration-workflow/issue-template.md` — split rationale,
   dependencies, the `backlogrun` command, and a child task list in task-list syntax (`- [ ] #N`). The epic
   exists as the **non-closing home for the split rationale**. When the children have no required order,
@@ -80,3 +80,5 @@ split is found.
   **database id**, not its issue number; a failure here is non-fatal). Never fold the relation into the
   creation call. (3) Send Telegram notification listing all created issues. (4) Present the command
   `backlogrun #<E> --only`. (5) **Stop** — do not implement.
+
+Before filing, run `pnpm josh issue:lint <body-file>` and apply every label in its `labels:` answer at creation, following `prompts/collaboration-workflow/issue-template.md` for classification.

package/.claude/skills/workflow-commands/observation-filing.md

@@ -29,6 +29,8 @@ backlog pool (`backlogrun-steps.md` → "What one invocation approves").
 
 The detail below is read at the filing decision, and the marker suite pins the rules here.
 
+Before filing an observation, run `pnpm josh issue:lint <body-file>` and apply every label in its `labels:` answer at creation; `prompts/collaboration-workflow/issue-template.md` is the single source. Keep the depth label.
+
 ### The depth test — a discretionary filing cites the product work it blocked
 
 **A run that has just spent an hour inside the workflow tooling files findings about the workflow
@@ -55,7 +57,7 @@ cap's branch-2 filing all pass through a `gh api … issues` call, and the depth
 beside whatever `route:` label that call already carries.
 
 ```bash
-gh api repos/{owner}/{repo}/issues -f title="<title>" -f 'labels[]=depth:1' -f body="<body>"
+gh api repos/{owner}/{repo}/issues -f title="<title>" -f 'labels[]=depth:1' -F body=@<body-file>
 gh api repos/{owner}/{repo}/issues/<N>/labels -f 'labels[]=depth:1'   # an Issue already filed
 ```
 

package/.claude/skills/workflow-commands/prerequisite.md

@@ -25,8 +25,10 @@ stays countable by filing route afterwards. **This paragraph belongs to the prer
 the table** — the label means a filing the run is *blocked by*, so the observation row carries no
 `route:` label of its own (§2i):
 
+Before that call, run `pnpm josh issue:lint <body-file>` and apply every label in its `labels:` answer at creation; `prompts/collaboration-workflow/issue-template.md` is the single source. Keep `route:tier-a` and `depth`.
+
 ```bash
-gh api repos/{owner}/{repo}/issues -f title="<title>" -f 'labels[]=route:tier-a' -f 'labels[]=depth:<n>' -f body="<body>"
+gh api repos/{owner}/{repo}/issues -f title="<title>" -f 'labels[]=route:tier-a' -f 'labels[]=depth:<n>' -F body=@<body-file>
 ```
 
 Every "file the prerequisite" below means that labelled filing, and it always happens **first**: the

package/.claude/skills/workflow-commands/target-repository.md

@@ -41,7 +41,7 @@ backlogrun joshuafolkken/kit#858 --only
   never clone. The one exception is the split path's epic, since `pnpm josh epic` only writes the
   repository it runs in — run it in that repository's checkout, or fall back to `gh api
   repos/<owner/repo>/labels …` followed by `gh api repos/<owner/repo>/issues -f title="<epic-title>" -f
-  'labels[]=epic' -f body="<body>"`, and report that `epic:check` could not be run. The promote arm has
+  'labels[]=epic' -F body=@<body-file>`, and report that `epic:check` could not be run. The promote arm has
   no such fallback: with no checkout there, file the children and stop.
 - **The implementing entries require a checkout and never create one — when the target is another
   repository.** A prefix naming the session's own repository changes nothing (`fullrun kit#412` in the

package/.github/pull_request_template.md

@@ -1 +1,13 @@
 closes #
+
+## Release classification
+
+Add exactly one label before merging:
+
+- `breaking-change` — any incompatible change, even when it also adds a feature or fixes a bug
+- `enhancement` — a compatible new feature or improvement
+- `bugfix` — a compatible fix
+- `other-change` — documentation, dependencies, or maintenance included in Other Changes
+- `ignore-for-release` — omit this pull request from the changelog
+
+Automated pull requests without a classification label are treated as Other Changes. If an automated pull request needs another classification or exclusion, add that one label.

package/.github/release.yml

@@ -13,6 +13,9 @@ changelog:
       labels:
         - Semver-Minor
         - enhancement
+    - title: Bug Fixes 🐛
+      labels:
+        - bugfix
     - title: Other Changes
       labels:
         - '*'

package/.github/workflows/ci.yml

@@ -6,6 +6,7 @@ on:
 
   pull_request:
     branches: [main]
+    types: [opened, synchronize, reopened, labeled, unlabeled]
 
 # A push run is grouped by the commit it carries, so a later push to main never cancels an earlier
 # one. Without the sha every push to main shares one group — `github.ref` is `refs/heads/main` for
@@ -351,6 +352,10 @@ jobs:
       - name: Run verification gate
         run: pnpm josh gate --verbose --no-unit
 
+      - name: Check release classification
+        if: github.event_name == 'pull_request'
+        run: pnpm josh pr:classification
+
   # The other half of the gate, on a runner of its own. It carries the same setup steps as
   # `static-checks` rather than sharing them: a GitHub job is its own machine, so every job that
   # needs Node sets Node up, and this workflow already writes that preamble once per job. The
@@ -425,6 +430,9 @@ jobs:
       - name: Run unit tests
         run: pnpm josh test:unit
 
+      - name: Verify optional ESLint consumer install
+        run: pnpm exec tsx scripts/package/verify-optional-eslint-install.ts
+
   # **The required status check. `Checks` is a name the branch ruleset already requires, and this job
   # is what keeps that name meaning what it meant** (joshuafolkken/kit#1226) — every check the single
   # `Checks` job used to run has passed. It runs no checks itself; it reads the two halves' results.

package/.github/workflows/production.yml

@@ -2,9 +2,18 @@ name: Release to Production
 on:
   repository_dispatch:
     types: [new-tag-created]
+  workflow_call:
+    inputs:
+      tag:
+        required: true
+        type: string
 
 jobs:
   update-branch:
+    if: github.repository != 'joshuafolkken/kit' || inputs.tag != ''
+    concurrency:
+      group: production-update
+      queue: max
     runs-on: ubuntu-latest
     permissions:
       contents: write
@@ -24,7 +33,7 @@ jobs:
           # repository_dispatch always runs on the default branch, so the event ref
           # resolves to that branch, not the released tag. Use the tag carried in the
           # dispatch payload (set by auto-tag.yml) as the merge source instead.
-          REF_NAME: ${{ github.event.client_payload.tag }}
+          REF_NAME: ${{ inputs.tag || github.event.client_payload.tag }}
         run: |
           if [ -z "$REF_NAME" ]; then
             echo "::error::new-tag-created dispatch carried no tag payload; aborting." >&2

package/.github/workflows/publish.yml

@@ -1,4 +1,5 @@
 name: Publish
+run-name: Publish ${{ github.event.client_payload.tag }}
 
 on:
   repository_dispatch:
@@ -6,6 +7,9 @@ on:
 
 jobs:
   publish-github:
+    concurrency:
+      group: package-publish
+      queue: max
     runs-on: ubuntu-latest
     timeout-minutes: 10
     permissions:
@@ -36,11 +40,24 @@ jobs:
 
       - run: pnpm install --frozen-lockfile --ignore-scripts
 
-      - run: pnpm publish --no-git-checks --tag latest --registry https://npm.pkg.github.com
+      - name: Select GitHub Packages tag
+        id: publish-tag
+        run: |
+          version=$(node -p "require('./package.json').version")
+          latest=$(cd "$RUNNER_TEMP" && npm view @joshuafolkken/kit dist-tags.latest --registry https://npm.pkg.github.com)
+          tag=$(pnpm exec tsx scripts/release/publish-tag-cli.ts "$version" "$latest")
+          echo "tag=$tag" >> "$GITHUB_OUTPUT"
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      - run: pnpm publish --no-git-checks --tag ${{ steps.publish-tag.outputs.tag }} --registry https://npm.pkg.github.com
         env:
           NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
   publish-npm:
+    concurrency:
+      group: package-publish
+      queue: max
     runs-on: ubuntu-latest
     timeout-minutes: 10
     permissions:
@@ -72,5 +89,58 @@ jobs:
 
       - run: pnpm pack --out "$RUNNER_TEMP/kit.tgz"
 
+      - name: Select npm tag
+        id: publish-tag
+        run: |
+          version=$(node -p "require('./package.json').version")
+          latest=$(cd "$RUNNER_TEMP" && npm view @joshuafolkken/kit dist-tags.latest --registry https://registry.npmjs.org)
+          tag=$(pnpm exec tsx scripts/release/publish-tag-cli.ts "$version" "$latest")
+          echo "tag=$tag" >> "$GITHUB_OUTPUT"
+
       - name: Publish to npm
-        run: cd "$RUNNER_TEMP" && npm publish kit.tgz --access public --tag latest --registry https://registry.npmjs.org --userconfig /dev/null
+        run: cd "$RUNNER_TEMP" && npm publish kit.tgz --access public --tag ${{ steps.publish-tag.outputs.tag }} --registry https://registry.npmjs.org --userconfig /dev/null
+
+  update-production:
+    needs: [publish-github, publish-npm]
+    permissions:
+      contents: write
+    uses: ./.github/workflows/production.yml
+    with:
+      tag: ${{ github.event.client_payload.tag }}
+
+  create-release:
+    needs: [publish-github, publish-npm, update-production]
+    runs-on: ubuntu-latest
+    timeout-minutes: 65
+    permissions:
+      actions: read
+      contents: write
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          ref: ${{ github.event.client_payload.tag }}
+          fetch-depth: 0
+
+      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
+        with:
+          node-version: 24
+
+      - name: Resolve pnpm version
+        id: pnpm-version
+        run: |
+          version=$(node -p "const m = require('./package.json'); m.packageManager?.match(/^pnpm@([^+]+)/)?.[1] ?? (m.devEngines?.packageManager?.name === 'pnpm' ? m.devEngines.packageManager.version?.split('+')[0] : 'latest') ?? 'latest'")
+          test -n "$version"
+          echo "version=$version" >> "$GITHUB_OUTPUT"
+
+      - uses: pnpm/setup@fbda4c85fc2e1e08721cd8763afea8f48d60f024 # v3.0.0
+        with:
+          version: ${{ steps.pnpm-version.outputs.version }}
+          install: false
+
+      - run: pnpm install --frozen-lockfile --ignore-scripts
+
+      - name: Publish GitHub Release
+        run: pnpm exec tsx scripts/release/github-release-cli.ts
+        env:
+          GH_TOKEN: ${{ github.token }}
+          RELEASE_TAG: ${{ github.event.client_payload.tag }}

package/CLAUDE.md

@@ -108,6 +108,7 @@ For every code modification, in order:
 
    - **Tests are required for ALL code changes** (bug fixes, timing/animation fixes and refactors included): bug fix → regression test; UI/animation/timing → E2E for the observable change; logic/utility → unit; refactor → tests pinning existing behavior BEFORE the change (`prompts/refactoring.md`).
    - **Non-runtime updates (pre-approved manual-only exception)**: a change touching no executable runtime code path may proceed with manual verification — declare it in Step 0 and state why. It covers docs, non-executable config, editor/IDE files, and cosmetic asset swaps with no selector/path change; the mechanically exempt (`*.md`, `.editorconfig`, `.idea/**`, `.vscode/**`, `prompts/**`) are recognized by the command below, and the rest stay the exemption a person declares. A test infeasible for a runtime change needs its reason stated and user approval.
+   - **static の HTML/CSS 例外:** `package.json` に `josh.profile: static` が記録され、変更が HTML/CSS だけなら自動テストの代わりにブラウザーで表示を確認する。対象ページを開き、想定する画面幅でレイアウト・リンク・HTML 内の操作を確認し、観察結果を報告する。HTML/CSS と同時に変更した場合も、JavaScript と TypeScript のファイルには自動テストが必要。`pnpm josh test:declared` はこの場合だけ理由を添えて `exempt` と表示する。
    - **The commit stage answers this mechanically**: `pnpm josh test:declared` prints `required` / `exempt` / `satisfied` from the changed paths, and a runtime change with no test is refused at `pnpm josh git -y` on `required` — add the declared test or declare the non-runtime exception, then reissue (`prompts/collaboration-workflow/rule-delivery.md`).
    - **Read a target's line headroom before editing: `pnpm josh lines <path>`** — near the limit, `Target` carries the splitting plan.
 
@@ -121,6 +122,7 @@ For every code modification, in order:
 Run the full verification set **in order**; do not skip, reorder, or report completion on a failed or skipped step without the user agreeing. Inside a `fullrun` / `backlogrun` the gate runs beside the review and the merge chain (`workflow-commands` skill → §2, `prompts/review.md`).
 
 0. **Test gate** — no tests added? Continue only under the non-runtime exception (Step 0) or explicit approval; otherwise stop and add tests.
+   static プロファイルの HTML/CSS だけの変更には、Step 0 の手動ブラウザー確認を適用できる。
 1. **Refactor** — `prompts/refactoring.md`, until no high/medium items remain.
 2. **`pnpm josh gate`** — lint, type check, spell check and unit tests concurrently. One gate per run; while implementing re-run a single check by name (`pnpm josh lint:related` / `pnpm josh cspell:dot` / `pnpm josh test:related`).
 3. **Self-review** — a subagent runs `/code-review` per `prompts/review.md` (never a main-line `Skill` load); level from the changed paths, at most two rounds, high/medium findings resolved. `prompts/review.md` → "Review round cap".

package/README.md

@@ -7,7 +7,7 @@ Shared toolchain config and CLI for TypeScript projects — ESLint, Prettier, Ty
 
 ## Prerequisites
 
-- [Node.js](https://nodejs.org/) with [pnpm](https://pnpm.io/)
+- [Node.js](https://nodejs.org/) 22.19.0 or later with [pnpm](https://pnpm.io/) — [getting-started.md](./docs/getting-started.md) covers installing both
 - [gh CLI](https://cli.github.com/) for `josh version` and existing GitHub Packages consumers. It is not required to install kit from public npm; see [authentication.md](./docs/authentication.md) for setup when needed.
 
 ## Quick start
@@ -24,6 +24,7 @@ Using the kit inside a project? See [docs/package.md](./docs/package.md).
 | Guide                                           | What it covers                                                                   |
 | ----------------------------------------------- | -------------------------------------------------------------------------------- |
 | [why.md](./docs/why.md)                         | Why kit exists — the AI-development problems it solves, for practitioners        |
+| [getting-started.md](./docs/getting-started.md) | First install for an `index.html` site or a non-Node project, without Git        |
 | [authentication.md](./docs/authentication.md)   | GitHub Packages auth for existing projects                                       |
 | [cli.md](./docs/cli.md)                         | Install and use the global `josh` CLI                                            |
 | [package.md](./docs/package.md)                 | Use the kit as a project devDependency — configs, prompts, scripts, `josh init`  |

package/dist/CLAUDE.md

@@ -108,6 +108,7 @@ For every code modification, in order:
 
    - **Tests are required for ALL code changes** (bug fixes, timing/animation fixes and refactors included): bug fix → regression test; UI/animation/timing → E2E for the observable change; logic/utility → unit; refactor → tests pinning existing behavior BEFORE the change (`node_modules/@joshuafolkken/kit/prompts/refactoring.md`).
    - **Non-runtime updates (pre-approved manual-only exception)**: a change touching no executable runtime code path may proceed with manual verification — declare it in Step 0 and state why. It covers docs, non-executable config, editor/IDE files, and cosmetic asset swaps with no selector/path change; the mechanically exempt (`*.md`, `.editorconfig`, `.idea/**`, `.vscode/**`, `prompts/**`) are recognized by the command below, and the rest stay the exemption a person declares. A test infeasible for a runtime change needs its reason stated and user approval.
+   - **static の HTML/CSS 例外:** `package.json` に `josh.profile: static` が記録され、変更が HTML/CSS だけなら自動テストの代わりにブラウザーで表示を確認する。対象ページを開き、想定する画面幅でレイアウト・リンク・HTML 内の操作を確認し、観察結果を報告する。HTML/CSS と同時に変更した場合も、JavaScript と TypeScript のファイルには自動テストが必要。`pnpm josh test:declared` はこの場合だけ理由を添えて `exempt` と表示する。
    - **The commit stage answers this mechanically**: `pnpm josh test:declared` prints `required` / `exempt` / `satisfied` from the changed paths, and a runtime change with no test is refused at `pnpm josh git -y` on `required` — add the declared test or declare the non-runtime exception, then reissue (`node_modules/@joshuafolkken/kit/prompts/collaboration-workflow/rule-delivery.md`).
    - **Read a target's line headroom before editing: `pnpm josh lines <path>`** — near the limit, `Target` carries the splitting plan.
 
@@ -121,6 +122,7 @@ For every code modification, in order:
 Run the full verification set **in order**; do not skip, reorder, or report completion on a failed or skipped step without the user agreeing. Inside a `fullrun` / `backlogrun` the gate runs beside the review and the merge chain (`workflow-commands` skill → §2, `node_modules/@joshuafolkken/kit/prompts/review.md`).
 
 0. **Test gate** — no tests added? Continue only under the non-runtime exception (Step 0) or explicit approval; otherwise stop and add tests.
+   static プロファイルの HTML/CSS だけの変更には、Step 0 の手動ブラウザー確認を適用できる。
 1. **Refactor** — `node_modules/@joshuafolkken/kit/prompts/refactoring.md`, until no high/medium items remain.
 2. **`pnpm josh gate`** — lint, type check, spell check and unit tests concurrently. One gate per run; while implementing re-run a single check by name (`pnpm josh lint:related` / `pnpm josh cspell:dot` / `pnpm josh test:related`).
 3. **Self-review** — a subagent runs `/code-review` per `node_modules/@joshuafolkken/kit/prompts/review.md` (never a main-line `Skill` load); level from the changed paths, at most two rounds, high/medium findings resolved. `node_modules/@joshuafolkken/kit/prompts/review.md` → "Review round cap".

package/dist/CLAUDE.static.md

@@ -0,0 +1,8 @@
+# Project instructions
+
+- 既存のファイルと利用者の設定を尊重し、変更する前に内容を確認する。
+- 変更には検証を付け、実行した結果を報告する。
+- HTML、CSS、JavaScript のファイルがある場合は Prettier で整形する。
+- 画面に見える変更をした場合はブラウザーで表示と操作を確認する。
+- JavaScript または TypeScript の動作を変更した場合は、その動作を確認する自動テストを追加する。
+- Git や GitHub を使う場合だけ、それぞれのワークフローを利用する。

package/dist/hooks/batch-guard.js

@@ -9,12 +9,12 @@ import {
   load_environment_file,
   notice_refusal_path,
   refusal_path
-} from "./chunk-FRJKVSK3.js";
-import "./chunk-36UE53LS.js";
-import "./chunk-FNFOLFFV.js";
-import "./chunk-264QY6KS.js";
-import "./chunk-FXAKJKTB.js";
-import "./chunk-SSX23SJ2.js";
+} from "./chunk-ROULPSQC.js";
+import "./chunk-7XQ6TK3R.js";
+import "./chunk-SXPTRFPG.js";
+import "./chunk-2PGRQ62K.js";
+import "./chunk-WPALEIRX.js";
+import "./chunk-RKUAD3I6.js";
 export {
   DISABLED_VALUES,
   SWITCH_ENV_KEY,

package/dist/hooks/{chunk-264QY6KS.js → chunk-2PGRQ62K.js}

@@ -1,6 +1,6 @@
 import {
   ENV_FILE_NAME
-} from "./chunk-SSX23SJ2.js";
+} from "./chunk-RKUAD3I6.js";
 
 // scripts/lib/json-value.ts
 function parse_or_undefined(text) {
@@ -684,6 +684,12 @@ var FILTER_ARGUMENTS = "[filters...]";
 var MATCH_ARGUMENTS = "[--match]";
 var PATH_ARGUMENTS = "<path...>";
 var DEV_COMMANDS = {
+  "pr:classification": {
+    script: "scripts/ci/pr-classification.ts",
+    description: "Require one release classification on a pull request",
+    category: "Development",
+    reference: ["", "automation", ["none"]]
+  },
   [GATE_COMMAND]: {
     script: "scripts/gate/verification-gate.ts",
     description: "Run lint, type check, spell check and unit tests concurrently",
@@ -727,14 +733,7 @@ var DEV_COMMANDS = {
     reference: ["", "developer", ["none"]]
   },
   format: {
-    // prettier first here, unlike `format:edited`, and deliberately: `eslint --fix` exits 1
-    // whenever a non-autofixable error remains, so putting it first behind `&&` would mean one
-    // unused variable anywhere in the tree stops prettier from running at all.
-    shell: [
-      "sh",
-      "-c",
-      `pnpm exec prettier --write . && pnpm exec eslint . --fix ${ESLINT_CACHE_FLAGS.join(" ")}`
-    ],
+    script: "scripts/lint/format.ts",
     description: "Format code with prettier and eslint",
     category: "Development",
     reference: ["", "developer", ["files", "processes"]]
@@ -1003,12 +1002,25 @@ var MAINTENANCE_COMMANDS = {
 };
 
 // scripts/josh/josh-commands-project.ts
+var PROFILE_ARGUMENTS = "[--profile static|node]";
 var PROJECT_COMMANDS = {
+  profile: {
+    script: "scripts/init/project-profile-cli.ts",
+    description: "Show the project profile and the reason for it",
+    category: "Project",
+    reference: [PROFILE_ARGUMENTS, "developer", ["files"]]
+  },
+  start: {
+    script: "scripts/init/start.ts",
+    description: "Initialize a project for the GitHub Issue workflow",
+    category: "Project",
+    reference: [PROFILE_ARGUMENTS, "developer", ["files", "git", "network"]]
+  },
   init: {
     script: "scripts/init/init.ts",
     description: "Initialize config in a new project",
     category: "Project",
-    reference: ["", "developer", ["files", "processes"]]
+    reference: [PROFILE_ARGUMENTS, "developer", ["files", "processes"]]
   },
   sync: {
     script: "scripts/sync/sync.ts",
@@ -1242,11 +1254,14 @@ var ALIASES = {
   c: "check",
   pt: "port",
   i: "init",
+  pf: "profile",
+  st: "start",
   sy: "sync",
   rmi: "registry:migrate",
   sys: "sync:scope",
   g: "git",
   gp: "pr",
+  prc: "pr:classification",
   fu: "followup",
   nf: "notify",
   obf: "observations:flush",

package/dist/hooks/chunk-3V37IID6.js

@@ -0,0 +1,82 @@
+// scripts/build/local-bin.ts
+import { existsSync, readFileSync } from "node:fs";
+import { createRequire } from "node:module";
+import path from "node:path";
+
+// scripts/lib/schemas.ts
+import { z } from "zod";
+var overrides_snapshot_schema = z.record(z.string(), z.string());
+var package_version_schema = z.object({ version: z.string() });
+var package_named_version_schema = z.looseObject({ name: z.string(), version: z.string() });
+var package_with_version_schema = z.looseObject({ version: z.string() });
+var ls_global_dependency_schema = z.looseObject({ version: z.string() });
+var ls_global_dependencies_schema = z.record(z.string(), ls_global_dependency_schema).optional();
+var pnpm_ls_global_schema = z.array(
+  z.looseObject({
+    dependencies: ls_global_dependencies_schema
+  })
+);
+var vscode_settings_schema = z.record(z.string(), z.unknown());
+var with_scripts_schema = z.looseObject({
+  scripts: z.record(z.string(), z.string()).optional()
+});
+var with_development_deps_schema = z.looseObject({
+  devDependencies: z.record(z.string(), z.string()).optional()
+});
+var with_package_manager_schema = z.looseObject({
+  packageManager: z.string().optional()
+});
+var with_development_engine_schema = z.looseObject({
+  devEngines: z.record(z.string(), z.unknown()).optional()
+});
+var bin_entry_schema = z.union([z.string(), z.record(z.string(), z.string())]).optional();
+var package_bin_schema = z.looseObject({ bin: bin_entry_schema });
+var json_object_schema = z.record(z.string(), z.unknown());
+var string_array_schema = z.array(z.string());
+var string_record_schema = z.record(z.string(), z.string());
+
+// scripts/build/local-bin.ts
+var NODE_MODULES = "node_modules";
+var BIN_DIR = ".bin";
+var WINDOWS_PLATFORM = "win32";
+var WINDOWS_SHIM_SUFFIX = ".cmd";
+var PACKAGE_JSON = "package.json";
+function resolve_local_bin(project_root, bin_name) {
+  const shim = process.platform === WINDOWS_PLATFORM ? `${bin_name}${WINDOWS_SHIM_SUFFIX}` : bin_name;
+  return path.join(project_root, NODE_MODULES, BIN_DIR, shim);
+}
+function ancestor_directories(start_directory) {
+  const directories = [];
+  let current = start_directory;
+  while (!directories.includes(current)) {
+    directories.push(current);
+    current = path.dirname(current);
+  }
+  return directories;
+}
+function find_local_bin_upwards(start_directory, bin_name) {
+  return ancestor_directories(start_directory).map((directory) => resolve_local_bin(directory, bin_name)).find((candidate) => existsSync(candidate));
+}
+function read_bin_entry(manifest_path, package_name, bin_name) {
+  const { bin } = package_bin_schema.parse(JSON.parse(readFileSync(manifest_path, "utf8")));
+  if (typeof bin === "string") return bin_name === path.basename(package_name) ? bin : void 0;
+  return bin?.[bin_name];
+}
+function resolve_package_bin(base_directory, package_name, bin_name) {
+  try {
+    const resolve_from = createRequire(path.join(base_directory, PACKAGE_JSON));
+    const manifest_path = resolve_from.resolve(`${package_name}/${PACKAGE_JSON}`);
+    const bin_entry = read_bin_entry(manifest_path, package_name, bin_name);
+    if (bin_entry === void 0) return void 0;
+    const cli_entry = path.join(path.dirname(manifest_path), bin_entry);
+    return existsSync(cli_entry) ? cli_entry : void 0;
+  } catch {
+    return void 0;
+  }
+}
+
+export {
+  resolve_local_bin,
+  find_local_bin_upwards,
+  resolve_package_bin
+};

package/dist/hooks/{chunk-36UE53LS.js → chunk-7XQ6TK3R.js}

@@ -1,13 +1,13 @@
 import {
   lane_child_marker
-} from "./chunk-FNFOLFFV.js";
+} from "./chunk-SXPTRFPG.js";
 import {
   time_bundle_call,
   time_format,
   time_round_trips,
   time_spans,
   time_transcript_line
-} from "./chunk-264QY6KS.js";
+} from "./chunk-2PGRQ62K.js";
 
 // scripts/lane/lane-guard-policy.ts
 var DEFAULT_MODE = "refuse";