@cbartens/bkit 5.5.1 → 6.1.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 (425) hide show
  1. package/.bkit/README.md +167 -154
  2. package/.bkit/core/.agents/context.md +95 -29
  3. package/.bkit/core/.agents/docs.md +18 -15
  4. package/.bkit/core/.agents/plugins/bkit/hooks/bkit-gateguard.cjs +1 -0
  5. package/.bkit/core/.agents/plugins/bkit/hooks/bkit-guardrails.cjs +6 -5
  6. package/.bkit/core/.agents/plugins/bkit/hooks/bkit-readguard.cjs +1 -0
  7. package/.bkit/core/.agents/plugins/bkit/hooks/bkit-rules.cjs +65 -0
  8. package/.bkit/core/.agents/rules.md +112 -102
  9. package/.bkit/core/.agents/skills.md +63 -15
  10. package/.bkit/core/.bkit/README.md +167 -154
  11. package/.bkit/core/.bkit/authoring.md +747 -0
  12. package/.bkit/core/.bkit/cli.md +407 -0
  13. package/.bkit/core/.bkit/cloud.md +283 -195
  14. package/.bkit/core/.bkit/comparison.md +45 -43
  15. package/.bkit/core/.bkit/install.md +166 -95
  16. package/.bkit/core/.bkit/jsonl.md +339 -196
  17. package/.bkit/core/.bkit/pipeline.md +142 -145
  18. package/.bkit/core/.bkit/prompts.md +295 -264
  19. package/.bkit/core/.bkit/providers.md +460 -277
  20. package/.bkit/core/.bkit/router.md +69 -0
  21. package/.bkit/core/.bkit/templates.md +530 -256
  22. package/.bkit/core/.bkit/trackers.md +116 -65
  23. package/.bkit/core/.bkit/workflows.md +742 -618
  24. package/.bkit/core/.claude/hooks/bkit-gateguard.cjs +2 -2
  25. package/.bkit/core/.claude/hooks/bkit-guardrails.cjs +3 -3
  26. package/.bkit/core/.claude/hooks/bkit-preflight.sh +45 -14
  27. package/.bkit/core/.codex/hooks/bkit-guardrails.cjs +3 -3
  28. package/.bkit/core/.codex/hooks/bkit-rules.cjs +57 -0
  29. package/.bkit/core/.cursor/hooks/bkit-guardrails.cjs +7 -7
  30. package/.bkit/core/.cursor/hooks/bkit-preflight.sh +47 -12
  31. package/.bkit/core/.opencode/plugin/bkit-rules.js +89 -0
  32. package/.bkit/core/AGENTS.md +6 -80
  33. package/.bkit/core/docs/templates/bkit-audit-accessibility.md +128 -130
  34. package/.bkit/core/docs/templates/bkit-audit-adoption.md +104 -94
  35. package/.bkit/core/docs/templates/bkit-audit-agents.md +96 -98
  36. package/.bkit/core/docs/templates/bkit-audit-aio-seo.md +100 -103
  37. package/.bkit/core/docs/templates/bkit-audit-analytics.md +141 -107
  38. package/.bkit/core/docs/templates/bkit-audit-annotations.md +99 -97
  39. package/.bkit/core/docs/templates/bkit-audit-app-performance.md +122 -121
  40. package/.bkit/core/docs/templates/bkit-audit-app-store.md +158 -101
  41. package/.bkit/core/docs/templates/bkit-audit-architecture.md +114 -96
  42. package/.bkit/core/docs/templates/bkit-audit-ci-performance.md +76 -97
  43. package/.bkit/core/docs/templates/bkit-audit-config.md +123 -101
  44. package/.bkit/core/docs/templates/bkit-audit-cost.md +86 -99
  45. package/.bkit/core/docs/templates/bkit-audit-coverage.md +76 -93
  46. package/.bkit/core/docs/templates/bkit-audit-database.md +102 -95
  47. package/.bkit/core/docs/templates/bkit-audit-dead-code.md +165 -108
  48. package/.bkit/core/docs/templates/bkit-audit-deferrals.md +115 -109
  49. package/.bkit/core/docs/templates/bkit-audit-dependencies.md +265 -113
  50. package/.bkit/core/docs/templates/bkit-audit-documentation.md +119 -118
  51. package/.bkit/core/docs/templates/bkit-audit-duplication.md +140 -111
  52. package/.bkit/core/docs/templates/bkit-audit-failures.md +111 -106
  53. package/.bkit/core/docs/templates/bkit-audit-flakes.md +100 -99
  54. package/.bkit/core/docs/templates/bkit-audit-gates.md +107 -103
  55. package/.bkit/core/docs/templates/bkit-audit-issues.md +105 -105
  56. package/.bkit/core/docs/templates/bkit-audit-llm.md +134 -85
  57. package/.bkit/core/docs/templates/bkit-audit-logs.md +124 -125
  58. package/.bkit/core/docs/templates/bkit-audit-models.md +99 -78
  59. package/.bkit/core/docs/templates/bkit-audit-privacy.md +56 -76
  60. package/.bkit/core/docs/templates/bkit-audit-prompts.md +63 -78
  61. package/.bkit/core/docs/templates/bkit-audit-red-team.md +125 -93
  62. package/.bkit/core/docs/templates/bkit-audit-reliability.md +97 -96
  63. package/.bkit/core/docs/templates/bkit-audit-repo.md +170 -98
  64. package/.bkit/core/docs/templates/bkit-audit-security.md +207 -121
  65. package/.bkit/core/docs/templates/bkit-audit-slop.md +78 -95
  66. package/.bkit/core/docs/templates/bkit-audit-testing.md +163 -139
  67. package/.bkit/core/docs/templates/bkit-audit-usability.md +114 -96
  68. package/.bkit/core/docs/templates/bkit-plan.md +158 -281
  69. package/.bkit/core/engine/checks/after/auth.ts +40 -37
  70. package/.bkit/core/engine/checks/after/ci-yml.ts +104 -31
  71. package/.bkit/core/engine/checks/after/github.ts +95 -17
  72. package/.bkit/core/engine/checks/after/index.ts +21 -8
  73. package/.bkit/core/engine/checks/after/suppression.ts +8 -5
  74. package/.bkit/core/engine/checks/after/tools.ts +125 -123
  75. package/.bkit/core/engine/checks/before/context-fetch.ts +227 -33
  76. package/.bkit/core/engine/checks/before/env.ts +3 -3
  77. package/.bkit/core/engine/checks/before/files.ts +5 -4
  78. package/.bkit/core/engine/checks/before/index.ts +25 -1
  79. package/.bkit/core/engine/checks/before/repo.ts +208 -2
  80. package/.bkit/core/engine/checks/status-holes.ts +916 -123
  81. package/.bkit/core/engine/checks/tips/catalogue.ts +82 -20
  82. package/.bkit/core/engine/checks/tips/detect.ts +66 -0
  83. package/.bkit/core/engine/checks/tips/index.ts +52 -11
  84. package/.bkit/core/engine/cli.ts +251 -130
  85. package/.bkit/core/engine/commands/analysis.ts +282 -199
  86. package/.bkit/core/engine/commands/ci/ci.ts +363 -29
  87. package/.bkit/core/engine/commands/ci/pins.ts +172 -0
  88. package/.bkit/core/engine/commands/ci/push-gate.ts +223 -0
  89. package/.bkit/core/engine/commands/comply.ts +77 -103
  90. package/.bkit/core/engine/commands/install/doctor.ts +2 -2
  91. package/.bkit/core/engine/commands/install/install.ts +57 -18
  92. package/.bkit/core/engine/commands/install/uninstall.ts +86 -55
  93. package/.bkit/core/engine/commands/install/upgrade.ts +32 -15
  94. package/.bkit/core/engine/commands/land.ts +139 -18
  95. package/.bkit/core/engine/commands/lib.ts +381 -22
  96. package/.bkit/core/engine/commands/registry.ts +10 -2
  97. package/.bkit/core/engine/commands/setup/setup.ts +8 -7
  98. package/.bkit/core/engine/commands/stats.ts +260 -0
  99. package/.bkit/core/engine/commands/tips.ts +10 -5
  100. package/.bkit/core/engine/commands/workflow/branches.ts +2215 -176
  101. package/.bkit/core/engine/commands/workflow/challenge.ts +748 -0
  102. package/.bkit/core/engine/commands/workflow/completeness.ts +109 -0
  103. package/.bkit/core/engine/commands/workflow/context.ts +1249 -47
  104. package/.bkit/core/engine/commands/workflow/counters.ts +483 -95
  105. package/.bkit/core/engine/commands/workflow/decisions.ts +585 -0
  106. package/.bkit/core/engine/commands/workflow/disk.ts +238 -56
  107. package/.bkit/core/engine/commands/workflow/fids.ts +811 -33
  108. package/.bkit/core/engine/commands/workflow/issues.ts +413 -64
  109. package/.bkit/core/engine/commands/workflow/ledgers.ts +1333 -36
  110. package/.bkit/core/engine/commands/workflow/locks.ts +28 -2
  111. package/.bkit/core/engine/commands/workflow/plan-blocks.ts +691 -0
  112. package/.bkit/core/engine/commands/workflow/plan-versions.ts +21 -0
  113. package/.bkit/core/engine/commands/workflow/plans.ts +257 -0
  114. package/.bkit/core/engine/commands/workflow/prs.ts +178 -33
  115. package/.bkit/core/engine/commands/workflow/repo.ts +66 -8
  116. package/.bkit/core/engine/commands/workflow/roadmap.ts +72 -22
  117. package/.bkit/core/engine/commands/workflow/run-facts.ts +492 -0
  118. package/.bkit/core/engine/commands/workflow/runs.ts +827 -79
  119. package/.bkit/core/engine/commands/workflow/runtime.ts +25 -1
  120. package/.bkit/core/engine/commands/workflow/skills.ts +1 -0
  121. package/.bkit/core/engine/commands/workflow/status.ts +329 -33
  122. package/.bkit/core/engine/commands/workflow/step-table.ts +381 -0
  123. package/.bkit/core/engine/commands/workflow/steps.ts +841 -105
  124. package/.bkit/core/engine/commands/workflow/summary-findings.ts +177 -0
  125. package/.bkit/core/engine/commands/workflow/summary.ts +544 -0
  126. package/.bkit/core/engine/commands/workflow/tasks.ts +409 -0
  127. package/.bkit/core/engine/commands/workflow/test-blocks.ts +254 -0
  128. package/.bkit/core/engine/commands/workflow/tests-changed.ts +201 -0
  129. package/.bkit/core/engine/commands/workflow/tests.ts +2124 -330
  130. package/.bkit/core/engine/commands/workflow/tracker.ts +1195 -0
  131. package/.bkit/core/engine/commands/workflow/workflows.ts +1197 -235
  132. package/.bkit/core/engine/commands/workflow/worktrees.ts +543 -24
  133. package/.bkit/core/engine/install/cloud-env.ts +251 -121
  134. package/.bkit/core/engine/install/context-ci-workflow.ts +102 -0
  135. package/.bkit/core/engine/install/manifest.ts +67 -17
  136. package/.bkit/core/engine/install/modules/antigravity.ts +3 -2
  137. package/.bkit/core/engine/install/modules/cloud.ts +24 -16
  138. package/.bkit/core/engine/install/modules/codex.ts +15 -2
  139. package/.bkit/core/engine/install/modules/core.ts +1196 -45
  140. package/.bkit/core/engine/install/modules/cursor.ts +6 -6
  141. package/.bkit/core/engine/install/modules/opencode.ts +18 -6
  142. package/.bkit/core/engine/install/template-notes.ts +130 -0
  143. package/.bkit/core/engine/install/version-file.ts +9 -4
  144. package/.bkit/core/engine/install/write.ts +5 -0
  145. package/.bkit/core/engine/ledgers/compact.ts +124 -0
  146. package/.bkit/core/engine/ledgers/journal.ts +291 -0
  147. package/.bkit/core/engine/ledgers/migrate.ts +92 -0
  148. package/.bkit/core/engine/ledgers/status.ts +249 -21
  149. package/.bkit/core/engine/ledgers/telemetry.ts +1397 -253
  150. package/.bkit/core/engine/render/hosts.ts +118 -14
  151. package/.bkit/core/engine/render/models.ts +12 -0
  152. package/.bkit/core/engine/shared/bkit-latest.ts +26 -4
  153. package/.bkit/core/engine/shared/branches.ts +4 -1
  154. package/.bkit/core/engine/shared/dep-updater.ts +60 -0
  155. package/.bkit/core/engine/shared/egress.ts +8 -1
  156. package/.bkit/core/engine/shared/json.ts +25 -7
  157. package/.bkit/core/engine/shared/package-manager.ts +9 -0
  158. package/.bkit/core/engine/shared/settings.ts +243 -31
  159. package/.bkit/core/engine/shared/text.ts +361 -0
  160. package/.bkit/core/engine/shared/timeouts.ts +2 -0
  161. package/.bkit/core/engine/tools/cli-doc.ts +111 -0
  162. package/.bkit/core/engine/tools/grammar-density.ts +215 -0
  163. package/.bkit/core/engine/tools/instructions-sources.ts +832 -0
  164. package/.bkit/core/engine/tools/instructions.ts +1802 -0
  165. package/.bkit/core/hooks/antigravity-hook.js +25 -10
  166. package/.bkit/core/hooks/gateguard-engine.js +54 -29
  167. package/.bkit/core/hooks/guardrails-shell.js +4 -5
  168. package/.bkit/core/hooks/guardrails-tiers.js +10 -4
  169. package/.bkit/core/hooks/preflight-linear.sh +9 -9
  170. package/.bkit/core/hooks/preflight-rules.sh +8 -0
  171. package/.bkit/core/hooks/readguard-engine.js +29 -10
  172. package/.bkit/core/hooks/session-rules-advisory.js +61 -0
  173. package/.bkit/core/prompts/bkit-audit-generate.md +202 -94
  174. package/.bkit/core/prompts/bkit-build-challenge-1.md +76 -34
  175. package/.bkit/core/prompts/bkit-build-challenge-2.md +85 -38
  176. package/.bkit/core/prompts/bkit-build-install-skills.md +50 -28
  177. package/.bkit/core/prompts/bkit-build-plan-convert.md +85 -0
  178. package/.bkit/core/prompts/bkit-build-plan-current.md +59 -36
  179. package/.bkit/core/prompts/bkit-build-plan-gaps-remediate.md +101 -36
  180. package/.bkit/core/prompts/bkit-build-plan-tasks.md +149 -0
  181. package/.bkit/core/prompts/bkit-build-plan-tests.md +120 -0
  182. package/.bkit/core/prompts/bkit-build-plan-verify.md +104 -43
  183. package/.bkit/core/prompts/bkit-debug-abort-handover.md +47 -32
  184. package/.bkit/core/prompts/bkit-debug-failure-diagnose.md +109 -57
  185. package/.bkit/core/prompts/bkit-debug-failure-remediate.md +65 -39
  186. package/.bkit/core/prompts/bkit-debug-failure-reproduce.md +53 -31
  187. package/.bkit/core/prompts/bkit-debug-failure-soak.md +65 -34
  188. package/.bkit/core/prompts/bkit-design-brainstorm-ideate-1.md +46 -31
  189. package/.bkit/core/prompts/bkit-design-brainstorm-ideate-2.md +45 -31
  190. package/.bkit/core/prompts/bkit-design-brainstorm-ideate-3.md +43 -30
  191. package/.bkit/core/prompts/bkit-design-generate.md +80 -46
  192. package/.bkit/core/prompts/bkit-design-organise.md +83 -32
  193. package/.bkit/core/prompts/bkit-design-review-1.md +70 -50
  194. package/.bkit/core/prompts/bkit-design-review-2.md +65 -46
  195. package/.bkit/core/prompts/bkit-design-spike.md +64 -40
  196. package/.bkit/core/prompts/bkit-design-update.md +53 -28
  197. package/.bkit/core/prompts/bkit-plan-generate.md +101 -29
  198. package/.bkit/core/prompts/bkit-plan-review-1.md +78 -41
  199. package/.bkit/core/prompts/bkit-plan-review-2.md +78 -35
  200. package/.bkit/core/prompts/bkit-plan-scope-check.md +116 -0
  201. package/.bkit/core/prompts/bkit-plan-update.md +86 -31
  202. package/.bkit/core/prompts/bkit-ship-conflict-resolve.md +94 -50
  203. package/.bkit/core/prompts/bkit-ship-deferred-sweep.md +91 -41
  204. package/.bkit/core/prompts/bkit-ship-update-docs.md +45 -24
  205. package/.bkit/core/prompts/bkit-utility-compress-markdown.md +65 -49
  206. package/.bkit/core/prompts/bkit-utility-update-decisions.md +87 -42
  207. package/.bkit/core/prompts/bkit-utility-update-deferrals.md +81 -37
  208. package/.bkit/core/prompts/bkit-utility-update-documentation.md +43 -25
  209. package/.bkit/core/prompts/bkit-utility-update-failures.md +84 -37
  210. package/.bkit/core/prompts/bkit-utility-update-knowledge.md +88 -42
  211. package/.bkit/core/prompts/bkit-utility-update-roadmap.md +92 -39
  212. package/.bkit/core/prompts/bkit-utility-update-tracker.md +159 -60
  213. package/.bkit/core/workflows/bkit-auto.md +89 -58
  214. package/.bkit/core/workflows/bkit-build.md +967 -517
  215. package/.bkit/core/workflows/bkit-debug.md +555 -387
  216. package/.bkit/core/workflows/bkit-design.md +319 -283
  217. package/.bkit/core/workflows/bkit-plan.md +319 -342
  218. package/.bkit/core/workflows/bkit-ship.md +525 -328
  219. package/.bkit/shared/.agents/plugins/bkit/hooks.json +10 -0
  220. package/.bkit/shared/.bkit/.env.example +2 -2
  221. package/.bkit/shared/.claude/bkit-cloud.md +12 -10
  222. package/.bkit/shared/.claude/settings.json +14 -0
  223. package/.bkit/shared/.codex/bkit-cloud.md +98 -0
  224. package/.bkit/shared/.codex/hooks.json +20 -0
  225. package/.bkit/shared/.cursor/bkit-cloud.md +3 -3
  226. package/.bkit/shared/.cursor/mcp.json +1 -1
  227. package/.bkit/shared/.cursor/rules/bkit-rules.mdc +1 -1
  228. package/.bkit/shared/.gitattributes +1 -1
  229. package/.bkit/shared/.mcp.json +1 -1
  230. package/.bkit/shared/.opencode/opencode.json +12 -1
  231. package/.bkit/shared/CLAUDE.md +6 -2
  232. package/.bkit/shared/GEMINI.md +5 -2
  233. package/.bkit/shared/docs/architecture.md +4 -7
  234. package/.bkit/shared/docs/data-schema.md +4 -7
  235. package/.bkit/shared/docs/deployments.md +241 -168
  236. package/.bkit/shared/docs/design.md +11 -12
  237. package/.bkit/shared/docs/noise.md +8 -7
  238. package/.bkit/shared/docs/observability.md +5 -8
  239. package/.bkit/shared/docs/security.md +35 -17
  240. package/.bkit/shared/docs/setup.md +29 -18
  241. package/.bkit/shared/docs/technology.md +3 -6
  242. package/.bkit/shared/docs/testing.md +289 -174
  243. package/.bkit/shared/gitignore +6 -2
  244. package/.bkit/templates/.claude/hooks/bkit-cloud-bootstrap.sh +15 -16
  245. package/.bkit/templates/.cursor/Dockerfile +12 -8
  246. package/.bkit/templates/.cursor/environment.json +1 -1
  247. package/.bkit/templates/.github/ISSUE_TEMPLATE/bkit-bug.yml +10 -8
  248. package/.bkit/templates/.github/ISSUE_TEMPLATE/bkit-change.yml +45 -12
  249. package/.bkit/templates/.github/ISSUE_TEMPLATE/bkit-idea.yml +3 -3
  250. package/.bkit/templates/.github/renovate.json5 +34 -6
  251. package/.bkit/templates/.github/workflows/bkit-ci.yml +54 -51
  252. package/.bkit/templates/.github/workflows/bkit-cloud.yml +34 -33
  253. package/.bkit/templates/.github/workflows/bkit-health.yml +97 -0
  254. package/.bkit/templates/.github/workflows/bkit-renovate.yml +5 -4
  255. package/.bkit/templates/.github/workflows/bkit-trivy.yml +5 -4
  256. package/.bkit/templates/.husky/pre-commit +2 -2
  257. package/.bkit/templates/.husky/pre-push +96 -36
  258. package/.bkit/templates/.prettierignore +6 -0
  259. package/.bkit/templates/.vale.ini +27 -27
  260. package/.bkit/templates/context/bkit-cloudrun.md +23 -15
  261. package/.bkit/templates/context/bkit-expo.md +70 -52
  262. package/.bkit/templates/context/bkit-github.md +93 -56
  263. package/.bkit/templates/context/bkit-inngest.md +21 -15
  264. package/.bkit/templates/context/bkit-maestro.md +22 -16
  265. package/.bkit/templates/context/bkit-playwright.md +23 -17
  266. package/.bkit/templates/context/bkit-resend.md +12 -10
  267. package/.bkit/templates/context/bkit-sentry.md +30 -20
  268. package/.bkit/templates/context/bkit-serena.md +8 -7
  269. package/.bkit/templates/context/bkit-stripe.md +14 -13
  270. package/.bkit/templates/context/bkit-supabase.md +16 -13
  271. package/.bkit/templates/context/bkit-tavily.md +14 -11
  272. package/.bkit/templates/context/bkit-vercel.md +27 -18
  273. package/.bkit/templates/docs/capabilities.md +15 -14
  274. package/.bkit/templates/scripts/ci/{check-accepted-divergences.mjs → bkit-check-accepted-divergences.mjs} +6 -3
  275. package/.bkit/templates/scripts/ci/{check-accepted-divergences.test.mjs → bkit-check-accepted-divergences.test.mjs} +3 -3
  276. package/.bkit/templates/scripts/ci/{check-capstone.mjs → bkit-check-capstone.mjs} +2 -2
  277. package/.bkit/templates/scripts/ci/{check-capstone.test.mjs → bkit-check-capstone.test.mjs} +4 -4
  278. package/.bkit/templates/scripts/ci/{check-dependency-audit.mjs → bkit-check-dependency-audit.mjs} +103 -18
  279. package/.bkit/templates/scripts/ci/{check-dependency-audit.test.mjs → bkit-check-dependency-audit.test.mjs} +31 -3
  280. package/.bkit/templates/scripts/ci/bkit-machine-lock.sh +387 -0
  281. package/.bkit/templates/scripts/ci/bkit-test-awake.mjs +75 -0
  282. package/.bkit/templates/scripts/ci/bkit-test-awake.test.mjs +160 -0
  283. package/.bkit/templates/scripts/ci/lanes/{resolve-push-base.mjs → bkit-resolve-push-base.mjs} +3 -3
  284. package/.bkit/templates/scripts/ci/lanes/{resolve-push-base.test.mjs → bkit-resolve-push-base.test.mjs} +4 -4
  285. package/.bkit/templates/scripts/cleanup/bkit-disk-prune.mjs +10 -2
  286. package/.bkit/templates/scripts/graphify/bkit-graph-drift.py +1 -1
  287. package/.bkit/templates/scripts/graphify/bkit-graph-eager.py +3 -3
  288. package/.bkit/templates/scripts/graphify/bkit-graph-embed.py +63 -0
  289. package/.bkit/templates/scripts/graphify/bkit-graph-imports.py +2 -2
  290. package/.bkit/templates/scripts/graphify/bkit-graph-pre-push.sh +69 -18
  291. package/.bkit/templates/scripts/graphify/bkit-graph-repair.py +3 -3
  292. package/.bkit/templates/scripts/graphify/bkit-graph-surface.py +1 -1
  293. package/.bkit/templates/scripts/graphify/bkit-graphify-graphml.py +1 -1
  294. package/.bkit/templates/scripts/graphify/bkit-graphify-rollup.py +197 -126
  295. package/.bkit/templates/scripts/graphify/bkit-graphify.sh +64 -41
  296. package/.bkit/templates/scripts/slop/bkit-slop-type-suppression.mjs +23 -7
  297. package/.bkit/templates/slop-scan.config.json +9 -2
  298. package/CHANGELOG.md +231 -0
  299. package/README.md +278 -89
  300. package/dist/checks/after/auth.js +36 -33
  301. package/dist/checks/after/ci-yml.js +91 -30
  302. package/dist/checks/after/github.js +91 -17
  303. package/dist/checks/after/index.js +22 -11
  304. package/dist/checks/after/suppression.js +8 -5
  305. package/dist/checks/after/tools.js +111 -114
  306. package/dist/checks/before/context-fetch.js +218 -33
  307. package/dist/checks/before/env.js +3 -3
  308. package/dist/checks/before/files.js +5 -3
  309. package/dist/checks/before/index.js +20 -3
  310. package/dist/checks/before/repo.js +197 -2
  311. package/dist/checks/status-holes.js +739 -114
  312. package/dist/checks/tips/catalogue.js +70 -19
  313. package/dist/checks/tips/detect.js +62 -0
  314. package/dist/checks/tips/index.js +51 -9
  315. package/dist/cli.js +234 -124
  316. package/dist/commands/analysis.js +174 -141
  317. package/dist/commands/ci/ci.js +302 -25
  318. package/dist/commands/ci/pins.js +142 -0
  319. package/dist/commands/ci/push-gate.js +194 -0
  320. package/dist/commands/comply.js +54 -91
  321. package/dist/commands/install/doctor.js +2 -2
  322. package/dist/commands/install/install.js +50 -19
  323. package/dist/commands/install/uninstall.js +82 -55
  324. package/dist/commands/install/upgrade.js +21 -11
  325. package/dist/commands/land.js +137 -17
  326. package/dist/commands/lib.js +295 -21
  327. package/dist/commands/registry.js +10 -2
  328. package/dist/commands/setup/setup.js +8 -7
  329. package/dist/commands/stats.js +175 -0
  330. package/dist/commands/tips.js +7 -3
  331. package/dist/commands/workflow/branches.js +1873 -152
  332. package/dist/commands/workflow/challenge.js +609 -0
  333. package/dist/commands/workflow/completeness.js +97 -0
  334. package/dist/commands/workflow/context.js +1045 -46
  335. package/dist/commands/workflow/counters.js +385 -86
  336. package/dist/commands/workflow/decisions.js +484 -0
  337. package/dist/commands/workflow/disk.js +214 -56
  338. package/dist/commands/workflow/fids.js +706 -33
  339. package/dist/commands/workflow/issues.js +349 -59
  340. package/dist/commands/workflow/ledgers.js +1123 -37
  341. package/dist/commands/workflow/locks.js +26 -2
  342. package/dist/commands/workflow/plan-blocks.js +501 -0
  343. package/dist/commands/workflow/plan-versions.js +22 -0
  344. package/dist/commands/workflow/plans.js +205 -0
  345. package/dist/commands/workflow/prs.js +154 -35
  346. package/dist/commands/workflow/repo.js +58 -8
  347. package/dist/commands/workflow/roadmap.js +58 -23
  348. package/dist/commands/workflow/run-facts.js +421 -0
  349. package/dist/commands/workflow/runs.js +670 -72
  350. package/dist/commands/workflow/runtime.js +15 -1
  351. package/dist/commands/workflow/skills.js +1 -0
  352. package/dist/commands/workflow/status.js +282 -34
  353. package/dist/commands/workflow/step-table.js +308 -0
  354. package/dist/commands/workflow/steps.js +703 -96
  355. package/dist/commands/workflow/summary-findings.js +117 -0
  356. package/dist/commands/workflow/summary.js +388 -0
  357. package/dist/commands/workflow/tasks.js +378 -0
  358. package/dist/commands/workflow/test-blocks.js +231 -0
  359. package/dist/commands/workflow/tests-changed.js +172 -0
  360. package/dist/commands/workflow/tests.js +1695 -305
  361. package/dist/commands/workflow/tracker.js +983 -0
  362. package/dist/commands/workflow/workflows.js +1014 -222
  363. package/dist/commands/workflow/worktrees.js +432 -26
  364. package/dist/install/cloud-env.js +233 -99
  365. package/dist/install/context-ci-workflow.js +85 -0
  366. package/dist/install/manifest.js +64 -17
  367. package/dist/install/modules/antigravity.js +3 -2
  368. package/dist/install/modules/cloud.js +25 -16
  369. package/dist/install/modules/codex.js +12 -2
  370. package/dist/install/modules/core.js +1090 -48
  371. package/dist/install/modules/cursor.js +6 -6
  372. package/dist/install/modules/opencode.js +13 -7
  373. package/dist/install/template-notes.js +116 -0
  374. package/dist/install/version-file.js +9 -4
  375. package/dist/ledgers/compact.js +87 -0
  376. package/dist/ledgers/journal.js +233 -0
  377. package/dist/ledgers/migrate.js +81 -0
  378. package/dist/ledgers/status.js +176 -13
  379. package/dist/ledgers/telemetry.js +1010 -125
  380. package/dist/render/hosts.js +104 -14
  381. package/dist/render/models.js +12 -0
  382. package/dist/shared/bkit-latest.js +26 -4
  383. package/dist/shared/branches.js +3 -1
  384. package/dist/shared/dep-updater.js +49 -0
  385. package/dist/shared/egress.js +8 -1
  386. package/dist/shared/json.js +20 -7
  387. package/dist/shared/package-manager.js +6 -0
  388. package/dist/shared/settings.js +181 -24
  389. package/dist/shared/text.js +333 -0
  390. package/dist/shared/timeouts.js +2 -0
  391. package/dist/tools/cli-doc.js +97 -0
  392. package/dist/tools/grammar-density.js +183 -0
  393. package/dist/tools/instructions-sources.js +720 -0
  394. package/dist/tools/instructions.js +1623 -0
  395. package/package.json +156 -51
  396. package/.bkit/core/.bkit/lite.md +0 -73
  397. package/.bkit/core/engine/commands/harvest.ts +0 -459
  398. package/.bkit/core/engine/commands/workflow/workstreams.ts +0 -166
  399. package/.bkit/core/engine/tools/wording.ts +0 -748
  400. package/.bkit/core/prompts/bkit-build-challenge-reconcile.md +0 -69
  401. package/.bkit/core/prompts/bkit-build-challenge-remediate.md +0 -71
  402. package/.bkit/core/prompts/bkit-build-challenge-tests.md +0 -74
  403. package/.bkit/core/prompts/bkit-build-plan-execute.md +0 -76
  404. package/.bkit/core/prompts/bkit-build-summary.md +0 -94
  405. package/.bkit/core/prompts/bkit-debug-summary.md +0 -96
  406. package/.bkit/core/prompts/bkit-design-summary.md +0 -107
  407. package/.bkit/core/prompts/bkit-plan-complexity-check.md +0 -67
  408. package/.bkit/core/prompts/bkit-plan-complexity-split.md +0 -88
  409. package/.bkit/core/prompts/bkit-plan-review-3.md +0 -93
  410. package/.bkit/core/prompts/bkit-plan-scope-check-1.md +0 -85
  411. package/.bkit/core/prompts/bkit-plan-scope-check-2.md +0 -85
  412. package/.bkit/core/prompts/bkit-plan-summary.md +0 -107
  413. package/.bkit/core/prompts/bkit-ship-summary.md +0 -78
  414. package/.bkit/templates/scripts/ci/bkit-local-stack-lock.sh +0 -194
  415. package/dist/commands/harvest.js +0 -353
  416. package/dist/commands/workflow/workstreams.js +0 -143
  417. package/dist/tools/wording.js +0 -680
  418. /package/.bkit/templates/.vale/styles/{House → Bkit}/Filler.yml +0 -0
  419. /package/.bkit/templates/.vale/styles/{House → Bkit}/Hedging.yml +0 -0
  420. /package/.bkit/templates/.vale/styles/{House → Bkit}/LLMSlop.yml +0 -0
  421. /package/.bkit/templates/.vale/styles/{House → Bkit}/Verbose.yml +0 -0
  422. /package/.bkit/templates/scripts/ci/{accepted-advisories.json → bkit-accepted-advisories.json} +0 -0
  423. /package/.bkit/templates/scripts/ci/{accepted-divergences.json → bkit-accepted-divergences.json} +0 -0
  424. /package/.bkit/templates/scripts/launchd/{launchd.env.example → bkit-launchd.env.example} +0 -0
  425. /package/.bkit/templates/scripts/launchd/{ai.bkit.launchd.plist → bkit-launchd.plist} +0 -0
