@cbartens/bkit 6.0.0 → 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.
- package/.bkit/README.md +154 -151
- package/.bkit/core/.agents/context.md +95 -29
- package/.bkit/core/.agents/docs.md +17 -15
- package/.bkit/core/.agents/plugins/bkit/hooks/bkit-gateguard.cjs +1 -0
- package/.bkit/core/.agents/plugins/bkit/hooks/bkit-guardrails.cjs +6 -5
- package/.bkit/core/.agents/plugins/bkit/hooks/bkit-readguard.cjs +1 -0
- package/.bkit/core/.agents/plugins/bkit/hooks/bkit-rules.cjs +65 -0
- package/.bkit/core/.agents/rules.md +108 -107
- package/.bkit/core/.agents/skills.md +63 -15
- package/.bkit/core/.bkit/README.md +154 -151
- package/.bkit/core/.bkit/authoring.md +714 -84
- package/.bkit/core/.bkit/cli.md +407 -0
- package/.bkit/core/.bkit/cloud.md +281 -193
- package/.bkit/core/.bkit/comparison.md +43 -41
- package/.bkit/core/.bkit/install.md +154 -84
- package/.bkit/core/.bkit/jsonl.md +193 -130
- package/.bkit/core/.bkit/pipeline.md +114 -114
- package/.bkit/core/.bkit/prompts.md +272 -165
- package/.bkit/core/.bkit/providers.md +457 -271
- package/.bkit/core/.bkit/router.md +69 -0
- package/.bkit/core/.bkit/templates.md +529 -256
- package/.bkit/core/.bkit/trackers.md +80 -52
- package/.bkit/core/.bkit/workflows.md +589 -504
- package/.bkit/core/.claude/hooks/bkit-gateguard.cjs +2 -2
- package/.bkit/core/.claude/hooks/bkit-guardrails.cjs +3 -3
- package/.bkit/core/.claude/hooks/bkit-preflight.sh +45 -14
- package/.bkit/core/.codex/hooks/bkit-guardrails.cjs +3 -3
- package/.bkit/core/.codex/hooks/bkit-rules.cjs +57 -0
- package/.bkit/core/.cursor/hooks/bkit-guardrails.cjs +7 -7
- package/.bkit/core/.cursor/hooks/bkit-preflight.sh +47 -12
- package/.bkit/core/.opencode/plugin/bkit-rules.js +89 -0
- package/.bkit/core/AGENTS.md +5 -73
- package/.bkit/core/docs/templates/bkit-audit-accessibility.md +127 -105
- package/.bkit/core/docs/templates/bkit-audit-adoption.md +104 -70
- package/.bkit/core/docs/templates/bkit-audit-agents.md +94 -72
- package/.bkit/core/docs/templates/bkit-audit-aio-seo.md +99 -78
- package/.bkit/core/docs/templates/bkit-audit-analytics.md +140 -82
- package/.bkit/core/docs/templates/bkit-audit-annotations.md +98 -72
- package/.bkit/core/docs/templates/bkit-audit-app-performance.md +121 -96
- package/.bkit/core/docs/templates/bkit-audit-app-store.md +157 -76
- package/.bkit/core/docs/templates/bkit-audit-architecture.md +113 -71
- package/.bkit/core/docs/templates/bkit-audit-ci-performance.md +75 -72
- package/.bkit/core/docs/templates/bkit-audit-config.md +122 -76
- package/.bkit/core/docs/templates/bkit-audit-cost.md +85 -74
- package/.bkit/core/docs/templates/bkit-audit-coverage.md +75 -68
- package/.bkit/core/docs/templates/bkit-audit-database.md +101 -70
- package/.bkit/core/docs/templates/bkit-audit-dead-code.md +164 -83
- package/.bkit/core/docs/templates/bkit-audit-deferrals.md +115 -86
- package/.bkit/core/docs/templates/bkit-audit-dependencies.md +264 -88
- package/.bkit/core/docs/templates/bkit-audit-documentation.md +118 -93
- package/.bkit/core/docs/templates/bkit-audit-duplication.md +139 -86
- package/.bkit/core/docs/templates/bkit-audit-failures.md +110 -81
- package/.bkit/core/docs/templates/bkit-audit-flakes.md +99 -74
- package/.bkit/core/docs/templates/bkit-audit-gates.md +105 -77
- package/.bkit/core/docs/templates/bkit-audit-issues.md +104 -80
- package/.bkit/core/docs/templates/bkit-audit-llm.md +131 -58
- package/.bkit/core/docs/templates/bkit-audit-logs.md +123 -100
- package/.bkit/core/docs/templates/bkit-audit-models.md +98 -53
- package/.bkit/core/docs/templates/bkit-audit-privacy.md +56 -52
- package/.bkit/core/docs/templates/bkit-audit-prompts.md +63 -54
- package/.bkit/core/docs/templates/bkit-audit-red-team.md +124 -68
- package/.bkit/core/docs/templates/bkit-audit-reliability.md +95 -70
- package/.bkit/core/docs/templates/bkit-audit-repo.md +169 -73
- package/.bkit/core/docs/templates/bkit-audit-security.md +206 -96
- package/.bkit/core/docs/templates/bkit-audit-slop.md +77 -70
- package/.bkit/core/docs/templates/bkit-audit-testing.md +162 -114
- package/.bkit/core/docs/templates/bkit-audit-usability.md +113 -71
- package/.bkit/core/docs/templates/bkit-plan.md +138 -132
- package/.bkit/core/engine/checks/after/auth.ts +40 -37
- package/.bkit/core/engine/checks/after/ci-yml.ts +65 -2
- package/.bkit/core/engine/checks/after/index.ts +12 -2
- package/.bkit/core/engine/checks/after/tools.ts +80 -33
- package/.bkit/core/engine/checks/before/context-fetch.ts +227 -33
- package/.bkit/core/engine/checks/before/env.ts +1 -1
- package/.bkit/core/engine/checks/before/index.ts +7 -0
- package/.bkit/core/engine/checks/before/repo.ts +40 -0
- package/.bkit/core/engine/checks/status-holes.ts +916 -123
- package/.bkit/core/engine/checks/tips/catalogue.ts +68 -17
- package/.bkit/core/engine/checks/tips/detect.ts +32 -0
- package/.bkit/core/engine/checks/tips/index.ts +47 -6
- package/.bkit/core/engine/cli.ts +238 -84
- package/.bkit/core/engine/commands/analysis.ts +128 -76
- package/.bkit/core/engine/commands/ci/ci.ts +363 -29
- package/.bkit/core/engine/commands/ci/pins.ts +172 -0
- package/.bkit/core/engine/commands/ci/push-gate.ts +223 -0
- package/.bkit/core/engine/commands/install/uninstall.ts +21 -27
- package/.bkit/core/engine/commands/install/upgrade.ts +32 -15
- package/.bkit/core/engine/commands/land.ts +126 -11
- package/.bkit/core/engine/commands/lib.ts +303 -6
- package/.bkit/core/engine/commands/registry.ts +6 -2
- package/.bkit/core/engine/commands/setup/setup.ts +1 -0
- package/.bkit/core/engine/commands/stats.ts +91 -35
- package/.bkit/core/engine/commands/workflow/branches.ts +1477 -117
- package/.bkit/core/engine/commands/workflow/challenge.ts +114 -39
- package/.bkit/core/engine/commands/workflow/completeness.ts +109 -0
- package/.bkit/core/engine/commands/workflow/context.ts +433 -55
- package/.bkit/core/engine/commands/workflow/counters.ts +244 -39
- package/.bkit/core/engine/commands/workflow/decisions.ts +61 -17
- package/.bkit/core/engine/commands/workflow/disk.ts +237 -55
- package/.bkit/core/engine/commands/workflow/fids.ts +19 -1
- package/.bkit/core/engine/commands/workflow/issues.ts +6 -0
- package/.bkit/core/engine/commands/workflow/ledgers.ts +458 -18
- package/.bkit/core/engine/commands/workflow/locks.ts +2 -0
- package/.bkit/core/engine/commands/workflow/plan-blocks.ts +124 -15
- package/.bkit/core/engine/commands/workflow/plans.ts +257 -0
- package/.bkit/core/engine/commands/workflow/prs.ts +12 -3
- package/.bkit/core/engine/commands/workflow/repo.ts +8 -0
- package/.bkit/core/engine/commands/workflow/roadmap.ts +56 -15
- package/.bkit/core/engine/commands/workflow/run-facts.ts +22 -31
- package/.bkit/core/engine/commands/workflow/runs.ts +652 -34
- package/.bkit/core/engine/commands/workflow/runtime.ts +3 -0
- package/.bkit/core/engine/commands/workflow/skills.ts +1 -0
- package/.bkit/core/engine/commands/workflow/status.ts +200 -17
- package/.bkit/core/engine/commands/workflow/step-table.ts +75 -33
- package/.bkit/core/engine/commands/workflow/steps.ts +635 -24
- package/.bkit/core/engine/commands/workflow/summary-findings.ts +177 -0
- package/.bkit/core/engine/commands/workflow/summary.ts +192 -46
- package/.bkit/core/engine/commands/workflow/tasks.ts +409 -0
- package/.bkit/core/engine/commands/workflow/test-blocks.ts +254 -0
- package/.bkit/core/engine/commands/workflow/tests-changed.ts +201 -0
- package/.bkit/core/engine/commands/workflow/tests.ts +1285 -356
- package/.bkit/core/engine/commands/workflow/workflows.ts +228 -43
- package/.bkit/core/engine/commands/workflow/worktrees.ts +389 -47
- package/.bkit/core/engine/install/cloud-env.ts +251 -121
- package/.bkit/core/engine/install/context-ci-workflow.ts +102 -0
- package/.bkit/core/engine/install/manifest.ts +60 -12
- package/.bkit/core/engine/install/modules/antigravity.ts +3 -2
- package/.bkit/core/engine/install/modules/cloud.ts +3 -3
- package/.bkit/core/engine/install/modules/codex.ts +15 -2
- package/.bkit/core/engine/install/modules/core.ts +956 -52
- package/.bkit/core/engine/install/modules/cursor.ts +6 -6
- package/.bkit/core/engine/install/modules/opencode.ts +16 -4
- package/.bkit/core/engine/install/template-notes.ts +130 -0
- package/.bkit/core/engine/install/version-file.ts +3 -2
- package/.bkit/core/engine/install/write.ts +5 -0
- package/.bkit/core/engine/ledgers/compact.ts +124 -0
- package/.bkit/core/engine/ledgers/journal.ts +291 -0
- package/.bkit/core/engine/ledgers/status.ts +160 -9
- package/.bkit/core/engine/ledgers/telemetry.ts +158 -21
- package/.bkit/core/engine/render/hosts.ts +114 -14
- package/.bkit/core/engine/shared/bkit-latest.ts +26 -4
- package/.bkit/core/engine/shared/dep-updater.ts +60 -0
- package/.bkit/core/engine/shared/egress.ts +1 -1
- package/.bkit/core/engine/shared/package-manager.ts +9 -0
- package/.bkit/core/engine/shared/settings.ts +92 -17
- package/.bkit/core/engine/shared/timeouts.ts +2 -0
- package/.bkit/core/engine/tools/cli-doc.ts +111 -0
- package/.bkit/core/engine/tools/grammar-density.ts +1 -1
- package/.bkit/core/engine/tools/instructions-sources.ts +15 -17
- package/.bkit/core/engine/tools/instructions.ts +94 -43
- package/.bkit/core/hooks/antigravity-hook.js +25 -10
- package/.bkit/core/hooks/gateguard-engine.js +53 -29
- package/.bkit/core/hooks/guardrails-shell.js +4 -4
- package/.bkit/core/hooks/guardrails-tiers.js +3 -3
- package/.bkit/core/hooks/preflight-linear.sh +9 -9
- package/.bkit/core/hooks/preflight-rules.sh +8 -0
- package/.bkit/core/hooks/readguard-engine.js +29 -10
- package/.bkit/core/hooks/session-rules-advisory.js +61 -0
- package/.bkit/core/prompts/bkit-audit-generate.md +187 -116
- package/.bkit/core/prompts/bkit-build-challenge-1.md +56 -37
- package/.bkit/core/prompts/bkit-build-challenge-2.md +65 -45
- package/.bkit/core/prompts/bkit-build-install-skills.md +38 -29
- package/.bkit/core/prompts/bkit-build-plan-convert.md +43 -32
- package/.bkit/core/prompts/bkit-build-plan-current.md +49 -39
- package/.bkit/core/prompts/bkit-build-plan-gaps-remediate.md +79 -55
- package/.bkit/core/prompts/bkit-build-plan-tasks.md +149 -0
- package/.bkit/core/prompts/bkit-build-plan-tests.md +120 -0
- package/.bkit/core/prompts/bkit-build-plan-verify.md +87 -50
- package/.bkit/core/prompts/bkit-debug-abort-handover.md +36 -35
- package/.bkit/core/prompts/bkit-debug-failure-diagnose.md +96 -64
- package/.bkit/core/prompts/bkit-debug-failure-remediate.md +54 -45
- package/.bkit/core/prompts/bkit-debug-failure-reproduce.md +42 -33
- package/.bkit/core/prompts/bkit-debug-failure-soak.md +53 -37
- package/.bkit/core/prompts/bkit-design-brainstorm-ideate-1.md +35 -30
- package/.bkit/core/prompts/bkit-design-brainstorm-ideate-2.md +34 -29
- package/.bkit/core/prompts/bkit-design-brainstorm-ideate-3.md +32 -28
- package/.bkit/core/prompts/bkit-design-generate.md +68 -52
- package/.bkit/core/prompts/bkit-design-organise.md +73 -35
- package/.bkit/core/prompts/bkit-design-review-1.md +58 -54
- package/.bkit/core/prompts/bkit-design-review-2.md +54 -50
- package/.bkit/core/prompts/bkit-design-spike.md +54 -47
- package/.bkit/core/prompts/bkit-design-update.md +42 -31
- package/.bkit/core/prompts/bkit-plan-generate.md +76 -58
- package/.bkit/core/prompts/bkit-plan-review-1.md +63 -49
- package/.bkit/core/prompts/bkit-plan-review-2.md +60 -48
- package/.bkit/core/prompts/bkit-plan-scope-check.md +53 -46
- package/.bkit/core/prompts/bkit-plan-update.md +70 -52
- package/.bkit/core/prompts/bkit-ship-conflict-resolve.md +82 -50
- package/.bkit/core/prompts/bkit-ship-deferred-sweep.md +80 -45
- package/.bkit/core/prompts/bkit-ship-update-docs.md +35 -29
- package/.bkit/core/prompts/bkit-utility-compress-markdown.md +55 -49
- package/.bkit/core/prompts/bkit-utility-update-decisions.md +76 -49
- package/.bkit/core/prompts/bkit-utility-update-deferrals.md +70 -41
- package/.bkit/core/prompts/bkit-utility-update-documentation.md +33 -30
- package/.bkit/core/prompts/bkit-utility-update-failures.md +73 -43
- package/.bkit/core/prompts/bkit-utility-update-knowledge.md +77 -50
- package/.bkit/core/prompts/bkit-utility-update-roadmap.md +77 -45
- package/.bkit/core/prompts/bkit-utility-update-tracker.md +144 -68
- package/.bkit/core/workflows/bkit-auto.md +53 -30
- package/.bkit/core/workflows/bkit-build.md +635 -304
- package/.bkit/core/workflows/bkit-debug.md +301 -148
- package/.bkit/core/workflows/bkit-design.md +167 -95
- package/.bkit/core/workflows/bkit-plan.md +172 -84
- package/.bkit/core/workflows/bkit-ship.md +299 -152
- package/.bkit/shared/.agents/plugins/bkit/hooks.json +10 -0
- package/.bkit/shared/.claude/bkit-cloud.md +12 -10
- package/.bkit/shared/.claude/settings.json +3 -0
- package/.bkit/shared/.codex/bkit-cloud.md +98 -0
- package/.bkit/shared/.codex/hooks.json +20 -0
- package/.bkit/shared/.cursor/bkit-cloud.md +3 -3
- package/.bkit/shared/.opencode/opencode.json +1 -1
- package/.bkit/shared/CLAUDE.md +5 -1
- package/.bkit/shared/GEMINI.md +4 -1
- package/.bkit/shared/docs/architecture.md +4 -7
- package/.bkit/shared/docs/data-schema.md +4 -7
- package/.bkit/shared/docs/deployments.md +239 -166
- package/.bkit/shared/docs/design.md +11 -12
- package/.bkit/shared/docs/noise.md +8 -7
- package/.bkit/shared/docs/observability.md +5 -8
- package/.bkit/shared/docs/security.md +35 -17
- package/.bkit/shared/docs/setup.md +29 -18
- package/.bkit/shared/docs/technology.md +3 -6
- package/.bkit/shared/docs/testing.md +282 -176
- package/.bkit/shared/gitignore +6 -2
- package/.bkit/templates/.claude/hooks/bkit-cloud-bootstrap.sh +15 -16
- package/.bkit/templates/.cursor/Dockerfile +12 -8
- package/.bkit/templates/.cursor/environment.json +1 -1
- package/.bkit/templates/.github/ISSUE_TEMPLATE/bkit-bug.yml +10 -8
- package/.bkit/templates/.github/ISSUE_TEMPLATE/bkit-change.yml +24 -12
- package/.bkit/templates/.github/ISSUE_TEMPLATE/bkit-idea.yml +3 -3
- package/.bkit/templates/.github/renovate.json5 +34 -6
- package/.bkit/templates/.github/workflows/bkit-ci.yml +53 -50
- package/.bkit/templates/.github/workflows/bkit-cloud.yml +13 -14
- package/.bkit/templates/.github/workflows/bkit-health.yml +97 -0
- package/.bkit/templates/.github/workflows/bkit-renovate.yml +5 -4
- package/.bkit/templates/.github/workflows/bkit-trivy.yml +5 -4
- package/.bkit/templates/.husky/pre-commit +2 -2
- package/.bkit/templates/.husky/pre-push +95 -35
- package/.bkit/templates/.prettierignore +6 -7
- package/.bkit/templates/.vale.ini +27 -27
- package/.bkit/templates/context/bkit-cloudrun.md +23 -15
- package/.bkit/templates/context/bkit-expo.md +70 -52
- package/.bkit/templates/context/bkit-github.md +93 -56
- package/.bkit/templates/context/bkit-inngest.md +21 -15
- package/.bkit/templates/context/bkit-maestro.md +22 -16
- package/.bkit/templates/context/bkit-playwright.md +23 -17
- package/.bkit/templates/context/bkit-resend.md +12 -10
- package/.bkit/templates/context/bkit-sentry.md +30 -20
- package/.bkit/templates/context/bkit-serena.md +8 -7
- package/.bkit/templates/context/bkit-stripe.md +14 -13
- package/.bkit/templates/context/bkit-supabase.md +16 -13
- package/.bkit/templates/context/bkit-tavily.md +14 -11
- package/.bkit/templates/context/bkit-vercel.md +27 -18
- package/.bkit/templates/docs/capabilities.md +15 -14
- package/.bkit/templates/scripts/ci/{check-accepted-divergences.mjs → bkit-check-accepted-divergences.mjs} +6 -3
- package/.bkit/templates/scripts/ci/{check-accepted-divergences.test.mjs → bkit-check-accepted-divergences.test.mjs} +3 -3
- package/.bkit/templates/scripts/ci/{check-capstone.mjs → bkit-check-capstone.mjs} +2 -2
- package/.bkit/templates/scripts/ci/{check-capstone.test.mjs → bkit-check-capstone.test.mjs} +4 -4
- package/.bkit/templates/scripts/ci/{check-dependency-audit.mjs → bkit-check-dependency-audit.mjs} +103 -18
- package/.bkit/templates/scripts/ci/{check-dependency-audit.test.mjs → bkit-check-dependency-audit.test.mjs} +31 -3
- package/.bkit/templates/scripts/ci/bkit-machine-lock.sh +387 -0
- package/.bkit/templates/scripts/ci/bkit-test-awake.mjs +75 -0
- package/.bkit/templates/scripts/ci/bkit-test-awake.test.mjs +160 -0
- package/.bkit/templates/scripts/ci/lanes/{resolve-push-base.mjs → bkit-resolve-push-base.mjs} +3 -3
- package/.bkit/templates/scripts/ci/lanes/{resolve-push-base.test.mjs → bkit-resolve-push-base.test.mjs} +4 -4
- package/.bkit/templates/scripts/cleanup/bkit-disk-prune.mjs +9 -1
- package/.bkit/templates/scripts/graphify/bkit-graph-drift.py +1 -1
- package/.bkit/templates/scripts/graphify/bkit-graph-eager.py +3 -3
- package/.bkit/templates/scripts/graphify/bkit-graph-embed.py +63 -0
- package/.bkit/templates/scripts/graphify/bkit-graph-imports.py +2 -2
- package/.bkit/templates/scripts/graphify/bkit-graph-pre-push.sh +69 -18
- package/.bkit/templates/scripts/graphify/bkit-graph-repair.py +3 -3
- package/.bkit/templates/scripts/graphify/bkit-graph-surface.py +1 -1
- package/.bkit/templates/scripts/graphify/bkit-graphify-graphml.py +1 -1
- package/.bkit/templates/scripts/graphify/bkit-graphify-rollup.py +197 -126
- package/.bkit/templates/scripts/graphify/bkit-graphify.sh +64 -41
- package/.bkit/templates/scripts/slop/bkit-slop-type-suppression.mjs +23 -7
- package/.bkit/templates/slop-scan.config.json +9 -2
- package/CHANGELOG.md +119 -0
- package/README.md +250 -76
- package/dist/checks/after/auth.js +36 -33
- package/dist/checks/after/ci-yml.js +52 -2
- package/dist/checks/after/index.js +12 -4
- package/dist/checks/after/tools.js +73 -33
- package/dist/checks/before/context-fetch.js +218 -33
- package/dist/checks/before/env.js +1 -1
- package/dist/checks/before/index.js +6 -2
- package/dist/checks/before/repo.js +35 -1
- package/dist/checks/status-holes.js +739 -114
- package/dist/checks/tips/catalogue.js +59 -17
- package/dist/checks/tips/detect.js +30 -0
- package/dist/checks/tips/index.js +48 -6
- package/dist/cli.js +222 -84
- package/dist/commands/analysis.js +77 -53
- package/dist/commands/ci/ci.js +302 -25
- package/dist/commands/ci/pins.js +142 -0
- package/dist/commands/ci/push-gate.js +194 -0
- package/dist/commands/install/uninstall.js +23 -27
- package/dist/commands/install/upgrade.js +21 -11
- package/dist/commands/land.js +126 -10
- package/dist/commands/lib.js +244 -5
- package/dist/commands/registry.js +6 -2
- package/dist/commands/setup/setup.js +1 -0
- package/dist/commands/stats.js +69 -30
- package/dist/commands/workflow/branches.js +1232 -111
- package/dist/commands/workflow/challenge.js +90 -37
- package/dist/commands/workflow/completeness.js +97 -0
- package/dist/commands/workflow/context.js +371 -51
- package/dist/commands/workflow/counters.js +206 -40
- package/dist/commands/workflow/decisions.js +60 -17
- package/dist/commands/workflow/disk.js +213 -55
- package/dist/commands/workflow/fids.js +18 -1
- package/dist/commands/workflow/issues.js +6 -0
- package/dist/commands/workflow/ledgers.js +372 -21
- package/dist/commands/workflow/locks.js +2 -0
- package/dist/commands/workflow/plan-blocks.js +78 -14
- package/dist/commands/workflow/plans.js +205 -0
- package/dist/commands/workflow/prs.js +12 -3
- package/dist/commands/workflow/repo.js +6 -0
- package/dist/commands/workflow/roadmap.js +50 -17
- package/dist/commands/workflow/run-facts.js +23 -28
- package/dist/commands/workflow/runs.js +530 -33
- package/dist/commands/workflow/runtime.js +3 -0
- package/dist/commands/workflow/skills.js +1 -0
- package/dist/commands/workflow/status.js +166 -19
- package/dist/commands/workflow/step-table.js +61 -29
- package/dist/commands/workflow/steps.js +542 -26
- package/dist/commands/workflow/summary-findings.js +117 -0
- package/dist/commands/workflow/summary.js +154 -41
- package/dist/commands/workflow/tasks.js +378 -0
- package/dist/commands/workflow/test-blocks.js +231 -0
- package/dist/commands/workflow/tests-changed.js +172 -0
- package/dist/commands/workflow/tests.js +1013 -321
- package/dist/commands/workflow/workflows.js +191 -38
- package/dist/commands/workflow/worktrees.js +310 -42
- package/dist/install/cloud-env.js +233 -99
- package/dist/install/context-ci-workflow.js +85 -0
- package/dist/install/manifest.js +57 -12
- package/dist/install/modules/antigravity.js +3 -2
- package/dist/install/modules/cloud.js +3 -3
- package/dist/install/modules/codex.js +12 -2
- package/dist/install/modules/core.js +851 -53
- package/dist/install/modules/cursor.js +6 -6
- package/dist/install/modules/opencode.js +11 -5
- package/dist/install/template-notes.js +116 -0
- package/dist/install/version-file.js +3 -2
- package/dist/ledgers/compact.js +87 -0
- package/dist/ledgers/journal.js +233 -0
- package/dist/ledgers/status.js +115 -5
- package/dist/ledgers/telemetry.js +121 -17
- package/dist/render/hosts.js +100 -14
- package/dist/shared/bkit-latest.js +26 -4
- package/dist/shared/dep-updater.js +49 -0
- package/dist/shared/egress.js +1 -1
- package/dist/shared/package-manager.js +6 -0
- package/dist/shared/settings.js +59 -10
- package/dist/shared/timeouts.js +2 -0
- package/dist/tools/cli-doc.js +97 -0
- package/dist/tools/grammar-density.js +1 -1
- package/dist/tools/instructions-sources.js +15 -16
- package/dist/tools/instructions.js +83 -39
- package/package.json +58 -42
- package/.bkit/core/.bkit/lite.md +0 -73
- package/.bkit/core/engine/commands/workflow/workstreams.ts +0 -172
- package/.bkit/core/prompts/bkit-build-plan-execute.md +0 -124
- package/.bkit/templates/scripts/ci/bkit-local-stack-lock.sh +0 -194
- package/dist/commands/workflow/workstreams.js +0 -149
- /package/.bkit/templates/.vale/styles/{House → Bkit}/Filler.yml +0 -0
- /package/.bkit/templates/.vale/styles/{House → Bkit}/Hedging.yml +0 -0
- /package/.bkit/templates/.vale/styles/{House → Bkit}/LLMSlop.yml +0 -0
- /package/.bkit/templates/.vale/styles/{House → Bkit}/Verbose.yml +0 -0
- /package/.bkit/templates/scripts/ci/{accepted-advisories.json → bkit-accepted-advisories.json} +0 -0
- /package/.bkit/templates/scripts/ci/{accepted-divergences.json → bkit-accepted-divergences.json} +0 -0
- /package/.bkit/templates/scripts/launchd/{launchd.env.example → bkit-launchd.env.example} +0 -0
- /package/.bkit/templates/scripts/launchd/{ai.bkit.launchd.plist → bkit-launchd.plist} +0 -0
|
@@ -1,51 +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:**
|
|
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
|
-
> -
|
|
15
|
-
> -
|
|
16
|
-
> -
|
|
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.
|
|
17
20
|
|
|
18
21
|
## Universal Instructions
|
|
19
22
|
|
|
20
23
|
### Context & Goals
|
|
21
24
|
|
|
22
|
-
An error tracker does not
|
|
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.
|
|
23
26
|
|
|
24
|
-
**Applies when:** error tracker, runtime logs, or both.
|
|
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".
|
|
25
28
|
|
|
26
|
-
**Cadence:** every two weeks, whole window since previous report.
|
|
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.
|
|
27
30
|
|
|
28
31
|
**Anchor Standards:**
|
|
29
32
|
|
|
30
|
-
- Error-tracker release health (e.g
|
|
31
|
-
- Source maps and debug symbols (e.g
|
|
32
|
-
- Event grouping, fingerprints, and stack-trace rules (e.g
|
|
33
|
-
- Ownership rules (e.g
|
|
34
|
-
- Quotas and spike protection (e.g
|
|
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).
|
|
35
38
|
- OpenTelemetry semantic conventions, including GenAI; record the semconv version.
|
|
36
39
|
- W3C Trace Context, Level 1.
|
|
37
|
-
- Alerting on SLOs (e.g
|
|
40
|
+
- Alerting on SLOs (e.g., Google SRE Workbook, "Alerting on SLOs").
|
|
38
41
|
- bkit block of `docs/observability.md` (bkit version from `.bkit/version`): every rule and section
|
|
39
42
|
- bkit block of `docs/noise.md` (bkit version from `.bkit/version`): every rule and section
|
|
40
43
|
|
|
41
44
|
### Scope
|
|
42
45
|
|
|
43
|
-
-
|
|
44
|
-
-
|
|
45
|
-
-
|
|
46
|
-
-
|
|
47
|
-
-
|
|
48
|
-
-
|
|
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.
|
|
49
53
|
|
|
50
54
|
### Out of Scope
|
|
51
55
|
|
|
@@ -61,12 +65,12 @@ An error tracker does not distinguish a bug from a handled outcome logged at err
|
|
|
61
65
|
|
|
62
66
|
### Verdicts
|
|
63
67
|
|
|
64
|
-
|
|
68
|
+
Give each unresolved issue one verdict. The verdict decides everything downstream.
|
|
65
69
|
|
|
66
|
-
- **GENUINE ERROR:** unhandled failure, or handled
|
|
67
|
-
- **WRONG LEVEL:**
|
|
68
|
-
- **NOISE:** vendor or infrastructure, no app call site (SDK internals, tunnel egress, platform insight). Recommend tracker-side filter (e.g
|
|
69
|
-
- **OTHER:** fits
|
|
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`.
|
|
70
74
|
|
|
71
75
|
A test-origin tag narrows the lane. It does not make something noise, and it does not lower severity.
|
|
72
76
|
|
|
@@ -74,90 +78,103 @@ A test-origin tag narrows the lane. It does not make something noise, and it doe
|
|
|
74
78
|
|
|
75
79
|
#### Core
|
|
76
80
|
|
|
77
|
-
- [ ] **Permissions:** blocked
|
|
78
|
-
- [ ] **Error Tracker:** Steps 3-9 — read-only issue, event
|
|
79
|
-
- [ ] **Web:** Step 13 — fetch anchor standards. Fallback: versions
|
|
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.
|
|
80
84
|
|
|
81
85
|
#### Conditional
|
|
82
86
|
|
|
83
|
-
- [ ] **Runtime Logs:**
|
|
84
|
-
- [ ] **Language Server:**
|
|
85
|
-
- [ ] **Symbol Maps:**
|
|
86
|
-
- [ ] **User Reports:**
|
|
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`.
|
|
87
91
|
|
|
88
92
|
### 🔒 Gate 1: Prerequisites Check
|
|
89
93
|
|
|
90
|
-
- [ ] **Gaps named:** every missing item names its fallback and `Not Checked` entry.
|
|
91
|
-
- [ ] **Gate 1 — Verified:**
|
|
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.
|
|
92
96
|
|
|
93
97
|
### Probe Steps
|
|
94
98
|
|
|
95
|
-
- [ ] **Step 1 — Previous Run:** **Done when:**
|
|
96
|
-
- [ ] **Step 2 — Detect:** Find error tracker, runtime logs, or both. **Done when:**
|
|
97
|
-
- [ ] **Step 3 — Board:**
|
|
98
|
-
-
|
|
99
|
-
-
|
|
100
|
-
- Events by environment. Name each
|
|
101
|
-
- First seen
|
|
102
|
-
- Reported
|
|
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.
|
|
103
107
|
|
|
104
|
-
|
|
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.
|
|
105
109
|
|
|
106
|
-
- [ ] **Step 4 — Instrument:** Read tracker project settings, read-only, against anchor standards.
|
|
107
|
-
- Symbolication.
|
|
108
|
-
- Release and environment on every event. Release health on for each client.
|
|
109
|
-
- Dropped events since previous report: rate-limited, filtered, over quota, spike protection. Record each count
|
|
110
|
-
- Server-side grouping: fingerprint rules, stack-trace rules
|
|
111
|
-
- Ownership rules. CODEOWNERS import needs code mappings and team/user mappings.
|
|
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.
|
|
112
116
|
|
|
113
|
-
**Done when:** `Instrument` holds each check, dropped-event counts
|
|
117
|
+
**Done when:** `Instrument` holds each check, the dropped-event counts and the unowned share.
|
|
114
118
|
|
|
115
|
-
- [ ] **Step 5 — Stored Data:**
|
|
116
|
-
- 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).
|
|
117
|
-
- Model inputs
|
|
118
|
-
- Sample five recent events end to end (message, breadcrumbs, request, extra, tags) for names, emails, addresses
|
|
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.
|
|
119
123
|
|
|
120
124
|
**Done when:** `Stored Data` says what the sample found, by field.
|
|
121
125
|
|
|
122
|
-
- [ ] **Step 6 — Classify:**
|
|
123
|
-
- [ ] **Step 7 — Root Cause:**
|
|
124
|
-
-
|
|
125
|
-
-
|
|
126
|
-
-
|
|
127
|
-
-
|
|
128
|
-
-
|
|
129
|
-
-
|
|
130
|
-
|
|
131
|
-
|
|
132
|
-
|
|
133
|
-
|
|
134
|
-
|
|
135
|
-
|
|
136
|
-
|
|
137
|
-
|
|
138
|
-
|
|
139
|
-
|
|
140
|
-
|
|
141
|
-
|
|
142
|
-
|
|
143
|
-
|
|
144
|
-
|
|
145
|
-
-
|
|
146
|
-
-
|
|
147
|
-
-
|
|
148
|
-
|
|
149
|
-
|
|
150
|
-
|
|
151
|
-
-
|
|
152
|
-
|
|
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`.
|
|
153
169
|
|
|
154
170
|
### 🔒 Gate 2: Probes Check
|
|
155
171
|
|
|
156
|
-
- [ ] **Steps complete:** every step `[x]`, or
|
|
157
|
-
- [ ] **Evidence:** every finding cites
|
|
158
|
-
- [ ] **No tracker writes:** nothing resolved, archived, muted
|
|
159
|
-
- [ ] **No
|
|
160
|
-
- [ ] **
|
|
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.
|
|
161
178
|
|
|
162
179
|
## Findings
|
|
163
180
|
|
|
@@ -169,14 +186,14 @@ A test-origin tag narrows the lane. It does not make something noise, and it doe
|
|
|
169
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 |
|
|
170
187
|
| `LOW` | Noise with a named vendor frame; test-traffic issue already tagged; `docs/noise.md` wording drift |
|
|
171
188
|
|
|
172
|
-
Within a severity
|
|
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.
|
|
173
190
|
|
|
174
191
|
<!-- prettier-ignore -->
|
|
175
192
|
| ID | Severity | Verdict | Location | Evidence | Expected |
|
|
176
193
|
| --- | --- | --- | --- | --- | --- |
|
|
177
194
|
| PENDING | PENDING | PENDING | PENDING | PENDING | PENDING |
|
|
178
195
|
|
|
179
|
-
|
|
196
|
+
**If** the run finds nothing → write one row: `None`.
|
|
180
197
|
|
|
181
198
|
## Report
|
|
182
199
|
|
|
@@ -245,13 +262,19 @@ PENDING
|
|
|
245
262
|
|
|
246
263
|
### 🔒 Gate 3: Report Check
|
|
247
264
|
|
|
248
|
-
- [ ] **No placeholders:** no `PENDING` left
|
|
249
|
-
- [ ] **Summary:**
|
|
250
|
-
- [ ] **
|
|
251
|
-
- [ ] **
|
|
252
|
-
- [ ] **
|
|
253
|
-
- [ ] **
|
|
254
|
-
- [ ] **
|
|
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.
|
|
255
278
|
|
|
256
279
|
<!-- bkit:end -->
|
|
257
280
|
|