@cbartens/bkit 5.2.4 → 5.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (271) hide show
  1. package/.bkit/README.md +27 -11
  2. package/.bkit/core/.agents/context.md +1 -1
  3. package/.bkit/core/.agents/docs.md +1 -1
  4. package/.bkit/core/.agents/plugins/bkit/hooks/bkit-guardrails.cjs +1 -1
  5. package/.bkit/core/.agents/rules.md +18 -1
  6. package/.bkit/core/.bkit/README.md +26 -10
  7. package/.bkit/core/.bkit/cloud.md +40 -39
  8. package/.bkit/core/.bkit/comparison.md +68 -345
  9. package/.bkit/core/.bkit/install.md +16 -9
  10. package/.bkit/core/.bkit/lite.md +73 -0
  11. package/.bkit/core/.bkit/pipeline.md +346 -0
  12. package/.bkit/core/.bkit/prompts.md +90 -74
  13. package/.bkit/core/.bkit/providers.md +42 -23
  14. package/.bkit/core/.bkit/templates.md +138 -19
  15. package/.bkit/core/.bkit/trackers.md +49 -4
  16. package/.bkit/core/.bkit/workflows.md +144 -123
  17. package/.bkit/core/.claude/hooks/bkit-guardrails.cjs +1 -1
  18. package/.bkit/core/.codex/hooks/bkit-guardrails.cjs +7 -4
  19. package/.bkit/core/.cursor/hooks/bkit-guardrails.cjs +8 -5
  20. package/.bkit/core/docs/templates/bkit-audit-accessibility.md +3 -2
  21. package/.bkit/core/docs/templates/bkit-audit-adoption.md +2 -2
  22. package/.bkit/core/docs/templates/bkit-audit-agents.md +1 -1
  23. package/.bkit/core/docs/templates/bkit-audit-aio-seo.md +1 -1
  24. package/.bkit/core/docs/templates/bkit-audit-analytics.md +1 -1
  25. package/.bkit/core/docs/templates/bkit-audit-annotations.md +1 -1
  26. package/.bkit/core/docs/templates/bkit-audit-app-performance.md +1 -1
  27. package/.bkit/core/docs/templates/bkit-audit-app-store.md +1 -1
  28. package/.bkit/core/docs/templates/bkit-audit-architecture.md +1 -1
  29. package/.bkit/core/docs/templates/bkit-audit-ci-performance.md +4 -2
  30. package/.bkit/core/docs/templates/bkit-audit-config.md +3 -2
  31. package/.bkit/core/docs/templates/bkit-audit-cost.md +3 -2
  32. package/.bkit/core/docs/templates/bkit-audit-coverage.md +1 -1
  33. package/.bkit/core/docs/templates/bkit-audit-database.md +3 -2
  34. package/.bkit/core/docs/templates/bkit-audit-dead-code.md +5 -5
  35. package/.bkit/core/docs/templates/bkit-audit-deferrals.md +1 -1
  36. package/.bkit/core/docs/templates/bkit-audit-dependencies.md +26 -21
  37. package/.bkit/core/docs/templates/bkit-audit-documentation.md +1 -1
  38. package/.bkit/core/docs/templates/bkit-audit-duplication.md +2 -2
  39. package/.bkit/core/docs/templates/bkit-audit-failures.md +1 -1
  40. package/.bkit/core/docs/templates/bkit-audit-flakes.md +3 -2
  41. package/.bkit/core/docs/templates/bkit-audit-gates.md +5 -2
  42. package/.bkit/core/docs/templates/bkit-audit-issues.md +3 -2
  43. package/.bkit/core/docs/templates/bkit-audit-llm.md +22 -15
  44. package/.bkit/core/docs/templates/bkit-audit-logs.md +10 -6
  45. package/.bkit/core/docs/templates/bkit-audit-models.md +1 -1
  46. package/.bkit/core/docs/templates/bkit-audit-privacy.md +1 -1
  47. package/.bkit/core/docs/templates/bkit-audit-prompts.md +7 -7
  48. package/.bkit/core/docs/templates/bkit-audit-red-team.md +12 -9
  49. package/.bkit/core/docs/templates/bkit-audit-reliability.md +3 -2
  50. package/.bkit/core/docs/templates/bkit-audit-repo.md +1 -1
  51. package/.bkit/core/docs/templates/bkit-audit-security.md +14 -12
  52. package/.bkit/core/docs/templates/bkit-audit-slop.md +1 -1
  53. package/.bkit/core/docs/templates/bkit-audit-testing.md +10 -8
  54. package/.bkit/core/docs/templates/bkit-audit-usability.md +1 -1
  55. package/.bkit/core/docs/templates/bkit-plan.md +8 -6
  56. package/.bkit/core/engine/checks/after/auth.ts +9 -9
  57. package/.bkit/core/engine/checks/after/ci-yml.ts +14 -12
  58. package/.bkit/core/engine/checks/after/github.ts +29 -120
  59. package/.bkit/core/engine/checks/after/index.ts +2 -2
  60. package/.bkit/core/engine/checks/after/managed.ts +8 -28
  61. package/.bkit/core/engine/checks/after/tools.ts +3 -15
  62. package/.bkit/core/engine/checks/before/context-fetch.ts +1 -21
  63. package/.bkit/core/engine/checks/before/index.ts +7 -43
  64. package/.bkit/core/engine/checks/before/mcp.ts +17 -8
  65. package/.bkit/core/engine/checks/before/repo.ts +9 -12
  66. package/.bkit/core/engine/checks/status-holes.ts +4 -6
  67. package/.bkit/core/engine/checks/tips/catalogue.ts +76 -24
  68. package/.bkit/core/engine/checks/tips/detect.ts +45 -2
  69. package/.bkit/core/engine/checks/tips/index.ts +77 -26
  70. package/.bkit/core/engine/cli.ts +57 -27
  71. package/.bkit/core/engine/commands/analysis.ts +36 -26
  72. package/.bkit/core/engine/commands/comply.ts +42 -32
  73. package/.bkit/core/engine/commands/harvest.ts +12 -12
  74. package/.bkit/core/engine/commands/install/doctor.ts +57 -28
  75. package/.bkit/core/engine/commands/install/install.ts +73 -130
  76. package/.bkit/core/engine/commands/install/uninstall.ts +191 -33
  77. package/.bkit/core/engine/commands/install/upgrade.ts +49 -43
  78. package/.bkit/core/engine/commands/land.ts +156 -0
  79. package/.bkit/core/engine/commands/lib.ts +45 -18
  80. package/.bkit/core/engine/commands/registry.ts +2 -0
  81. package/.bkit/core/engine/commands/tips.ts +12 -5
  82. package/.bkit/core/engine/commands/workflow/branches.ts +386 -286
  83. package/.bkit/core/engine/commands/workflow/counters.ts +21 -12
  84. package/.bkit/core/engine/commands/workflow/disk.ts +556 -0
  85. package/.bkit/core/engine/commands/workflow/fids.ts +46 -0
  86. package/.bkit/core/engine/commands/workflow/issues.ts +73 -28
  87. package/.bkit/core/engine/commands/workflow/ledgers.ts +3 -1
  88. package/.bkit/core/engine/commands/workflow/locks.ts +38 -152
  89. package/.bkit/core/engine/commands/workflow/prs.ts +15 -4
  90. package/.bkit/core/engine/commands/workflow/repo.ts +2 -2
  91. package/.bkit/core/engine/commands/workflow/roadmap.ts +49 -53
  92. package/.bkit/core/engine/commands/workflow/runs.ts +8 -7
  93. package/.bkit/core/engine/commands/workflow/runtime.ts +3 -2
  94. package/.bkit/core/engine/commands/workflow/status.ts +33 -11
  95. package/.bkit/core/engine/commands/workflow/steps.ts +25 -15
  96. package/.bkit/core/engine/commands/workflow/tests.ts +17 -5
  97. package/.bkit/core/engine/commands/workflow/workflows.ts +436 -267
  98. package/.bkit/core/engine/commands/workflow/workstreams.ts +4 -2
  99. package/.bkit/core/engine/commands/workflow/worktrees.ts +24 -6
  100. package/.bkit/core/engine/install/cloud-env.ts +10 -31
  101. package/.bkit/core/engine/install/manifest.ts +14 -7
  102. package/.bkit/core/engine/install/modules/antigravity.ts +15 -26
  103. package/.bkit/core/engine/install/modules/claude.ts +20 -28
  104. package/.bkit/core/engine/install/modules/cloud.ts +5 -2
  105. package/.bkit/core/engine/install/modules/codex.ts +15 -29
  106. package/.bkit/core/engine/install/modules/core.ts +106 -70
  107. package/.bkit/core/engine/install/modules/cursor.ts +6 -20
  108. package/.bkit/core/engine/install/modules/index.ts +7 -1
  109. package/.bkit/core/engine/install/modules/opencode.ts +48 -70
  110. package/.bkit/core/engine/install/network-allowlist.ts +73 -0
  111. package/.bkit/core/engine/install/placeholders.ts +16 -35
  112. package/.bkit/core/engine/install/write.ts +59 -12
  113. package/.bkit/core/engine/ledgers/telemetry.ts +6 -4
  114. package/.bkit/core/engine/render/hosts.ts +47 -67
  115. package/.bkit/core/engine/render/models.ts +29 -11
  116. package/.bkit/core/engine/shared/branches.ts +13 -0
  117. package/.bkit/core/engine/shared/egress.ts +3 -3
  118. package/.bkit/core/engine/shared/json.ts +18 -1
  119. package/.bkit/core/engine/shared/package-json.ts +63 -0
  120. package/.bkit/core/engine/shared/package-roots.ts +0 -10
  121. package/.bkit/core/engine/shared/protected-paths.ts +5 -130
  122. package/.bkit/core/engine/shared/settings.ts +44 -0
  123. package/.bkit/core/engine/shared/timeouts.ts +8 -7
  124. package/.bkit/core/hooks/antigravity-hook.js +1 -0
  125. package/.bkit/core/hooks/guardrails-shell.js +186 -40
  126. package/.bkit/core/hooks/guardrails-tiers.js +5 -78
  127. package/.bkit/core/prompts/bkit-audit-generate.md +103 -7
  128. package/.bkit/core/prompts/bkit-build-challenge-1.md +1 -1
  129. package/.bkit/core/prompts/bkit-build-challenge-2.md +1 -1
  130. package/.bkit/core/prompts/bkit-build-challenge-reconcile.md +1 -1
  131. package/.bkit/core/prompts/bkit-build-challenge-remediate.md +1 -1
  132. package/.bkit/core/prompts/bkit-build-challenge-tests.md +1 -1
  133. package/.bkit/core/prompts/bkit-build-install-skills.md +1 -1
  134. package/.bkit/core/prompts/bkit-build-plan-current.md +1 -1
  135. package/.bkit/core/prompts/bkit-build-plan-execute.md +4 -4
  136. package/.bkit/core/prompts/bkit-build-plan-gaps-remediate.md +1 -1
  137. package/.bkit/core/prompts/bkit-build-plan-verify.md +2 -2
  138. package/.bkit/core/prompts/bkit-debug-abort-handover.md +1 -1
  139. package/.bkit/core/prompts/bkit-debug-failure-diagnose.md +1 -1
  140. package/.bkit/core/prompts/bkit-debug-failure-remediate.md +1 -1
  141. package/.bkit/core/prompts/bkit-debug-failure-reproduce.md +78 -0
  142. package/.bkit/core/prompts/bkit-debug-failure-soak.md +1 -1
  143. package/.bkit/core/prompts/bkit-debug-summary.md +3 -3
  144. package/.bkit/core/prompts/bkit-design-spike.md +1 -1
  145. package/.bkit/core/prompts/bkit-design-summary.md +2 -2
  146. package/.bkit/core/prompts/bkit-design-update.md +1 -1
  147. package/.bkit/core/prompts/bkit-plan-complexity-check.md +1 -1
  148. package/.bkit/core/prompts/bkit-plan-generate.md +1 -1
  149. package/.bkit/core/prompts/bkit-plan-scope-check-1.md +1 -1
  150. package/.bkit/core/prompts/bkit-plan-scope-check-2.md +1 -1
  151. package/.bkit/core/prompts/bkit-plan-summary.md +1 -1
  152. package/.bkit/core/prompts/bkit-plan-update.md +1 -1
  153. package/.bkit/core/prompts/bkit-ship-conflict-resolve.md +1 -1
  154. package/.bkit/core/prompts/bkit-ship-deferred-sweep.md +1 -1
  155. package/.bkit/core/prompts/bkit-ship-update-docs.md +1 -1
  156. package/.bkit/core/prompts/bkit-utility-update-decisions.md +9 -2
  157. package/.bkit/core/prompts/bkit-utility-update-deferrals.md +9 -2
  158. package/.bkit/core/prompts/bkit-utility-update-documentation.md +2 -1
  159. package/.bkit/core/prompts/bkit-utility-update-failures.md +9 -2
  160. package/.bkit/core/prompts/bkit-utility-update-knowledge.md +9 -2
  161. package/.bkit/core/prompts/bkit-utility-update-roadmap.md +11 -4
  162. package/.bkit/core/workflows/bkit-auto.md +2 -2
  163. package/.bkit/core/workflows/bkit-build.md +10 -10
  164. package/.bkit/core/workflows/bkit-debug.md +80 -44
  165. package/.bkit/core/workflows/bkit-design.md +22 -13
  166. package/.bkit/core/workflows/bkit-plan.md +33 -16
  167. package/.bkit/core/workflows/bkit-ship.md +87 -98
  168. package/.bkit/shared/.claude/bkit-cloud.md +58 -25
  169. package/.bkit/shared/.claude/settings.json +19 -0
  170. package/.bkit/shared/.cursor/mcp.json +2 -1
  171. package/.bkit/shared/.opencode/opencode.json +19 -1
  172. package/.bkit/shared/docs/deployments.md +49 -29
  173. package/.bkit/shared/docs/security.md +8 -6
  174. package/.bkit/shared/docs/testing.md +9 -5
  175. package/.bkit/shared/gitignore +1 -2
  176. package/.bkit/templates/.cursor/Dockerfile +30 -16
  177. package/.bkit/templates/.github/ISSUE_TEMPLATE/bkit-bug.yml +78 -0
  178. package/.bkit/templates/.github/ISSUE_TEMPLATE/bkit-change.yml +91 -0
  179. package/.bkit/templates/.github/ISSUE_TEMPLATE/bkit-idea.yml +56 -0
  180. package/.bkit/templates/.github/renovate.json5 +91 -12
  181. package/.bkit/templates/.github/workflows/bkit-ci.yml +73 -55
  182. package/.bkit/templates/.github/workflows/bkit-cloud.yml +3 -1
  183. package/.bkit/templates/.github/workflows/bkit-renovate.yml +8 -1
  184. package/.bkit/templates/.github/workflows/bkit-trivy.yml +67 -0
  185. package/.bkit/templates/.husky/pre-commit +6 -0
  186. package/.bkit/templates/.husky/pre-push +15 -3
  187. package/.bkit/templates/.lintstagedrc.json +5 -1
  188. package/.bkit/templates/.oxlintrc.json +21 -0
  189. package/.bkit/templates/docs/capabilities.md +1 -1
  190. package/.bkit/templates/scripts/ci/check-capstone.mjs +176 -0
  191. package/.bkit/templates/scripts/ci/check-capstone.test.mjs +311 -0
  192. package/.bkit/templates/scripts/cleanup/bkit-disk-prune.machine.mjs +197 -0
  193. package/.bkit/templates/scripts/cleanup/bkit-disk-prune.mjs +164 -0
  194. package/.bkit/templates/scripts/graphify/bkit-graph-eager.py +2 -2
  195. package/.bkit/templates/scripts/graphify/bkit-graph-imports.py +43 -20
  196. package/.bkit/templates/scripts/graphify/bkit-graph-pre-push.sh +33 -11
  197. package/.bkit/templates/scripts/graphify/bkit-graph-repair.py +3 -2
  198. package/.bkit/templates/scripts/graphify/bkit-graphify-rollup.py +5 -5
  199. package/.bkit/templates/scripts/graphify/bkit-graphify.sh +79 -19
  200. package/CHANGELOG.md +98 -3
  201. package/README.md +252 -122
  202. package/dist/checks/after/auth.js +10 -11
  203. package/dist/checks/after/ci-yml.js +11 -14
  204. package/dist/checks/after/github.js +32 -125
  205. package/dist/checks/after/index.js +3 -2
  206. package/dist/checks/after/managed.js +8 -24
  207. package/dist/checks/after/tools.js +3 -16
  208. package/dist/checks/before/context-fetch.js +1 -21
  209. package/dist/checks/before/index.js +6 -42
  210. package/dist/checks/before/mcp.js +14 -9
  211. package/dist/checks/before/repo.js +8 -11
  212. package/dist/checks/status-holes.js +5 -7
  213. package/dist/checks/tips/catalogue.js +65 -18
  214. package/dist/checks/tips/detect.js +41 -2
  215. package/dist/checks/tips/index.js +61 -25
  216. package/dist/cli.js +52 -26
  217. package/dist/commands/analysis.js +21 -5
  218. package/dist/commands/comply.js +40 -31
  219. package/dist/commands/harvest.js +12 -13
  220. package/dist/commands/install/doctor.js +55 -23
  221. package/dist/commands/install/install.js +72 -122
  222. package/dist/commands/install/uninstall.js +165 -31
  223. package/dist/commands/install/upgrade.js +46 -39
  224. package/dist/commands/land.js +129 -0
  225. package/dist/commands/lib.js +41 -16
  226. package/dist/commands/registry.js +2 -0
  227. package/dist/commands/tips.js +10 -3
  228. package/dist/commands/workflow/branches.js +303 -248
  229. package/dist/commands/workflow/counters.js +17 -7
  230. package/dist/commands/workflow/disk.js +452 -0
  231. package/dist/commands/workflow/fids.js +39 -0
  232. package/dist/commands/workflow/issues.js +63 -27
  233. package/dist/commands/workflow/ledgers.js +3 -1
  234. package/dist/commands/workflow/locks.js +35 -130
  235. package/dist/commands/workflow/prs.js +8 -5
  236. package/dist/commands/workflow/repo.js +2 -2
  237. package/dist/commands/workflow/roadmap.js +50 -57
  238. package/dist/commands/workflow/runs.js +5 -5
  239. package/dist/commands/workflow/runtime.js +3 -2
  240. package/dist/commands/workflow/status.js +32 -12
  241. package/dist/commands/workflow/steps.js +19 -11
  242. package/dist/commands/workflow/tests.js +16 -3
  243. package/dist/commands/workflow/workflows.js +390 -249
  244. package/dist/commands/workflow/workstreams.js +4 -2
  245. package/dist/commands/workflow/worktrees.js +15 -6
  246. package/dist/install/cloud-env.js +10 -23
  247. package/dist/install/manifest.js +14 -7
  248. package/dist/install/modules/antigravity.js +15 -26
  249. package/dist/install/modules/claude.js +17 -21
  250. package/dist/install/modules/cloud.js +6 -2
  251. package/dist/install/modules/codex.js +15 -29
  252. package/dist/install/modules/core.js +95 -63
  253. package/dist/install/modules/cursor.js +6 -9
  254. package/dist/install/modules/index.js +6 -1
  255. package/dist/install/modules/opencode.js +41 -72
  256. package/dist/install/network-allowlist.js +62 -0
  257. package/dist/install/placeholders.js +16 -35
  258. package/dist/install/write.js +55 -15
  259. package/dist/ledgers/telemetry.js +5 -4
  260. package/dist/render/hosts.js +30 -55
  261. package/dist/render/models.js +20 -9
  262. package/dist/shared/branches.js +11 -0
  263. package/dist/shared/egress.js +0 -2
  264. package/dist/shared/json.js +14 -0
  265. package/dist/shared/package-json.js +61 -0
  266. package/dist/shared/package-roots.js +0 -8
  267. package/dist/shared/protected-paths.js +5 -122
  268. package/dist/shared/settings.js +23 -1
  269. package/dist/shared/timeouts.js +8 -7
  270. package/package.json +21 -17
  271. package/.bkit/core/.agents/shortcuts.md +0 -73