@@ -1,59 +1,55 @@
1
- <!-- Note: Reports live at `docs/audits/{YYYYMM}/{slug}.md`. `{YYYYMM}` = UTC month of this run. `{slug}` = template basename without `bkit-audit-` and `.md`. **If** that month already has `{slug}.md` or `{slug}-{TIMESTAMP}.md` → write `{slug}-{TIMESTAMP}.md` (`{TIMESTAMP}` = `date -u +%Y%m%dT%H%M%SZ`). Never overwrite. The report is stamped with a `bkit:anchor` block recording the audited commit (`baseSha`) and branch (`baseRef`); never hand-author or edit it. `@bkit-audit-generate` fills this template. -->
2
-
3
1
  <!-- bkit:start -->
4
2
 
5
3
  {{BKIT_MANAGED_MARKER}}
6
4
 
5
+ <!-- Note: @bkit-audit-generate fills this template. The report lives at `docs/audits/{YYYYMM}/{slug}.md`, where `{YYYYMM}` is the UTC month of the run and `{slug}` is this file's name without `bkit-audit-` and `.md`. **If** that month already has `{slug}.md` or `{slug}-{TIMESTAMP}.md` → write `{slug}-{TIMESTAMP}.md`, where `{TIMESTAMP}` is the output of `date -u +%Y%m%dT%H%M%SZ`. NEVER overwrite an earlier report. The report is stamped with a `bkit:anchor` block that records the audited commit (`baseSha`) and branch (`baseRef`). NEVER write or edit that block by hand. -->
6
+
7
7
  # Log Triage
