@cbartens/bkit 5.0.0 → 5.0.1
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 +10 -14
- package/.bkit/core/.bkit/README.md +9 -13
- package/.bkit/core/.bkit/cloud.md +15 -24
- package/.bkit/core/.bkit/comparison.md +4 -1
- package/.bkit/core/.bkit/install.md +54 -149
- package/.bkit/core/.bkit/jsonl.md +5 -5
- package/.bkit/core/.bkit/templates.md +2 -3
- package/.bkit/core/.bkit/workflows.md +7 -3
- package/.bkit/core/engine/checks/after/auth.ts +16 -114
- package/.bkit/core/engine/checks/after/ci-yml.ts +36 -74
- package/.bkit/core/engine/checks/after/index.ts +156 -182
- package/.bkit/core/engine/checks/after/suppression.ts +53 -0
- package/.bkit/core/engine/checks/before/env.ts +4 -18
- package/.bkit/core/engine/checks/before/files.ts +2 -0
- package/.bkit/core/engine/cli.ts +4 -8
- package/.bkit/core/engine/commands/install/doctor.ts +9 -2
- package/.bkit/core/engine/commands/install/install.ts +24 -2
- package/.bkit/core/engine/commands/install/uninstall.ts +23 -0
- package/.bkit/core/engine/commands/install/upgrade.ts +14 -3
- package/.bkit/core/engine/commands/lib.ts +4 -3
- package/.bkit/core/engine/install/cloud-env.ts +0 -1
- package/.bkit/core/engine/install/modules/cloud.ts +2 -3
- package/.bkit/core/engine/install/modules/core.ts +33 -13
- package/.bkit/core/engine/install/payload-links.ts +150 -0
- package/.bkit/core/engine/install/template-copies.ts +1 -1
- package/.bkit/core/engine/shared/egress.ts +1 -1
- package/.bkit/core/workflows/bkit-debug.md +19 -12
- package/.bkit/shared/.bkit/.env.example +2 -24
- package/.bkit/shared/docs/deployments.md +2 -7
- package/.bkit/shared/docs/security.md +1 -1
- package/.bkit/shared/gitignore +5 -0
- package/.bkit/templates/.claude/hooks/bkit-cloud-bootstrap.sh +0 -5
- package/.bkit/templates/.cursor/Dockerfile +1 -1
- package/.bkit/templates/.cursor/environment.json +1 -1
- package/.bkit/templates/.github/renovate.json5 +0 -15
- package/.bkit/templates/.github/workflows/bkit-ci.yml +2 -22
- package/.bkit/templates/.github/workflows/bkit-cloud.yml +0 -2
- package/.bkit/templates/.github/workflows/bkit-renovate.yml +0 -5
- package/CHANGELOG.md +17 -0
- package/README.md +5 -6
- package/dist/checks/after/auth.js +16 -108
- package/dist/checks/after/ci-yml.js +30 -67
- package/dist/checks/after/index.js +136 -152
- package/dist/checks/after/suppression.js +39 -0
- package/dist/checks/before/env.js +4 -14
- package/dist/checks/before/files.js +2 -0
- package/dist/cli.js +4 -8
- package/dist/commands/install/doctor.js +4 -2
- package/dist/commands/install/install.js +16 -2
- package/dist/commands/install/uninstall.js +24 -0
- package/dist/commands/install/upgrade.js +14 -3
- package/dist/commands/lib.js +4 -3
- package/dist/install/cloud-env.js +0 -1
- package/dist/install/modules/cloud.js +2 -3
- package/dist/install/modules/core.js +33 -13
- package/dist/install/payload-links.js +119 -0
- package/dist/install/template-copies.js +1 -1
- package/dist/shared/egress.js +1 -1
- package/package.json +2 -2
- package/.bkit/core/engine/checks/after/vercel.ts +0 -101
- package/dist/checks/after/vercel.js +0 -102
|
@@ -2,19 +2,10 @@
|
|
|
2
2
|
|
|
3
3
|
{{BKIT_MANAGED_MARKER}}
|
|
4
4
|
|
|
5
|
-
First-time install and
|
|
5
|
+
First-time install and upgrade, install lifecycle, uninstall and recovery. Ships in the package at `node_modules/@cbartens/bkit/.bkit/core/.bkit/install.md` and is mirrored into the consumer repo at `.bkit/install.md`. Ongoing ops and triggering workflows: `.bkit/README.md`.
|
|
6
6
|
|
|
7
7
|
> [!IMPORTANT]
|
|
8
|
-
>
|
|
9
|
-
>
|
|
10
|
-
> 1. **Local shell** — pick one of two flows (see § Local env setup for details):
|
|
11
|
-
> - **(A) Quick:** `export BKIT_GH_TOKEN_INSTALL=<classic PAT>` in `~/.zshrc` or `~/.bashrc`. Works immediately, single-step. Same token leaks into every shell.
|
|
12
|
-
> - **(B) direnv + `.bkit/.env` (recommended for daily use):** `brew install direnv` once per machine, then `.bkit/.env` (gitignored, scaffolded by `bkit install`) auto-loads on `cd`. Tokens scoped to the repo, not your whole shell. Note: `.bkit/.env` only exists _after_ `bkit install` runs, so for the first install you need either (A) or a one-off `export` in the current shell.
|
|
13
|
-
> 2. **`.npmrc` at repo root** — registry mapping only; token goes in pnpm user-level config via `pnpm config set` — see § Consumer CI auth below
|
|
14
|
-
> 3. **GitHub Actions repo secret** — `gh secret set BKIT_GH_TOKEN_INSTALL --body=<token>` per consumer repo
|
|
15
|
-
> 4. **Vercel env vars** (if applicable) — `vercel env add BKIT_GH_TOKEN_INSTALL preview/production`
|
|
16
|
-
>
|
|
17
|
-
> **Use a classic PAT, not fine-grained.** GitHub Packages npm registry currently rejects fine-grained PATs with HTTP 403 even when `Packages: read` is granted (verified 2026-05). Until GitHub fixes this, classic with `read:packages` scope is the only working option.
|
|
8
|
+
> **bkit installs from npmjs.** `@cbartens/bkit` is public on `https://registry.npmjs.org`; `pnpm add -D @cbartens/bkit` resolves with no registry mapping, PAT, or CI/Vercel env.
|
|
18
9
|
|
|
19
10
|
## Quick install / upgrade — paste into your AI
|
|
20
11
|
|
|
@@ -22,50 +13,33 @@ Two paste blocks below — **install** (first time) and **upgrade** (already on
|
|
|
22
13
|
|
|
23
14
|
### Install — first time
|
|
24
15
|
|
|
25
|
-
|
|
16
|
+
No token or registry setup is needed — `@cbartens/bkit` is public on npmjs. Copy the block below into Claude Code / Cursor / any coding agent.
|
|
26
17
|
|
|
27
18
|
````text
|
|
28
19
|
Install the latest `@cbartens/bkit` in this repo and finish setup.
|
|
29
|
-
1.
|
|
30
|
-
2.
|
|
20
|
+
1. `@cbartens/bkit` is public on npmjs — no registry mapping, no PAT, no env. Confirmed.
|
|
21
|
+
2. Install and seed hosts in one Bash call (`bkit install` requires named modules — core implicit; if `bkit` not on PATH use `pnpm bkit`):
|
|
31
22
|
```bash
|
|
32
|
-
|
|
33
|
-
```
|
|
34
|
-
Verify without leaking: `echo "len=${#BKIT_GH_TOKEN_INSTALL}"`.
|
|
35
|
-
3. Ensure root `.npmrc` has registry mapping only (token NOT stored here — pnpm >=10.34.3 401s on project-`.npmrc` `${BKIT_GH_TOKEN_INSTALL}` substitution):
|
|
36
|
-
```
|
|
37
|
-
@cbartens:registry=https://npm.pkg.github.com
|
|
38
|
-
```
|
|
39
|
-
Then auth + install + seed hosts in one Bash call (`bkit install` requires named modules — core implicit; if `bkit` not on PATH use `pnpm bkit`):
|
|
40
|
-
```bash
|
|
41
|
-
set -a; source <ENV-FILE-PATH>; set +a; \
|
|
42
|
-
pnpm config set "//npm.pkg.github.com/:_authToken=$BKIT_GH_TOKEN_INSTALL" && \
|
|
43
|
-
pnpm add -D @cbartens/bkit@latest && \
|
|
23
|
+
pnpm add -D @cbartens/bkit@latest && \
|
|
44
24
|
bkit install --claude --cursor
|
|
45
25
|
```
|
|
46
26
|
Writes `.agents/`, `.claude/`, `.cursor/` and the `bkit:gate:*` `package.json` scripts, and copies the templates (CI workflow, hooks, tool configs) into `.bkit/templates/` without applying them. `.bkit/templates.md` lists each template plus the tool scripts and devDeps the gates chain.
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
|
|
27
|
+
3. Read `.bkit/advisories.md` end-to-end. For every `[advisory]`/`[blocker]`: apply its **Action** unless truly N/A. If you skip, state advisory id and why.
|
|
28
|
+
4. Read `.bkit/templates.md`, then compare each template in `.bkit/templates/` (CI workflows, git hooks, lint and Vale configs, Cursor config, dependency updaters, etc.) with this repo. bkit never applies templates, so adoption is your job: adopt unless adoption would break existing functionality. For any template not adopted, state which and why.
|
|
29
|
+
5. Re-run `bkit check` (or `pnpm bkit check`). Fix remaining drift/advisories you can. End with: resolved version, advisories applied, advisories skipped (with reasons), templates adopted/skipped (with reasons).
|
|
50
30
|
````
|
|
51
31
|
|
|
52
32
|
### Upgrade — already installed
|
|
53
33
|
|
|
54
|
-
Same paste block ships in `.bkit/README.md` (mirrored into consumer repos on install — keep both in sync when editing). Copy when the repo already has `@cbartens/bkit`. Prefer `bkit upgrade --latest` (bumps the package **and** resyncs managed files) — do **not** only `pnpm add`.
|
|
34
|
+
Same paste block ships in `.bkit/README.md` (mirrored into consumer repos on install — keep both in sync when editing). Copy when the repo already has `@cbartens/bkit`. Prefer `bkit upgrade --latest` (bumps the package **and** resyncs managed files) — do **not** only `pnpm add`.
|
|
55
35
|
|
|
56
36
|
````text
|
|
57
37
|
Upgrade `@cbartens/bkit` to the latest version in this repo and finish the resync.
|
|
58
|
-
1.
|
|
59
|
-
```bash
|
|
60
|
-
set -a; source <ENV-FILE-PATH> 2>/dev/null; set +a; \
|
|
61
|
-
pnpm config set "//npm.pkg.github.com/:_authToken=$BKIT_GH_TOKEN_INSTALL" && \
|
|
62
|
-
bkit upgrade --latest
|
|
63
|
-
```
|
|
64
|
-
If token already exported (direnv / shell profile), skip `source`:
|
|
38
|
+
1. Bump and resync in one step (no token — npmjs is public). If `bkit` is not on PATH, use `pnpm bkit`:
|
|
65
39
|
```bash
|
|
66
40
|
bkit upgrade --latest
|
|
67
41
|
```
|
|
68
|
-
|
|
42
|
+
Do **not** only `pnpm add @cbartens/bkit@latest` — that refreshes the package without resyncing managed files.
|
|
69
43
|
2. Read `.bkit/advisories.md` end-to-end. For every `[advisory]`/`[blocker]`: apply its **Action** unless truly N/A. If you skip, state advisory id and why.
|
|
70
44
|
3. Read the template changes `bkit upgrade` printed (or `git diff .bkit/templates`), then `.bkit/templates.md`. bkit never applies templates, so adoption is your job: adopt each change unless it would break existing functionality. For any change not adopted, state which and why.
|
|
71
45
|
4. Re-run `bkit check` (or `pnpm bkit check`). Fix remaining drift/advisories you can. End with: resolved version, advisories applied, advisories skipped (with reasons), templates adopted/skipped (with reasons).
|
|
@@ -73,29 +47,25 @@ Upgrade `@cbartens/bkit` to the latest version in this repo and finish the resyn
|
|
|
73
47
|
|
|
74
48
|
## Install
|
|
75
49
|
|
|
76
|
-
bkit is
|
|
50
|
+
bkit is published publicly on **npmjs** (`https://registry.npmjs.org`). Add to a consumer repo:
|
|
77
51
|
|
|
78
52
|
```bash
|
|
79
|
-
pnpm add -D @cbartens/bkit
|
|
53
|
+
pnpm add -D @cbartens/bkit
|
|
80
54
|
```
|
|
81
55
|
|
|
82
56
|
### Adding a new consumer — checklist
|
|
83
57
|
|
|
84
|
-
Run these in order on a brand-new consumer repo.
|
|
58
|
+
Run these in order on a brand-new consumer repo.
|
|
85
59
|
|
|
86
60
|
<!-- prettier-ignore -->
|
|
87
61
|
| # | Step | Detail |
|
|
88
62
|
| --- | --- | --- |
|
|
89
|
-
| 1 |
|
|
90
|
-
| 2 |
|
|
91
|
-
| 3 |
|
|
92
|
-
| 4 |
|
|
93
|
-
| 5 | Run `bkit install --claude --cursor` to seed both hosts (writes `.bkit/.env.example`; `.envrc` is a template in `.bkit/templates/`) | [§ Install](#install) (this section) |
|
|
94
|
-
| 5a | Set up direnv + `.bkit/.env` so every subsequent shell auto-loads `BKIT_GH_TOKEN_INSTALL`, `BKIT_GH_TOKEN`, `BKIT_LINEAR_API_KEY` | [§ Local env setup](#local-env-setup) |
|
|
95
|
-
| 6 | If deploying to Vercel: add `BKIT_GH_TOKEN_INSTALL` to Vercel env vars | [§ Consumer Vercel auth](#consumer-vercel-auth) |
|
|
96
|
-
| 7 | Push to a feature branch and verify CI runs green | — |
|
|
63
|
+
| 1 | `pnpm add -D @cbartens/bkit` — no token, no registry mapping | this section |
|
|
64
|
+
| 2 | Run `bkit install --claude --cursor` to seed both hosts (writes `.bkit/.env.example`; `.envrc` is a template in `.bkit/templates/`) | this section |
|
|
65
|
+
| 3 | Set up direnv + `.bkit/.env` for `BKIT_GH_TOKEN` (GitHub MCP) and `BKIT_LINEAR_API_KEY` — no registry token | [§ Local env setup](#local-env-setup) |
|
|
66
|
+
| 4 | Push to a feature branch and verify CI runs green | — |
|
|
97
67
|
|
|
98
|
-
|
|
68
|
+
No CI step, secret, `.npmrc` mapping or Vercel env is needed — CI reaches npmjs anonymously.
|
|
99
69
|
|
|
100
70
|
### Then in the consumer repo
|
|
101
71
|
|
|
@@ -133,17 +103,25 @@ bkit check
|
|
|
133
103
|
|
|
134
104
|
**Opt-in flags:** `--tracker=github|linear`, `--auto=claude|cursor` (cloud agents), `--opencode=<provider>` (additive opencode execution host — `openrouter`, `ollama`, `opencode-zen`, `opencode-go`). Dependency updaters: copy an example and own it. See [§ Optional post-install decisions](#optional-post-install-decisions).
|
|
135
105
|
|
|
106
|
+
### Payload view links — `.bkit/core` + `.bkit/shared`
|
|
107
|
+
|
|
108
|
+
Install and upgrade create two **relative symlinks** into the installed package, so the payload sources (workflows, prompts, hooks) are browsable in-repo: `.bkit/core` → `../node_modules/@cbartens/bkit/.bkit/core`, same shape for `shared`. Views, not copies — always the installed version, zero drift. Rules:
|
|
109
|
+
|
|
110
|
+
- Both paths sit in the `.gitignore` managed block — they dangle on a fresh clone or in CI (no `node_modules`); `bkit install` / `upgrade` recreates them.
|
|
111
|
+
- The `bkit` binary reads its payload from the package regardless; the links are browse-only. Editors resolve them to the `node_modules/…` paths.
|
|
112
|
+
- A real directory at either path is never clobbered (advisory `payload-link-real-dir`) — remove it yourself and re-run install to get the link. A platform that refuses symlinks (Windows without Developer Mode) falls back to a junction, then to advisory `payload-link-failed` — never a failure.
|
|
113
|
+
- `bkit uninstall` removes the links (symlinks only — consumer content stays).
|
|
114
|
+
|
|
136
115
|
> **⚠️ Moving bkit versions: use `bkit upgrade --latest` (or `--to=<version>`).** Bumps `@cbartens/bkit` **and** resyncs `.agents/` payload + `.bkit/version` pin in one atomic step — two can never drift apart. Bare `pnpm add @cbartens/bkit` (or Renovate/Dependabot bump) only refreshes `package.json` + lockfile — does **not** resync; skipping resync reds CI on `bkit check` drift gate. If you bump package separately, run `bkit upgrade` afterward and commit resync alongside version bump in same PR.
|
|
137
116
|
|
|
138
117
|
### Local env setup
|
|
139
118
|
|
|
140
|
-
Two flows — pick one. Both
|
|
119
|
+
Two flows — pick one. Both put `BKIT_GH_TOKEN` in shell for the GitHub MCP server; Linear repos also need `BKIT_LINEAR_API_KEY`. Use `gh auth login` for CLI.
|
|
141
120
|
|
|
142
121
|
#### Flow A — Shell export (quickest, no extra deps)
|
|
143
122
|
|
|
144
123
|
```bash
|
|
145
124
|
# Add to ~/.zshrc (or ~/.bashrc)
|
|
146
|
-
export BKIT_GH_TOKEN_INSTALL=<classic PAT, read:packages> # pnpm → npm.pkg.github.com
|
|
147
125
|
export BKIT_GH_TOKEN=<fine-grained PAT> # GitHub MCP
|
|
148
126
|
export BKIT_LINEAR_API_KEY=<Linear personal API key> # Linear MCP + preflight
|
|
149
127
|
|
|
@@ -169,7 +147,7 @@ echo 'eval "$(direnv hook zsh)"' >> ~/.zshrc && source ~/.zshrc
|
|
|
169
147
|
# 3. One-time per consumer repo (after `bkit install`)
|
|
170
148
|
cp .bkit/templates/.envrc .envrc # unless you already have one
|
|
171
149
|
cp .bkit/.env.example .bkit/.env
|
|
172
|
-
# Edit .bkit/.env: set
|
|
150
|
+
# Edit .bkit/.env: set BKIT_GH_TOKEN, BKIT_LINEAR_API_KEY
|
|
173
151
|
direnv allow # trust the .envrc
|
|
174
152
|
|
|
175
153
|
# 4. Verify
|
|
@@ -181,16 +159,6 @@ After step 4, restart open Claude Code / Cursor sessions in this repo so new env
|
|
|
181
159
|
|
|
182
160
|
`.bkit/.env` gitignored — never commit. Cloud sessions (Claude Code on the web, Cursor Background Agents): set same names in respective online dashboards; see `.bkit/cloud.md` § Environment variables. `bkit install` / `bkit check` advisories detect missing direnv, blank required keys, un-allowed `.envrc` — follow whichever fires.
|
|
183
161
|
|
|
184
|
-
#### One-time per machine — register the GH Packages token with pnpm
|
|
185
|
-
|
|
186
|
-
After either flow makes `BKIT_GH_TOKEN_INSTALL` available in shell, write into pnpm user-level auth config so local `pnpm install` resolves `@cbartens/bkit`:
|
|
187
|
-
|
|
188
|
-
```bash
|
|
189
|
-
pnpm config set "//npm.pkg.github.com/:_authToken=$BKIT_GH_TOKEN_INSTALL"
|
|
190
|
-
```
|
|
191
|
-
|
|
192
|
-
pnpm >=10.34.3 does not authenticate project-`.npmrc` `${BKIT_GH_TOKEN_INSTALL}` env-substitution (401s on download) — user-level step required; committed `.npmrc` carries only registry mapping. `pnpm config set` writes `~/.npmrc` on pnpm 10.x and `~/.config/pnpm/auth.ini` on pnpm 11.x (whichever pnpm reads) — same command across pnpm versions.
|
|
193
|
-
|
|
194
162
|
## Cloud agent environments (Claude Code on the web + Cursor Background Agents)
|
|
195
163
|
|
|
196
164
|
bkit ships repo-side scaffolding for both cloud agents. Opt-in `bkit install --auto=claude` writes no file; the per-session install hook (`.claude/hooks/bkit-cloud-bootstrap.sh`), the phase-routed `.github/workflows/bkit-cloud.yml` and the Cursor cloud image files (`.cursor/Dockerfile`, `.cursor/environment.json`) are templates in `.bkit/templates/` that you copy and own. (`.cursor/hooks.json` — Linear preflight wiring — ships with `--cursor`, not `--auto`.) Install without `--auto` ships zero cloud footprint. **Online-dashboard** half (Claude env in `claude.ai/code`, Cursor env vars in `Cursor → Settings → Background Agents`) configured once per machine / account.
|
|
@@ -225,77 +193,6 @@ In this example, `hooks.SessionStart` is bkit-declared scope (from template). `h
|
|
|
225
193
|
- `bkit check` surfaces `tier2-json-drift` advisory when `deepContains` fails and **exits 1** (CI drift gate); writes nothing — consumer reviews and re-runs `bkit install` to reconverge.
|
|
226
194
|
- `.cursor/hooks.json` uses Cursor v1 keyed-object schema: `{"version": 1, "hooks": {"sessionStart": [...], "sessionStop": [...]}}`.
|
|
227
195
|
|
|
228
|
-
## Consumer CI auth
|
|
229
|
-
|
|
230
|
-
bkit resolves from **GitHub Packages npm registry**. Authentication requires:
|
|
231
|
-
|
|
232
|
-
1. **Create a classic PAT** on GitHub with `read:packages` scope:
|
|
233
|
-
- GitHub Settings → Developer settings → Personal access tokens → **Tokens (classic)** → Scope: `read:packages`
|
|
234
|
-
- Copy the generated token
|
|
235
|
-
|
|
236
|
-
> **⚠️ Use a classic PAT, not fine-grained.** GitHub Packages npm registry currently rejects fine-grained PATs with HTTP 403, even when `Packages: read` is granted. Confirmed against `npm.pkg.github.com` 2026-05-06. If/when GitHub fixes this, fine-grained PATs will become preferred (narrower scope); for now classic is the only working option.
|
|
237
|
-
|
|
238
|
-
2. **Add the secret** to your consumer repo:
|
|
239
|
-
- GitHub repo → Settings → Secrets and variables → Actions → New repository secret
|
|
240
|
-
- Name: `BKIT_GH_TOKEN_INSTALL`
|
|
241
|
-
- Value: paste the PAT
|
|
242
|
-
|
|
243
|
-
3. **Add `.npmrc`** at your repo root (committed, no secrets) — registry mapping ONLY. Auth token **not** stored here:
|
|
244
|
-
|
|
245
|
-
```
|
|
246
|
-
@cbartens:registry=https://npm.pkg.github.com
|
|
247
|
-
```
|
|
248
|
-
|
|
249
|
-
4. The `bkit-ci.yml` template's install step writes token into pnpm user-level config before install (copy it from `.bkit/templates/.github/workflows/bkit-ci.yml`, or add the step to your own workflow):
|
|
250
|
-
|
|
251
|
-
```yaml
|
|
252
|
-
- name: Install Dependencies
|
|
253
|
-
run: |
|
|
254
|
-
pnpm config set "//npm.pkg.github.com/:_authToken=$BKIT_GH_TOKEN_INSTALL"
|
|
255
|
-
pnpm install --frozen-lockfile
|
|
256
|
-
env:
|
|
257
|
-
BKIT_GH_TOKEN_INSTALL: ${{ secrets.BKIT_GH_TOKEN_INSTALL }}
|
|
258
|
-
```
|
|
259
|
-
|
|
260
|
-
> **⚠️ Why `pnpm config set`, not `.npmrc`:** pnpm >=10.34.3 does not authenticate project-`.npmrc` `${BKIT_GH_TOKEN_INSTALL}` env-substitution — `pnpm install` 401s on `@cbartens/bkit` download (`ERR_PNPM_FETCH_401`) even when token set. `pnpm config set` writes token to pnpm user-level config (`~/.npmrc` on pnpm 10.x, `~/.config/pnpm/auth.ini` on pnpm 11.x). Leftover `_authToken` line in project `.npmrc` must be **removed** — 401s and, by config precedence (project > user), shadows user-level token. Note: `pnpm view @cbartens/bkit` (metadata) may still resolve with broken setup — verify with real `pnpm install`, not `view`.
|
|
261
|
-
|
|
262
|
-
### Agent access to `BKIT_GH_TOKEN_INSTALL`
|
|
263
|
-
|
|
264
|
-
If permission rules block direct reads of `.env*` files (e.g. `Read(./.env*)`, `Bash(grep ... .env*)` denied), token still cannot be read — but **can** be exported into child process for duration of single command. Use in single Bash tool call:
|
|
265
|
-
|
|
266
|
-
```bash
|
|
267
|
-
set -a; source apps/web/.env.preview 2>/dev/null; set +a; <command that needs the token>
|
|
268
|
-
```
|
|
269
|
-
|
|
270
|
-
- `source` is shell builtin, not file I/O — agent permission layer (gates `Read` / `grep` / `cat`) does not see it. Token text never enters agent context.
|
|
271
|
-
- `<command>` (e.g. `pnpm view @cbartens/bkit`, `bkit check`) inherits `BKIT_GH_TOKEN_INSTALL` via environment.
|
|
272
|
-
- Verify token loaded **without leaking value**: `echo "len=${#BKIT_GH_TOKEN_INSTALL}"`.
|
|
273
|
-
|
|
274
|
-
**Caveat:** shell state does not persist between separate Bash tool calls. `source` and consuming command must run in **same** invocation — chain with `;` or `&&`. When directing another agent, name file path explicitly (e.g. _"source `apps/web/.env.preview` in-line; registry needs `BKIT_GH_TOKEN_INSTALL`"_).
|
|
275
|
-
|
|
276
|
-
## Consumer Vercel auth
|
|
277
|
-
|
|
278
|
-
Vercel runs own `pnpm install` in fresh build container — cannot run pre-install shell step. pnpm >=10.34.3 does not authenticate project-`.npmrc` `${BKIT_GH_TOKEN_INSTALL}` env-substitution, so set token via one-line `installCommand` writing pnpm user-level config before install.
|
|
279
|
-
|
|
280
|
-
1. **Add `BKIT_GH_TOKEN_INSTALL` to Vercel env vars** for each environment that builds (preview + production at minimum):
|
|
281
|
-
|
|
282
|
-
```bash
|
|
283
|
-
vercel env add BKIT_GH_TOKEN_INSTALL preview
|
|
284
|
-
vercel env add BKIT_GH_TOKEN_INSTALL production
|
|
285
|
-
```
|
|
286
|
-
|
|
287
|
-
Or via web: Vercel project → Settings → Environment Variables. Token value = same PAT as GitHub Actions secret (scope: `read:packages`).
|
|
288
|
-
|
|
289
|
-
2. **Set `installCommand` in `vercel.json`** so token reaches pnpm user-level auth config before install (remove any pre-existing git-shim `installCommand`):
|
|
290
|
-
|
|
291
|
-
```json
|
|
292
|
-
{
|
|
293
|
-
"installCommand": "pnpm config set //npm.pkg.github.com/:_authToken=$BKIT_GH_TOKEN_INSTALL && pnpm install"
|
|
294
|
-
}
|
|
295
|
-
```
|
|
296
|
-
|
|
297
|
-
3. **Trigger redeploy** (push commit) and watch Vercel build log for `pnpm install` resolving `@cbartens/bkit` from `npm.pkg.github.com`.
|
|
298
|
-
|
|
299
196
|
## Install lifecycle
|
|
300
197
|
|
|
301
198
|
`bkit install` runs three phases in sequence:
|
|
@@ -318,20 +215,12 @@ Module dispatch writes managed files.
|
|
|
318
215
|
|
|
319
216
|
**Phase 3 — Post-install (re-detect + unified output)**
|
|
320
217
|
|
|
321
|
-
After writes, bkit re-runs
|
|
218
|
+
After writes, bkit re-runs credential and environment checks — some only accurate post-install (e.g. the `bkit:gate:*` scripts core just seeded into `package.json`). The table also lists the module advisories that render in the same checklist.
|
|
322
219
|
|
|
323
220
|
<!-- prettier-ignore -->
|
|
324
221
|
| `id` | When |
|
|
325
222
|
| --- | --- |
|
|
326
|
-
| `gh-bkit-token-unset-shell` / `gh-bkit-token-empty-shell` | `BKIT_GH_TOKEN_INSTALL` unset (or set but empty) in shell |
|
|
327
|
-
| `npmrc-missing-gh-packages` | `.npmrc` exists but lacks the `@cbartens` registry mapping |
|
|
328
|
-
| `npmrc-authtoken-line` | `.npmrc` carries a `//npm.pkg.github.com/:_authToken=…` line (401s on pnpm >=10.34.3; move it to pnpm user-level config) |
|
|
329
|
-
| `gh-bkit-token-secret-missing` | `gh secret list` confirms secret absent |
|
|
330
|
-
| `gh-bkit-token-secret-unknown` | `gh` CLI unavailable/unauthenticated |
|
|
331
223
|
| `gh-mcp-token-unset-shell` / `gh-mcp-token-empty-shell` | `BKIT_GH_TOKEN` (GitHub MCP auth) unset/empty in shell while a `github` MCP server is configured — the whole tracker/PR/board MCP surface fails to connect. Suppressed in CI. |
|
|
332
|
-
| `vercel-env-missing-preview` | `vercel.json` detected; token absent in preview |
|
|
333
|
-
| `vercel-env-missing-production` | `vercel.json` detected; token absent in production |
|
|
334
|
-
| `ci-yml-missing-token-env` | bkit-ci.yml install step lacks the `pnpm config set` auth step and/or the `BKIT_GH_TOKEN_INSTALL` env mapping |
|
|
335
224
|
| `tracker-setup-none` / `-github` / `-linear` | Optional post-install decision — which issue tracker is wired (`bkit.issueTracker`). `none` nudges `bkit install --tracker=…`. See [§ Optional post-install decisions](#optional-post-install-decisions). |
|
|
336
225
|
| `github-project-board-sync-unconfigured` | GitHub tracker active but Projects v2 board sync is half-configured (`bkit.githubProject` absent and/or `.mcp.json` lacks the `projects` toolset) — sync silently no-ops. Silence with `bkit.githubProject: false`. |
|
|
337
226
|
| `github-project-status-field-id-format` | `bkit.githubProject` is configured but `statusFieldId` holds a GraphQL node id (`PVTSSF_…`) or non-number — `projects_write` needs the numeric field id, so board sync silently no-ops. Re-derive via `gh api /orgs/<org>/projectsV2/<number>/fields`. |
|
|
@@ -360,9 +249,25 @@ interface PreflightFinding {
|
|
|
360
249
|
}
|
|
361
250
|
```
|
|
362
251
|
|
|
363
|
-
Findings
|
|
252
|
+
Findings render as `--- i/N [severity] id ---` with `Detect:` and `Action:` lines. The console banner and the `.bkit/advisories.md` artifact render the same text — copy either into a coding assistant to apply fixes in sequence.
|
|
253
|
+
|
|
254
|
+
**Dismissing an advisory (per package).** A detector can be right in general and still fire where the condition is deliberately not applicable — a rule-linter whose test titles mention `@live`, an integration lane mocked by design. Opt the owning package out in its `package.json`:
|
|
364
255
|
|
|
365
|
-
|
|
256
|
+
```json
|
|
257
|
+
{
|
|
258
|
+
"bkit": {
|
|
259
|
+
"ignoreAdvisories": ["tagged-tests-no-ci-home"]
|
|
260
|
+
}
|
|
261
|
+
}
|
|
262
|
+
```
|
|
263
|
+
|
|
264
|
+
<!-- prettier-ignore -->
|
|
265
|
+
| Rule | Behaviour |
|
|
266
|
+
| --- | --- |
|
|
267
|
+
| Scope | Per package, read from the **owning** package's `package.json` — the package holding the test file for `tagged-tests-no-ci-home`, the repo root for `test-integration-env-not-asserted` (the only manifest it reads). A sibling package with a real finding stays flagged. |
|
|
268
|
+
| Severity | Advisory only. A `blocker` is never suppressible, whatever the manifest says. |
|
|
269
|
+
| Visibility | The console banner and `.bkit/advisories.md` carry one suppressed-advisory line per dismissal (`N advisory` / `N advisories`), so a stale opt-out cannot hide a finding silently. |
|
|
270
|
+
| Coverage | Wired for `tagged-tests-no-ci-home` and `test-integration-env-not-asserted`. No other advisory is suppressible; an id matching no advisory is ignored. |
|
|
366
271
|
|
|
367
272
|
## Optional post-install decisions
|
|
368
273
|
|
|
@@ -404,7 +309,7 @@ Tracker and cloud agents reverse by re-running install with the other flag. Upda
|
|
|
404
309
|
|
|
405
310
|
## Doctor
|
|
406
311
|
|
|
407
|
-
`bkit doctor` is **diagnostic verb** — runs Phase 1 preflight + Phase 3
|
|
312
|
+
`bkit doctor` is **diagnostic verb** — runs Phase 1 preflight + Phase 3 credential detectors, exits 0. Changes no managed file; like `bkit check` regenerates `.bkit/advisories.md` artifact (creates `.bkit/` if absent — repo that never installed bkit gains that one file).
|
|
408
313
|
|
|
409
314
|
```bash
|
|
410
315
|
# Diagnose drift without running install
|
|
@@ -413,7 +318,7 @@ bkit doctor
|
|
|
413
318
|
|
|
414
319
|
Use `bkit doctor` to:
|
|
415
320
|
|
|
416
|
-
- Check
|
|
321
|
+
- Check `BKIT_GH_TOKEN` presence in shell (GitHub MCP auth) and the cloud-router (`ANTHROPIC_API_KEY`) repo secret.
|
|
417
322
|
- Surface `bkit-version-pin-stale` advisory (installed version ahead of `.bkit/version`).
|
|
418
323
|
- Preview all advisories `bkit install` would show post-install, without triggering writes.
|
|
419
324
|
- Verify environment ready before `bkit install` on new machine.
|
|
@@ -422,7 +327,7 @@ Use `bkit doctor` to:
|
|
|
422
327
|
|
|
423
328
|
## Uninstall
|
|
424
329
|
|
|
425
|
-
`bkit uninstall` surgically removes bkit-managed content while preserving consumer customisations.
|
|
330
|
+
`bkit uninstall` surgically removes bkit-managed content while preserving consumer customisations. The `.bkit/core` / `.bkit/shared` payload view links go with a full/core uninstall (symlinks only — a real directory at either path is consumer content and stays).
|
|
426
331
|
|
|
427
332
|
```bash
|
|
428
333
|
# Uninstall EVERYTHING — all modules, including the cloud add-on if present.
|
|
@@ -468,7 +373,7 @@ Bare uninstall removes bkit-managed files and strips bkit-managed blocks, but **
|
|
|
468
373
|
|
|
469
374
|
## Phase 3 exit-1 and recovery
|
|
470
375
|
|
|
471
|
-
When `bkit install` detects **blocker-severity** finding in Phase 3 (e.g. `
|
|
376
|
+
When `bkit install` detects **blocker-severity** finding in Phase 3 (e.g. `owned-hook-missing` — a bkit-owned hook file is gone, so the guard or setup step it holds does not run), exits 1 and prints single-line recovery command:
|
|
472
377
|
|
|
473
378
|
```
|
|
474
379
|
[bkit-install] 1 Phase 3 blocker(s) detected. Recovery:
|
|
@@ -466,11 +466,11 @@ Indented for readability — **on disk each row = single physical line** (§ Wri
|
|
|
466
466
|
"step": "plan-generate",
|
|
467
467
|
"subagent": "bkit-plan-generate",
|
|
468
468
|
"model": "claude-opus-4-8",
|
|
469
|
-
"key": "bkit-distribution-via-
|
|
470
|
-
"summary": "
|
|
471
|
-
"description": "
|
|
472
|
-
"rationale": "
|
|
473
|
-
"alternatives": "
|
|
469
|
+
"key": "bkit-distribution-via-npmjs",
|
|
470
|
+
"summary": "publish @cbartens/bkit publicly on npmjs",
|
|
471
|
+
"description": "publish @cbartens/bkit publicly on npmjs; consumers install with no registry mapping, PAT, or CI/Vercel env",
|
|
472
|
+
"rationale": "public install needs no registry mapping or token; release.yml publishes from CI via npm OIDC trusted publishing",
|
|
473
|
+
"alternatives": "private registry with a read token, git-dependency install, Releases tarball, vendor per-consumer",
|
|
474
474
|
"status": "ACTIVE",
|
|
475
475
|
"references": ["ISSUE-138", "ISSUE-130", "package.json", ".github/workflows/release.yml"]
|
|
476
476
|
}
|
|
@@ -146,7 +146,6 @@ pnpm add -D prettier@^3.5.3 slop-scan@^0.3.0 lint-staged@^17.0.0 husky@^9.1.7
|
|
|
146
146
|
Parallel lanes `bkit-tests-static` (typecheck, prettier, Vale, slop, actionlint, `bkit check`) and `bkit-tests-unit`, joined by the `bkit-tests-check` capstone, plus the commented full CI scaffold reference for the other tiers. Workflows care: `/bkit-ship` waits on its runs and merges only when the `bkit.capstoneJob` job (default `bkit-tests-check`) is present and green at the head; `bkit setup protect-main` makes that job the required check; `bkit-cloud.yml` triggers on a workflow named `bkit-ci`. `bkit install` reads your copy for advisories (`ci-yml-missing-token-env`, `bkit-stub-*`, `ci-yml-missing-actionlint`, `ci-yml-capstone-contract-drift`). Reference: https://docs.github.com/en/actions.
|
|
147
147
|
|
|
148
148
|
- Install: nothing beyond the gate tool scripts above, a `test` script, and `packageManager` in `package.json` (`pnpm/action-setup` reads it; do not add `with: version:`).
|
|
149
|
-
- Secrets: `BKIT_GH_TOKEN_INSTALL` (`read:packages`) → `docs/deployments.md` § Consumer CI auth.
|
|
150
149
|
- Adapt: `{{DEFAULT_BRANCH}}`, `{{NODE_VERSION}}`. Non-Node repo → replace the Node / pnpm setup, install and check steps with your stack's.
|
|
151
150
|
- Capstone: `bkit-tests-check` `needs:` every lane and runs on `!cancelled()`, never `always()`. Each lane you adopt from the reference goes into its `needs:` and its assert, or that lane's failure cannot red the merge. It asserts each lane's executed-test count once the lane writes one (the `Run Unit Tests` step comment shows the vitest form); an unreported count is a warning, a count of 0 a failure. Renaming the job → set `bkit.capstoneJob`.
|
|
152
151
|
- Adopt a scaffold lane only when its tier exists (`docs/testing.md`). Each `# bkit-stub:<id> —` header raises an install advisory until you enable or delete that stub.
|
|
@@ -227,7 +226,7 @@ cp .bkit/templates/scripts/slop/bkit-slop-type-suppression.mjs scripts/slop/
|
|
|
227
226
|
|
|
228
227
|
## direnv — `.envrc`
|
|
229
228
|
|
|
230
|
-
Loads `.bkit/.env` on `cd`, so local sessions see `BKIT_GH_TOKEN`,
|
|
229
|
+
Loads `.bkit/.env` on `cd`, so local sessions see `BKIT_GH_TOKEN`, tracker keys. bkit reads your `.envrc` (its `dotenv*` and `unset` lines, never executed) to fill the env blocks of `.claude/bkit-cloud.md` / `.cursor/bkit-cloud.md`; preflight's direnv advisories key on it. Reference: https://direnv.net/docs/installation.html.
|
|
231
230
|
|
|
232
231
|
```bash
|
|
233
232
|
brew install direnv # then add the shell hook from the link
|
|
@@ -274,7 +273,7 @@ launchctl getenv BKIT_OPENROUTER_API_KEY # bootstrap proof
|
|
|
274
273
|
Editor defaults (`settings.json`: prettier format-on-save, extension recommendations) and the Cursor Cloud Agent image (`environment.json` → `Dockerfile` + per-snapshot `install`). Cloud agents run bkit workflows; `bkit install --auto=cursor` (needs `--tracker=linear`) points at the two cloud files. Reference: https://cursor.com/docs/cloud-agent/setup.
|
|
275
274
|
|
|
276
275
|
- `Dockerfile`: the `bkit toolchain` section installs what bkit's workflows use (git, jq, python3, gh, pinned Vale, corepack-pinned pnpm). Adapt `FROM`, the Node major and repo extras outside it.
|
|
277
|
-
- `environment.json` `install`:
|
|
276
|
+
- `environment.json` `install`: `pnpm install --frozen-lockfile`, then `vale sync` when `.vale.ini` exists.
|
|
278
277
|
- Secrets: Cloud Agents dashboard → Runtime Secrets (`.bkit/cloud.md`).
|
|
279
278
|
- Traps: the corepack pnpm pin must match `packageManager`. Keep the `bkit toolchain` section as shipped so the template diff on upgrade stays readable.
|
|
280
279
|
|
|
@@ -785,11 +785,15 @@ GitHub Actions: `push.head_commit.message` vs `pull_request.title`. Template bki
|
|
|
785
785
|
<!-- prettier-ignore -->
|
|
786
786
|
| `PUSH_MODE` | When | CI event fired by debug push | Marker surface | Mechanism |
|
|
787
787
|
| --- | --- | --- | --- | --- |
|
|
788
|
-
| `LOCAL` | Debug invoked on a `dev` / `main` failure
|
|
788
|
+
| `LOCAL` | Debug invoked on a `dev` / `main` failure, or a feature branch with no open PR | `push` event reads `head_commit.message` | **Commit message** | `bkit [verbose ci]` appended conditionally via `VERBOSE_SUFFIX=""; [ "$PUSH_MODE" = "LOCAL" ] && VERBOSE_SUFFIX=" bkit [verbose ci]"` immediately before the relevant commits in `bkit-debug.md` (Step 6 `fix`, Step 7 `soak`, Step 9 `summary`, Step 10 `close-workflow`, Step 10 `create-pr`). PR-mode runs skip the suffix (`pull_request` events ignore commit messages). Self-clearing per push — non-debug pushes return to default. |
|
|
789
789
|
| `PR` | Debug invoked on a feature branch with an open PR (the dominant case) | `pull_request.synchronize` reads `pull_request.title` | **PR title** | Step 8 (Push Remediation) runs `gh pr edit --title` to idempotently append `bkit [verbose ci]` to the PR title (skip if already present) immediately before the push. Step 10 (Close Workflow) sub-step 1 strips it via `sed` + `gh pr edit` on a successful close. Failure Path / handover **do not strip** — the post-handover human investigator wants continued verbose CI. |
|
|
790
790
|
|
|
791
791
|
Both paths idempotent — re-run skips when present; orphan markers cleaned by next debug Step 10 strip on successful close.
|
|
792
792
|
|
|
793
|
+
**Close PR-create decision:** the Step-1 `PUSH_MODE` does **not** gate PR creation — Step 10 probes live PR state (`bkit prs probe --head="{BRANCH}" --base=dev`), sets `TRIGGER_PR` from `{PR_OPEN}`, adopts a mid-run PR (`bkit prs open --existing=reuse`) rather than blind-creating into the Failure Path, then the gate asserts the dispatched `pull_request` run on every feature-branch close. `PUSH_MODE` = marker-surface hint only.
|
|
794
|
+
|
|
795
|
+
**Invariant:** a successful debug/build close leaves a PR to `dev` (created or adopted) with a run the gate asserts; the Failure Path leaves the `[skip ci]` handover + abort-guard and dispatches no CI.
|
|
796
|
+
|
|
793
797
|
**Cleanup invariant:** PR-title marker stripped on successful `/bkit-debug` close (Step 10, `PUSH_MODE = PR`). Failure Path / handover preserve intentionally — post-handover investigator wants continued verbose CI. Cleanup via: (a) next `/bkit-debug` close success, (b) manual strip, (c) PR merge — squash subject inherits `bkit [verbose ci]` → one post-merge dev CI verbose (harmless, recovery evidence).
|
|
794
798
|
|
|
795
799
|
**Manual override:** append `bkit [verbose ci]` to any commit message or PR title — env block honours both. Debug auto-propagation removes manual need for dominant retry-evidence case.
|
|
@@ -1156,7 +1160,7 @@ Outcome-verification gate: after final loud push, confirms bkit CI check dispatc
|
|
|
1156
1160
|
|
|
1157
1161
|
- **Build Step 18:** close-workflow commit → `bkit branches push --mode=feature --require-ci` (no PR yet, no CI) → `bkit prs open` (the PR creation fires CI) → `bkit runs dispatch --pr=`.
|
|
1158
1162
|
- **Debug Step 10 PR-mode:** close-workflow push (sub-step 2, `--require-ci`) = CI trigger; gate in sub-step 6.
|
|
1159
|
-
- **Debug Step 10 LOCAL-mode:** create-pr push (sub-step
|
|
1163
|
+
- **Debug Step 10 LOCAL-mode:** create-pr push (sub-step 6, `--require-ci`) = CI trigger, its block re-deriving `AUTO_ROUTE_SUFFIX`; gate in sub-step 7.
|
|
1160
1164
|
- **Ship:** OUT of scope. Step 15 reads the squash commit's CI with `bkit runs gate --head=<SQUASH_SHA>` and records `ship-merge-ci`. CI-Dispatch at ship would mask "essential tests skipped" signal ship backstops.
|
|
1161
1165
|
- **Ship Step 9 duplicate-dispatch probe (not the gate):** `bkit runs wait --head=<VALIDATED_HEAD> --branch= --until=present --dispatch-if-absent` probes for a CI-workflow run at that head, presence only (`SHIP_PROBE_ATTEMPTS` x `SHIP_PROBE_INTERVAL_S`), and runs `gh workflow run {bkit.ciWorkflow}` only on no-run. The head move it follows (Path B `bkit prs update-branch`) already fires `pull_request` at the same SHA, and the template `bkit-ci.yml` groups `pull_request` by PR number but `workflow_dispatch` by ref — different groups, so neither cancels the other and both runs complete. The probe carries no outcome vocabulary and is never a pass condition (no `self-healed`/`no-ci` path exists at ship): the head-anchored completion poll (`--until=completed`) and `bkit runs gate` at Gate 10 still own the verdict, so the "masks essential tests skipped" objection does not apply. Probe `err` → dispatch. Row `ship-revalidate-dispatch` records `probe` / `dispatched` / `attempts`. The 60s budget is load-bearing: a `pull_request` run surfacing after it reproduces the duplicate this probe removes. Auto-fired runs typically appear ~10-20s after the push, but auto-fire is intermittent, so the probe MUST keep failing safe to dispatch rather than reading a slow or absent run as "no CI".
|
|
1162
1166
|
- **Ship Gate 10 + squash `--body ""`:** merge — squash subject = dev HEAD.
|
|
@@ -1223,7 +1227,7 @@ Rationale: invariant **contextual** — bkit pushes `[skip ci]` intermediately (
|
|
|
1223
1227
|
| --- | --- | --- | --- |
|
|
1224
1228
|
| `/bkit-build` | 18 (close-workflow) | Final commit `chore({FID}): close-workflow`, no skip tags + `bkit branches push --require-ci` + `bkit prs open` + CI-Dispatch poll | Drops `bkit [skip ci]` from the existing status commit; the PR creation on that head fires `pull_request`; gate confirms dispatch |
|
|
1225
1229
|
| `/bkit-debug` | 10 (close-workflow) PR-mode | Final commit `chore({FID}): close-workflow`, no skip tags + `git push` + CI-Dispatch poll | PR-mode: close-workflow push is the CI-triggering push; gate in sub-step 6 |
|
|
1226
|
-
| `/bkit-debug` | 10 (close-workflow) LOCAL-mode | Separate create-pr push in sub-step
|
|
1230
|
+
| `/bkit-debug` | 10 (close-workflow) LOCAL-mode | Separate create-pr push in sub-step 6 + CI-Dispatch poll | LOCAL-mode: create-pr push is the CI-triggering push; gate in sub-step 7 |
|
|
1227
1231
|
| `/bkit-ship` | 10 (merge-pr) | `bkit prs merge` (`gh pr merge --squash --body ""`) — squash subject becomes dev HEAD, body empty | `gh pr merge` is the only API; empty body strips PR-body `bkit [skip ci]` from the squash subject. Step 15 then gates the squash commit with `bkit runs gate --squash-of=<PR>` (not a CI-Dispatch Gate) |
|
|
1228
1232
|
| `/bkit-ship` | 8 (pre-merge bookkeeping) | `docs({FID}): ship bookkeeping bkit [skip ci]` pushed to `{SHIP_BRANCH}` | Docs, logs, ledgers, skill removals ride the PR; CI carried forward from `CODE_HEAD` by the gate's `--validated`, so no run is spent on them. |
|
|
1229
1233
|
| `/bkit-ship` | 15 (post-merge close) | `docs({FID}): ship DONE bkit [skip ci]` → `dev`, or a `ship-close/{FID}` PR when `dev` refuses the push | Post-merge status / telemetry only; PR already merged, dev's CI fired by Step 10, no re-trigger needed. |
|