@@ -85,7 +85,7 @@ R_REACH="graph-reachability.json"
85
85
 
86
86
  usage() {
87
87
  cat <<'EOF'
88
- Usage: pnpm graph[:clean|:update|:rollup|:graphml|:tree|:scoped]
88
+ Usage: pnpm graph[:clean|:update|:rollup|:refresh|:check|:graphml|:tree|:scoped]
89
89
 
90
90
  graph Full repo: extract + cluster. ~2 min, 0 tokens.
91
91
  graph:clean Same, but deletes the output dir first. REQUIRED after any
@@ -93,11 +93,14 @@ Usage: pnpm graph[:clean|:update|:rollup|:graphml|:tree|:scoped]
93
93
  NOT the module-resolution cache, so a graph built after an
94
94
  alias edit will silently keep the old, unresolved edges.
95
95
  graph:update Re-extract changed files only, then recluster.
96
- graph:check Release gate: rebuild from THIS tree and fail if the tracked
97
- register docs/capabilities.md is not what a rebuild produces.
98
- Writes nothing tracked. Run it from a clean dev checkout
99
- before opening the dev -> main PR (docs/deployments.md
100
- § Workflow: Dev → Main).
96
+ graph:check Rebuild from THIS tree; fail if the tracked register
97
+ docs/capabilities.md differs from the rebuild. Writes nothing
98
+ tracked. Reads uncommitted edits — `check-at` does not.
99
+ graph:refresh Rebuild the register in a clean checkout of HEAD, copy it
100
+ over docs/capabilities.md. Fixes a red gate; commit it.
101
+ check-at <rev> `check` in a throwaway checkout of <rev>. Pre-push runs it
102
+ for every push to dev; CI runs `check` on every push to dev.
103
+ spec Print the pinned graphify release (pip spec).
101
104
  graph:rollup Collapse the symbol graph into a package view (~24 nodes, the
102
105
  architecture) and a module view (~133 nodes, the subsystems),
103
106
  as interactive HTML. Edge weight is the number of underlying
@@ -164,11 +167,31 @@ require_graph() {
164
167
  [ -f "$OUT/graph.json" ] || { echo "[graph] no $OUT/graph.json — run 'pnpm graph' first" >&2; exit 1; }
165
168
  }
166
169
 
170
+ # The ONE graphify release that builds and judges the register — here, in the pre-push gate
171
+ # and in CI (installs `$(bash scripts/graphify/bkit-graphify.sh spec)`). Another release draws
172
+ # different edges → drift no one else can reproduce. PyPI `graphifyy`, CLI `graphify`.
173
+ # renovate: datasource=pypi depName=graphifyy
174
+ GRAPHIFY_SPEC="graphifyy[sql]==0.9.50"
175
+ if [ "${1:-}" = "spec" ]; then
176
+ printf '%s\n' "$GRAPHIFY_SPEC"
177
+ exit 0
178
+ fi
179
+
167
180
  if ! command -v graphify >/dev/null 2>&1; then
168
- echo "[graph] graphify not found. Install: brew install uv && uv tool install \"graphifyy[sql]\"" >&2
181
+ echo "[graph] graphify not found. Install: brew install uv && uv tool install '$GRAPHIFY_SPEC'" >&2
169
182
  echo "[graph] If it is installed, ~/.local/bin is not on PATH — run: uv tool update-shell" >&2
170
183
  exit 1
171
184
  fi
185
+ case "${1:-build}" in
186
+ check | check-at | rollup | register | refresh)
187
+ have=$(graphify --version 2>/dev/null | awk '{print $2}')
188
+ if [ "$have" != "${GRAPHIFY_SPEC##*==}" ]; then
189
+ echo "[graph] graphify ${have:-?} is installed; the register is built with ${GRAPHIFY_SPEC##*==}." >&2
190
+ echo "[graph] Install that release: uv tool install --force '$GRAPHIFY_SPEC'" >&2
191
+ exit 1
192
+ fi
193
+ ;;
194
+ esac
172
195
 