8
8
 
9
9
  > [!CAUTION]
10
- > **Purpose:** Judge the error-tracker stream and runtime logs it cannot see: real issues, wrong level, failures that never arrived.
10
+ > **Purpose:** A judgement on the error-tracker stream and on the runtime logs it cannot see: real issues, the wrong level, and failures that never arrived.
11
11
  >
12
12
  > **Rules:**
13
13
  >
14
- > - Read-only audit; never edit code, config, or data.
15
- > - `Universal Instructions` apply to all projects; `Project Instructions` apply only to this project.
16
- > - Local audit instructions / overrides → `Project Instructions` below the bkit-managed block; universal instructions stay in-block.
17
- > - Any tools mentioned in `Universal Instructions` are examples only; swap for actual tools in final output; drop inapplicable.
18
- > - Use dense token-efficient phrasing; no filler / hedging / restating; tables > prose, bullets > paragraphs.
19
- > - Read `.agents/docs.md` → load docs for workflow / step / task; skip missing; cite docs inline where required.
20
- > - Every claim cites this run's evidence (`file:line`, or command / query and its output) and tool behind it; a previous report's figure, list, or status is a lead, not evidence.
21
- > - Read this document once at session start; do not trust session memory; do not re-read on every loop iteration.
22
- > - never resolve, archive, mute, or edit tracker issues, dashboards, alert rules, or sample rates.
23
- > - never copy log free text, an event payload, or a personal-data value into the report. Cite ids, status codes, error codes, and timestamps.
24
- > - Before first vendor-config or error-text read → name fields that can carry credentials (e.g. request headers in monitor config, URLs with query tokens, error messages echoing a request). Field decides, not value shape: value with no secret prefix still counts. Report field and class only (e.g. `auth header present`), never value.
14
+ > - NEVER resolve, archive, mute or edit tracker issues, dashboards, alert rules or sample rates.
15
+ > - NEVER copy log free text, an event payload or a personal-data value into the report.
16
+ > - Cite ids, status codes, error codes and timestamps instead.
17
+ > - Before the first read of vendor config or error text, name the fields that can carry credentials (e.g., request headers in monitor config, URLs with query tokens, error messages that echo a request).
18
+ > - The field decides, not the shape of the value: a value with no secret prefix still counts.
19
+ > - Report the field and its class only (e.g., `auth header present`), NEVER the value.
25
20
 
