@cbartens/bkit 5.5.0 → 6.0.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.
- package/.bkit/README.md +30 -20
- package/.bkit/core/.agents/docs.md +1 -0
- package/.bkit/core/.agents/rules.md +51 -26
- package/.bkit/core/.bkit/README.md +29 -19
- package/.bkit/core/.bkit/authoring.md +117 -0
- package/.bkit/core/.bkit/cloud.md +11 -11
- package/.bkit/core/.bkit/comparison.md +5 -5
- package/.bkit/core/.bkit/install.md +20 -20
- package/.bkit/core/.bkit/jsonl.md +202 -122
- package/.bkit/core/.bkit/lite.md +1 -1
- package/.bkit/core/.bkit/pipeline.md +49 -52
- package/.bkit/core/.bkit/prompts.md +106 -167
- package/.bkit/core/.bkit/providers.md +29 -32
- package/.bkit/core/.bkit/templates.md +44 -18
- package/.bkit/core/.bkit/trackers.md +60 -28
- package/.bkit/core/.bkit/workflows.md +399 -359
- package/.bkit/core/AGENTS.md +16 -22
- package/.bkit/core/docs/templates/bkit-audit-accessibility.md +14 -38
- package/.bkit/core/docs/templates/bkit-audit-adoption.md +16 -40
- package/.bkit/core/docs/templates/bkit-audit-agents.md +19 -43
- package/.bkit/core/docs/templates/bkit-audit-aio-seo.md +16 -40
- package/.bkit/core/docs/templates/bkit-audit-analytics.md +14 -38
- package/.bkit/core/docs/templates/bkit-audit-annotations.md +11 -35
- package/.bkit/core/docs/templates/bkit-audit-app-performance.md +15 -39
- package/.bkit/core/docs/templates/bkit-audit-app-store.md +12 -36
- package/.bkit/core/docs/templates/bkit-audit-architecture.md +16 -40
- package/.bkit/core/docs/templates/bkit-audit-ci-performance.md +16 -40
- package/.bkit/core/docs/templates/bkit-audit-config.md +18 -42
- package/.bkit/core/docs/templates/bkit-audit-cost.md +16 -40
- package/.bkit/core/docs/templates/bkit-audit-coverage.md +15 -39
- package/.bkit/core/docs/templates/bkit-audit-database.md +16 -40
- package/.bkit/core/docs/templates/bkit-audit-dead-code.md +15 -39
- package/.bkit/core/docs/templates/bkit-audit-deferrals.md +15 -38
- package/.bkit/core/docs/templates/bkit-audit-dependencies.md +16 -40
- package/.bkit/core/docs/templates/bkit-audit-documentation.md +11 -35
- package/.bkit/core/docs/templates/bkit-audit-duplication.md +18 -42
- package/.bkit/core/docs/templates/bkit-audit-failures.md +13 -37
- package/.bkit/core/docs/templates/bkit-audit-flakes.md +12 -36
- package/.bkit/core/docs/templates/bkit-audit-gates.md +14 -38
- package/.bkit/core/docs/templates/bkit-audit-issues.md +15 -39
- package/.bkit/core/docs/templates/bkit-audit-llm.md +16 -40
- package/.bkit/core/docs/templates/bkit-audit-logs.md +14 -38
- package/.bkit/core/docs/templates/bkit-audit-models.md +12 -36
- package/.bkit/core/docs/templates/bkit-audit-privacy.md +12 -36
- package/.bkit/core/docs/templates/bkit-audit-prompts.md +15 -39
- package/.bkit/core/docs/templates/bkit-audit-red-team.md +15 -39
- package/.bkit/core/docs/templates/bkit-audit-reliability.md +15 -39
- package/.bkit/core/docs/templates/bkit-audit-repo.md +12 -36
- package/.bkit/core/docs/templates/bkit-audit-security.md +13 -37
- package/.bkit/core/docs/templates/bkit-audit-slop.md +14 -38
- package/.bkit/core/docs/templates/bkit-audit-testing.md +12 -36
- package/.bkit/core/docs/templates/bkit-audit-usability.md +16 -40
- package/.bkit/core/docs/templates/bkit-plan.md +97 -226
- package/.bkit/core/engine/checks/after/ci-yml.ts +39 -30
- package/.bkit/core/engine/checks/after/github.ts +101 -72
- package/.bkit/core/engine/checks/after/index.ts +10 -12
- package/.bkit/core/engine/checks/after/suppression.ts +8 -5
- package/.bkit/core/engine/checks/after/tools.ts +47 -92
- package/.bkit/core/engine/checks/before/env.ts +2 -2
- package/.bkit/core/engine/checks/before/files.ts +5 -4
- package/.bkit/core/engine/checks/before/index.ts +18 -1
- package/.bkit/core/engine/checks/before/repo.ts +168 -2
- package/.bkit/core/engine/checks/tips/catalogue.ts +16 -5
- package/.bkit/core/engine/checks/tips/detect.ts +34 -0
- package/.bkit/core/engine/checks/tips/index.ts +10 -7
- package/.bkit/core/engine/cli.ts +20 -53
- package/.bkit/core/engine/commands/analysis.ts +171 -140
- package/.bkit/core/engine/commands/ci/ci.ts +6 -6
- package/.bkit/core/engine/commands/comply.ts +77 -103
- package/.bkit/core/engine/commands/install/doctor.ts +2 -2
- package/.bkit/core/engine/commands/install/install.ts +57 -18
- package/.bkit/core/engine/commands/install/uninstall.ts +65 -28
- package/.bkit/core/engine/commands/land.ts +18 -12
- package/.bkit/core/engine/commands/lib.ts +79 -17
- package/.bkit/core/engine/commands/registry.ts +4 -0
- package/.bkit/core/engine/commands/setup/setup.ts +7 -7
- package/.bkit/core/engine/commands/stats.ts +204 -0
- package/.bkit/core/engine/commands/tips.ts +10 -5
- package/.bkit/core/engine/commands/workflow/branches.ts +741 -62
- package/.bkit/core/engine/commands/workflow/challenge.ts +673 -0
- package/.bkit/core/engine/commands/workflow/context.ts +853 -29
- package/.bkit/core/engine/commands/workflow/counters.ts +267 -84
- package/.bkit/core/engine/commands/workflow/decisions.ts +541 -0
- package/.bkit/core/engine/commands/workflow/disk.ts +2 -2
- package/.bkit/core/engine/commands/workflow/fids.ts +793 -33
- package/.bkit/core/engine/commands/workflow/issues.ts +427 -105
- package/.bkit/core/engine/commands/workflow/ledgers.ts +884 -27
- package/.bkit/core/engine/commands/workflow/locks.ts +26 -2
- package/.bkit/core/engine/commands/workflow/plan-blocks.ts +582 -0
- package/.bkit/core/engine/commands/workflow/plan-versions.ts +21 -0
- package/.bkit/core/engine/commands/workflow/prs.ts +166 -30
- package/.bkit/core/engine/commands/workflow/repo.ts +59 -7
- package/.bkit/core/engine/commands/workflow/roadmap.ts +16 -7
- package/.bkit/core/engine/commands/workflow/run-facts.ts +501 -0
- package/.bkit/core/engine/commands/workflow/runs.ts +179 -49
- package/.bkit/core/engine/commands/workflow/runtime.ts +22 -1
- package/.bkit/core/engine/commands/workflow/status.ts +142 -29
- package/.bkit/core/engine/commands/workflow/step-table.ts +339 -0
- package/.bkit/core/engine/commands/workflow/steps.ts +213 -88
- package/.bkit/core/engine/commands/workflow/summary.ts +398 -0
- package/.bkit/core/engine/commands/workflow/tests.ts +1013 -148
- package/.bkit/core/engine/commands/workflow/tracker.ts +1195 -0
- package/.bkit/core/engine/commands/workflow/workflows.ts +984 -207
- package/.bkit/core/engine/commands/workflow/workstreams.ts +11 -5
- package/.bkit/core/engine/commands/workflow/worktrees.ts +276 -22
- package/.bkit/core/engine/install/manifest.ts +11 -9
- package/.bkit/core/engine/install/modules/cloud.ts +21 -13
- package/.bkit/core/engine/install/modules/core.ts +325 -7
- package/.bkit/core/engine/install/modules/opencode.ts +2 -2
- package/.bkit/core/engine/install/version-file.ts +6 -2
- package/.bkit/core/engine/ledgers/migrate.ts +92 -0
- package/.bkit/core/engine/ledgers/status.ts +92 -15
- package/.bkit/core/engine/ledgers/telemetry.ts +1261 -254
- package/.bkit/core/engine/render/hosts.ts +4 -0
- package/.bkit/core/engine/render/models.ts +12 -0
- package/.bkit/core/engine/shared/branches.ts +4 -1
- package/.bkit/core/engine/shared/egress.ts +7 -0
- package/.bkit/core/engine/shared/json.ts +25 -7
- package/.bkit/core/engine/shared/settings.ts +202 -33
- package/.bkit/core/engine/shared/text.ts +361 -0
- package/.bkit/core/engine/tools/grammar-density.ts +215 -0
- package/.bkit/core/engine/tools/instructions-sources.ts +834 -0
- package/.bkit/core/engine/tools/instructions.ts +1751 -0
- package/.bkit/core/hooks/gateguard-engine.js +24 -23
- package/.bkit/core/hooks/guardrails-shell.js +2 -3
- package/.bkit/core/hooks/guardrails-tiers.js +7 -1
- package/.bkit/core/hooks/readguard-engine.js +2 -2
- package/.bkit/core/prompts/bkit-audit-generate.md +62 -25
- package/.bkit/core/prompts/bkit-build-challenge-1.md +40 -17
- package/.bkit/core/prompts/bkit-build-challenge-2.md +44 -17
- package/.bkit/core/prompts/bkit-build-install-skills.md +26 -13
- package/.bkit/core/prompts/bkit-build-plan-convert.md +74 -0
- package/.bkit/core/prompts/bkit-build-plan-current.md +26 -13
- package/.bkit/core/prompts/bkit-build-plan-execute.md +74 -26
- package/.bkit/core/prompts/bkit-build-plan-gaps-remediate.md +64 -23
- package/.bkit/core/prompts/bkit-build-plan-verify.md +57 -33
- package/.bkit/core/prompts/bkit-debug-abort-handover.md +30 -14
- package/.bkit/core/prompts/bkit-debug-failure-diagnose.md +34 -14
- package/.bkit/core/prompts/bkit-debug-failure-remediate.md +34 -17
- package/.bkit/core/prompts/bkit-debug-failure-reproduce.md +26 -13
- package/.bkit/core/prompts/bkit-debug-failure-soak.md +31 -16
- package/.bkit/core/prompts/bkit-design-brainstorm-ideate-1.md +21 -11
- package/.bkit/core/prompts/bkit-design-brainstorm-ideate-2.md +20 -11
- package/.bkit/core/prompts/bkit-design-brainstorm-ideate-3.md +20 -11
- package/.bkit/core/prompts/bkit-design-generate.md +33 -13
- package/.bkit/core/prompts/bkit-design-organise.md +25 -12
- package/.bkit/core/prompts/bkit-design-review-1.md +31 -15
- package/.bkit/core/prompts/bkit-design-review-2.md +28 -13
- package/.bkit/core/prompts/bkit-design-spike.md +30 -13
- package/.bkit/core/prompts/bkit-design-update.md +33 -19
- package/.bkit/core/prompts/bkit-plan-generate.md +75 -19
- package/.bkit/core/prompts/bkit-plan-review-1.md +50 -27
- package/.bkit/core/prompts/bkit-plan-review-2.md +59 -28
- package/.bkit/core/prompts/bkit-plan-scope-check.md +109 -0
- package/.bkit/core/prompts/bkit-plan-update.md +61 -24
- package/.bkit/core/prompts/bkit-ship-conflict-resolve.md +27 -15
- package/.bkit/core/prompts/bkit-ship-deferred-sweep.md +31 -16
- package/.bkit/core/prompts/bkit-ship-update-docs.md +30 -15
- package/.bkit/core/prompts/bkit-utility-compress-markdown.md +24 -14
- package/.bkit/core/prompts/bkit-utility-update-decisions.md +32 -14
- package/.bkit/core/prompts/bkit-utility-update-deferrals.md +29 -14
- package/.bkit/core/prompts/bkit-utility-update-documentation.md +28 -13
- package/.bkit/core/prompts/bkit-utility-update-failures.md +31 -14
- package/.bkit/core/prompts/bkit-utility-update-knowledge.md +33 -14
- package/.bkit/core/prompts/bkit-utility-update-roadmap.md +38 -17
- package/.bkit/core/prompts/bkit-utility-update-tracker.md +43 -20
- package/.bkit/core/workflows/bkit-auto.md +54 -46
- package/.bkit/core/workflows/bkit-build.md +577 -458
- package/.bkit/core/workflows/bkit-debug.md +348 -333
- package/.bkit/core/workflows/bkit-design.md +201 -237
- package/.bkit/core/workflows/bkit-plan.md +210 -321
- package/.bkit/core/workflows/bkit-ship.md +328 -278
- package/.bkit/shared/.bkit/.env.example +2 -2
- package/.bkit/shared/.claude/settings.json +11 -0
- package/.bkit/shared/.cursor/mcp.json +1 -1
- package/.bkit/shared/.cursor/rules/bkit-rules.mdc +1 -1
- package/.bkit/shared/.gitattributes +1 -1
- package/.bkit/shared/.mcp.json +1 -1
- package/.bkit/shared/.opencode/opencode.json +11 -0
- package/.bkit/shared/CLAUDE.md +2 -2
- package/.bkit/shared/GEMINI.md +2 -2
- package/.bkit/shared/docs/architecture.md +1 -1
- package/.bkit/shared/docs/data-schema.md +1 -1
- package/.bkit/shared/docs/deployments.md +16 -28
- package/.bkit/shared/docs/design.md +1 -1
- package/.bkit/shared/docs/noise.md +1 -1
- package/.bkit/shared/docs/observability.md +2 -2
- package/.bkit/shared/docs/security.md +1 -1
- package/.bkit/shared/docs/setup.md +1 -1
- package/.bkit/shared/docs/technology.md +1 -1
- package/.bkit/shared/docs/testing.md +27 -10
- package/.bkit/templates/.claude/hooks/bkit-cloud-bootstrap.sh +1 -1
- package/.bkit/templates/.github/ISSUE_TEMPLATE/bkit-change.yml +26 -5
- package/.bkit/templates/.github/workflows/bkit-ci.yml +22 -84
- package/.bkit/templates/.github/workflows/bkit-cloud.yml +21 -19
- package/.bkit/templates/.husky/pre-push +52 -13
- package/.bkit/templates/.prettierignore +7 -0
- package/.bkit/templates/scripts/ci/bkit-local-stack-lock.sh +194 -0
- package/.bkit/templates/scripts/ci/check-capstone.mjs +2 -4
- package/.bkit/templates/scripts/ci/check-capstone.test.mjs +4 -23
- package/.bkit/templates/scripts/ci/lanes/resolve-push-base.mjs +104 -23
- package/.bkit/templates/scripts/ci/lanes/resolve-push-base.test.mjs +103 -6
- package/.bkit/templates/scripts/cleanup/bkit-disk-prune.mjs +1 -1
- package/.bkit/templates/scripts/graphify/bkit-graph-pre-push.sh +3 -1
- package/.bkit/templates/scripts/prettier/bkit-insert-ignore.mjs +49 -29
- package/CHANGELOG.md +142 -0
- package/README.md +58 -34
- package/dist/checks/after/ci-yml.js +39 -29
- package/dist/checks/after/github.js +99 -72
- package/dist/checks/after/index.js +11 -13
- package/dist/checks/after/suppression.js +8 -5
- package/dist/checks/after/tools.js +40 -83
- package/dist/checks/before/env.js +2 -2
- package/dist/checks/before/files.js +5 -3
- package/dist/checks/before/index.js +15 -2
- package/dist/checks/before/repo.js +163 -2
- package/dist/checks/tips/catalogue.js +14 -5
- package/dist/checks/tips/detect.js +32 -0
- package/dist/checks/tips/index.js +7 -5
- package/dist/cli.js +19 -47
- package/dist/commands/analysis.js +109 -100
- package/dist/commands/ci/ci.js +6 -6
- package/dist/commands/comply.js +54 -91
- package/dist/commands/install/doctor.js +2 -2
- package/dist/commands/install/install.js +50 -19
- package/dist/commands/install/uninstall.js +59 -28
- package/dist/commands/land.js +16 -12
- package/dist/commands/lib.js +51 -16
- package/dist/commands/registry.js +4 -0
- package/dist/commands/setup/setup.js +7 -7
- package/dist/commands/stats.js +136 -0
- package/dist/commands/tips.js +7 -3
- package/dist/commands/workflow/branches.js +656 -56
- package/dist/commands/workflow/challenge.js +556 -0
- package/dist/commands/workflow/context.js +709 -30
- package/dist/commands/workflow/counters.js +208 -75
- package/dist/commands/workflow/decisions.js +441 -0
- package/dist/commands/workflow/disk.js +2 -2
- package/dist/commands/workflow/fids.js +689 -33
- package/dist/commands/workflow/issues.js +362 -99
- package/dist/commands/workflow/ledgers.js +762 -27
- package/dist/commands/workflow/locks.js +24 -2
- package/dist/commands/workflow/plan-blocks.js +437 -0
- package/dist/commands/workflow/plan-versions.js +22 -0
- package/dist/commands/workflow/prs.js +142 -32
- package/dist/commands/workflow/repo.js +52 -7
- package/dist/commands/workflow/roadmap.js +9 -7
- package/dist/commands/workflow/run-facts.js +426 -0
- package/dist/commands/workflow/runs.js +144 -43
- package/dist/commands/workflow/runtime.js +12 -1
- package/dist/commands/workflow/status.js +130 -29
- package/dist/commands/workflow/step-table.js +276 -0
- package/dist/commands/workflow/steps.js +171 -80
- package/dist/commands/workflow/summary.js +275 -0
- package/dist/commands/workflow/tests.js +834 -136
- package/dist/commands/workflow/tracker.js +983 -0
- package/dist/commands/workflow/workflows.js +834 -195
- package/dist/commands/workflow/workstreams.js +11 -5
- package/dist/commands/workflow/worktrees.js +221 -22
- package/dist/install/manifest.js +11 -9
- package/dist/install/modules/cloud.js +22 -13
- package/dist/install/modules/core.js +326 -7
- package/dist/install/modules/opencode.js +2 -2
- package/dist/install/version-file.js +6 -2
- package/dist/ledgers/migrate.js +81 -0
- package/dist/ledgers/status.js +61 -8
- package/dist/ledgers/telemetry.js +905 -124
- package/dist/render/hosts.js +4 -0
- package/dist/render/models.js +12 -0
- package/dist/shared/branches.js +3 -1
- package/dist/shared/egress.js +7 -0
- package/dist/shared/json.js +20 -7
- package/dist/shared/settings.js +147 -26
- package/dist/shared/text.js +333 -0
- package/dist/tools/grammar-density.js +183 -0
- package/dist/tools/instructions-sources.js +721 -0
- package/dist/tools/instructions.js +1579 -0
- package/package.json +114 -23
- package/.bkit/core/engine/commands/harvest.ts +0 -459
- package/.bkit/core/engine/tools/wording.ts +0 -748
- package/.bkit/core/prompts/bkit-build-challenge-reconcile.md +0 -69
- package/.bkit/core/prompts/bkit-build-challenge-remediate.md +0 -71
- package/.bkit/core/prompts/bkit-build-challenge-tests.md +0 -74
- package/.bkit/core/prompts/bkit-build-summary.md +0 -94
- package/.bkit/core/prompts/bkit-debug-summary.md +0 -96
- package/.bkit/core/prompts/bkit-design-summary.md +0 -107
- package/.bkit/core/prompts/bkit-plan-complexity-check.md +0 -67
- package/.bkit/core/prompts/bkit-plan-complexity-split.md +0 -88
- package/.bkit/core/prompts/bkit-plan-review-3.md +0 -93
- package/.bkit/core/prompts/bkit-plan-scope-check-1.md +0 -85
- package/.bkit/core/prompts/bkit-plan-scope-check-2.md +0 -85
- package/.bkit/core/prompts/bkit-plan-summary.md +0 -107
- package/.bkit/core/prompts/bkit-ship-summary.md +0 -78
- package/.bkit/templates/scripts/ci/lanes/check-tree-cache.mjs +0 -138
- package/.bkit/templates/scripts/ci/lanes/check-tree-cache.test.mjs +0 -181
- package/dist/commands/harvest.js +0 -353
- package/dist/tools/wording.js +0 -680
|
@@ -12,9 +12,12 @@
|
|
|
12
12
|
//
|
|
13
13
|
// Default paths: `.agents`, `docs`, `README.md`. A directory walk skips `skills/` trees (vendored)
|
|
14
14
|
// and `docs/audits/` + `docs/plans/` (records, kept as written); a file named explicitly is always
|
|
15
|
-
// processed. Tables inside fenced code blocks (``` / ~~~)
|
|
15
|
+
// processed. Tables inside fenced code blocks (``` / ~~~), inside `<!-- -->` comment blocks, and
|
|
16
|
+
// already wrapped are skipped.
|
|
16
17
|
// `--check` writes nothing and exits 1 if any file would change — use it as a gate.
|
|
17
|
-
// Exit 1 also on table damage escaping cannot repair (see auditText), with or without --check
|
|
18
|
+
// Exit 1 also on table damage escaping cannot repair (see auditText), with or without --check —
|
|
19
|
+
// except in the record trees, where the damage is printed as a warning: a record holds text quoted
|
|
20
|
+
// from elsewhere (issue comments, CI logs), so nobody can fix it there.
|
|
18
21
|
|
|
19
22
|
import fs from "node:fs";
|
|
20
23
|
import path from "node:path";
|
|
@@ -28,6 +31,8 @@ const INLINE_CODE = /`[^`\n]*`/g;
|
|
|
28
31
|
const DEFAULT_ROOTS = [".agents", "docs", "README.md"];
|
|
29
32
|
// Record trees: written once, never reformatted.
|
|
30
33
|
const RECORD_DIRS = ["docs/audits", "docs/plans"];
|
|
34
|
+
const relTo = (root, p) => path.relative(root, path.resolve(root, p)).split(path.sep).join("/");
|
|
35
|
+
const isRecord = (r) => RECORD_DIRS.some((d) => r === d || r.startsWith(`${d}/`));
|
|
31
36
|
|
|
32
37
|
const stripNl = (line) => line.replace(/\n$/, "");
|
|
33
38
|
const leadingSpaces = (line) => /^ */.exec(line)[0];
|
|
@@ -85,25 +90,32 @@ function normalizeSeparator(line) {
|
|
|
85
90
|
return `${leadingSpaces(line)}| ${cells.join(" | ")} |${nl}`;
|
|
86
91
|
}
|
|
87
92
|
|
|
88
|
-
// ``` / ~~~ fences across a line walk. Shared by processText and
|
|
89
|
-
// a table inside
|
|
90
|
-
|
|
91
|
-
|
|
93
|
+
// ``` / ~~~ fences and `<!-- -->` comment blocks across a line walk. Shared by processText and
|
|
94
|
+
// auditText so they never disagree: a table inside either is illustrative or hidden text, neither
|
|
95
|
+
// rewritten nor reported. A comment block follows CommonMark's HTML-block rule: it opens on a line
|
|
96
|
+
// starting with `<!--` and runs to the first line containing `-->`, so a one-line comment such as
|
|
97
|
+
// `<!-- prettier-ignore -->` hides nothing below it. Inserting that one-liner inside an open
|
|
98
|
+
// comment would close the comment early and expose everything after it.
|
|
99
|
+
class OpaqueBlockTracker {
|
|
92
100
|
marker = "";
|
|
93
101
|
|
|
94
|
-
// True when `line` opens, sits inside, or closes a fence.
|
|
102
|
+
// True when `line` opens, sits inside, or closes a fence or a comment block.
|
|
95
103
|
feed(line) {
|
|
96
104
|
const s = line.trimStart();
|
|
97
|
-
if (
|
|
98
|
-
|
|
99
|
-
|
|
100
|
-
|
|
101
|
-
|
|
102
|
-
|
|
103
|
-
|
|
105
|
+
if (this.marker) {
|
|
106
|
+
const closes = this.marker === "-->" ? line.includes("-->") : s.startsWith(this.marker);
|
|
107
|
+
if (closes) this.marker = "";
|
|
108
|
+
return true;
|
|
109
|
+
}
|
|
110
|
+
if (s.startsWith("```") || s.startsWith("~~~")) {
|
|
111
|
+
this.marker = s.slice(0, 3);
|
|
112
|
+
return true;
|
|
104
113
|
}
|
|
105
|
-
if (s.startsWith(
|
|
106
|
-
|
|
114
|
+
if (s.startsWith("<!--")) {
|
|
115
|
+
if (!s.slice(4).includes("-->")) this.marker = "-->";
|
|
116
|
+
return true;
|
|
117
|
+
}
|
|
118
|
+
return false;
|
|
107
119
|
}
|
|
108
120
|
}
|
|
109
121
|
|
|
@@ -112,7 +124,7 @@ const linesWithEnds = (src) => src.match(/[^\n]*\n|[^\n]+$/g) ?? [];
|
|
|
112
124
|
export function processText(src) {
|
|
113
125
|
const lines = linesWithEnds(src);
|
|
114
126
|
const out = [];
|
|
115
|
-
const fence = new
|
|
127
|
+
const fence = new OpaqueBlockTracker();
|
|
116
128
|
let i = 0;
|
|
117
129
|
while (i < lines.length) {
|
|
118
130
|
const line = lines[i];
|
|
@@ -158,7 +170,7 @@ export function processText(src) {
|
|
|
158
170
|
// Run on the POST-format text, so nothing escaping already fixed is reported twice.
|
|
159
171
|
export function auditText(src) {
|
|
160
172
|
const lines = src.split("\n");
|
|
161
|
-
const fence = new
|
|
173
|
+
const fence = new OpaqueBlockTracker();
|
|
162
174
|
const problems = [];
|
|
163
175
|
let i = 0;
|
|
164
176
|
while (i < lines.length) {
|
|
@@ -202,13 +214,9 @@ export function auditText(src) {
|
|
|
202
214
|
// Markdown files under the given roots. Walks skip `skills/` trees (third-party content: any file
|
|
203
215
|
// whose PARENT dirs include `skills`, so a file merely named skills.md is kept) and the record trees.
|
|
204
216
|
export function collectTargets(args, root = process.cwd()) {
|
|
205
|
-
const rel = (p) => path.relative(root, path.resolve(root, p)).split(path.sep).join("/");
|
|
206
217
|
const walked = (p) => {
|
|
207
|
-
const r =
|
|
208
|
-
return (
|
|
209
|
-
!path.dirname(r).split("/").includes("skills") &&
|
|
210
|
-
!RECORD_DIRS.some((d) => r === d || r.startsWith(`${d}/`))
|
|
211
|
-
);
|
|
218
|
+
const r = relTo(root, p);
|
|
219
|
+
return !path.dirname(r).split("/").includes("skills") && !isRecord(r);
|
|
212
220
|
};
|
|
213
221
|
const files = [];
|
|
214
222
|
for (const arg of args.length ? args : DEFAULT_ROOTS) {
|
|
@@ -237,6 +245,7 @@ export function main(argv, { root = process.cwd(), log = console.log } = {}) {
|
|
|
237
245
|
let changed = 0;
|
|
238
246
|
const unformatted = [];
|
|
239
247
|
const problems = [];
|
|
248
|
+
const warnings = [];
|
|
240
249
|
for (const file of targets) {
|
|
241
250
|
const abs = path.resolve(root, file);
|
|
242
251
|
const src = fs.readFileSync(abs, "utf8");
|
|
@@ -249,7 +258,8 @@ export function main(argv, { root = process.cwd(), log = console.log } = {}) {
|
|
|
249
258
|
log(`updated: ${file}`);
|
|
250
259
|
}
|
|
251
260
|
}
|
|
252
|
-
|
|
261
|
+
const found = isRecord(relTo(root, file)) ? warnings : problems;
|
|
262
|
+
for (const p of auditText(next)) found.push([file, ...p]);
|
|
253
263
|
}
|
|
254
264
|
if (checkOnly) {
|
|
255
265
|
for (const file of unformatted) log(`needs formatting: ${file}`);
|
|
@@ -257,15 +267,25 @@ export function main(argv, { root = process.cwd(), log = console.log } = {}) {
|
|
|
257
267
|
} else {
|
|
258
268
|
log(`\n${changed}/${targets.length} files updated`);
|
|
259
269
|
}
|
|
270
|
+
const report = (list) => {
|
|
271
|
+
for (const [file, lineNo, kind, detail] of list) {
|
|
272
|
+
log(` ${file}:${lineNo} [${kind}]`);
|
|
273
|
+
log(` ${detail}`);
|
|
274
|
+
}
|
|
275
|
+
};
|
|
260
276
|
if (problems.length) {
|
|
261
277
|
log(
|
|
262
278
|
`\n${problems.length} table defect(s) escaping cannot repair — a pipe in plain cell\n` +
|
|
263
279
|
"prose is indistinguishable from a column delimiter, so these need a human:\n",
|
|
264
280
|
);
|
|
265
|
-
|
|
266
|
-
|
|
267
|
-
|
|
268
|
-
|
|
281
|
+
report(problems);
|
|
282
|
+
}
|
|
283
|
+
if (warnings.length) {
|
|
284
|
+
log(
|
|
285
|
+
`\nWARN: ${warnings.length} table defect(s) in records (${RECORD_DIRS.join(", ")}) — kept as\n` +
|
|
286
|
+
"written, not a failure:\n",
|
|
287
|
+
);
|
|
288
|
+
report(warnings);
|
|
269
289
|
}
|
|
270
290
|
return problems.length || unformatted.length ? 1 : 0;
|
|
271
291
|
}
|
package/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,148 @@ Format: `## [version] — YYYY-MM-DD`
|
|
|
6
6
|
|
|
7
7
|
---
|
|
8
8
|
|
|
9
|
+
## [6.0.0] — 2026-10-25
|
|
10
|
+
|
|
11
|
+
### Breaking Changes
|
|
12
|
+
|
|
13
|
+
- **BREAKING — `bkit <noun> <verb>` prints text, not JSON; `--json` prints the old JSON.** stdout is `key: value` lines, nested keys indented under their parent, lists of flat rows as markdown tables. A hook, script or CI step that parses bkit output (piped to `jq`, or read with `JSON.parse`) reads nothing until it adds `--json`. The `bkit-cloud-bootstrap.sh` and `bkit-disk-prune.mjs` templates pass `--json`; copy the change into adopted copies. Setup tip `bkit-output-json` names each file still parsing text. Text output also leaves out the keys no workflow reads (each verb's `textOmit`, e.g. the written ledger `row`); `--json` prints every key. #681
|
|
14
|
+
- **BREAKING — the `package.json` `bkit` settings are grouped into sections, and `bkit upgrade` moves them for you.** `tracker` (`default`, `github`, `linear`, `jira`), `cloud.agent`, `providers.opencode` (`default`, `installed`), `testing` (`minPushPaths`, `ciCapstone`, `ciWorkflow`, `shipGate`), `workflows` (`minFreeGb`, `worktree`, `tasks`, and the ask points), `prompts.roadmapNext`, `dependencies.updater` and `advisories.ignore`. On install and upgrade, `migrateBkitLayout` moves each flat key to its section once and deletes the old key; `loopPause` becomes `ask` on every ask point. A value already at the new path wins, and the file keeps its indent. bkit reads only the new layout, so a script of yours that reads an old key from `package.json` reads nothing. `docs/migrations.md` lists every move. #693
|
|
15
|
+
- **BREAKING — `bkit prs merge` refuses a PR whose base is not `dev`.** It exits 8 and merges nothing, and `bkit prs open --base=main` is refused too: bkit opens and merges into `dev` only, and releases stay manual. A consumer script that merges a PR into another base through `bkit prs merge` breaks. #650
|
|
16
|
+
- **BREAKING — `bkit harvest` and `bkit analysis` are removed.** `bkit stats` replaces `bkit analysis` for a repo's own report. Collecting stats across repos is no longer part of the package. #683
|
|
17
|
+
- **BREAKING — `.bkit/.env` names the Jira key `BKIT_JIRA_API_KEY`.** `bkit upgrade` renames `BKIT_JIRA_API_TOKEN` lines in place and keeps the value. #675
|
|
18
|
+
|
|
19
|
+
### Added
|
|
20
|
+
|
|
21
|
+
- **`bkit context fetch` writes a JSON list from a context-fetch block as a markdown table.** It runs the same block runner as `bkit context run-block` (which stays). With `--render=table` (the default), a JSON array of flat objects becomes a table when the table parses back to the same values and types; anything else is written as printed, and stderr logs `render: raw (<reason>)`. The output as printed is copied to `{OUTBOX}/{name}.raw.{ext}` first, never committed; the clamp record gains `render`. `/bkit-debug` Step 4 fetches through it. #681
|
|
22
|
+
- **New verbs and flags for the git work workflows did by hand.** Each prints only the fields the workflow reads next. #679
|
|
23
|
+
- `bkit branches push --mode=plain [--set-upstream] [--ahead-of=<ref>]`: a feature-branch push, never forced; exit 21 when on `dev` / `main` or nothing is ahead.
|
|
24
|
+
- `bkit branches push --commit=<msg> [--label=…] --file --workflow`: one marker commit per run (auto-route suffix from the labels), then the push.
|
|
25
|
+
- `bkit branches fast-forward --onto=<ref>`: fetch and fast-forward; exit 22 when the local branch diverged.
|
|
26
|
+
- `bkit branches scan-diff --base=<ref>` with `--paths=<regex>`, `--marker=<text>` or `--code`: exit 0 when the diff has a match, 1 when not.
|
|
27
|
+
- `bkit branches force-build`: see Fixed.
|
|
28
|
+
- `bkit prs open --file --workflow`: a re-run reuses the PR the first run opened.
|
|
29
|
+
- `bkit workflows start --branch` (exit 15 on another branch; ship clears stale sentinels), `bkit workflows close --summary --summary-missing`, `bkit workflows handover --list-stray`.
|
|
30
|
+
- `bkit worktrees setup --issue` (ship prints `branchWarning`), `bkit counters route --rows=<type>:<next|count>`, `bkit status meta --debug-attempt=run`, `bkit runs gate --fetch`.
|
|
31
|
+
- `bkit ledgers commit --path=<file>` commits one file alone; `--stage-tracked-updates` with a commit mode commits tracked modifications too.
|
|
32
|
+
- **Workflows run from the prompt alone, with no issue, design or plan.** A missing issue no longer stops design, plan, build, debug or ship. Step 1 recovers the issue from a `FID` the prompt names or a `feat/{FID}` branch (`bkit fids parse`); with none, the run warns once (line 1 of its final message) and continues, skipping every tracker read, label, comment, board call and kill-switch check. Workflows still never create an issue. A run with no issue mints its `FID` as `{branch-suffix}-{slug}` with every all-digit word dropped, so no tracker can read it as an issue id; when a finished run already used that name, `bkit fids resolve` takes the first free `-b`, `-c`, … suffix (naming the `FID` in the prompt is how you continue a run). A `feat/{FID}` branch gives its suffix verbatim as the `FID` for any lowercase slug (`feat/upgrade-react-19`), and the issue id in it counts only when `.bkit/issues.jsonl` has a feature row for it; a branch suffix that is not a lowercase slug (`feat/Fix_CI`) stops the run and asks you to rename the branch or name an issue. #650
|
|
33
|
+
- **`bkit fids check --issue` and `bkit steps gate --issue`.** Passing the run's issue id (or an empty value for a run with no issue) checks the `FID` against it: with an issue the `FID` must embed that same id, with none any lowercase slug passes. `bkit prs open --issue` puts only `<!-- bkit:fid={FID} -->` in the PR body when there is no issue. #650
|
|
34
|
+
- **`/bkit-debug` on `dev` works in place, on its own paths and its own commits.** Steps 9 and 10 push nothing. Step 11 pushes only the run's commits with `bkit branches push --mode=dev`, then waits for the `dev` CI run at the pushed commit (`bkit runs dispatch --sha`, `bkit runs wait --until=completed`, `bkit runs gate --capstone-only`) before it releases the lock. A red run, a refused push or a replay conflict goes to the Failure Path naming the run; a file someone else changed during the run stops the workflow and asks you. #650
|
|
35
|
+
- **`bkit stats` writes this repo's stats report to `.bkit/stats.md`.** It reads only this repo's `.bkit/stats.jsonl`, `.bkit/friction.jsonl` and `docs/deferrals.jsonl`, and prints the report too. `chat` / `run` rows are not counted. Always exits 0. #683
|
|
36
|
+
- **Plan caps are a `package.json` setting, `bkit.workflows.tasks`.** `maxPerGroup` (default 3) and `maxTestsPerGroup` (default 15) cap each plan group's tasks and `TEST FIRST` tests; `maxTestsPerTask` (default 10) and `maxTestFilesPerTask` (default 3) cap each task. Install and upgrade add any missing key and never change a set one. A value that is not a whole number of 1 or more falls back to its default, and `bkit check` shows advisory `bkit-tasks-invalid`. `bkit tests plan-check` and `bkit challenge merge` read them; `bkit repo info` prints them as `tasks`, and `/bkit-plan` and `/bkit-build` pass them to every agent that writes, reviews, executes or verifies plan tasks; no prompt carries a number of its own. When `.github/ISSUE_TEMPLATE/bkit-change.yml` shows a cap as `(default N)` with N other than the configured value, `bkit check` shows advisory `bkit-tasks-form-stale` naming the number to change. #668
|
|
37
|
+
|
|
38
|
+
- **`bkit workflows summary` writes each phase's summary.** Design, plan, build, debug and ship run it at their Summary step instead of a summary subagent. It reads the run's `status.jsonl` rows, the plan files, `docs/deferrals.jsonl` and the Decision Pause files, writes `{workflow}-summary.md` and prints `verdict`, `failures`, `reasons` and `nextStep`. FAIL: a build plan task left unticked, a build with no plan file (`No plan file`), the last test run FAIL, or a step whose last row is FAIL with no later step answering it. CONCERNS: a step whose last row is CONCERNS, an item accepted at a Decision Pause, or a deferral written this run. The recommended next command comes from a fixed table per workflow and verdict. Ship's summary shows the PR's size from `gh` (`--pr`), and drops the line when `gh` fails. Ship now runs it after `@bkit-ship-update-docs` returns, not beside it. #682
|
|
39
|
+
- **`bkit challenge merge` turns build challenge findings into plan tasks.** It reads one or two challenge reports, each finding a task block under `## Findings Log` with `Severity`, `Class`, `Fixable`, `Location`, `DONE WHEN` and `TEST FIRST`. Findings at the same `path:line` merge into one (the worse severity wins); a location accepted at a Decision Pause is dropped, including a path with no file extension (`Makefile:12`). A finding at the `Location` and severity of an earlier challenge task that is still open reopens that task instead of adding a twin: its `**Round:**` line gains the round (`1, 2`) and it is listed in `reopened` and `fixTasks`. One already done in an earlier round gets a new task. CRITICAL, HIGH and MEDIUM findings are appended to `{FID}-plan.md` (`--plan`) as task blocks numbered after its last task, in new last groups of at most `bkit.workflows.tasks.maxPerGroup` tasks (default 3). More than 4 x `bkit.workflows.tasks.maxPerGroup` findings writes nothing and routes `pause` with `overflow` set, so the owner picks which to fix. Each LOW finding becomes a `docs/deferrals.jsonl` row with `reason` `low-severity`. The plan is checked before it is written: a failing check (exit 23) changes no file and prints the `problems`; Build Step 10 then re-runs the reviewers once with them, as it does for exit 22. It prints `route`: `pause` when a finding says `Fixable: false`, round 2 left tasks or the findings overflow, `fix` when it appended or reopened tasks, else `none`; also `fixTasks` (reopened, then appended), `appended`, `reopened`, `deferred` (rows written), `dropped`, `plan` and `round`. `overflow` counts only new CRITICAL, HIGH and MEDIUM findings. A report with findings but no task blocks exits 22. Running it again with the same reports appends nothing. Build Step 10 runs it. #682
|
|
40
|
+
- **`bkit status resume --workflow=<name>` names where a stopped run picks up.** It reads `status.jsonl` and prints the step after the active `IN_PROGRESS` run's last `DONE` step (`step`, `number`, `title`, `after`, `group`, `active`, and for build `challengeRound` and `challengeDone`). A build stopped after a Decision Pause resumes where that decision's row sends it: each row records `route` (`fix` → Plan Execute, `verify` → Plan Verify, `tests` → Run Tests). Steps 1-2 run again on every resume, so their rows place no resume point; rows of steps the workflow no longer has are ignored; a step whose next step depends on its verdict resumes at itself; a Plan Execute row with verdict `HANDOVER` resumes at Plan Execute for the same group. A build stopped in one of the removed challenge steps resumes at Run Tests. Every workflow's Resume line calls it. Exit 2 for an unknown workflow, 3 for an unreadable log. #682
|
|
41
|
+
|
|
42
|
+
- **`bkit context brief` writes one build group's brief.** `--plan` and `--group=N` (or `--next`, the first group with an open task) write `build-brief-{G}-{n}.md` into the `--dir` logs folder: the plan's title, Context & Goals, Narrative, Success Criteria and Out of Scope; every group and task with its state; the group's open task blocks word for word; the reds `status.jsonl` (`--file`) already holds for them, each marked "test written and seen failing; code may be partly done"; one line per earlier task they depend on; the plan's `Reuse Inventory` rows and `Architecture & Component Changes` entries that name the open tasks' `CREATE` / `UPDATE` / `DELETE` files; and the `--note-file` text under Deviations. A task is done when its box is ticked or a `build-plan-execute-*-log.md` in the folder has its `DONE — TASK N` line. It prints only `artifact`, `bytes`, `group`, `tasks`, `workBytes` and `workCap` (8192), so the orchestrator never reads the brief. Inventory rows and Architecture entries past the 8 KB work cap are left out and counted, and the brief names the plan section to read instead; task blocks over the cap warn. `--next` with nothing open writes nothing and prints `group: null`. #668
|
|
43
|
+
- **`bkit check` lists plans the next build will convert.** Advisory `plan-task-markers-missing` names each `docs/plans/{YYYYMM}/{FID}-plan.md` with no task markers whose FID has not shipped (`archive/` and `logs/` are not read). Nothing to do by hand: the FID's next `/bkit-build` converts it. #668
|
|
44
|
+
- **Workflow closes record how full each subagent's context got, and `bkit stats` reports it.** On Claude Code, `bkit workflows close` adds `ctx` to the `outcome` row: for each agent type, how many subagents ran (`runs`) and the largest context one model call reached (`peak`), read from the closing session's subagent transcripts that started during the run. `.bkit/stats.md` gains `## Agent context peaks` (agent type, subagents, runs, peak, runs over 160,000 tokens), or "No context data." when no run recorded any. Other hosts record nothing: Cursor keeps no token counts, and Codex, opencode and Antigravity give no confirmed way to tell this run's transcripts apart. A run spread over two Claude Code sessions counts only the closing session. A transcript folder that cannot be read is skipped and never fails the close. #668
|
|
45
|
+
- **`bkit status route --step=` prints `parentSha`,** the commit HEAD was at when the step's last row was written. For a `build-group-start` row that is the group's start commit, so `bkit context diff --base=<parentSha>` reviews only that group's commits. #668
|
|
46
|
+
|
|
47
|
+
- **Every bkit Claude Code subagent summarises its context at 300,000 tokens at the latest.** Each `bkit-*` agent (and the `utility-*` release agents) carries `autoCompactWindow: 300000` in its frontmatter; it only lowers the window, so a lower repo or user setting and `CLAUDE_CODE_AUTO_COMPACT_WINDOW` still win (Claude Code v2.1.296+). Codex, opencode, Cursor and Antigravity have no working per-agent setting, so their renderers drop the field; `.bkit/providers.md` § Context compaction lists each host's answer with its source. Your main session's window stays your setting. #668
|
|
48
|
+
|
|
49
|
+
- **`bkit counters progress`** reports how a fix loop is going since the last decision: problems after each round (`5 → 2`), whether the rounds changed source code, the last and next fix strategy, minutes per round, a trend (`closing` / `stuck` / `worse`) and a recommendation. #670
|
|
50
|
+
- **Step 1 of every phase workflow resolves the issue and `FID` in the engine.** The workflow writes the session prompt to `{SESSION_DIR}/prompt.md` (`bkit repo info` now prints `sessionDir`, a new folder per run under the outbox, pruned after 7 days). `bkit fids parse --prompt-file` prints the issue it names (`source`, `issue`, `ref`, `fidNamed`) for GitHub, Linear or Jira. `bkit fids resolve` replaces the prose chain: a `FID` the prompt names, the `feat/{FID}` branch, the feature logged for the issue (on `dev` too), a mint from the title, then a free `-b`, `-c`, … suffix and the format check, in one call. `bkit fids plans` counts build's sub-plans and tells build and ship when there is no plan. `bkit fids design --description-file --prompt-file` gives plan its parent design and audit report paths; a named file that is missing exits 7. #677
|
|
51
|
+
- **`bkit workflows start` prints where a resumed run picks up.** `lastDoneStep` is the run's last finished step, and `openDecision` the build Decision Pause still waiting for an answer, with every field Step 3 of the pause needs. The workflows no longer read `status.jsonl` or decision files by hand to resume. #677
|
|
52
|
+
- **The engine reads and writes the tracker; the tracker MCP is the fallback.** On GitHub (`gh` with `BKIT_GH_TOKEN`), Linear (its GraphQL API with `BKIT_LINEAR_API_KEY`) and Jira (the Rovo MCP endpoint over HTTP with `BKIT_JIRA_API_KEY`), bkit verbs now post step comments (`steps finish --post`, `issues comment --post`, `workflows fail|handover|close|links --post`), write labels, state and the board move (`issues labels --write`), and read issues. Each prints `tracker`; the workflow calls the tracker MCP only when a verb exits 80 or prints `done` = false. A re-run never posts the same step comment twice: `status.jsonl` records each post as an `engine-action` row, and close-time comments are checked against the issue's last 5 comments. #675
|
|
53
|
+
- **New tracker verbs.** `bkit issues fetch` writes the issue's description, comments and facts to the session folder (or the outbox) and prints only `title`, `url`, `state` and `labels`. `bkit issues related` reads each related-search hit and writes the related-issues file. `bkit issues blocked-by` prints a build's open blockers. `bkit workflows input` writes the run's input file. `bkit runs context` prints `ref`, the issue as `/bkit-auto` passes it on. #675
|
|
54
|
+
- **`bkit workflows close --final-return` prints the run's last message.** It holds the summary, the issue link, `## Suggested Replies` and `## bkit Tips`; `--warning`, `--line` and `--suggest` add the run's own lines. `workflows close` and `workflows fail` delete the run's session folder when given `--session-dir`. #675
|
|
55
|
+
- **`bkit tests run` counts failing tests itself and writes the trimmed log.** It empties `{log}.reports/` next to the log and passes it to the gate as `$BKIT_TEST_REPORT_DIR`; `failures` is the failing plus erroring test cases in the JUnit files written there. A FAIL with no reports prints `failures: null` and a hint, never a guessed count. `--artifact --fid --step --attempt` copies the log into the plan folder, trims it and records the trim in the same call (exit 5 when that fails); build Steps 7 and 14 and debug Step 3 use it, and drop `--failures` when the count is unknown. Wire your test runners' JUnit output into that folder (`docs/testing.md` § JUnit reports for bkit). #678
|
|
56
|
+
- **`bkit status route --prompt-file` decides debug's start.** For `--workflow=debug` it prints `debugAttempt`, `debugMode`, `soakEntry`, `repro` and `gates` from the session prompt and the current run (`--fid` and `--month` stand in for `--file`). Debug's Step 1 is one call instead of jq and prose. `[live=off]` now counts only in the session prompt, not in the issue body. #678
|
|
57
|
+
- **Every trimmed file keeps its untouched original in the outbox.** `context clamp`, `context run-block`, `context diff` and `tests run --artifact` copy the original to `{OUTBOX}/{name}.raw.{ext}` before cutting it (never committed). The clamp record gains `raw`, `source` (the command and inputs that produced the file) and `fetchedAt`. `context clamp` takes `--source`. #678
|
|
58
|
+
- **After-check `github-project-token-scope`.** With a GitHub board configured, `bkit check` warns when `BKIT_GH_TOKEN` cannot write it (a classic token without the `project` scope, or a fine-grained token that cannot see the board), and names the fix. Skipped on cloud runtimes, where the engine never moves the board. #675
|
|
59
|
+
- **Every point where a run can ask you has an `ask` setting and a hard limit.** `package.json` `bkit.workflows.<workflow>.<point>` holds both: `design.grill` (`maxTurns`, default 6), `build.verify`, `build.challenge`, `build.tests`, `debug.fix`, `debug.soak` and `ship.merge` (`maxAttempts`, default 2), each `ask: true` by default. A used-up limit always goes to the Failure Path, and a question never resets a count. With `ask: false`, or in a headless GitHub Actions run, the run takes each recommendation: `Fix now` is applied, and an `Accept` is recorded as assumed. Questions with no recommendation are still asked in a session and go to the Failure Path headless. `bkit counters route --point=` and `bkit counters max --point=` read the settings; a bad value falls back to its default with the advisory `bkit-ask-settings-invalid`. #671
|
|
60
|
+
- **`bkit decisions compose`, `apply` and `pending` handle build questions from pause to ship.** `compose` writes the Decision Pause file in one question layout from the orchestrator's items JSON, with the progress block and the loop question first for `--loop=verify|tests`. `apply --by=headless` takes each recommendation and writes `Accept (assumed)`; it exits 4 when questions with no recommendation are left. `/bkit-ship` lists the assumed items with `pending` at its new Confirm Assumed Items step and asks you to confirm each: `apply --by=owner --confirm` writes the real acceptance, `--reject` records the rejection, and `pending --defer` writes one `needs-decision` deferral per item rejected or never confirmed; ship still merges. #671
|
|
61
|
+
- **`.bkit/authoring.md` holds the authoring rules for every agent-read markdown file.** Docs, prompts and workflows share one set: § All Agent-Read Files, § Notation (one job per punctuation mark, the closed list of capitalised words), § Docs, § Prompts and Workflows, § Prompts Only and § Workflows Only. It ships with the other `.bkit/*.md` docs and has a row in `.agents/docs.md`; `.bkit/prompts.md` and `.bkit/workflows.md` keep only the explanations behind the rules. #684
|
|
62
|
+
|
|
63
|
+
### Changed
|
|
64
|
+
|
|
65
|
+
- **Ship, debug and build make no raw `git` / `gh` calls, `jq` pipes or hand copies.** Every one is now a `bkit` verb, and a test in `workflow-fence-syntax.test.ts` fails on any that comes back (the `{BKIT}` bootstrap line is the one named exception). Ship Step 5 now stops when the fetch of the PR branch fails, where it used to carry on with the local copy. #679
|
|
66
|
+
- **Each agent that reads the run's diff gets a fresh diff file.** Build Steps 7, 9 and 10, debug Step 10, ship Step 5 and every Failure Path handover run `bkit context diff --reset-log` into `tmp/bkit-diff-{FID}.md` right before the agent; the Large Diff Guard rule is gone. Past 10000 lines the file names the files it does not show whole, and the security challenger reads each security-relevant one with its own `git diff`. `context diff` prints `omitted` and takes `--reset-log`. #678
|
|
67
|
+
- **`/bkit-plan` runs one review round with two reviewers and one scope check.** Step 5 runs `@bkit-plan-review-1` (tightness and task order), `@bkit-plan-review-2` (regression risk) and `@bkit-plan-scope-check` (template, criteria and verification) in parallel; Step 6 applies all three reports in one pass to `plan-v2-reviewed.md`. The separate scope round and its apply step are gone. review-1 fails a plan only for a task-order cycle no reordering fixes or a plan that contradicts its design. `bkit upgrade` removes the retired agent files from each host. A plan paused mid-review under the old steps: run `/bkit-plan` again. #665
|
|
68
|
+
- **Build Step 10 runs only the security reviewer on a small change.** `bkit challenge gate` fetches `origin dev` first (offline, it measures against the last fetch and logs that), then measures `origin/dev...HEAD` (`docs/plans/**` excluded) on every pass: under 300 lines and 10 files, `@bkit-build-challenge-2` runs alone and challenge-1 is skipped; a larger change runs both. Each pass writes a `challenge-gate` row to `status.jsonl`, the summary's `## Challenge` section says when challenge-1 was skipped, the `outcome` row carries `build.challenge.gate`, and `bkit stats` counts runs by size. #665
|
|
69
|
+
- **`.bkit/prompts.md` § Model Overrides rows naming an agent bkit no longer ships are reported.** `bkit install`, `check` and `upgrade` list them as the `model-override-unknown-agent` advisory; those rows are not applied. #665
|
|
70
|
+
- **The build challenge is one step, and build has 15 steps.** Step 10 runs the two challenge reviewers, then `bkit challenge merge` adds their findings to the plan as tasks, each with a test to write first. Fixable findings go back through Plan Execute and Plan Verify once (round 2 reviews again but never fixes on its own); a finding no agent can fix, or anything left after round 2, goes to the Decision Pause. Accepting a challenge task there ticks it in the plan. The challenge's `status.jsonl` row records the round it ran as, and `bkit status resume` reports it back as `challengeRound`, so a resumed build picks up the right round. The challenge runs at most two rounds: once a round-2 challenge has merged, `bkit status resume` prints `challengeDone: true` and Step 10 goes on to Run Tests, and a round-2 `Fix now` runs the fix without a third review. A build resumed into an open challenge Decision Pause re-runs the size check and the merge, which finds its tasks already in the plan and writes nothing, and asks the same questions again. The old Steps 11-13 (reconcile, remediate, edge-case tests) are gone, and Steps 14-18 are now 11-15: Run Tests 11, Failure Diagnose 12, Failure Remediate 13, Summary 14, Close Workflow & Create PR 15. `MAX_CHALLENGE_REMEDIATE_ATTEMPT` is removed. #682
|
|
71
|
+
- **`@bkit-build-plan-execute` writes `docs/knowledge.jsonl` gotcha rows** once its tasks' tests pass, now that it fixes challenge findings. #682
|
|
72
|
+
- **`/bkit-plan` writes its tasks in groups and checks the plan after every write; it has 8 steps.** `@bkit-plan-generate` writes groups of task blocks in build order, each group at most 3 tasks and 15 `TEST FIRST` tests. A task's `DEPENDS ON` takes task numbers (`1, 2`) or `TASK N` names. Step 3 runs `bkit tests plan-check --existence=refuse` on the draft straight after the agent, and Step 6 runs it again on `plan-v2-reviewed.md`; a refused plan goes back to the same agent once to fix only the lines the report names, and a second refusal fails the run. A draft still holding `PENDING` (the agent hit its turn cap) gets one more `@bkit-plan-generate` that fills only the `PENDING` sections. Fetch Context no longer checks the draft. Summary is Step 7 and Close Workflow Step 8; a plan stopped after the old Complexity Split resumes at Summary. #668
|
|
73
|
+
- **`bkit tests plan-check` refuses more malformed plans.** Group numbers must ascend through the file, and task numbers within a group, because the build runs groups in file order; neither may be 0. `DEPENDS ON`, `DONE WHEN`, `TEST FIRST` and `TEST EXCEPTION` may each appear once per task. A bold `**TASK N:**` line inside another task's block, and a task depending on itself, are refused. A code fence that is never closed is reported by its line ("nothing after it is read"). A plan with Windows line endings (CRLF) reads like any other, and `DEPENDS ON: none (...)` names no task. #668
|
|
74
|
+
- **`bkit tests green` reports a `DELETE` that did not happen.** A plan task's `DELETE` line whose file still exists, or whose name is still found in the tree (`git grep`, untracked files included, the plan folder skipped), is a `delete-still-referenced` gap. A `DELETE` and `CREATE` of the same thing is a move and is not checked; for a file-only `DELETE` with a `CREATE` of the same file name, the new file and paths to it are not counted as references; when the search itself fails, the gap says `references not checked`. Plan Verify reads each hit: a different thing with the same name is no gap, anything else is `Fixable: true`. A `§ heading` must match a heading line exactly, and in a JSON, YAML or TOML file a dotted key must match its full path (flat or nested, one-line JSON included); in code and other files it matches its last segment. `bkit tests green --group=N` exits 2 when the group is missing or has no tasks. #668
|
|
75
|
+
- **`bkit workflows promote` copies `{FID}-plan.md` only.** It no longer copies or archives `{FID}-plan-N.md` sub-plans and prints no `subPlans`; a `{FID}-plan-N.md` an older run left in the bucket stays where it is and nothing reads it. The newest draft never counts `plan-vN-split.md` or `plan-vN-K.md`, so a re-run of an old split plan promotes its new reviewed plan. `bkit branches land` checks only the one canonical doc. #668
|
|
76
|
+
- **`/bkit-build` runs one plan group at a time.** Steps 6-8 loop over the groups of `{FID}-plan.md`: `bkit context brief --next` writes the group's brief and `@bkit-build-plan-execute` reads only that; verify judges the group's own diff (`bkit context diff --base=` the group's start commit) and is the only step that ticks tasks; the gate between groups writes a `build-group-gate` row (it was `build-subplan-gate`). Verify attempts count per group (`bkit.workflows.build.verify.maxAttempts`). Holistic verify (Step 9) and the challenge (Step 10) run once, after the last group. A Decision Pause `Fix now` writes a task block into the paused group when it stays within 3 tasks and 15 tests, else into a new group right after it; Accept writes a `TEST EXCEPTION` field. `@bkit-build-plan-execute`, `@bkit-build-plan-verify` and `@bkit-build-plan-gaps-remediate` now stop at 100 turns. Near its turn cap `@bkit-build-plan-execute` sets the verdict `HANDOVER`; Step 6 then runs the group once more with a fresh brief that leaves out its `DONE` tasks, counted as a handover, not a failed attempt, and the re-run keeps the existing log. The tracker comment shows `HANDOVER`. #668
|
|
77
|
+
- **A build with no plan, or a plan with no task markers, gets one written first.** Step 3 runs `bkit tests plan-check`; when it finds no plan or no task blocks, the new `@bkit-build-plan-convert` agent writes `{FID}-plan.md` in task-block form, and the check runs again. It works from `build-input-{RUN}.md`, which Step 2 writes for every build with the prompt, the issue text and the plan as it arrived, keeping an existing plan's other sections; where the plan and the issue disagree, the plan wins. Only the convert agent reads `build-input-{RUN}.md`: it holds the whole plan again, so execute, verify, install-skills, the challenge agents and diagnose work from the plan or the group's brief instead, and run instructions in the session prompt (a redo, a resume, a constraint) reach each brief's `Deviations` section through `bkit context brief --note-file`. Ship no longer records `planSource`. A build already past its execute step finishes on the bkit version it started on: upgrade between builds, not during one. On a plan with no task markers `bkit tests green` stops with "this plan has no task markers; run /bkit-build again to convert it" instead of reporting zero tasks. #668
|
|
78
|
+
- **Workflow input files are dated, and the newer text wins.** `bkit workflows input` writes the issue description and each human comment as its own section, each comment with the time it was posted, and dates the plan, design and audit report sections by their last commit's author date (uncommitted changes count as newer than any commit). Every agent that reads an input file is told: where two sections disagree, the newer one wins, and older text still counts wherever nothing newer contradicts it. `###### bkit:ignore-earlier` is still the only way to drop text. `/bkit-build` also runs `@bkit-build-plan-convert` when the issue has comments posted after the plan's last commit, so those comments change the plan before any code; `workflows input` prints the count as `newerThanPlan`. #691
|
|
79
|
+
- **The change issue form shows the plan's full task block.** Its Tasks example and `.bkit/trackers.md` § Issue shapes show every field a plan task has: `CREATE` / `READ` / `UPDATE` / `DELETE`, `DEPENDS ON`, `DONE WHEN`, `TEST FIRST` and `TEST EXCEPTION`, with the group and per-task caps. Free text still works: the build converts it. Copy the updated `.github/ISSUE_TEMPLATE/bkit-change.yml` from `.bkit/templates/` if you use the form. #668
|
|
80
|
+
- **A `TEST EXCEPTION` written in an issue is a request the owner confirms.** The convert agent and `@bkit-plan-generate` copy it into the task word for word and never write one of their own. `bkit tests green` now checks who wrote an exception on a task with no `TEST FIRST` too: one last changed by a workflow step commit is an `exception-refused` gap, which verify marks `Fixable: false`, so the build stops at the Decision Pause. Accept replaces the field with your reason and the date, so its plan-only commit always has a change and git credits you. A plain `TEST FIRST: n/a — reason` is not checked. #668
|
|
81
|
+
- **Subagents carry their bkit rules in the prompt and read only what sits below `bkit:end`.** Each `.bkit/core/prompts/*.md` agent has a `**bkit Rules:**` block holding, word for word, the bkit rules it acts on. Its `**Rules:**` line now reads `.agents/rules.md` below `<!-- bkit:end -->` only (`Universal Rules`, skipping `Orchestrator Rules`): an agent that can search finds that line with `grep -n` and reads from there, so it never loads the bkit block. `bkit-build-plan-execute` also carries `Check gotchas first`. A rule every subagent must follow belongs under `## Project Rules` › `### Universal Rules`; `## Project Settings` still reaches subagents. Workflows still read all of `.agents/rules.md`. #666
|
|
82
|
+
- **A sentence in two or more prompts, or two or more workflows, has one master wording.** It is a clause in `.bkit/instructions.md` § Clauses, and `pnpm instructions:sync` keeps every copy in step: it rewrites near copies and old wordings, and the check fails on a prompt or workflow missing its clause. The cut-off was 5 prompts and 3 workflows; audit templates stay at 5. #684
|
|
83
|
+
- **Plan and audit templates hold shape only; the prompts that act on them carry the rules.** `docs/templates/bkit-plan.md` keeps its headings, tables, checkbox labels, owner callouts and the lines the engine parses, and drops every instruction block (37.4 KB to 15.7 KB, so every new plan is that much smaller). The 35 audit templates drop their shared boilerplate; `bkit-audit-generate` carries it once. `bkit-build-plan-execute` ticks every applicable Pre-Flight and gate box and continues without asking. The `Permissions`, `No placeholders` and `Process Improvements` report boxes each say in a few words what they check. Your `Project Instructions` below `bkit:end` still apply: step titles, numbers and the `Permissions` label are unchanged. #667
|
|
84
|
+
- **Nine rules join `.agents/rules.md`:** New file locations, UI design, Dependencies, Tests discriminate, Test-only files, Explicit logging, CLIs over dashboards, Server-side validation, Multi-store writes. They lived only in the plan template, so agents working without bkit now get them too. #667
|
|
85
|
+
- **Six rules are sharper.** R24 allows appending a log line to your own step output file with `>>`; R43 excepts standing audit parents; R61 lets docs-only landings push straight to `dev` through `bkit branches land`, with a PR only when the push is refused; R62 accepts an explicit empty merge body; R94 excepts a workflow's named decision points; R98 resolves `FID` from tracker markers, or from a `feat/{FID}` branch when no tracker is wired. #666
|
|
86
|
+
- **`bkit-utility-update-tracker` never comments on issues,** reads labels through the tracker MCP first, and lists bugs it finds under `## Found Bugs` for the orchestrator to file; `bkit-utility-update-roadmap` does the same and lists every container with its URL. #666
|
|
87
|
+
- **Every planner prompt that writes `TEST FIRST` names the per-task caps,** as do the issue shapes: 1 to `bkit.workflows.tasks.maxTestsPerTask` tests (default 10) across at most `bkit.workflows.tasks.maxTestFilesPerTask` test files (default 3), the caps `bkit tests plan-check` enforces. A test pins these defaults to the engine's. #667
|
|
88
|
+
- **The `**Code reads:**` line names `grep -l` before `grep -n`,** limits whole-file reads to short files or files being rewritten, and allows a re-read after context was summarised. Prompts with neither `Grep` nor `Bash` no longer carry it. The `**Tools:**` header label is now `**Verify tools:**`. #666
|
|
89
|
+
- **Install and upgrade write every `bkit` setting into `package.json`.** Each setting is now visible where you look for it. A missing key gets its default (for example `workflows.build.verify`, `prompts.roadmapNext: 25`, `testing.minPushPaths`, `workflows.worktree.copy`, the tracker progress and review states); a choice not made yet (`tracker.default`, `cloud.agent`, `tracker.github.project`, `providers.opencode.default`, ...) gets `""` or `[]`, which reads exactly like absent, so the tracker and cloud setup nudges still show. A key already set is never touched, nested blocks get their missing keys, and `bkit check` reports a missing one. #670
|
|
90
|
+
- **Fix loops ask you before each further round.** The build verify → fix-gaps loop and the build tests → diagnose → fix loop stop at the Decision Pause after a failed round while their limit has rounds left, instead of retrying on their own. The pause opens with the progress report and asks whether to run another fix round, worded so "yes" takes its recommendation; **Try again** runs exactly one more round, using the next strategy, and the fixer reads your answer. Whether a loop asks, and how many rounds it gets, are its ask point's `ask` and `maxAttempts` settings (#671). #670
|
|
91
|
+
- **`.bkit/stats.md` is committed.** The managed `.gitignore` block no longer ignores it, so commit the file after `bkit stats`. It holds no timestamp and changes only when the ledgers do. #683
|
|
92
|
+
- **`/bkit-ship` of `dev` or `main` prints the engine's refusal and stops.** It releases its lock first. `bkit worktrees setup` also refuses `main` in place for design, plan and build. #650
|
|
93
|
+
- **`api.github.com` is in the egress allowlist.** The engine's GitHub tracker calls need it on runtimes that filter egress. #675
|
|
94
|
+
|
|
95
|
+
### Fixed
|
|
96
|
+
|
|
97
|
+
- **`/bkit-debug` runs the integration gate when no e2e gate is declared.** Debug Step 3 now tries `bkit:gate:static-unit-integration` before `bkit:gate:static-unit`, so it runs the same gate as build; it used to skip integration tests and could report green on a failure build caught.
|
|
98
|
+
- **The `rm -rf` guard covers the home folder itself.** Every host denies `rm -rf` / `rm -fr` on `~`, `$HOME` and `${HOME}` (bare, with `/` or `/*`), as well as `/`. The hooks also catch `-Rf` and `-r -f`. Only `~/*` and `$HOME/*` were denied before.
|
|
99
|
+
- **`bkit check` passes after `bkit uninstall --opencode` or `--auto`.** A targeted uninstall resets the module's `bkit.providers.opencode` or `bkit.cloud.agent` keys to unset (`""`, `[]`) instead of deleting them, so check no longer reports them as missing.
|
|
100
|
+
- **`[force build]` now reaches CI on a pull request.** CI reads markers from the PR title on `pull_request` events, so the empty `[force build]` commit build Step 18 pushed was ignored. The new `bkit branches force-build` adds ` bkit [force build]` to the open PR's title, then pushes the empty marker commit, whose `synchronize` event starts the run that reads the title. It never amends, and a re-run does not push a second marker. Build calls it after `prs open` when the branch changes a `migrations/` or `migrate/` directory. The consumer CI template reads the marker differently from bkit's own `bkit-ci.yml`: the PR title on `pull_request`, else the head commit message, including on `workflow_dispatch`; bkit's own reads the head commit only on pushes to `main` / `dev`. #679
|
|
101
|
+
- **A finished debug run no longer forces the next run into SOAK.** Soak rows from a closed run used to count on the next run of the same `FID`. #678
|
|
102
|
+
- **A SOAK escalation survives a resumed debug run.** An escalation recorded only in `workflow-meta` used to be lost on resume, and the run restarted in NORMAL. #678
|
|
103
|
+
- **`bkit status route` reads a FAIL with no `failures` as `null`.** It used to print 0. #678
|
|
104
|
+
- **`/bkit-debug` no longer stages the whole tree for its CI-trigger commit.** It runs `git commit --allow-empty` only. On a feature branch, the design, plan, build and debug Failure Paths remove only files the run created by mistake, never other agents' changes. #666
|
|
105
|
+
- **A debug or build after a failed ship starts instead of stopping at Step 2.** A failed ship saves its record to `dev` and leaves the feature worktree as it was; the next resume rebase refused to start over those files (exit 9). `bkit worktrees setup` now commits what an earlier run left uncommitted before that rebase (`chore({FID}): carry the failed ship record left uncommitted bkit`, reported as `carriedSha`). An untracked log `dev` already holds is dropped first so `dev`'s copy wins (`carriedDropped`), and the `bkit.workflows.worktree.copy` entries (such as `.env`) are never committed. Exit 9 now means only that this commit was refused. #662
|
|
106
|
+
- **Failure handovers and close commits never commit the `bkit.workflows.worktree.copy` entries either.** `bkit workflows handover --push` on a feature branch and `bkit workflows close --message` used to commit the whole worktree, so a `.env` that setup copied in and the project had not gitignored could land in a pushed commit. Both now leave those entries out. #662
|
|
107
|
+
- **The ship naming warning fires on a run with no issue.** A branch not named for the `FID` now warns when `ISSUE_ID` is empty; an empty id used to match every branch name. #650
|
|
108
|
+
- **Build Step 15.9 and debug Step 11.9 kill-switch checks skip when `ISSUE_ID` is empty,** and ship Step 14.3's label calls skip on a merged run with no issue. #650
|
|
109
|
+
- **The build boundary gate (Step 7) and the debug local test run (Step 3) can pass their own format check.** Both wrote their test log straight into `docs/plans/{YYYYMM}/logs/{FID}/`, where the gate's `prettier --check .` found the half-written log and failed. They now log to the outbox and copy the finished log in. The `.prettierignore` template gains three `docs/plans/*/logs/*/` lines (`run-tests-*.md`, `build-subplan-gate-*.md`, `context-tests-local-*.md`); templates are copy-and-own, so a consumer that already adopted `.prettierignore` adds the three lines by hand. #650
|
|
110
|
+
|
|
111
|
+
### Removed
|
|
112
|
+
|
|
113
|
+
- **The `bkit-plan-complexity-split` subagent and plan Step 7 Complexity Split.** Groups of task blocks replace sub-plans. `bkit upgrade` deletes its host copies. #668
|
|
114
|
+
- **The chat-stats template (`.bkit/templates/scripts/stats/`).** An adopted `scripts/stats/` copy keeps working on its own; delete it if unused. #683
|
|
115
|
+
- **Three plan subagents: `bkit-plan-review-3`, `bkit-plan-scope-check-1` and `bkit-plan-scope-check-2`.** `/bkit-plan` runs `@bkit-plan-review-1`, `@bkit-plan-review-2` and one `@bkit-plan-scope-check` instead. `bkit upgrade` deletes their host copies; a `## Model Overrides` row naming one of them is reported as `model-override-unknown-agent` and can be deleted. #665
|
|
116
|
+
- **The five summary subagents: `bkit-plan-summary`, `bkit-design-summary`, `bkit-build-summary`, `bkit-debug-summary` and `bkit-ship-summary`.** `bkit workflows summary` writes the summary instead. `bkit upgrade` deletes their host copies; a `## Model Overrides` row naming one of them no longer matches an agent and can be deleted. Past `status.jsonl` and `.bkit/stats.jsonl` rows that name them stay as written. #682
|
|
117
|
+
- **Three build challenge subagents: `bkit-build-challenge-reconcile`, `bkit-build-challenge-remediate` and `bkit-build-challenge-tests`.** `bkit challenge merge` folds the findings into the plan, and Plan Execute fixes and tests them. `bkit upgrade` deletes their host copies; a `## Model Overrides` row naming one of them no longer matches an agent and can be deleted. Past `status.jsonl` rows that name them stay as written. #682
|
|
118
|
+
|
|
119
|
+
---
|
|
120
|
+
|
|
121
|
+
## [5.5.1] — 2026-10-22
|
|
122
|
+
|
|
123
|
+
### Breaking Changes
|
|
124
|
+
|
|
125
|
+
- **BREAKING — the GitHub board setting is `bkit.github.project`, the board's URL.** It sits under `bkit.github` beside `progress` and `review`, the same shape as `bkit.linear` and `bkit.jira`. Paste the board URL from the browser: `"github": { "project": "https://github.com/orgs/<org>/projects/<number>" }`, or `/users/<login>/…` for a personal board; a trailing `/views/<n>` is fine. Status is set by option name, `In progress` and `In review` by default (the names GitHub's board templates use); set `bkit.github.progress` / `review` if your board names them differently. You no longer look up a Status field id or option ids. Personal boards now work: the old setting always asked for an organization's board, so a personal board failed with a 404. `bkit upgrade` moves an old `bkit.githubProject` for you; if it logs that an option id has no name, set that name by hand. The `github-project-status-field-id-format` advisory is gone with the field id. `bkit issues labels --board` prints two payloads, `addItem` and `updateItem`; `listItems` is gone, and `boardSkipped` can be `project-url-invalid`. `bkit repo info` prints `trackerBoard`.
|
|
126
|
+
|
|
127
|
+
### Added
|
|
128
|
+
|
|
129
|
+
- **A local stack lock keeps worktrees off each other's local services.** Every worktree of a repo shares each local service whose names and ports come from the repo's config (a Docker database, an emulator), so a reset from one worktree wiped the data under another worktree's test run. Copy the new template `.bkit/templates/scripts/ci/bkit-local-stack-lock.sh` to `scripts/ci/`, wrap the `package.json` scripts that start, reset or stop the stack in its `run` mode, and source it in local runners that test against the stack. A second run waits and names the run holding the stack; the lock frees itself within a second of its run ending, however the run ends; CI skips it. The new `.agents/rules.md` rule `Shared local stack` tells agents to use those scripts, never the raw command. Setup: `.bkit/templates.md` § Local stack lock.
|
|
130
|
+
- **`.agents/rules.md` gets a `Project Settings` section for where your services live.** A table at the end of the file holds the identifiers agents pass to MCP servers and CLIs: the GitHub repo and project board, Sentry org and project, Supabase project refs, Vercel team and project. Agents read the file every session, so they no longer have to guess or ask. It is reference only and changes no workflow, gate or permission. New installs get the section with commented example rows; in an existing install, add `## Project Settings` after your `Project Rules` and fill in a `Service | Setting | Value` table. Put non-secret identifiers only; tokens stay in env files.
|
|
131
|
+
|
|
132
|
+
- **On a push to `dev`, the pre-push slop scan compares against the same commit CI does.** CI's slop scan on a `dev` push compares against the head of the last green CI run on `dev`; pre-push compared against the merge-base with `origin/dev`. Once a red push had landed a slop finding on `dev`, every later local check passed while CI stayed red. `scripts/ci/lanes/resolve-push-base.mjs` gains a local mode, `--local --branch=dev --head=<pushed sha>`: it reads the repo from `origin`, uses `origin/dev` where CI uses `event.before`, and tests ancestry against the pushed commit. The `.husky/pre-push` template runs it on a `dev` push, exports the result as `SLOP_BASE_REF` (which `bkit ci slop` already reads), and prints the base it chose and why. When `gh` cannot list the runs, the hook prints a loud warning and uses `origin/dev`. Other branches, and repos without the script, are unchanged. CI mode picks the same base as before; when the run lookup fails, its logged source now reads `event-before (run lookup failed)`. To adopt: re-copy `scripts/ci/lanes/resolve-push-base.mjs` and its `.test.mjs` from `.bkit/templates/scripts/ci/lanes/`, and paste the `Slop base on a dev push` block from the template into your `.husky/pre-push`, after `pnpm bkit check`. A pre-push check of your own that should diff against CI's base (migration immutability, say) can read `SLOP_BASE_REF`. (#653)
|
|
133
|
+
|
|
134
|
+
### Changed
|
|
135
|
+
|
|
136
|
+
- **`.bkit/prompts.md` § Orchestrators says how to set up the Claude Code session an orchestrator runs in.** Subagents carry their own `model:` and `effort:`, but `/bkit-*` orchestrators run on whatever the session runs. The new table says to launch on `claude-opus-5-5` for `/bkit-design`, `/bkit-plan` and `/bkit-debug` and on `claude-sonnet-5-5` for `/bkit-build` and `/bkit-ship`, and to leave effort alone: medium is already Claude Code's default for the 5.5 models, and a top-level `effortLevel` in `~/.claude/settings.json` does not reach them. It shows how to change effort for one session or one repo, and when to open `claude-fable-5-1` by hand: to refine an idea before `/bkit-design`, and to work a bug from the debug handover when `/bkit-debug` is stuck on it. Two warnings: `CLAUDE_CODE_EFFORT_LEVEL` flattens every subagent to one level, and a `maxEffortLevel` below `xhigh` caps the `xhigh` agents. bkit ships no `effortLevel`; nothing to do in your repo.
|
|
137
|
+
- **Both docs-sync agents run on Sonnet 5.5 at `high`.** On Claude Code, `@bkit-ship-update-docs` moves from `claude-opus-5-5` to `claude-sonnet-5-5`, at about half the cost on every ship. `@bkit-utility-update-documentation` moves from `medium` to `high`, because it checks every doc against the code with no feature diff to narrow the search. The ship agent follows on the other tools, as every agent follows its Claude tier: `composer-2.5` on Cursor and `gpt-5.6-terra` on Codex (Antigravity and opencode already pinned the same model for both tiers). `bkit upgrade` picks it up.
|
|
138
|
+
- **The `.husky/pre-push` template runs its fast checks before the gates, and runs the capability register check itself.** `bkit check` used to wait for the full gate, and the register check was a snippet you pasted at the end, so a drifted install or a stale `docs/capabilities.md` blocked a push only after 10-15 minutes of lint and tests had passed. Now both run straight after the CI-token guards and stop the push in seconds (the register check in ~30s). The template calls `scripts/graphify/bkit-graph-pre-push.sh` when you have copied it, and skips it on a min push; without the script nothing changes. In your adopted copy, move `pnpm bkit check` and any register block above the `bkit:gate*` block, or re-copy the `Fast blocking checks` and `Capability register` blocks from the template. Other quick extras that can block (a few seconds, needing nothing the gates build) belong there too.
|
|
139
|
+
- **A workflow's `## bkit Tips` bolds the star and silence questions like each tip's title.** `**Do you like bkit?**` and `**Want to silence these tips?**` (or `this tip`) now open their lines in bold, so all three paragraphs read the same. Bare `bkit tips` and `--all`, which are plain terminal lists, are unchanged.
|
|
140
|
+
- **The `bkit-ci.yml` template drops `Check Tree Cache`.** It never skipped anything: a feature PR's files have never been pushed to `dev` or the default branch, and a release PR runs in mirror mode with every lane off. The template's lanes run their steps unconditionally, `bkit-tests-unit` loses its `cache_skip` output, and `check-capstone.mjs` drops the `<LANE>_CACHE_SKIP` exemption, so a lane that ran 0 tests fails the capstone whatever that variable says. In your adopted copy, delete the `Check Tree Cache` step from each lane, `steps.cache.outputs.skip != 'true'` from every `if:` (and an `if:` it leaves empty), each lane's `cache_skip` output, the capstone's `*_CACHE_SKIP` variables, and `scripts/ci/lanes/check-tree-cache.mjs` with its `.test.mjs`. A lane's job-level `actions: read` was for the cache only; keep `contents: read` and `pull-requests: write`. Then re-copy `scripts/ci/check-capstone.mjs` and its `.test.mjs`. Until you do, a copy that keeps the step still works; it just never skips.
|
|
141
|
+
- **`bkit worktrees setup` starts a new feature branch from local `dev` when it holds unpushed commits.** When local `dev` is ahead of `origin/dev` and nothing else differs, the branch is cut from local `dev`, and a resumed worktree rebases onto it, so the worktree has those commits; the command says how many and reminds you to push `dev` before the feature PR. When the two have diverged, it stays on `origin/dev` and says so. The output gains `baseRef` (`dev` or `origin/dev`), and `baseSha` is the merge base with it.
|
|
142
|
+
- **`bkit worktrees setup` runs `direnv allow` in the new worktree.** It does so only when the worktree's `.envrc` is byte-identical to the main checkout's, so the worktree gets the trust you already gave and nothing more. A differing `.envrc`, or direnv missing or failing, is reported and never stops setup. The output gains `direnvAllowed`.
|
|
143
|
+
|
|
144
|
+
### Fixed
|
|
145
|
+
|
|
146
|
+
- **The `bkit-insert-ignore.mjs` template leaves tables inside multi-line `<!-- -->` comments alone.** It treated a commented-out table as a real one and offered to insert `<!-- prettier-ignore -->` inside the comment, which would close the comment early and show the rest of it on the page; `--check` failed on such a table and blocked the push. The `Project Settings` example rows that new installs get in `.agents/rules.md` are such a table. Tables in a comment are now skipped like tables in a code fence. Re-copy `scripts/prettier/bkit-insert-ignore.mjs` from `.bkit/templates/scripts/prettier/`.
|
|
147
|
+
- **`.agents/rules.md` `New worktree` names the real setting.** It said `bkit.worktreeCopy`; the `package.json` key is `bkit.worktree.copy`. The rule also says `bkit worktrees setup` does the copy, the install and `direnv allow` itself.
|
|
148
|
+
|
|
149
|
+
---
|
|
150
|
+
|
|
9
151
|
## [5.5.0] — 2026-10-21
|
|
10
152
|
|
|
11
153
|
### Breaking Changes
|