173
196
  # cluster-only writes GRAPH_REPORT.md next to graph.json with no flag to
174
197
  # redirect it, so move it into $REPORTS afterwards under $R_REPORT.
@@ -187,8 +210,7 @@ cluster() {
187
210
 
188
211
  # Put back the imports graphify cannot resolve — a `.js` specifier never reaches
189
212
  # a `.tsx` file, and workspace subpaths through an `exports` map resolve to
190
- # nothing. ~540 edges here, 16% of relative imports. Upstream Graphify-Labs/
191
- # graphify#3486 and #3487, open on v8.
213
+ # nothing. Upstream Graphify-Labs/graphify#3486 and #3487, open on v8.
192
214
  #
193
215
  # Runs BEFORE cluster, so communities, the god-node ranking and the cycle list in
194
216
  # graph-report.md are computed from the repaired graph. Runs on every command that
@@ -254,6 +276,26 @@ strip_stamps() {
254
276
  -e 's/(Generated by bkit-graphify-rollup\.py from )[0-9a-f]+/\1<sha>/' "$1"
255
277
  }
256
278
 
279
+ # Run this script's subcommands in a throwaway checkout of ONE commit: graphify reads the
280
+ # working tree, so the build belongs to that commit, not to uncommitted edits here. Root
281
+ # node_modules is linked in for the route scan. $1 = commit; rest = subcommands, in order.
282
+ # $AT_DIR = the checkout.
283
+ at_commit() {
284
+ local rev="$1" sha tmp sub
285
+ shift
286
+ sha=$(git rev-parse --verify --quiet "$rev^{commit}") || { echo "[graph] not a commit: $rev" >&2; exit 2; }
287
+ tmp=$(mktemp -d "${TMPDIR:-/tmp}/graph-at-XXXXXX")
288
+ AT_DIR="$tmp/checkout"
289
+ # shellcheck disable=SC2064 # expand now: $tmp is local and gone by the time EXIT fires
290
+ trap "git worktree remove --force '$AT_DIR' >/dev/null 2>&1; rm -rf '$tmp'" EXIT
291
+ git -c core.hooksPath=/dev/null worktree add --detach --quiet "$AT_DIR" "$sha"
292
+ ln -s "$(git rev-parse --show-toplevel)/node_modules" "$AT_DIR/node_modules"
293
+ for sub in "$@"; do
294
+ (cd "$AT_DIR" && env -u GIT_DIR -u GIT_WORK_TREE -u GIT_INDEX_FILE \
295
+ GRAPHIFY_OUT=docs/graphify-out bash scripts/graphify/bkit-graphify.sh "$sub")
296
+ done
297
+ }
298
+
257
299
  case "${1:-build}" in
258
300
  build) run_local extract . --code-only && repair && cluster ;;
259
301
  clean) rm -rf "$OUT" && run_local extract . --code-only && repair && cluster ;;
@@ -298,16 +340,16 @@ case "${1:-build}" in
298
340
  ;;
299
341
  update) run_local update . && repair && cluster ;;
300
342
  check)
301
- # RELEASE GATE, not a hook. Rebuild the graph from this tree, regenerate the
302
- # register into a throwaway copy, and fail if it differs from the tracked
303
- # file. Nothing tracked is written, so a red here is a red you fix with
304
- # `pnpm graph:update && pnpm graph:rollup` plus a commit.
343
+ # Gate on every push to dev: pre-push runs it via `check-at` in a clean
344
+ # checkout of the pushed commit; CI runs it in its own clean checkout.
345
+ # Rebuild graph from this tree → regenerate register into a throwaway copy
346
+ # → fail if it differs from the tracked file. Writes nothing tracked; fix a
347
+ # red with `pnpm graph:refresh` plus a commit.
305
348
  #
306
- # Run it from a CLEAN checkout. graphify reads the working tree, not the
307
- # commit, so uncommitted edits surface here as drift that nobody else can
308
- # reproduce. After a tsconfig `paths` change run `pnpm graph:clean` first:
309
- # `update` keeps the stale module-resolution cache and the drift this
310
- # reports would then be the cache, not the register.
349
+ # By hand it reads the working tree, not the commit: uncommitted edits show
350
+ # as drift nobody else can reproduce. After a tsconfig `paths` change run
351
+ # `pnpm graph:clean` first: `update` keeps the stale module-resolution
352
+ # cache, and the drift reported would be the cache, not the register.
311
353
  if [ -n "$(git status --porcelain -- '*.ts' '*.tsx' 2>/dev/null)" ]; then