26
21
  ## Universal Instructions
27
22
 
28
23
  ### Context & Goals
29
24
 
30
- An error tracker does not distinguish a bug from a handled outcome logged at error. Both arrive unresolved; the second kind is usually most of the stream. Target failure: **noise that trains people to ignore the board, so the one real defect goes unread.**
25
+ An error tracker does not tell a bug apart from a handled outcome logged at error. Both arrive unresolved, and the second kind is usually most of the stream. The failure this audit targets is noise that trains people to ignore the board, so the one real defect goes unread.
31
26
 
32
- **Applies when:** error tracker, runtime logs, or both. None → one `N/A` row with evidence, never "clean".
27
+ **Applies when:** the project has an error tracker, runtime logs, or both. **If** it has neither → write one `N/A` row with its evidence, and never report the surface as "clean".
33
28
 
34
- **Cadence:** every two weeks, whole window since previous report. Extra pass: after release on a rail with no other coverage; when production event count > zero; after vendor status incident while those logs still hold it. Retention shorter than interval = finding → drain or shorter cadence.
29
+ **Cadence:** Run once every two weeks, over the whole window since the previous report. Run an extra pass in each of these three cases: (1) after a release on a rail with no other coverage; (2) when the production event count is above zero; (3) after a vendor status incident, while the logs still hold it. **If** log retention is shorter than the interval → it is a finding; propose a drain or a shorter cadence.
35
30
 
36
- **Anchor Standards:** record version and date read. Newer version → `Standards` step reads what changed.
31
+ **Anchor Standards:**
37
32
 
38
- - Error-tracker release health (e.g. Sentry). Record SDK versions; unversioned docs record the date read.
39
- - Source maps and debug symbols (e.g. Sentry Debug IDs, Hermes maps, dSYM, ProGuard).
40
- - Event grouping, fingerprints, and stack-trace rules (e.g. Sentry).
41
- - Ownership rules (e.g. Sentry ownership, a CODEOWNERS import).
42
- - Quotas and spike protection (e.g. Sentry).
33
+ - Error-tracker release health (e.g., Sentry). Record SDK versions; unversioned docs record the date read.
34
+ - Source maps and debug symbols (e.g., Sentry Debug IDs, Hermes maps, dSYM, ProGuard).
35
+ - Event grouping, fingerprints, and stack-trace rules (e.g., Sentry).
36
+ - Ownership rules (e.g., Sentry ownership, a CODEOWNERS import).
37
+ - Quotas and spike protection (e.g., Sentry).
43
38
  - OpenTelemetry semantic conventions, including GenAI; record the semconv version.
44
39
  - W3C Trace Context, Level 1.
45
- - Alerting on SLOs (e.g. Google SRE Workbook, "Alerting on SLOs").
40
+ - Alerting on SLOs (e.g., Google SRE Workbook, "Alerting on SLOs").
46
41
  - bkit block of `docs/observability.md` (bkit version from `.bkit/version`): every rule and section
47
42
  - bkit block of `docs/noise.md` (bkit version from `.bkit/version`): every rule and section
48
43
 
49
44
  ### Scope
50
45
 
51
- - Unresolved tracker issues over the window: verdict, root cause, blast radius, disposition.
52
- - Stream trust: symbolication, release, environment, dropped events, grouping, ownership.
53
- - Personal data the tracker stores.
54
- - Swallowed errors in code behind this sweep's issues; user reports with no event.
55
- - Runtime logs the tracker cannot see: retention vs cadence, match to tracker, trace correlation.
56
- - Uptime monitors, cron coverage, alert routing, alert quality, on-call.
46
+ - Give each unresolved tracker issue in the window a verdict, a root cause, a blast radius and a disposition.
47
+ - Check that the stream can be trusted: symbolication, release, environment, dropped events, grouping and ownership.
48
+ - Check the personal data the tracker stores.
49
+ - Find swallowed errors in the code behind this sweep's issues.
50
+ - Find user reports with no event.
51
+ - Read the runtime logs the tracker cannot see: retention against cadence, the match to the tracker, and trace correlation.
52
+ - Check uptime monitors, cron coverage, alert routing, alert quality and on-call.
57
53
 
58
54
  ### Out of Scope
59
55
 
@@ -69,115 +65,116 @@ An error tracker does not distinguish a bug from a handled outcome logged at err
69
65
 
70
66
  ### Verdicts
71
67
 
72
- One per unresolved issue. Verdict decides everything downstream.
68
+ Give each unresolved issue one verdict. The verdict decides everything downstream.
73
69
 
74
- - **GENUINE ERROR:** unhandled failure, or handled with wrong handling. Root-cause it. Fix = next step.
75
- - **WRONG LEVEL:** working as intended, filed at error: 2xx response, guard did its job, or docblock documents branch. Recommend level change. Do not edit call site.
76
- - **NOISE:** vendor or infrastructure, no app call site (SDK internals, tunnel egress, platform insight). Recommend tracker-side filter (e.g. `beforeSend` denylist) and `docs/noise.md` row. Do not add filter here. Denylist = vendor frames with no call site, not app code.
77
- - **OTHER:** fits none. Say why and what the issue needs. Same `OTHER` on 2 runs → propose new verdict in `Process Improvements`.
70
+ - **GENUINE ERROR:** an unhandled failure, or a failure handled the wrong way. Root-cause it. The fix is the next step.
71
+ - **WRONG LEVEL:** the code works as intended but is filed at error: a 2xx response, a guard that did its job, or a branch its docblock documents. Recommend a level change. Do not edit the call site.
72
+ - **NOISE:** the event comes from a vendor or infrastructure, with no app call site (SDK internals, tunnel egress, platform insight). Recommend a tracker-side filter (e.g., a `beforeSend` denylist) and a `docs/noise.md` row. Do not add the filter here. The denylist holds vendor frames with no call site, not app code.
73
+ - **OTHER:** it fits no other verdict. Say why and what the issue needs. **If** the same `OTHER` shows up on 2 runs → propose a new verdict in `Process Improvements`.
78
74
 
79
75
  A test-origin tag narrows the lane. It does not make something noise, and it does not lower severity.
80
76
 
81
77
  ### Pre-Flight / Dependencies
82
78
 
83
- **Checkpoint:** Check off all core items. Check conditional items only when applicable. Each item: available → tool and version; missing → fallback, gap in `Not Checked`, fix in `Process Improvements`. Unnamed gap reads as passed. never abort for a missing capability.
84
-
85
- **Credentials:** probe direnv before marking a token / env var missing: `direnv exec . sh -c '[ -n "${VAR}" ] && echo set || echo unset'`; `unset` = missing. Run credentialed CLIs as `direnv exec . <cmd>`. No direnv (cloud session) → plain env check. Report names, never values.
86
-
87
79
  #### Core
88
80
 
89
- Always verify.
90
-
91
- - [ ] **Permissions:** Before Step 1 — one cheap read-only call per tool this run uses (every item below, every rule under `Project Instructions` `Permissions`), e.g. `gh run list --limit 1`, one MCP read, one anchor-standard fetch. Blocked / denied (here or in any step) → record call verbatim and narrow allow rule clearing it (e.g. `Bash(gh run list *)`) in `Not Checked`, `Process Improvements`, and `Project Instructions` `Permissions`; run every step the remaining tools allow; work needing blocked call → `Not Checked`. never stop the run for a blocked call; never retry or reword a blocked call to get past it.
92
- - [ ] **Error Tracker:** Steps 3–9 — read-only issue, event, and alert APIs, e.g. tracker MCP, REST. Fallback: skip tracker steps; runtime-log steps still run; tracker sections `Not Checked`. Never "clean".
93
- - [ ] **Web:** Step 13 — fetch anchor standards. Fallback: versions recorded as unread.
81
+ - [ ] **Permissions:** every blocked call is recorded.
82
+ - [ ] **Error Tracker:** Steps 3-9 — read-only issue, event and alert APIs (e.g., tracker MCP, REST). Fallback: skip the tracker steps, still run the runtime-log steps, and mark the tracker sections `Not Checked`. Never report them as "clean".
83
+ - [ ] **Web:** Step 13 — fetch the anchor standards. Fallback: record the versions as unread.
94
84
 
95
85
  #### Conditional
96
86
 