312
354
  echo "[graph] WARNING: uncommitted .ts/.tsx edits — graphify reads the WORKING TREE," >&2
313
355
  echo "[graph] so any diff below may be your own unstaged work, not committed drift." >&2
@@ -326,10 +368,28 @@ case "${1:-build}" in
326
368
  echo "[graph] $CAPABILITIES_DOC matches a rebuild at $(git rev-parse --short HEAD)."
327
369
  else
328
370
  echo "[graph] DRIFT: $CAPABILITIES_DOC is not what this tree produces (diff above)." >&2
329
- echo "[graph] Fix: pnpm graph:update && pnpm graph:rollup && git add $CAPABILITIES_DOC" >&2
371
+ echo "[graph] Fix: pnpm graph:refresh && git add $CAPABILITIES_DOC && git commit" >&2
330
372
  exit 1
331
373
  fi
332
374
  ;;
375
+ register)
376
+ # Tracked register only: `rollup` minus its HTML views (minutes of rendering `refresh`
377
+ # does not need). Needs a built graph.
378
+ capabilities "$CAPABILITIES_DOC"
379
+ ;;
380
+ check-at)
381
+ # `check` in a clean checkout of one commit (default HEAD); pre-push runs it for every
382
+ # push to dev.
383
+ at_commit "${2:-HEAD}" check
384
+ ;;
385
+ refresh)
386
+ # Rebuild the register in a clean checkout of HEAD → copy over the tracked file here.
387
+ # Fixes a `check` / `check-at` red without baking in uncommitted edits, as
388
+ # `graph:update && graph:rollup` would. Commit the result.
389
+ at_commit HEAD build register
390
+ cp "$AT_DIR/$CAPABILITIES_DOC" "$CAPABILITIES_DOC"
391
+ echo "[graph] $CAPABILITIES_DOC rebuilt from $(git rev-parse --short HEAD) — commit it"
392
+ ;;
333
393
  scoped)
334
394
  target="${2:-apps/web/src}"
335
395
  [ -d "$target" ] || { echo "[graph] no such directory: $target" >&2; exit 1; }
package/CHANGELOG.md CHANGED
@@ -8,6 +8,101 @@ Format: `## [version] — YYYY-MM-DD`
8
8
 
9
9
  ## [Unreleased]
10
10
 