97
- Verify only when applicable.
98
-
99
- - [ ] **Runtime Logs:** Hosted platforms → Step 11 — read-only log APIs, e.g. vendor CLIs, MCPs. Log access: `.agents/context.md` `context-fetch` blocks below `bkit:end` are ready-made read-only readers (`bkit context list-blocks` → each block's `context` and `body`); set a body's `# Customise:` knobs to the audit window; run it via `direnv exec . bash`. Skipped credential = not read, never clean. Fallback: each skipped source named in `Not Checked`.
100
- - [ ] **Language Server:** Typed language → Step 7 — references, e.g. Serena, `tsserver`. Fallback: text search only; name it on every blast-radius row.
101
- - [ ] **Symbol Maps:** Release builds → Step 4 — source maps and native symbols. Fallback: unsymbolicated = finding; call-site table marked unbuildable.
102
- - [ ] **User Reports:** Feedback channel exists → Step 10 — tracker user feedback, support inbox, store reviews. Fallback: `Not Checked`.
87
+ - [ ] **Runtime Logs:** **If** the project runs on hosted platforms → Step 11 — read-only log APIs (e.g., vendor CLIs, MCPs). Log access: the `context-fetch` blocks below `bkit:end` in `.agents/context.md` are ready-made read-only readers. `bkit context list-blocks` prints each block's `context` and `body`. Set a body's `# Customise:` knobs to the audit window, and run it with `direnv exec . bash`. A source skipped for a missing credential is not read, and never clean. Fallback: name each skipped source in `Not Checked`.
88
+ - [ ] **Language Server:** **If** the language is typed → Step 7 — references (e.g., Serena, `tsserver`). Fallback: text search only, and name it on every blast-radius row.
89
+ - [ ] **Symbol Maps:** **If** there are release builds → Step 4 — source maps and native symbols. Fallback: record an unsymbolicated stack as a finding, and mark the call-site table unbuildable.
90
+ - [ ] **User Reports:** **If** a feedback channel exists → Step 10 — tracker user feedback, support inbox, store reviews. Fallback: `Not Checked`.
103
91
 
104
92
  ### 🔒 Gate 1: Prerequisites Check
105
93
 
106
- **Checkpoint.** Verify and check `[x]` all applicable boxes above, then continue to `Probe Steps` without asking.
107
-
108
- - [ ] **Gaps named:** every missing item names its fallback and `Not Checked` entry.
109
- - [ ] **Gate 1 - Verified:** All Core items checked. All applicable Conditional items checked.
94
+ - [ ] **Gaps named:** every missing item names its fallback and its `Not Checked` entry.
95
+ - [ ] **Gate 1 — Verified:** every item above, every Core item and every applicable Conditional item is checked.
110
96
 
111
97
  ### Probe Steps
112
98
 
113
- - [ ] **Step 1 — Previous Run:** Audited commit = this report's `bkit:anchor` `baseSha`. Read newest prior report for this slug under `docs/audits/`; its commit = its `bkit:anchor` `baseSha`, else the HEAD its `Previous Run` recorded. Count findings fixed / still open; age of oldest open. Open after 2 runs → re-raise with age. **Done when:** closure rate in `Previous Run`, or run marked baseline.
114
- - [ ] **Step 2 — Detect:** Find error tracker, runtime logs, or both. **Done when:** evidence in `Checked`, or `N/A` and STOP.
115
- - [ ] **Step 3 — Board:** Same figures every run for comparison. Window = since previous report; also trailing-30-day when that is tracker default:
116
- - Unresolved count, and issue short ids.
117
- - Regressed count.
118
- - Events by environment. Name each. Call out production.
119
- - First seen, per issue, UTC.
120
- - Reported vs platform failures. Per platform re-reporting failures to the tracker (e.g. job runner, host): platform failure count beside tracker event count, same window. Ratio < 1 = reports lost.
99
+ - [ ] **Step 1 — Previous Run:** **Done when:** `Previous Run` holds the closure rate, or the run is marked baseline.
100
+ - [ ] **Step 2 — Detect:** Find the error tracker, the runtime logs, or both. **Done when:** `Checked` holds evidence, or `N/A` is recorded → **STOP**.
101
+ - [ ] **Step 3 — Board:** Record the same figures on every run, so runs compare. The window is the time since the previous report. Also record the trailing 30 days when that is the tracker's default. Compare the tracker's event retention with the window before trusting any figure, because the tracker has nothing older to count.
102
+ - The unresolved count, taken from a per-id lookup, and the issue short ids. Issue search drops groups whose events have expired.
103
+ - The regressed count.
104
+ - Events by environment. Name each environment, and call out production.
105
+ - First seen per issue, in UTC.
106
+ - Reported against platform failures. For each platform that re-reports failures to the tracker (e.g., job runner, host), put the platform failure count beside the tracker event count for the same window. **If** the ratio is < 1 → reports were lost.
121
107
 
122
- Production count > zero → reprioritize everything. No real user traffic → numbers describe CI/test traffic, not user impact; report says so. Resolve release SHA per issue (`git rev-parse`, `git branch --contains`) before branch attribution. Integration-branch HEAD event = dev-side bug, not PR-under-review defect. Release health per client (e.g. web, native): crash-free sessions and crash-free users, per release and environment; latest-release adoption. Low traffic → describes CI; report says so. Previous report expected fix → confirm held and duration. Miss in window = finding. "Shipped" fix absent from default branch = still live = finding. **Done when:** `Board` holds the five figures, release health, and those confirmations.
108
+ **If** the production count is above zero → reprioritize everything. **If** there is no real user traffic → the numbers describe CI or test traffic, not user impact, and the report says so. Resolve the release SHA per issue (`git rev-parse`, `git branch --contains`) before attributing it to a branch. An event at the integration branch's HEAD is a dev-side bug, not a defect in the PR under review. Record release health per client (e.g., web, native): crash-free sessions and crash-free users per release and environment, and latest-release adoption. **If** traffic is low → the numbers describe CI, and the report says so. **If** the previous report expected a fix → confirm that it held, and for how long. A miss in the window is a finding. A "shipped" fix that is absent from the default branch is still live, and is a finding. **Done when:** `Board` holds the five figures, release health and those confirmations.
123
109
 
124
- - [ ] **Step 4 — Instrument:** Read tracker project settings, read-only, against anchor standards.
125
- - Symbolication. One recent production event and one non-production: frames show original file/line, event carries debug ids, release set. Native client → Hermes maps, dSYM, ProGuard uploads where that client exists. Unsymbolicated stack → call-site table unbuildable = finding.
126
- - Release and environment on every event. Release health on for each client.
127
- - Dropped events since previous report: rate-limited, filtered, over quota, spike protection. Record each count. Dropped events read like a quiet board. Record spike protection and per-key rate limits set.
128
- - Server-side grouping: fingerprint rules, stack-trace rules, inbound filters. List issues merged since previous report (hand or grouping assistant, e.g. Sentry Seer). SDK-side fingerprints = Level step. New inbound filter or merge can hide a class.
129
- - Ownership rules. CODEOWNERS import needs code mappings and team/user mappings. Unmapped owner = silently ignored. Record share of unresolved issues with no owner.
110
+ - [ ] **Step 4 — Instrument:** Read the tracker project settings, read-only, against the anchor standards.
111
+ - Symbolication. Open one recent production event and one non-production event: the frames show the original file and line, the event carries debug ids, and the release is set. **If** there is a native client → check the Hermes map, dSYM and ProGuard uploads where that client exists. An unsymbolicated stack makes the call-site table unbuildable, and is a finding.
112
+ - Release and environment are set on every event. Release health is on for each client.
113
+ - Dropped events since the previous report: rate-limited, filtered, over quota, and spike protection. Record each count, because dropped events read like a quiet board. Record the spike protection and per-key rate limits that are set.
114
+ - Server-side grouping: fingerprint rules, stack-trace rules and inbound filters. List the issues merged since the previous report, by hand or by a grouping assistant (e.g., Sentry Seer). SDK-side fingerprints belong to the Level step. A new inbound filter or merge can hide a class.
115
+ - Ownership rules. A CODEOWNERS import needs code mappings and team/user mappings. An unmapped owner is silently ignored. Record the share of unresolved issues with no owner.
130
116
 
131
- **Done when:** `Instrument` holds each check, dropped-event counts, unowned share.
117
+ **Done when:** `Instrument` holds each check, the dropped-event counts and the unowned share.
132
118
 
133
- - [ ] **Step 5 — Stored Data:** Tracker holds copies of what the app handles.
134
- - Server-side scrubbing: data-scrubber rules, IP storage, send-default-PII flag in each init, session-replay masking, user context the app sets (id only). Client scrubber = other half; this step = server half. Wider lifecycle → `bkit-audit-privacy`.
135
- - Model inputs/outputs. Tracker AI integration can record prompts/responses; current SDKs may default on (e.g. `recordInputs`, `recordOutputs` follow gen-AI collection flag defaulting on). Default depends on SDK version → read integration page for installed one. Read options in each init; open one recent gen-AI span. Message/mail content can land in gen-AI span attributes.
136
- - Sample five recent events end to end (message, breadcrumbs, request, extra, tags) for names, emails, addresses, message text. Report by field. Never copy value.
119
+ - [ ] **Step 5 — Stored Data:** The tracker holds copies of what the app handles.
120
+ - Server-side scrubbing: the data-scrubber rules, IP storage, the send-default-PII flag in each init, session-replay masking, and the user context the app sets (id only). The client scrubber is the other half; this step checks the server half. The wider lifecycle belongs to `bkit-audit-privacy`.
121
+ - Model inputs and outputs. The tracker's AI integration can record prompts and responses, and current SDKs may default this on (e.g., `recordInputs`, `recordOutputs` follow the gen-AI collection flag, which defaults on). The default depends on the SDK version, so read the integration page for the installed one. Read the options in each init, and open one recent gen-AI span. Message and mail content can land in gen-AI span attributes.
122
+ - Sample five recent events end to end (message, breadcrumbs, request, extra, tags) for names, emails, addresses and message text. Report by field. NEVER copy a value.
137
123
 
138
124
  **Done when:** `Stored Data` says what the sample found, by field.
139
125
 
140
- - [ ] **Step 6 — Classify:** One verdict per unresolved issue. Tracker performance issues (e.g. N+1, slow DB spans) and Web Vitals regressions: not classified. Record count on `Board`; name defect-like ones for `bkit-audit-app-performance`. Flake mechanism → note for `bkit-audit-flakes`. **Done when:** every unresolved issue has verdict in `Issues`; performance count on `Board`.
141
- - [ ] **Step 7 — Root Cause:** Each `GENUINE ERROR` and any issue whose verdict depends on call site. Message = symptom. Read call site → path → blast radius. Call-site table = artefact: callers sharing broken mechanism vs not. Language server, where available: stack symbol → every referencing symbol → diagnostics for that file. Pace reference queries; partial answer = indistinguishable from real. Re-run surprising low count. Empty = inconclusive → corroborate with text search; say which count from where. Ask why no test caught it. Every suite mocking SDK = second finding. Verify constraints against live system, not memory: actual predicate, rolled-back insert, host vs published IP ranges. Say what is unverifiable. Teardown often deletes rows an event points at → non-production findings corroborated by mechanism, not row. A mechanism that fits is not a confirmed cause. **Done when:** each `GENUINE ERROR` row in `Issues` has root cause, call-site table, the method that produced it, what is not established, and the file a later change would touch.
142
- - [ ] **Step 8 — Level:** Each `WRONG LEVEL`: recommend error-level log → warning, plus `docs/noise.md` row (call site, reason). Do not edit. Do not recommend tracker denylist for app code. Before downgrading, check hypothesis that would make it real defect; record check. Read both symbols; do not search column name. Fingerprint explosion: message with varying payload (ids, arrays) needs stable grouping key and pinned test before left in stream. **Done when:** each `WRONG LEVEL` row names the level change, the hypothesis checked, any fingerprint gap, and the file a later change would touch.
143
- - [ ] **Step 9 — Disposition:** Recommend resolve, archive, or leave open and why, per issue. This run does not resolve or archive. Recommend resolve only when code that files the issue changed and shipped. Resolving ahead of fix hides only signal on rails with no other coverage. Archived / muted issues too: per `docs/noise.md` archive or mute row, compare window events with the row's recorded trigger. Past trigger → recommend un-archive. **Done when:** `Issues` states resolve, archive, or leave open for every issue; every archive / mute row checked against its trigger.
144
- - [ ] **Step 10 — Invisible:** Tracker only sees errors that reach it. Caught then neither logged nor rethrown = invisible to caller and this sweep. Quiet board ≠ evidence shape absent. Look only in code behind this sweep's issues (`bkit-audit-reliability` sweeps rest):
145
- - `catch` blocks that neither rethrow, return error, nor log at warn or above. Start with DB writes and outbound calls.
146
- - Client calls whose error is never read: result discarded, or success destructured without error.
147
- - Promises started without `await` or rejection handler on write path.
148
-
149
- Text search finds candidates; read each. Deliberate best-effort (telemetry, fire-and-forget notification) OK when code says so. Real one → `docs/failures.jsonl` row, which the audit agent writes; Expected names `bkit-audit-database` when miss is grant, policy, or write role. Users see same shape: tracker user feedback, support inbox, store reviews since previous report. User-reported failure with no matching event = this class. Next step = runtime half: swallowed DB error may appear in DB log. **Done when:** `Invisible` lists each candidate read, and its verdict.
150
-
151
- - [ ] **Step 11 — Runtime Logs:** Read each runtime-log source in `Project Instructions` and each `context=runtime` block in `.agents/context.md` for whole window since previous report, not tool default short window. Record retention from plan page and window part source could not cover. Retention < cadence = finding → drain or shorter cadence. Skipped reader (credential, tool, block) = not read, never clean. No reader → vendor console by hand, or not read and why. Note whether server logs share one structured shape (request id, trace id, hashed tenant id, error code) so queries are filters not text search; tracker log product or OTel log exporter in use. Test and production share vendor resource (e.g. sending domain, API key) → read its reputation signal (e.g. bounce and complaint rate per sender) for window; separate resources → `not shared`; vendor exposes no such metric → name missing signal, `Not Checked`. Per log error:
152
- - Match tracker first (timestamps; trace id joins). Covered → note platform evidence on issue. Same incident, not second finding.
153
- - Group by time across sources. Cluster within few minutes = one outage; write once.
154
- - Tracker empty → gap = finding. Noise (why), or failure that should have been reported. Second → Expected names signal: log at call site, upstream-outage classifier pattern, or health-endpoint check. Monitor/capacity alert = next step, not this run.
155
- - Never copy log line free text. PII-safe fields reader already selects.
156
-
157
- Check correlation without clock. Every inbound-request → background-work path: one trace (e.g. W3C `traceparent`, tracker trace header) spans host, job runner, DB calls, in tracker and job-runner traces. Broken hop = finding. Without it, time grouping = only join. Platform failure re-reported to tracker → counts must match; platform failure with no tracker event = broken reporter. **Done when:** `Runtime Logs` row per source: read or not (why) · window covered · retention · error count · matched tracker issues. Row per shared vendor resource: reputation per sender, `not shared`, or `Not Checked` (why). Correlation recorded. `Board` holds reported-vs-platform ratio per reporting platform.
158
-
159
- - [ ] **Step 12 — Alarms:** Prior steps read what arrived. This step checks what is meant to arrive still can. Per observability doc (health endpoint, alert routing, uptime monitors):
160
- - Uptime monitors. List each: last check-in, last failure, still right URL/environment. Status-only assertion can pass on login wall when checker follows redirects.
161
- - Cron coverage. Every clock job health endpoint should know. Unknown job can stop silently. Read every run, not each job's newest: run started and unfinished past its timeout = finding.
162
- - Health state store. Read store health endpoint writes check results to (table, key): per check, last result + last evaluated. Row older than its schedule = finding, whatever its last result (stale `ok` = dead check). No store (checks computed live) → record with evidence. Row without timestamp → record gap. Read needs write-capable credential → `Not Checked`; never borrow one.
163
- - Alert routing. Rule exists, destination current, last real alert seen. Alert never seen fire since created = unproven, not healthy. Destination by role or doc section; no personal address.
164
- - Alert quality. Count fired since previous report, share that led to action, time to acknowledge. Rule fired repeatedly with no action = noise; name it. Rule with no environment filter letting non-production noise reach person = noise; name it.
165
- - On-call. Who gets production alerts OOH, if no ack, whether quiet hours suppress anything critical. Before launch, developer inbox OK only as written answer.
166
-
167
- No error tracker → monitor list and alert rules `Not Checked`; cron coverage still from repo. Before launch, much unproven for lack of traffic. Record what could not be proven and why. Missing monitor = next step, not this run. **Done when:** `Alarms` row per monitor and cron: last check-in · runs left unfinished · what could not be proven. Row per state-store check: last result · last evaluated, or `no state store` with evidence. Alert-quality numbers and on-call answer included.
168
-
169
- - [ ] **Step 13 — Standards:** Confirm current version per anchor standard; read changes since previous report's version. `Standards Coverage`: one row per tracker setup practice (symbolication, release, environment, release health, grouping, ownership, quotas, spike protection, scrubbing) and per trace-propagation and SLO-alerting practice → checked (name step) / not applicable (why) / finding. Per bkit anchor (doc section, rule, or issue shape): one row → followed (name step or evidence) / not applicable (why) / finding; departure with no recorded reason (e.g. `docs/decisions.jsonl` row, accepted-divergence entry) = finding. Unapplied recommended practice → adopt (propose step) / reject (why) / not applicable. **Done when:** no empty row.
170
- - [ ] **Step 14 — Anything Else:** (a) Everything changed since previous report's commit touching error reporting and logs (tracker init and integrations, scrubber, upstream-outage classifier, new error-level call sites, alert rules, uptime and cron monitors, log-fetch blocks, new outside services) → one-line verdict each. (b) Bounded ~30 min pass: what senior SRE flags that no step asks; read since previous run (incidents, new `docs/failures.jsonl` rows, vendor status incidents) — what would no step catch? Any error source this run saw that `Runtime Logs` does not name → record and propose source in `Process Improvements`. **Done when:** `Beyond the Steps` holds both passes, or `none`. Class seen on 2 runs → propose step in `Process Improvements`.
126
+ - [ ] **Step 6 — Classify:** Give each unresolved issue one verdict. Do not classify tracker performance issues (e.g., N+1, slow DB spans) or Web Vitals regressions. Record their count on `Board`, and name the defect-like ones for `bkit-audit-app-performance`. **If** an issue shows a flake mechanism → note it for `bkit-audit-flakes`. **Done when:** every unresolved issue has a verdict in `Issues`, and the performance count is on `Board`.
127
+ - [ ] **Step 7 — Root Cause:** Root-cause each `GENUINE ERROR`, and any issue whose verdict depends on the call site. The message is the symptom.
128
+ - Read the call site, then the path, then the blast radius. The call-site table is the artefact: the callers that share the broken mechanism, and those that do not.
129
+ - **If** a language server is available → go from the stack symbol to every referencing symbol, then to the diagnostics for that file.
130
+ - Pace the reference queries, because a partial answer looks the same as a real one.
131
+ - Re-run a surprisingly low count. An empty result is inconclusive: corroborate it with text search, and say which count came from where.
132
+ - Ask why no test caught it. Every suite that mocks the SDK is a second finding.
133
+ - Verify constraints against the live system, not memory: the actual predicate, a rolled-back insert, the host against the published IP ranges.
134
+ - Say what cannot be verified.
135
+ - Teardown often deletes the rows an event points at, so corroborate non-production findings by mechanism, not by row. A mechanism that fits is not a confirmed cause.
136
+
137
+ **Done when:** each `GENUINE ERROR` row in `Issues` has a root cause, a call-site table, the method that produced it, what is not established, and the file a later change would touch.
138
+
139
+ - [ ] **Step 8 — Level:** For each `WRONG LEVEL`, recommend moving the error-level log to warning, plus a `docs/noise.md` row (call site, reason). Do not edit. Do not recommend a tracker denylist for app code. Before downgrading, check the hypothesis that would make it a real defect, and record the check. Read both symbols; do not search for the column name. Watch for fingerprint explosion: a message with a varying payload (ids, arrays) needs a stable grouping key and a pinned test before it is left in the stream. **Done when:** each `WRONG LEVEL` row names the level change, the hypothesis checked, any fingerprint gap, and the file a later change would touch.
140
+ - [ ] **Step 9 — Disposition:** For each issue, recommend resolve, archive or leave open, and say why. This run does not resolve or archive. Recommend resolve only when the code that files the issue has changed and shipped, because resolving ahead of the fix hides the only signal on rails with no other coverage. Check archived / muted issues too: for each archive or mute row in `docs/noise.md`, compare the window's events with the row's recorded trigger. **If** the events are past the trigger → recommend un-archiving. **Done when:** `Issues` states resolve, archive or leave open for every issue, and every archive / mute row is checked against its trigger.
141
+ - [ ] **Step 10 — Invisible:** The tracker sees only the errors that reach it. An error that is caught, then neither logged nor rethrown, is invisible to the caller and to this sweep. A quiet board is not evidence that the shape is absent. Look only in the code behind this sweep's issues (`bkit-audit-reliability` sweeps the rest):
142
+ - `catch` blocks that neither rethrow, return an error, nor log at warn or above. Start with DB writes and outbound calls.
143
+ - Client calls whose error is never read: the result is discarded, or the success value is destructured without the error.
144
+ - Promises on a write path started without `await` or a rejection handler.
145
+
146
+ Text search finds candidates; read each one. Deliberate best-effort code (telemetry, a fire-and-forget notification) is fine when the code says so. **If** a candidate is real → it gets a `docs/failures.jsonl` row, which this run writes. **If** the miss is a grant, a policy or a write role → `Expected` names `bkit-audit-database`. Users see the same shape: read the tracker user feedback, support inbox and store reviews since the previous report. A user-reported failure with no matching event belongs to this class. The next step is the runtime half: a swallowed DB error may appear in the DB log. **Done when:** `Invisible` lists each candidate read, and its verdict.
147
+
148
+ - [ ] **Step 11 — Runtime Logs:** Read each runtime-log source in `Project Instructions` and each `context=runtime` block in `.agents/context.md` over the whole window since the previous report, not the tool's short default window. Record the retention from the plan page, and the part of the window a source could not cover. **If** retention is < the cadence → it is a finding; propose a drain or a shorter cadence. A skipped reader (credential, tool, block) is not read, and never clean. **If** there is no reader → read the vendor console by hand, or record that it was not read and why. **If** CI writes to production resources → name CI as a runtime-log source. Note whether server logs share one structured shape (request id, trace id, hashed tenant id, error code), so that queries are filters, not text search, and whether a tracker log product or an OTel log exporter is in use. **If** test and production share a vendor resource (e.g., a sending domain, an API key) → read its reputation signal (e.g., bounce and complaint rate per sender) for the window. **If** the resources are separate → record `not shared`. **If** the vendor exposes no such metric → name the missing signal, and mark it `Not Checked`. For each log error:
149
+ - Match it to the tracker first (timestamps; trace id joins). **If** it is covered → note the platform evidence on the issue. It is the same incident, not a second finding.
150
+ - Join retry log lines to the request's final outcome before counting failures. A retry that later succeeded is not a failure.
151
+ - Group errors by time across sources. A cluster within a few minutes is one outage; write it once.
152
+ - **If** the tracker is empty for it → the gap is a finding. Record whether it is noise (and why), or a failure that should have been reported. **If** it should have been reported → `Expected` names the signal: a log at the call site, an upstream-outage classifier pattern, or a health-endpoint check. A monitor or capacity alert is the next step, not this run.
153
+ - NEVER copy log-line free text. Use the PII-safe fields the reader already selects.
154
+
155
+ Check correlation without the clock. On every inbound-request → background-work path, one trace (e.g., W3C `traceparent`, a tracker trace header) spans the host, job runner and DB calls, in both the tracker and the job-runner traces. A broken hop is a finding, because without the trace, time grouping is the only join. **If** platform failures are re-reported to the tracker → the counts must match, and a platform failure with no tracker event means a broken reporter. **Done when:** `Runtime Logs` has a row per source: read or not (why) · window covered · retention · error count · matched tracker issues. It has a row per shared vendor resource: reputation per sender, `not shared`, or `Not Checked` (why). Correlation is recorded, and `Board` holds the reported-vs-platform ratio per reporting platform.
156
+
157
+ - [ ] **Step 12 — Alarms:** The earlier steps read what arrived. This step checks that what is meant to arrive still can. Follow the observability doc (health endpoint, alert routing, uptime monitors):
158
+ - Uptime monitors. List each one with its last check-in, its last failure, and whether it still points at the right URL and environment. A status-only assertion can pass on a login wall when the checker follows redirects.
159
+ - Cron coverage. The health endpoint should know every clock job, because an unknown job can stop silently. Read every run, not only each job's newest: a run that started and is unfinished past its timeout is a finding. For each scheduled job, read the outcome of each run (status code or exit code), not only that it ran: a rejected run can log at info level. A job that did not write its owned rows in its window is a finding, even when it exited 0. **If** there are no scheduled jobs → record the skip with evidence of absence.
160
+ - Health state store. Read the store the health endpoint writes check results to (table, key): for each check, the last result and when it was last evaluated. A row older than its schedule is a finding, whatever its last result, because a stale `ok` is a dead check. **If** there is no store (checks are computed live) → record that with evidence. **If** a row has no timestamp → record the gap. **If** the read needs a write-capable credential → mark it `Not Checked`; never borrow one.
161
+ - Alert routing. Check that the rule exists, that the destination is current, and when a real alert was last seen. An alert never seen to fire since it was created is unproven, not healthy. Name the destination by role or doc section, with no personal address.
162
+ - Alert quality. Record the count fired since the previous report, the share that led to action, and the time to acknowledge. A rule that fired repeatedly with no action is noise; name it. A rule with no environment filter that lets non-production noise reach a person is noise; name it.
163
+ - On-call. Record who gets production alerts out of hours, who gets them when nobody acknowledges, and whether quiet hours suppress anything critical. Before launch, a developer inbox is acceptable only as a written answer.
164
+
165
+ **If** there is no error tracker → mark the monitor list and alert rules `Not Checked`, and still read cron coverage from the repo. Before launch, much stays unproven for lack of traffic. Record what could not be proven, and why. A missing monitor is the next step, not this run. **Done when:** `Alarms` has a row per monitor and cron: last check-in · runs left unfinished · what could not be proven. It has a row per state-store check: last result · last evaluated, or `no state store` with evidence. The alert-quality numbers and the on-call answer are included.
166
+
167
+ - [ ] **Step 13 — Standards:** Confirm the current version of each anchor standard, and read what changed since the previous report's version. Give `Standards Coverage` one row per tracker setup practice (symbolication, release, environment, release health, grouping, ownership, quotas, spike protection, scrubbing) and per trace-propagation and SLO-alerting practice, each marked checked (naming the step), not applicable (saying why) or finding. Give each bkit anchor (a doc section, rule or issue shape) one row, marked followed (with the step or evidence), not applicable (saying why) or finding. A departure with no recorded reason (e.g., a `docs/decisions.jsonl` row or an accepted-divergence entry) is a finding. Mark each recommended practice the project does not apply as adopt (with a proposed step), reject (saying why) or not applicable. **Done when:** no row is empty.
168
+ - [ ] **Step 14 — Anything Else:** (a) Give a one-line verdict on each change since the previous report's commit that touches error reporting and logs: tracker init and integrations, the scrubber, the upstream-outage classifier, new error-level call sites, alert rules, uptime and cron monitors, log-fetch blocks, and new outside services. (b) In a bounded pass of about 30 minutes, note what a senior SRE would flag that no step asks about. Read what happened since the previous run (incidents, new `docs/failures.jsonl` rows, vendor status incidents), and ask what no step would catch. **If** this run saw an error source that `Runtime Logs` does not name → record it, and propose the source in `Process Improvements`. **Done when:** `Beyond the Steps` holds both passes, or says `none`. **If** one class of issue is seen on 2 runs → propose a step for it in `Process Improvements`.
171
169
 
172
170
  ### 🔒 Gate 2: Probes Check
173
171
 
174
- **Checkpoint.** Verify and check `[x]` all boxes below, then continue to `Findings` without asking.
175
-
176
- - [ ] **Steps complete:** every step `[x]`, or explicit skip with evidence the surface is absent.
177
- - [ ] **Evidence:** every finding cites re-checkable evidence and the tool behind it.
178
- - [ ] **No tracker writes:** nothing resolved, archived, muted, or edited; no sample rate or alert rule changed.
179
- - [ ] **No payloads:** no log free text, event payload, personal-data value, or credential-field value in the report.
180
- - [ ] **Gate 2 - Verified:** Every checkbox above independently verified and checked off.
172
+ - [ ] **Steps complete:** every step is `[x]`, or skipped with evidence that its surface is absent.
173
+ - [ ] **Evidence:** every finding cites evidence someone can check again, and the tool that produced it.
174
+ - [ ] **No tracker writes:** nothing was resolved, archived, muted or edited.
175
+ - [ ] **No config changes:** no sample rate or alert rule changed.
176
+ - [ ] **No payloads:** no log free text, event payload, personal-data value or credential-field value is in the report.
177
+ - [ ] **Gate 2 — Verified:** every item above holds.
181
178
 
182
179
  ## Findings
183
180
 
@@ -189,14 +186,14 @@ Verify only when applicable.
189
186
  | `MEDIUM` | Handled outcome filed at error; unsymbolicated stack; no owner on most unresolved issues; alert that has never fired, or fires with no action; fingerprint explosion; user report with no event |
190
187
  | `LOW` | Noise with a named vendor frame; test-traffic issue already tagged; `docs/noise.md` wording drift |
191
188
 
192
- Scale per `.bkit/jsonl.md` § Severity. Within a severity: production first, then blast radius. A test-origin tag does not lower severity. A quiet board is not a pass.
189
+ Within a severity, list production first, then order by blast radius. A test-origin tag does not lower severity. A quiet board is not a pass.
193
190
 
194
191
  <!-- prettier-ignore -->
195
192
  | ID | Severity | Verdict | Location | Evidence | Expected |
196
193
  | --- | --- | --- | --- | --- | --- |
197
194
  | PENDING | PENDING | PENDING | PENDING | PENDING | PENDING |
198
195
 
199
- Empty and clean → one row `None`.
196
+ **If** the run finds nothing → write one row: `None`.
200
197
 
201
198
  ## Report
202
199
 
@@ -265,17 +262,19 @@ PENDING
265
262
 
266
263
  ### 🔒 Gate 3: Report Check
267
264
 
268
- **Checkpoint.** Verify and check `[x]` all boxes below, then stop.
269
-
270
- - [ ] **No placeholders:** Findings table and every `Report` section have no `PENDING`.
271
- - [ ] **Summary:** names count per severity, what is new, the single most important finding, the unresolved count, and the production event count.
272
- - [ ] **Series:** `Board` counts beside previous report's counts, or marked baseline.
273
- - [ ] **Writes:** only this report and template `Project Instructions` changed; throwaway worktrees / remote targets removed.
274
- - [ ] **Process Improvements:** `Universal` = proposed step changes, template untouched; `Project` = edits applied below `bkit:end`; each `none` if empty.
275
- - [ ] **Suggested Issues:** every `MEDIUM`+ finding ID in exactly one row; every row has a `Next Step`.
276
- - [ ] **Gate 3 - Verified:** Every checkbox above independently verified and checked off.
277
-
278
- > `Project Instructions` below `bkit:end` are consumer-owned — `bkit install` never overwrites them, `bkit check` drift stays clean. Add project-specific tools, paths, commands, and checks there, keyed by section or step title; never results.
265
+ - [ ] **No placeholders:** no `PENDING` is left.
266
+ - [ ] **Summary:** `Summary` gives the count per severity.
267
+ - [ ] **What is new:** `Summary` says what is new.
268
+ - [ ] **Top finding:** `Summary` names the single most important finding.
269
+ - [ ] **Unresolved:** `Summary` gives the unresolved count.
270
+ - [ ] **Production events:** `Summary` gives the production event count.
271
+ - [ ] **Series:** the report shows `Board` counts beside the previous report's numbers, or marks the run as baseline.
272
+ - [ ] **Writes:** this run changed only this report, the template's `Project Instructions` and its own `docs/failures.jsonl` rows.
273
+ - [ ] **Throwaways removed:** every throwaway worktree or remote target is removed.
274
+ - [ ] **Process Improvements:** `Universal` and `Project` are both filled.
275
+ - [ ] **Suggested Issues:** every `MEDIUM`+ finding ID is in exactly one `Suggested Issues` row.
276
+ - [ ] **Next Step:** every `Suggested Issues` row has a `Next Step`.
277
+ - [ ] **Gate 3 — Verified:** every item above holds.
279
278
 
280
279
  <!-- bkit:end -->
281
280