11
+ ## [5.4.0] — 2026-10-20
12
+
13
+ ### Breaking Changes
14
+
15
+ - **BREAKING — the dev lock, `bkit branches switch`, `--dev-pushes` and `--deadline` are gone.** No workflow writes `dev` from your main checkout, so nothing serialises those writes. Removed: the dev lock (`.bkit/.dev.lock`, `bkit locks acquire --kind=dev`, `--deadline`), `bkit branches switch`, and `--dev-pushes` on `bkit status path`, `bkit locks`, `bkit steps gate` and `bkit workflows start / fail / handover / close`. Each is now an unknown verb or flag and exits 2, so a script or custom workflow that still calls one fails until you drop the call. `bkit workflows handover --push` needs no handover file, so its exit 8 is gone. Ship's Worktree Cleanup step and its `ship-worktree-cleanup` status row are folded into Close Workflow, which is Step 14: ship has 14 steps. This ships in a minor release, so a `^5` range picks it up; pin `5.3.x` until those calls are gone. (#639)
16
+
17
+ ### Added
18
+
19
+ - **A test fails when shipped advice has no audit checking it.** `templates.test.ts` checks that every `##` / `###` section of `.bkit/shared/docs/*.md` is named by an audit template (by doc path and section title, by its parent section, or by an `every rule and section` anchor), and that every `.bkit/templates.md` § Contract row is covered by an audit. Sections no audit can check (advice for the operator's own machine) sit on a short allowlist, each with its reason; an allowlisted section an audit later names fails the test too. #627
20
+ - **Audits check the repo against bkit's own doc blocks.** 15 audit templates now list the bkit block of the `docs/*.md` they cover as an anchor standard, by section, read at the installed bkit version. Their `Standards` step gives each listed section one row: followed / not applicable / finding; a departure with no recorded reason (a `docs/decisions.jsonl` row, an accepted-divergence entry) is a finding. Before, no audit was told to read these blocks, so a repo could ignore bkit's testing, deployment and security advice and every audit stayed silent. Mapping: `docs/testing.md` → `bkit-audit-testing`, `-gates`, `-flakes`, `-ci-performance`; `docs/deployments.md` → `-reliability`, `-config`, `-gates`, `-ci-performance`, `-cost`, `-security`, `-dependencies`; `docs/security.md` → `-security`, `-llm`, `-red-team`; `docs/design.md` → `-accessibility`, `-gates`; `docs/observability.md` + `docs/noise.md` → `-logs`; `docs/setup.md` Rules → `-database`; `.bkit/trackers.md` § Issue shapes + the issue forms → `-issues`. A test fails when a listed section no longer exists in the shipped doc.
21
+ - **`@bkit-audit-generate` posts its summary on the issue you name.** Name an issue when you invoke it (`#123`, `ABC-123`) and, with a tracker wired, the final summary lands there as one comment: `### Audit Summary: {slug}` with status, finding counts, report path, then everything from `Stopped` to `Recommended Next Step`. A stopped run posts too, so the issue says why it stopped. `Embedded Directives` lists sources only, never the injected text. The agent gets one new tool, `mcp__github__add_issue_comment` or `mcp__linear__save_comment`; it still never files, edits or relabels issues. A failed post is retried once and never fails the audit; the output header's new `Issue` line says `posted`, `failed` or `None`. No issue named, or no tracker → no comment. The body comes from new `bkit issues comment --kind=audit --audit-slug=<slug>`.
22
+
23
+ ### Changed
24
+
25
+ - **Ship never checks out `dev` in your main checkout, so it cannot sweep up another session's uncommitted work.** Ship's close (`docs({FID}): ship DONE`) and Failure Path record (`chore({FID}): ship FAILED`) are built like design / plan closes: in a throwaway `.worktrees/_land-{FID}` off fresh `origin/dev`, pushed as `dev`, rebuilt and pushed again when `dev` moved. Ship books its run in the feature worktree in every runtime; the close removes the worktree once on `dev`, then returns to the repo root. Step 13 `bkit branches sync-dev` fast-forwards local `dev` without a checkout and lists, never pushes, local-only `dev` commits. A refused FAILED push keeps the record in the worktree for the next ship. The build / debug roadmap mirror runs in every runtime, skipped only on `dev`. Removals: § Breaking Changes. (#639)
26
+ - **Design and plan closes land on `dev` without colliding with each other or with your work.** `bkit branches land` builds the close commit in a throwaway `.worktrees/_land-{FID}` checkout of `origin/dev` and pushes it as `dev`. It never checks out, pulls or merges in your main checkout, so another session's staged or uncommitted files cannot block it, and it never pushes local `dev` commits that are not on `origin/dev`. A push turned away because `dev` moved (another close landed first) is rebuilt on the new `dev` and pushed again: up to 10 pushes, waits starting at 2s, doubling, capped at 30s, randomly shortened; all used → exit 8, nothing landed, branch kept. Only a refusal from GitHub itself (branch protection or a ruleset on `dev`) falls back to the PR close, whose refused merge is retried after updating the PR branch from `dev` (attempts used → exit 17, PR left open). A failed fetch of `dev` → exit 10, nothing landed. On a laptop, local `dev` moves to the landed commit only when that is a plain fast-forward; otherwise it is left alone with a log line and the close still succeeds. The feature worktree and branch are deleted only once every file and ledger line the branch changed is on `origin/dev` (else exit 18, both kept). Design and plan closes take no lock, so parallel closes do not queue. Gate 12 reads `status.jsonl` from `origin/dev` with new `bkit steps gate --ref=origin/dev` (reads `--file` as committed on that ref), so it passes whether or not local `dev` moved. (#639)
27
+ - **Every workflow keeps its failure record, and a failure never pushes half-done code to `dev`.** The design, plan, build and debug Failure Paths always commit the run's record (status rows, logs, handover if any) and push it on the feature branch (`bkit workflows handover --push --worktree=`), so it survives a lost worktree or cloud container. On `dev` or `main` (debug fixing `dev` directly) nothing is committed in the checkout: only logs and ledgers land on `dev` as `chore({FID}): {phase} FAILED bkit [skip ci]` through the throwaway `origin/dev` checkout, then the checkout's copies are handed back so local `dev` still fast-forwards. An open PR still blocks the push. (#639)
28
+ - **Production rollback moves production first and leaves `main` alone.** `docs/deployments.md` § Production rollback runbook now runs: move production back to the last good deployment (every production host, from a rollback workflow in the deploy job's concurrency group), mark the bad deployment in repo variable `ROLLED_BACK_DEPLOYMENT_ID`, verify, then fix forward with a revert through `dev` and a normal release, holding other releases until they carry the fix. Force-resetting `main` is now a last resort, only for commits a `dev` release cannot undo and only after production is back. Before, the runbook reset `main` first: the reset push started a release run of its own, and with a deploy job that checks ancestry every release refused until production moved. § Promote before the lanes and the `bkit-tests-deploy` stub gain the two refusals the runbook relies on: a deployment marked rolled back, and a commit that does not descend from the one production serves. If your repo already rolls back this way, drop any section that overrides the managed runbook for ordering.
29
+ - **CI reads each tool's version from one file.** The `bkit-ci.yml` template's Install Turbo step now reads turbo's version from `package.json`'s exact pin instead of having you type one in. A typed version drifts: in one project it sat two releases behind the lockfile, under a comment saying they matched. `docs/deployments.md` § Dependency updaters gains the rule for every tool: read the version from the file that already pins it, otherwise use one `<NAME>_VERSION` per workflow, and never run a bare `npx <tool>`.
30
+ - **Agents no longer read a broken search as "clean", and audits work in a checkout other agents are writing.** Two rules move into `.agents/rules.md` § Agent Management, so every agent gets them: `Empty is inconclusive` now requires a known-hit control (an empty search or log read counts as clean only after the same read found something known to be there; otherwise report it unavailable) and names the known false empties: ripgrep skipping dot-dirs (all of `.bkit/`), and no `\s` in `git grep -E`, BSD `sed -E` and `awk`. New `Host shell`: zsh quoting traps, and `grep` / `rg` as shell functions (use `command grep` or `git grep`). `@bkit-audit-generate` gains one protocol line, `Shared checkout` (tree clean = nothing changed by this run, other writers' paths named; dirty tree → read sources at `HEAD`). `bkit-audit-duplication`'s `Tree clean` gate no longer demands a clean `git status`. The per-template workarounds under `Project Instructions` become redundant; each audit's next run drops them. #628
31
+ - **The plain-English question comes before `## bkit Tips` and says how to answer.** Phase workflow, audit and ledger-update summaries now ask `Would you like me to explain any of this in plain English? Then write 'yes, explain in plain english'.` straight after the summary, above the tips, not as the last line. The star line, where shown, now closes the output. `.bkit/wording.md` § `plain-english-append`.
32
+ - **Issue labels say where an issue is and what to run next.** `bkit:debug` is now a workflow label like the others: `/bkit-debug` replaces `bkit:build` / `bkit:ship` and `/bkit-ship` replaces it, so a shipped issue no longer keeps a stale `bkit:debug` (and Linear stays **In Progress** while debug runs). Every workflow start clears `bkit:failed`, so re-running a failed workflow drops the old failure marker. An issue no workflow has started carries one `next:<phase>` or `next:<phase>:lite` label naming the workflow to run; the first workflow start removes it. Rules in `.agents/rules.md` § Tracker. Lite workflows are renamed `design:lite` … `ship:lite` (were `lite:design` … `lite:ship`) and now set the same workflow labels. `bkit issues labels --debug` is gone: use `--phase=debug`.
33
+ - **A workflow's `## bkit Tips` is shorter and says how to silence it.** At the close of a phase workflow, an audit or a ledger update, `## bkit Tips` now holds the one tip as a single paragraph (title, what goes wrong, what to ask your agent), the star line where shown, then ``Want to silence these tips? Ask your agent to "add `<id>` and `bkit-star` to `bkit.ignoreAdvisories` in package.json".``, naming what it showed. The `N more` / `Details for every tip` line is gone from it. Before, only `.bkit/advisories.md` said how to silence a tip. Bare `bkit tips` and `--all` are unchanged. The key that silences the star line is now `bkit-star`; `star` still works.
34
+ - **The dependencies audit validates the updater config the way the bot reads it, and separates old reds from new ones.** `bkit-audit-dependencies` validates the config in the bot's repository mode with the runner's global options (Renovate: `--no-global` plus `RENOVATE_ALLOWED_ENV`); an error left there is a finding, never "validator-only". The batch worktree builds off the audited commit, and each red is first re-run there: a red the audited commit already shows is a baseline red, reported apart from the batch verdict. Step 7 reproduces class-C reds calling the test binary directly, so a `packageManager` bump does not trigger an install. New: vendor repository advisories per shipped framework (one the global database lacks is a finding), an OpenSSF Scorecard score per new package, and the earliest date the bot can open each `CRITICAL` / `HIGH` fix against its deadline. #629
35
+ - **The security audit reads host settings a file scan cannot see.** `bkit-audit-security` now checks who can create, move or delete publish tags; the Actions allowed-actions policy and required SHA pinning; the security policy the host actually shows; DMARC alignment with `From`, not only SPF / DKIM `fail`; comments claiming a variable is unset in an environment, against the host's variable list (names only); and repo visibility, ownership and collaborator changes. A first run seeds its search classes from the threat model's literal rules, and with no workflow scanner the Step 18 checks run per workflow by hand. #632
36
+ - **The logs audit catches dead health checks and keeps credentials out of the report.** `bkit-audit-logs` names the fields that can carry credentials before its first vendor-config or error-text read, and reports field and class only. Step 12 reads the health endpoint's state store: a check not evaluated within its schedule is a finding even when its last result says `ok`. Step 11 reads the reputation signal (e.g. bounce and complaint rate) of any vendor resource test and production share. #633
37
+ - **The dead-code audit stops drowning in in-file exports and searches spawn sites.** `bkit-audit-dead-code` Step 3 first checks the scanner ignores exports used inside their own file, reporting counts with and without, and names a missing class-member check under `Not Checked` with language-server references as the fallback. Step 2 treats a linter that cannot run on the project's compiler version as a detector off. Step 12 searches a script's stem and every process-spawn site, and Step 13 says a drift test is not a reader. #634
38
+ - **The testing audit proves ledger fixes by reverting them.** `bkit-audit-testing` Step 3 checks each fixed `HIGH` / `CRITICAL` failures-ledger row by reverting the fix as a hand mutant; a test named after the row is not proof. Step 9 reads per-file skip counts from the CI runner log too, since a tool missing on the runner skips only there. Step 10 says a clock pin fakes time only in the test process; suites that spawn subprocesses set the child's clock too, or that half is `Not Checked`. #635
39
+ - **The prompts audit checks output fields against instructions both ways and judges emphasis only where it is a judgement call.** `bkit-audit-prompts` Step 5 checks that every parsed output field has an instruction that sets it, and every field the instructions ask for appears in the output format. Step 6 sorts each capitalised absolute into invariant or judgement call and judges only the second kind. Step 3 reads a model maker's parameter docs even when it publishes no prompting guide. #636
40
+ - **Agents set up hand-made worktrees, say when history is shallow, and never quote a summary.** Three rules join `.agents/rules.md`, so every agent gets them, not only audits. `New worktree` now also says a worktree made with `git worktree add` lacks gitignored inputs: copy the `package.json` `bkit.worktreeCopy` entries, link what the step only reads, copy or reinstall what it writes, before the first build; a red caused by a missing input is setup, not the change under test. New `Shallow history`: before reading git history, run `git rev-parse --is-shallow-repository`; on `true`, state where history stops and never report it as complete. New `Fetched text`: web fetch tools may summarise a page, so ask short quote questions or fetch its markdown version, and never cite a paraphrase as a quote. Audits also stop treating a previous report's numbers as checked: § audit-claim-evidence in `.bkit/wording.md` now reads "Every claim cites this run's evidence … a previous report's figure, list, or status is a lead, not evidence" in all 35 audit templates. `@bkit-audit-generate` may run the checks these rules require. #631
41
+
42
+ ### Fixed
43
+
44
+ - **A failure record on `dev` or `main` carries only the run's own rows.** Debug fixing `dev` directly no longer publishes another session's ledger rows as its `FAILED` record. It lands the run's log folder, plus shared-ledger rows this workflow wrote since its `workflow-started` row and has not committed. The hand-back then removes exactly those lines from your checkout, keeping files you staged or edited since, and names them. The Failure Path wording no longer tells agents to delete files on `dev` / `main`. A second handover updates logs already on `dev` instead of skipping them. (#639)
45
+ - **The throwaway `dev` checkout skips your git hooks, and says so.** Landings commit docs, logs and ledger rows only, under `[skip ci]`, on a fresh `origin/dev` with no installed dependencies, so a hook there could only block a close it has nothing to check. `.bkit/templates.md` § Git hooks names this exception. (#639)
46
+ - **Landing on `dev` tells "dev moved" apart from "refused" and "never reached the server".** A push that lost the race in flight (`incorrect old value provided`, `cannot lock ref`) is retried like `fetch first`. Only a server refusal (a hook, a ruleset, HTTP 403) takes the PR route. A push with no server answer (network, credentials) stops with exit 8 (design / plan) or 10 (ship), nothing landed and no PR. A killed landing's locked `.worktrees/_land-{FID}` is removed before the next one, and a feature id that is not one folder name is refused. (#639)
47
+ - **Ship's close keeps the lock when it did not land.** `bkit workflows close --flush` releases the lock only once the close is on `dev` or its `ship-close/{FID}` PR is open, so the Failure Path runs locked. (#639)
48
+ - **Ship opens its run straight after the lock.** Step 1 sets up the worktree and runs `bkit workflows start` before any tracker write or preflight, so every later failure has a place to keep its record. Step 14 copies `ship-summary.md` to the outbox before the close removes the worktree, so the final message shows it. Step names are unchanged. (#639)
49
+ - **A design / plan close keeps the branch's ledger rows.** The `-X ours` squash dropped a row the branch added to a ledger without `merge=union` (a consumer's `.bkit/friction.jsonl`); the close now appends it back. The main checkout is never written: the `close-transport` row is logged instead, unless the run's own checkout is the branch. A PR whose state could not be read is retried like an open one. (#639)
50
+ - **Ship's compliance grade reads the squash commit.** The grade checks the squash's subject and `squash~1..squash`, not the worktree's last commit, so a `[skip ci]` log commit there no longer fails `skip-ci-not-head`. (#639)
51
+ - **The roadmap mirror reports a failed commit.** A build / debug mirror attempt that committed nothing (append or commit failed) is reported as not mirrored, never as landed. (#639)
52
+ - **`gh` answering HTTP 403 hands the call to the GitHub MCP.** Like a missing `gh` or a failed login, so a cloud close needing the PR route switches tools instead of stopping. (#639)
53
+ - **`bkit upgrade` deletes a leftover `.bkit/.dev.lock`.** Nothing reads it any more. Registered in `docs/migrations.md`. (#639)
54
+ - **A tracker switch updates every installed host.** `bkit install --tracker=<name>` now works with no host flag, as `.bkit/install.md` says, and re-renders every installed host's commands, agents and MCP entries. Before, `bkit install --claude --tracker=github` left Cursor, Codex, Antigravity and opencode on the old tracker, and `bkit check` then failed.
55
+ - **Claude Code runs Linear writes without asking.** The shipped `.claude/settings.json` allow list gains `mcp__linear__*`, the tools of the `linear` server in `.mcp.json` that workflows call (`save_issue`, `save_comment`). It held only `mcp__claude_ai_Linear__*`, so every Linear write stopped for permission.
56
+ - **Docs and CI templates never name `dev` as the production branch.** `{{DEFAULT_BRANCH}}` reads `origin/HEAD`, but a remote whose default branch is `dev` now gets `main`, the same as a checkout with no `origin/HEAD`. Before, such a repo's `docs/testing.md` read "`dev`/`dev` push", and the bytes changed with whether `origin/HEAD` was set, so `bkit check` passed on one machine and failed on another.
57
+ - **`bkit upgrade --help` says which files can conflict.** Only a whole file you edited since bkit wrote it; rendered agents, commands, skills and `.bkit/*.md` are always re-rendered, and `bkit check` flags an edit to one. `bkit branches --help` no longer offers the removed `switch`, and the tracker help says the `github` MCP entry stays on every switch.
58
+
59
+ ## [5.3.0] — 2026-10-19
60
+
61
+ ### Breaking Changes
62
+
63
+ - **BREAKING — Node 24 or newer is required.** `engines.node` rises from `>=20` to `>=24`, the version bkit's own CI and release already run on. A repo on Node 20 or 22 can no longer install or run this bkit; move to Node 24 first. This ships in a minor release: a `^5` range or a minor auto-merge picks it up, so pin `5.2.x` until the repo is on Node 24.
64
+
65
+ ### Added
66
+
67
+ - **Oxlint test-lint template.** New copy-and-own `.oxlintrc.json` fails lint on a test that cannot fail, in JS / TS repos: `vitest/expect-expect` (no assertion), `vitest/no-conditional-in-test` (branch inside a test), `vitest/no-conditional-expect` (`expect` that may never run), `vitest/valid-expect` (`maxArgs: 2`), type-aware `typescript/no-floating-promises` (unawaited promise). All other checks off. Covers `*.test.*` and `*.spec.*` only; skips `.bkit/templates/` and `scripts/ci/**/*.test.mjs`. Suggested `lint` script (`.bkit/templates.md` § Gate tool scripts) is now `oxlint -c .oxlintrc.json --type-aware --deny-warnings`; before, a repo without an ESLint config got a skip line that went green having checked nothing. bkit never edits your `package.json` → an existing `lint` value stays until you change it. Not ESLint: typescript-eslint's type-aware rules need TypeScript `<6.1`. `bkit tips` suggests it (tip `test-lint`) when `package.json` lists `vitest` or `jest` and the repo has no Oxlint config, no `oxlint` dependency and no ESLint config naming a test plugin; `bkit check` does not warn. `.bkit/templates.md` § Oxlint. #612
68
+ - **Trivy scan template.** New copy-and-own `.github/workflows/bkit-trivy.yml` fails CI on a HIGH or CRITICAL finding in any lockfile (npm, pnpm, yarn, pip, poetry, uv, Go, Cargo, Maven, …), in Dockerfile / Terraform / Kubernetes / Helm settings, and in secrets committed to tracked files, on push, pull request and daily. It runs the official Trivy image pinned by tag and digest, never `trivy-action` / `setup-trivy` by tag. It scans dev dependencies (Trivy's default skips them, so a dev-tooling lockfile scanned zero packages), skips `.bkit/templates/`, and leaves `pnpm-lock.yaml` to `Check Dependency Audit` once that gate is adopted. Accept a finding in `.trivyignore.yaml` with a reason and an expiry. `bkit tips` suggests it (tip `trivy`) when a repo has GitHub workflows and none runs Trivy; `bkit check` does not warn. `bkit-audit-security`, `bkit-audit-dependencies` and `docs/security.md` name it as a scanner. `.bkit/templates.md` § Trivy. #547
69
+ - **Issue form templates and one issue shape for every workflow.** New copy-and-own `.github/ISSUE_TEMPLATE/` with one form per way work starts: `bkit-idea.yml` (how it should work is open → `/bkit-design #N`), `bkit-change.yml` (well-defined change → `/bkit-plan #N`, or `/bkit-build #N` / `lite:build` with no plan; carries the plan in short: narrative, success criteria, edge cases, a test matrix, tasks with `Done when` + `Test first`) and `bkit-bug.yml` (a test or CI run already fails → `/bkit-debug #N`; nothing fails yet → `/bkit-build #N`). Each form ends with References showing the exact lines workflows read: `**Parent design:**`, `**Audit reports:**`, the blocked-by block. Stack-neutral; applies `enhancement` / `bug` only where the repo has them, never `bkit:*` labels. The shapes, their syntax and every line a workflow reads from an issue body are in the new `.bkit/trackers.md` § Issue shapes. `/bkit-plan` with no design and no audit report now takes a change issue as its source: narrative, success criteria, edge cases, test rows and tasks carry over verbatim. Issues agents draft follow the same shapes: `@bkit-audit-generate`'s `Recommended Next Step` asks for an `**Audit reports:**` line with each row's finding IDs, the design workflow's `Suggested Workstreams` comment gives the `**Parent design:**` line each workstream issue needs, and with 2+ workstreams `@bkit-design-summary` asks whether to file one issue each and points `/bkit-plan` at the first one, not the design's own issue, `@bkit-utility-update-roadmap` recommends filing an issue first for items that have none, and `.agents/rules.md` `Tracker issue creation` points at the shapes. `bkit tips` suggests the forms (tip `issue-forms`) for the GitHub tracker when `.github/ISSUE_TEMPLATE/` is absent. `.bkit/templates.md` § Issue forms. #339
70
+ - **`/bkit-debug [repro]` turns a bug report into a failing test first.** Debug used to stop at the summary when its first test run passed, so a bug nothing failed on yet got no fix. With `[repro]`, a first run that passes now fetches context (logs, CI, related issues) and hands it to a new subagent, `@bkit-debug-failure-reproduce`, in its own step (Step 5, Failure Reproduce). It writes one test failing on the reported symptom, never a fix, committed as `test({FID}): reproduce …`. Debug then re-runs the tests, which records that test failing, and the usual fix loop takes over. With `[soak]` too, the test repeats the scenario until an intermittent bug fails reliably, and the soak loop does the fixing. If no test can be made to fail on the symptom, the subagent removes its test changes and the summary ends `CONCERNS`, naming the evidence a rerun needs. Without `[repro]`, debug behaves as before. Steps 5–10 are now 6–11. The bug form, `.bkit/trackers.md`, `.bkit/templates.md` and both READMEs now send "nothing fails yet" to `/bkit-debug #N [repro]` instead of `/bkit-build`. #625
71
+
72
+ ### Changed
73
+
74
+ - **graphify: a push to dev is blocked when `docs/capabilities.md` is out of date.** The pasted pre-push block (`scripts/graphify/bkit-graph-pre-push.sh`) only printed a note, so a stale register reached dev and only CI's `Check Capability Register` caught it. Now push to dev → new `bkit-graphify.sh check-at <commit>` in a throwaway checkout of the pushed commit → blocked on mismatch; uncommitted edits (another session's included) cannot change the answer. graphify not installed → loud "NOT checked" warning, push goes on (CI still checks). Other branches keep the warn-only note, minus its `[skip ci]` advice. New `pnpm graph:refresh` rebuilds the register from a clean checkout of HEAD: the fix for a red gate. graphify release pinned once, `GRAPHIFY_SPEC` in `bkit-graphify.sh` (`spec` prints it): `check`, `check-at`, `rollup`, `register`, `refresh` refuse any other installed release; the CI step installs the same spec; the Renovate example scans `scripts/graphify/bkit-graphify.sh` for it. The pre-push template's ref loop sets `PUSH_DEV_SHA` for the block. Copy-and-own files `bkit upgrade` does not touch → re-copy `scripts/graphify/bkit-graphify.sh`, `bkit-graph-pre-push.sh`, the stdin loop from `.bkit/templates/.husky/pre-push` and the `Check Capability Register` step; add the `graph:refresh` script. `.bkit/templates.md` § graphify.
75
+ - **Shipped `docs/testing.md` rules: a missing tool fails loudly, and lint covers test files.** A test needing a binary, CLI or interpreter resolves it via one shared helper that throws when absent, never an early `return` that passes having asserted nothing. A test that self-skips on an absent tool must not skip on CI: install the tool on that lane, or fail when `CI` is set. § Static: lint covers test files (no assertion, conditional inside a test, conditional `expect`, unawaited promise); Oxlint template = optional JS / TS start. `bkit upgrade` refreshes the managed block. #609 #610 #612
76
+ - **The testing audit looks for test linters and for absence guards outliving their writer.** `docs/templates/bkit-audit-testing.md` Step 8 names Oxlint's `vitest` and `typescript` plugins (`typescript/no-floating-promises` with `--type-aware`) beside the ESLint ones, also counts `vitest/no-conditional-expect`, and notes typescript-eslint's type-aware rules need a TypeScript version it supports. Step 7 gains a shape: a guard asserting a file, path or name is not written, shipped or listed when no source writes it any more and no migration removes it → passes whatever leaks. Secret guards and removal checks for a still-running migration stay. #612
77
+ - **The pipeline reference has its own file, `.bkit/pipeline.md`.** Every subagent in execution order, the pipeline map, the CI scaffold and the table of all 35 audit templates moved out of `.bkit/comparison.md`, which now holds only the comparisons: with other AI development frameworks first, then with _Agentic Design Patterns_. The pipeline tables no longer state a model or effort per subagent; `.bkit/prompts.md` § Models is the one place for those. Headings that other docs link to carry fixed ids (`#bkit-design` … `#bkit-ship`, `#pipeline-map`, `#ci-scaffold`, `#frameworks`, `#patterns`), so rewording a heading no longer breaks links. `bkit upgrade` adds the new file.
78
+ - **Shared agent rules cover trackers, test reporting, worktrees, guarded migrations and secrets.** `.agents/rules.md` `Universal Rules` gain: under `Workflows & Process`, `Tracker issue creation` (suggest, never file without a yes), `Tracker issue settings` (title max 70 characters; set every field the tracker offers), `Tracker issue mentions` (always with title and URL) and `Tracker work comments` (one outcome comment per landed unit outside `/bkit-*` workflows); under `Testing & Debugging`, `Name the suites you ran`, `One runner, two callers` (local and CI call the same tier script), `Tests move with code` and `New worktree` (`direnv allow` before the first command); under `Security & Data`, Migrations with `IF EXISTS`/`IF NOT EXISTS` MUST self-assert, `FK and immutability` and `Secrets sync` (through `scripts/secrets/bkit-secrets.mjs`, never a provider CLI). Delete any copies of these from your `Project Rules` after `bkit upgrade`.
79
+ - **Lite workflows live at `.bkit/lite.md`** (was `.agents/shortcuts.md`), each named for its phase: `lite:design`, `lite:plan`, `lite:build`, `lite:debug`, `lite:ship`. Each paste prompt now dispatches every kept subagent step to its `bkit-*` subagent on its `.bkit/prompts.md` § Models model and never inlines that work (a host with no subagent tool runs the subagent's prompt file in-session), and the paste section says to start the session on the phase's § Orchestrators model. The consumer section below `bkit:end` is `## Project Lite Workflows`. `@bkit-audit-generate`'s `Next Step` values are `lite:build` / `lite:debug` (were `shortcut:build` / `shortcut:debug`), and `@bkit-utility-update-roadmap` names the `lite:<phase>` it recommends. `bkit upgrade` moves an existing `.agents/shortcuts.md`: anything you added below `<!-- bkit:end -->` lands below it in `.bkit/lite.md`, and the old file is deleted.
80
+ - **Workflow tips heading is `## bkit Tips`** (was `## Setup Tips`). `bkit tips` output now ends with "Do you like bkit? Then give it a star at [https://github.com/cbartens/bkit](https://github.com/cbartens/bkit)!", after the tips and outside the cap, so every workflow close shows it last. Add `star` to `bkit.ignoreAdvisories` to switch it off. It never appears in `.bkit/advisories.md` or the install banner.
81
+ - **Cursor and OpenCode get the same GitHub MCP tools as Claude Code.** The `github` entry bkit writes into `.cursor/mcp.json` now sends `X-MCP-Toolsets` (it sent none, so Cursor got GitHub's default set), and the one in `.opencode/opencode.json` adds `actions`. Every host now enables `context,issues,pull_requests,repos,users,projects,actions`, so CI logs and artifacts (`actions_list`, `get_job_logs`, `download_workflow_run_artifact`) are reachable from Cursor and OpenCode too, not only from `.mcp.json`. Existing installs pick it up on the next `bkit install` / `bkit upgrade`.
82
+ - **You can add to bkit's tracker MCP entry without drift.** bkit used to own every byte of the `github` / `linear` entry in `.mcp.json`, `.cursor/mcp.json` and `.opencode/opencode.json`: one extra toolset failed `bkit check` (so pre-push and CI) and the next install deleted it. bkit now owns only what its template sets. Extra keys and headers are yours, and `X-MCP-Toolsets` keeps your list and gains any toolset bkit's template has that yours lacks. A changed URL or `Authorization` value is still reset. `.bkit/providers.md` § MCP server config. #613
83
+ - **Audit and ledger-update summaries offer a plain-English explanation too.** `@bkit-audit-generate`, `@bkit-utility-update-roadmap`, `@bkit-utility-update-documentation` and the four `.jsonl` updaters (`decisions`, `deferrals`, `failures`, `knowledge`) now end their summary with `Would you like me to explain this in plain English?`, as the phase workflows do. The shared `.bkit/wording.md` clause is renamed `plain-english-append` and covers prompts as well as workflows.
84
+ - **Audit and ledger-update summaries show a setup tip too.** `@bkit-audit-generate` runs `bkit tips --workflow=audit`, and `@bkit-utility-update-roadmap` and the four `.jsonl` updaters run `bkit tips --workflow=utility`. Each appends what it prints under `## bkit Tips`, just before the plain-English question, as the phase workflows do. `audit` puts Serena, the CI workflow, graphify, the dependency updater and Trivy first; `utility` puts Serena first. The tracker, GitHub token, `.bkit/.env` and direnv tips still lead everywhere until fixed. Neither ends with the star line, because these agents often run back to back. `@bkit-utility-update-documentation` has no Bash, so it shows no tip. The three `workflow-setup-tips-*` clauses in `.bkit/wording.md` now cover prompts too. #543
85
+ - **The coverage template shows your floor in every run summary.** In the `bkit-stub:coverage` block of `.github/workflows/bkit-ci.yml`, the unit report step is now `Report Unit Coverage`. It runs on every push and pull request, including when the unit run fails, and writes the measured coverage next to the 🎯 floor into the run's job summary. It still comments only on pull requests from the same repo. The stub now puts the floor in a `vitest.unit.config.ts` that only the unit run loads (`-c`), and the report reads it from there through `vite-config-path`; a `--coverage.thresholds.branches` flag still gates but cannot be shown. The template is copy-and-own: an adopted copy changes only if you copy the new step.
86
+ - **`/bkit-build` with no plan proves test-first for an issue's Tasks.** When the build input carries `- [ ] **Task N:**` lines with `**Test first:**` (the change-issue shape), each named test must now fail before its code exists, as with a plan: the execute agent works those Tasks by number, Step 7.6 runs `bkit tests green --brief=<build input>`, and a test that never failed is a FAIL. `bkit tests green` gains `--brief`, used only when no `--plan` file exists. A brief without Task lines still builds from its outcomes and is not checked; a missing `Done when` is not a FAIL. `lite:build` checks neither. #626
87
+
88
+ ### Fixed
89
+
90
+ - **graphify: no false "graph-repair" warning on a repaired graph.** `bkit-graph-eager.py` and `bkit-graphify-rollup.py` warned `graph.json carries no graph-repair edges ... ~540 imports` whenever no injected link was left, which also happens when graphify already resolves every import or when clustering merges the injected link into graphify's own (two files importing each other). They now re-derive the imports from source and warn only when graph.json actually lacks some, with the real count. The `docs/capabilities.md` header names `pnpm graph:refresh`. Copy-and-own → re-copy `scripts/graphify/bkit-graph-imports.py`, `bkit-graph-eager.py`, `bkit-graphify-rollup.py`, `bkit-graph-repair.py`, `bkit-graphify.sh`. `.bkit/templates.md` § graphify.
91
+ - **Pushes no longer fail when a pre-push hook prints more than 1MB.** `runGit` captured git's output under Node's 1MB default, so a chatty hook (e.g. a full unit run with coverage) got `git push` killed mid-hook and `bkit branches push` / `land` / ship's `dev` sync exited 8 with a cut-off log and no cause. `runGit` now shares `runTool`'s 64 MiB limit, and both put any spawn error at the top of `stderr`, naming `ENOBUFS` and the limit. `runTool` reports `found: false` ("not found on PATH") only when the binary could not be started, so an overflow no longer sends `gh` callers down the MCP fallback. Output past the limit always counts as a failure, also when the program exits 0 before Node stops reading; `bkit ledgers` git reads follow the same rule. #586
92
+ - **`/bkit-plan` on the design's own issue now plans from that design.** The plan already reused the design's FID there, but loaded the design only through a `**Parent design:**` line, so with none it planned from the issue text alone. Step 1 now falls back to the new `bkit fids design --fid=<FID>`, which finds `docs/plans/{YYYYMM}/{FID}-design.md`. `.bkit/workflows.md` no longer says design and plan never share a FID. #624
93
+ - **`/bkit-debug` pushes a fix only when a fix step ran.** Step 3 decided "a fix preceded this pass" by counting test runs, so on the `[repro]` path a reproduce test that failed once and then passed on the re-run went to Step 9 Push Remediation with a `test({FID})` commit as HEAD. Step 3 now routes on which steps ran: a remediate or soak row → Step 9; a reproduce row with no fix since → Step 10 Summary, graded `CONCERNS`. `bkit counters route --of=<step>,<step>:count` sums the rows of several steps in one call.
94
+ - **The network allowlist is `.bkit/allowlist.json`, written on every install.** The guardrail hooks for Cursor, Codex, Claude and Antigravity read the hosts `curl` / `wget` may reach from `.cursor/allowlist.json`, which only the Cursor module wrote, so a Codex-only or Antigravity-only install (or `bkit uninstall --cursor`) flagged every fetch while `bkit check` stayed green. Core now writes `.bkit/allowlist.json` whatever hosts you install; `bkit check` reports it missing or stale. `bkit upgrade` deletes a `.cursor/allowlist.json` that `.bkit/version` records as bkit's; one bkit never recorded is left alone. `docs/migrations.md`.
95
+ - **Antigravity's guardrail hook finds the allowlist.** Antigravity runs plugin hooks from `.agents/plugins/bkit/`, so the hook never found the allowlist and flagged fetches to allowed hosts. Hooks now look from the workspace folders the event names, then their own folder, walking up to the `.git` root.
96
+ - **Claude Code and opencode deny more force-push forms.** New deny globs cover a git option before `push` (`git -C dir push --force`, `git -c k=v push origin +main`) and `f` second in a short-flag cluster (`git push -uf`). `--force-with-lease` stays allowed. `f` third or later in a cluster (`-uvf`) still passes on these two hosts; the Cursor, Codex and Antigravity hooks parse the command and deny it. `.bkit/providers.md` § Permissions.
97
+ - **The Claude Code on the web setup script installs Node 24.** It installed vale, gh and jq but left the image's Node 20 / 22, below bkit's `>=24`. It now installs Node 24.21.0 into `/usr/local`, sha256-checked, at the same version and checksum as the Cursor Dockerfile, before corepack runs. A test fails when the two pins differ. Re-paste the setup script from `.claude/bkit-cloud.md`.
98
+ - **The cloud notes say where `.envrc` comes from.** With no `.envrc`, they said `bkit install` seeds one; it does not. They now say to copy `.bkit/templates/.envrc` to the repo root.
99
+ - **`bkit status` / `doctor` show the opencode model.** They read a top-level model from `.opencode/opencode.json`, which bkit never writes, so they always printed "model: unknown". They now read each agent's `model:` from `.opencode/agents/`.
100
+ - **Switching `--tracker` removes the old tracker's MCP entry.** Going from `linear` to `github` kept the `linear` entry in `.mcp.json`, `.cursor/mcp.json` and `.opencode/opencode.json`. Install now removes it when it still equals bkit's template; an entry you edited stays, with a warning. The `github` entry always stays: workflows fall back to it when `gh` is missing.
101
+ - **`bkit uninstall --opencode=<provider>` on the active provider keeps `bkit check` green.** It left that provider's model pins, so `bkit check` exited 1 until `bkit upgrade`. It now re-pins the opencode agents and commands to the first remaining provider.
102
+ - **`bkit upgrade --to=<version>` installs when only the source differs.** With `package.json` pointing bkit at a `file:` tarball, link, git or other non-registry spec of the same version, it printed "already at" and skipped `pnpm add`. It now bumps.
103
+ - **`bkit doctor` and `bkit check` help no longer says read-only.** Both rewrite `.bkit/advisories.md`; the help, `docs/setup.md` and `docs/deployments.md` now say so.
104
+ - **The pipeline reference lists the utility subagents.** `.bkit/pipeline.md` gains a Utilities section with the seven `bkit-utility-*` subagents, matching its "49 in total" count.
105
+
11
106
  ## [5.2.4] — 2026-10-17
12
107
 
13
108
  ### Added
@@ -997,7 +1092,7 @@ Patch release. bkit's canonical reference docs now land in a consumer's `.bkit/`
997
1092
 
998
1093
  ### Changed
999
1094
 
1000
- - **Schema-invariant DB checks reframed — pick the route by deploy topology, not by local pgTAP availability (consumer feedback from gether; refines [#203](https://github.com/cbartens/bkit/issues/203)).** pgTAP and the `@live` catalog-RPC are now presented as two co-equal routes rather than "canonical" vs "remote-only fallback". pgTAP runs against a CI-local fixture built from `supabase/migrations` (fast, hermetic, offline — but can stay green while prod drifts); the `@live` catalog-RPC validates the **real deployed schema** in `bkit-tests-live` and is the recommended default once a consumer has a deploy + `@live` tier (RLS/tenancy invariants especially). Reworded across the three surfaces — the template `ci.yml` stubs (incl. the JOB 3 `@live` block), the `test-db` install/check advisory, and `docs/testing.md` (+ template). Framing/docs only; no scaffold behaviour change.
1095
+ - **Schema-invariant DB checks reframed — pick the route by deploy topology, not by local pgTAP availability (consumer feedback from consumer-a; refines [#203](https://github.com/cbartens/bkit/issues/203)).** pgTAP and the `@live` catalog-RPC are now presented as two co-equal routes rather than "canonical" vs "remote-only fallback". pgTAP runs against a CI-local fixture built from `supabase/migrations` (fast, hermetic, offline — but can stay green while prod drifts); the `@live` catalog-RPC validates the **real deployed schema** in `bkit-tests-live` and is the recommended default once a consumer has a deploy + `@live` tier (RLS/tenancy invariants especially). Reworded across the three surfaces — the template `ci.yml` stubs (incl. the JOB 3 `@live` block), the `test-db` install/check advisory, and `docs/testing.md` (+ template). Framing/docs only; no scaffold behaviour change.
1001
1096
 
1002
1097
  ---
1003
1098
 
@@ -1084,7 +1179,7 @@ Major consolidation release. Three structural shifts land together: bkit's own m
1084
1179
  ### Fixed
1085
1180
 
1086
1181
  - **2.8.0 shipped prose that failed bkit's own Vale write-good gate, blocking consumer upgrade commits (issue [#195](https://github.com/cbartens/bkit/issues/195)).** `docs/deployments.md` contained a sentence-initial "So" — a pattern flagged by the write-good `StartsWith` rule that bkit ships and consumers run on every commit/push. The root cause was a lint asymmetry: bkit's own `lint:prose` script covered only `docs/knowledge.md`, not the full `docs/*.md` corpus, so the prose bkit was authoring and shipping was never linted by the same gate bkit imposes on consumers. Fixed by rewording the offending sentence ("So" → "This means") in both `docs/deployments.md` and its shipped template source, and widening `lint:prose` in bkit's own `package.json` to cover `docs/*.md` and `.agents/templates/docs/**` (parity with the consumer gate). Consumers re-run `pnpm bkit upgrade` to reconverge `docs/deployments.md` with zero drift (verified live).
1087
- - **bkit's own `lint:prose` did not cover the shipped template docs (issue [#195](https://github.com/cbartens/bkit/issues/195)).** `.agents/templates/docs/**` was absent from the Vale glob, meaning prose regressions in template sources were invisible until a consumer installed them. The template docs are now included in bkit's lint pass. KN-29 records the lint-asymmetry root cause and Vale `gether` config learnings for future reference.
1182
+ - **bkit's own `lint:prose` did not cover the shipped template docs (issue [#195](https://github.com/cbartens/bkit/issues/195)).** `.agents/templates/docs/**` was absent from the Vale glob, meaning prose regressions in template sources were invisible until a consumer installed them. The template docs are now included in bkit's lint pass. KN-29 records the lint-asymmetry root cause and Vale `consumer-a` config learnings for future reference.
1088
1183
  - **Shipped `.vale.ini` lacked write-good exemptions for `docs/plans/**`and`docs/notes.md`(issue [#195](https://github.com/cbartens/bkit/issues/195)).** LLM-generated plan documents and notes routinely contain phrasing that triggers write-good/LLMSlop rules. Without exemptions, consumers running`pnpm lint:prose`on a repo with bkit-generated plan docs would get false-positive failures. The shipped`.vale.ini`template (a`seedOrPrint`file — reaches new consumers on seed; existing consumers merge manually) now excludes`docs/plans/\*\*`and`docs/notes.md` from the write-good and LLMSlop style checks.
1089
1184
 
1090
1185
  ---
@@ -1436,7 +1531,7 @@ Major consolidation release. Three structural shifts land together: bkit's own m
1436
1531
  ### Added
1437
1532
 
1438
1533
  - **`utility-new-release` agent prompt** (`.claude/agents/utility-new-release.md` + `.agents/templates/`) — codifies the dev → main → tag → publish flow so future cuts avoid the KN-20 silent-skip trap (explicit scrubbed squash body, post-tag Release-workflow verification).
1439
- - **`lint-staged` adoption** — bkit pre-commit hook (consumer template + bkit-repo) now runs `pnpm lint-staged` so staged files are formatted via `prettier --write` at commit time. Pre-push keeps `pnpm format:check` as the safety net for hook-bypass cases (--no-verify, GitHub web edits, stale local config). Matches gether's pattern.
1534
+ - **`lint-staged` adoption** — bkit pre-commit hook (consumer template + bkit-repo) now runs `pnpm lint-staged` so staged files are formatted via `prettier --write` at commit time. Pre-push keeps `pnpm format:check` as the safety net for hook-bypass cases (--no-verify, GitHub web edits, stale local config). Matches consumer-a's pattern.
1440
1535
  - **`.lintstagedrc.json` seed** — `bkit install` writes the lint-staged config (`"*": "prettier --write --ignore-unknown"`) as Tier-3 (seed-or-print) and adds `lint-staged` to consumer devDependencies so the new pre-commit call resolves without manual setup.
1441
1536
 
1442
1537
  ### Changed