docks-kit 0.26.0 → 0.27.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.
@@ -295,8 +295,8 @@ Write each new condition by these rules:
295
295
  - Make each scan one frozen walk that stops at its first event and at the
296
296
  next command start.
297
297
  - Never put a group loop inside a lookaround over text of unbounded length.
298
- - Run `bunx vitest run cli/test/unit/ompTriggerRules.test.ts`. It runs the
299
- shape guard and the Bun backstop.
298
+ - Run `bunx vitest run cli/test/unit/ompTriggerRules.test.ts cli/test/unit/ompTriggerBackstop.test.ts`.
299
+ The first file runs the shape guard, and the second runs the Bun backstop.
300
300
  - When you rewrite a condition, run the old and the new condition on each
301
301
  buffer of the test table, and make sure that both give the same result.
302
302
 
@@ -314,8 +314,11 @@ must start with the forward key prefix, and this rejects the leading
314
314
  lookbehind that froze omp. No `|` can stand outside every group, because the
315
315
  alternative after it needs no key prefix. The shape guard cannot prove
316
316
  linear time. The backstop tests the measured input families for linear
317
- time: the test runs `cli/test/lib/ompTriggerBackstop.ts` under Bun, because
318
- the unit tests run on V8, which does not show the JavaScriptCore cost. A
317
+ time: `cli/test/unit/ompTriggerBackstop.test.ts` runs
318
+ `cli/test/lib/ompTriggerBackstop.ts` under Bun, because the unit tests run on
319
+ V8, which does not show the JavaScriptCore cost. That file is a Vitest project
320
+ of its own, which starts after every other unit file has ended, because the
321
+ backstop uses every core (DocksDocks/docks-kit#187). A
319
322
  condition can still backtrack on a run that no generator holds, so a new
320
323
  condition needs a new family when its shape is new. The backstop has these
321
324
  checks:
@@ -1,7 +1,7 @@
1
1
  # Installing docks-kit
2
2
 
3
3
  Supported hosts are Linux x64/arm64, macOS arm64, and Windows x64.
4
- Hosts outside this matrix fail before a launcher can fall back to Bun source.
4
+ Hosts outside this matrix fail before a launcher runs the Bun source.
5
5
 
6
6
  ## 1. Repo checkout (development / current users)
7
7
 
@@ -12,10 +12,8 @@ cd ~/projects/docks-kit
12
12
  ```
13
13
 
14
14
  POSIX hosts use `./docks-kit`. Windows uses `.\docks-kit.ps1`. Each
15
- launcher prefers a compiled binary in `cli/dist/` only when its reported
16
- version matches `package.json`. It then falls back to Bun-from-source and
17
- auto-installs Bun plus `node_modules` when needed. Each launcher reports and
18
- bypasses an ignored stale build.
15
+ launcher runs the checkout source with Bun and auto-installs Bun plus
16
+ `node_modules` when needed. A launcher never runs a file in `cli/dist/`.
19
17
 
20
18
  ### Move a checkout of DocksDocks/public
21
19
 
@@ -30,9 +28,10 @@ git remote set-url origin https://github.com/DocksDocks/docks-kit.git
30
28
  .\docks-kit.ps1 sync # Windows
31
29
  ```
32
30
 
33
- The update pulls from DocksDocks/docks-kit. The sync then deploys the skills
34
- with their new report target: a launcher that runs a fresh compiled binary
35
- skips the sync that the update chains. A global npm install needs nothing.
31
+ The update pulls from DocksDocks/docks-kit and chains a sync that deploys the
32
+ skills with their new report target. The explicit sync covers an older
33
+ checkout whose launcher still runs a binary from `cli/dist/`, because that
34
+ binary does not chain the sync. A global npm install needs nothing.
36
35
 
37
36
  ## 2. Global via Bun
38
37
 
@@ -51,11 +50,12 @@ release asset (`docks-kit.js.map`), matched by the bundle's `//# debugId=` line.
51
50
  Kit-home resolution remains available for checkout/package update behavior and
52
51
  display paths, but sync reads do not depend on it.
53
52
 
54
- ### Bun 1.4.4 install output
53
+ ### Bun 1.4.5 install output
55
54
 
56
- A supported global install completes with no blocked postinstall. The graph
57
- holds nine packages, and no package in it has an install script. `bun pm -g
58
- untrusted` reports zero untrusted dependencies with scripts. Neither
55
+ An install of the package completes with no blocked postinstall. The graph
56
+ holds nine packages, and no package in it has an install script: `bun pm
57
+ untrusted` in the consumer folder (`bun pm -g untrusted` after a global
58
+ install) reports zero untrusted dependencies with scripts. Neither
59
59
  `@parcel/watcher` nor `esbuild` is in the consumer graph.
60
60
 
61
61
  The install prints no peer dependency warning. The root pins `effect`,
@@ -74,7 +74,7 @@ tmp="$(mktemp)" && curl -fsSL https://raw.githubusercontent.com/DocksDocks/docks
74
74
 
75
75
  Download-then-run, never `curl | bash` — stream truncation has bitten this
76
76
  kit before. The installer bootstraps Bun when absent, runs
77
- `bun add -g docks-kit@latest`, and links the binary into `~/.local/bin`.
77
+ `bun add -g docks-kit@latest`, and links the CLI and Bun into `~/.local/bin`.
78
78
  This installer serves the two POSIX platforms. Windows uses the PowerShell
79
79
  installer below.
80
80
 
@@ -111,14 +111,11 @@ docks-kit update --no-sync # update only
111
111
  directory whose `package.json` has the name `docks-kit`. An invalid value
112
112
  causes an error instead of a fallback.
113
113
  2. The CLI uses the nearest kit root at or above its own module directory.
114
- 3. Next, the CLI uses the nearest kit root at or above the directory that holds
115
- the executable. A standalone binary inside `<checkout>/cli/dist` therefore
116
- resolves to the checkout.
117
- 4. Next, the CLI uses the nearest kit root at or above the current working
114
+ 3. Next, the CLI uses the nearest kit root at or above the current working
118
115
  directory, but only as a fallback.
119
- 5. Otherwise, the CLI uses the directory that holds the executable.
116
+ 4. Otherwise, the CLI uses the directory that holds the executable.
120
117
 
121
- Sources 2 and 3 identify the installation that is running. A globally installed
118
+ Source 2 identifies the installation that is running. A globally installed
122
119
  `docks-kit` updates the global package even when you run it from inside a
123
120
  docks-kit checkout. `DOCKS_KIT_HOME` lets you target a specific checkout on
124
121
  purpose.
@@ -132,8 +129,6 @@ plain flag-less `docks-kit sync`. It also refreshes plugins, even when the kit
132
129
  is already current: it moves `pi-intercom` to its pinned version. Pass
133
130
  `--no-sync`, then run `docks-kit sync --skip-plugin-refresh` to keep a present
134
131
  `pi-intercom` at its installed version.
135
- A compiled binary inside a checkout updates the checkout; on the next invocation
136
- the launcher bypasses that now-stale binary and uses updated source until rebuilt.
137
132
  Every `docks-kit sync` except `--dry-run` also does a best-effort behind-upstream
138
133
  check and nudges when the checkout is stale (silent offline / detached / no git).
139
134
 
@@ -171,20 +166,14 @@ npm install -g docks-kit@latest
171
166
 
172
167
  Verified on Bun 1.4.2 and npm 11, each in a clean HOME.
173
168
 
174
- ## No-Bun recovery
175
-
176
- No Bun or constrained sandbox: download the platform release binary from GitHub
177
- Releases and run it directly. No checkout or `DOCKS_KIT_HOME` is required for
178
- sync/config reads.
179
-
180
169
  ## Prerequisites
181
170
 
182
- - Bun for source/global installs; release binaries embed the runtime
171
+ - Bun for every install: the checkout launchers and the npm package both run on Bun
183
172
  - npm for an npm-installed kit
184
173
  - jq is optional doctor/test tooling; sync has no jq runtime dependency
185
174
  - curl is needed only to download Bun's upstream installer when Bun is absent:
186
175
  by the POSIX `docks-kit` launcher, by the POSIX `install.sh`, and by sync's
187
- Bun bootstrap on every host, release binaries included
176
+ Bun bootstrap on every host
188
177
  (`docks-kit toolchain ensure bun` too). `docks-kit.ps1` and `install.ps1`
189
178
  download Bun's installer with Invoke-WebRequest. An already-present Bun needs
190
179
  no curl.
@@ -11,10 +11,10 @@ AI-assisted dev environment on every machine.
11
11
  |-------|------|
12
12
  | `SoT/.omp/` | omp config deployed to `~/.omp/agent/` (AGENTS.md, config.yml, models.yml, mcp.json) plus `intercom.json` for pi intercom, plus the `plugin/` tree, deployed to `~/.docks-kit/omp-plugin` and linked as the `docks-kit-omp` omp plugin |
13
13
  | `SoT/toolchain.json` | Verified-version floors for external tools (see `docks-kit docs toolchain`) |
14
- | `cli/src/generated/sotPayload.ts` | Deterministic generated payload embedded in standalone/npm execution |
14
+ | `cli/src/generated/sotPayload.ts` | Deterministic generated payload embedded in the npm bundle |
15
15
  | `cli/src/engine-native/` | EngineNative mutation logic for sync/toolchain and the `docks-kit omp` session overlay |
16
16
  | `cli/` | This CLI (Effect 4 on Bun) plus bundled docs |
17
- | `docks-kit` / `docks-kit.ps1` | POSIX and Windows launchers: version-matching compiled binary → Bun-from-source, with Bun auto-install |
17
+ | `docks-kit` / `docks-kit.ps1` | POSIX and Windows launchers: host check → Bun-from-source, with Bun auto-install |
18
18
 
19
19
  ## Design rules
20
20
 
@@ -24,7 +24,7 @@ AI-assisted dev environment on every machine.
24
24
  summary; `--verbose` / `-v` also prints the no-op confirmations.
25
25
  - **Additive by default**: user-only keys and plugins survive a plain sync.
26
26
  - **Engine/CLI split**: the CLI adds UX (typed flags, pickers, docs, JSON);
27
- EngineNative owns mutation. No-Bun recovery is a platform release binary.
27
+ EngineNative owns mutation. Every install runs on Bun.
28
28
  - **Authoring/runtime split**: changes begin in `SoT/`; build/prepack freshness
29
29
  checks keep the generated in-memory payload byte-identical for every runtime.
30
30
 
@@ -3,16 +3,16 @@
3
3
  The supported host matrix is exact: Linux on x64 and arm64, macOS on arm64,
4
4
  and Windows on x64.
5
5
 
6
- | Platform | Architecture | docks-kit binary | Sync engine |
7
- |----------|--------------|------------------|-------------|
8
- | Linux | x64 | `docks-kit-linux-x64` | EngineNative (TS) |
9
- | Linux | arm64 | `docks-kit-linux-arm64` | EngineNative (TS) |
10
- | macOS | arm64 | `docks-kit-darwin-arm64` | EngineNative (TS) |
11
- | Windows | x64 | `docks-kit-windows-x64.exe` | EngineNative (TS) |
6
+ | Platform | Architecture | Sync engine |
7
+ |----------|--------------|-------------|
8
+ | Linux | x64 | EngineNative (TS) |
9
+ | Linux | arm64 | EngineNative (TS) |
10
+ | macOS | arm64 | EngineNative (TS) |
11
+ | Windows | x64 | EngineNative (TS) |
12
12
 
13
13
  POSIX hosts use the `docks-kit` launcher. Windows uses `docks-kit.ps1`.
14
- Hosts outside this table fail before either launcher can fall back to Bun
15
- source. The POSIX launcher and `install.sh` read the architecture of the
14
+ Hosts outside this table fail before either launcher runs the Bun source.
15
+ The POSIX launcher and `install.sh` read the architecture of the
16
16
  shell with `uname -m`. On an Apple silicon Mac, a shell that runs under
17
17
  Rosetta reports `x86_64` and gets the unsupported-host message, so run
18
18
  docks-kit from a native arm64 shell.
@@ -3,9 +3,8 @@ import { Console, Effect } from "effect";
3
3
  import type { SpawnSyncOptions, SpawnSyncReturns } from "node:child_process";
4
4
  import { existsSync, readFileSync } from "node:fs";
5
5
  import { join } from "node:path";
6
- import { bail, compiled } from "../engine";
6
+ import { bail } from "../engine";
7
7
  import { kitHome } from "../kitHome";
8
- import { DEPENDENCIES, defaultProbeExecutor, resolvePath } from "../engine-native/deps";
9
8
  import { p, spawnHost } from "../engine-native/exec";
10
9
  import { hostOs, type HostOs } from "../engine-native/os";
11
10
 
@@ -204,32 +203,6 @@ export const packageUpdateResult = (
204
203
  return { alreadyCurrent: false, message: `Updated ${before} -> ${after}.` };
205
204
  };
206
205
 
207
- export type UpdateBunCommand =
208
- | { readonly ok: true; readonly command: string }
209
- | { readonly ok: false; readonly diagnostic: string };
210
-
211
- /**
212
- * The Bun that reinstalls checkout dependencies. The source path always runs
213
- * under Bun, and the launcher may have picked a Bun that is not on PATH, so it
214
- * reuses `execPath`. A compiled binary resolves Bun like the dependency probe:
215
- * PATH, then $BUN_INSTALL/bin, then ~/.bun/bin.
216
- */
217
- export const updateBunCommand = async (
218
- isCompiled: boolean,
219
- execPath: string,
220
- home: string,
221
- resolveBun: () => Promise<string> = () => resolvePath(DEPENDENCIES.bun, defaultProbeExecutor),
222
- ): Promise<UpdateBunCommand> => {
223
- if (!isCompiled) return { ok: true, command: execPath };
224
- const resolved = await resolveBun();
225
- return resolved === ""
226
- ? {
227
- ok: false,
228
- diagnostic: `dependencies changed but Bun was not found - run 'bun install --frozen-lockfile' in ${home}, then docks-kit sync`,
229
- }
230
- : { ok: true, command: resolved };
231
- };
232
-
233
206
  export const updateCheckout = (home: string, skipSync: boolean, spawn: UpdateSpawn = spawnHost) =>
234
207
  Effect.gen(function* () {
235
208
  if (spawn("git", ["--version"], { stdio: "ignore" }).status !== 0) {
@@ -269,9 +242,8 @@ export const updateCheckout = (home: string, skipSync: boolean, spawn: UpdateSpa
269
242
 
270
243
  const touched = git(spawn, home, ["diff", "--name-only", before, after]).out.split("\n");
271
244
  if (touched.includes("bun.lock") || touched.includes("package.json")) {
272
- const bun = yield* Effect.promise(() => updateBunCommand(compiled, process.execPath, home));
273
- if (!bun.ok) return yield* bail(bun.diagnostic, 1);
274
- const res = spawn(bun.command, ["install", "--frozen-lockfile"], {
245
+ // The launcher may run a Bun that is not on PATH, so reuse the running one.
246
+ const res = spawn(process.execPath, ["install", "--frozen-lockfile"], {
275
247
  cwd: home,
276
248
  stdio: "inherit",
277
249
  });
@@ -288,13 +260,6 @@ export const updateCheckout = (home: string, skipSync: boolean, spawn: UpdateSpa
288
260
  );
289
261
  }
290
262
 
291
- if (compiled) {
292
- return yield* Console.log(
293
- changed
294
- ? "This compiled binary still runs the previous version - the checkout launcher will use updated source next time. Run: ./docks-kit sync (rebuild with bash cli/build-binaries.sh to restore the binary fast path)."
295
- : "This compiled binary cannot chain the sync. Run: ./docks-kit sync",
296
- );
297
- }
298
263
  if (skipSync)
299
264
  return yield* Console.log(
300
265
  changed ? "Kit updated. Run: docks-kit sync" : "Run: docks-kit sync",
@@ -366,7 +331,7 @@ export const updateCommand = Command.make("update", { noSync }, (config) =>
366
331
  return yield* updatePackage(home, config.noSync);
367
332
  }
368
333
  return yield* bail(
369
- `kit home ${home} is neither a git checkout nor a global package install - update it the way it was installed (e.g. download the latest release binary)`,
334
+ `kit home ${home} is neither a git checkout nor a global package install - reinstall the kit as a git checkout or with 'bun add -g docks-kit'`,
370
335
  );
371
336
  }),
372
337
  ).pipe(
@@ -204,15 +204,16 @@ active logger binding.
204
204
  output, and the channel and migration invariants to
205
205
  `cli/test/goldens/mutation.json`.
206
206
  - `.github/workflows/parity.yml` runs its portable lane on `ubuntu-24.04` and
207
- `macos-26`: generated-payload check, typecheck, unit tests, a clean-room
208
- package install smoke, and compilation and execution of the native host
209
- artifact. On `windows-2025`, two unit-test shards and the
210
- `portable-windows-checks` job (generated-payload check, typecheck, native
211
- artifact) run in parallel. The check `portable (windows-2025)` passes only
212
- when all three pass. The Linux-canonical snapshot lane stays on Ubuntu and
213
- runs both golden suites plus their prove-red checks.
214
- - `.github/workflows/release-cli.yml` publishes four binaries (Linux x64 and
215
- arm64, macOS arm64, Windows x64), plus `SHA256SUMS` and the npm package.
207
+ `macos-26`: generated-payload check, typecheck, unit tests, and a clean-room
208
+ package install smoke. On `windows-2025`, two unit-test shards and the
209
+ `portable-windows-checks` job (generated-payload check, typecheck, and a
210
+ global install that runs the bundle) run in parallel. The check
211
+ `portable (windows-2025)` passes only when all three pass. The
212
+ Linux-canonical snapshot lane stays on Ubuntu and runs both golden suites
213
+ plus their prove-red checks.
214
+ - `.github/workflows/release-cli.yml` attaches the bundle's source map
215
+ `docks-kit.js.map` to the GitHub release and publishes the npm package with
216
+ provenance.
216
217
 
217
218
  ## Non-Goals
218
219
 
@@ -1,16 +1,9 @@
1
1
  /**
2
- * Host-to-artifact map (Platform seam in DESIGN.md). The two launchers select
3
- * a compiled binary from this table, `cli/build-binaries.sh` builds its
4
- * targets, and `release-cli.yml` publishes its artifacts. Each of these files
5
- * lists the names by hand, so `cli/test/unit/hostTargets.test.ts` checks them
6
- * against this table:
7
- * - the artifact names and `uname` keys in the Bash launcher `docks-kit`;
8
- * - the artifact name and processor architecture in `docks-kit.ps1`;
9
- * - the default `TARGETS` list of `cli/build-binaries.sh`;
10
- * - the four artifact names in each of the two lists of
11
- * `.github/workflows/release-cli.yml`: the `with.path` list of the
12
- * `actions/upload-artifact` step in job `build`, and the `for asset in`
13
- * list of the `gh release upload` step in job `github-release`.
2
+ * Host support map (Platform seam in DESIGN.md). Each of the two launchers
3
+ * checks the host by hand before it runs Bun from source, so
4
+ * `cli/test/unit/hostTargets.test.ts` checks them against this table:
5
+ * - the `uname` keys in the Bash launcher `docks-kit`;
6
+ * - the processor architecture in `docks-kit.ps1`.
14
7
  * The same test also checks two facts outside this table: the generated Bun
15
8
  * pin in the two launchers and the two installers equals the
16
9
  * `SoT/toolchain.json` pin, and `docks-kit.ps1` and `install.ps1` hold only
@@ -30,10 +23,6 @@ export interface HostTarget {
30
23
  readonly id: TargetId;
31
24
  readonly platform: PlatformName;
32
25
  readonly arch: TargetArch;
33
- /** `bun build --compile --target=` value. */
34
- readonly bunTarget: string;
35
- /** Compiled binary file name, including the Windows `.exe` suffix. */
36
- readonly artifact: string;
37
26
  /** `uname -s`-`uname -m` keys the Bash launcher matches; empty on Windows. */
38
27
  readonly unameKeys: ReadonlyArray<string>;
39
28
  /**
@@ -54,8 +43,6 @@ const target = (
54
43
  id,
55
44
  platform,
56
45
  arch,
57
- bunTarget: `bun-${id}`,
58
- artifact: platform === "windows" ? `docks-kit-${id}.exe` : `docks-kit-${id}`,
59
46
  unameKeys,
60
47
  processorArchitectures,
61
48
  });
@@ -71,7 +58,7 @@ function targetFor(platform: PlatformName, arch: string): HostTarget | undefined
71
58
  return HOST_TARGETS.find((t) => t.platform === platform && t.arch === arch);
72
59
  }
73
60
 
74
- /** Resolve the artifact for a raw Node platform/arch pair. */
61
+ /** Resolve the supported host target for a raw Node platform/arch pair. */
75
62
  export function targetForHost(platform: NodeJS.Platform, arch: string): HostTarget | undefined {
76
63
  return targetFor(platformName(platform), arch);
77
64
  }
package/cli/src/engine.ts CHANGED
@@ -21,12 +21,6 @@ const requireSupportedHost = () => {
21
21
  );
22
22
  };
23
23
 
24
- // In a compiled executable process.execPath IS the CLI, so a re-spawn must
25
- // not pass main.ts. Guarded because the unit suite imports this module under
26
- // Node, where the `Bun` global is absent; only a Bun-hosted standalone
27
- // executable can be compiled, so absence means false.
28
- export const compiled: boolean = typeof Bun !== "undefined" && Bun.isStandaloneExecutable === true;
29
-
30
24
  const failureMessage = (error: unknown): string => {
31
25
  if (error instanceof Error && error.message !== "") return error.message;
32
26
  return typeof error === "string" && error !== "" ? error : "unknown error";
@@ -1,10 +1,10 @@
1
1
  // Generated by cli/scripts/generate-sot-payload.ts. DO NOT EDIT.
2
2
  // Edit SoT/ or package.json, then run: bun cli/scripts/generate-sot-payload.ts
3
3
 
4
- export const GENERATED_PACKAGE_VERSION = "0.26.0"
4
+ export const GENERATED_PACKAGE_VERSION = "0.27.0"
5
5
 
6
6
  export const GENERATED_PAYLOAD_TEXT = {
7
- "SoT/toolchain.json": "{\n \"$comment\": \"Kit toolchain manifest - DATA only (versions, floors, policy); version probing and the doctor report live in cli/src/engine-native/toolchain.ts, and the one managed install lives in cli/src/engine-native/bun.ts bunBootstrap. kind: check (doctor visibility only) | managed (kit installs it when missing) | pin (no binary probe - a version pin for a package the kit installs through another tool, such as `omp install`; the required `via` names that tool in the doctor table). policy (managed only): present (install when missing, never upgrade). `verified` = last kit-tested version; `pinnable` marks a tool whose `verified` release the bootstrap can install by exact tag. Supply-chain stance: every kit-driven package install from npm, GitHub releases, or `omp install` is pinned to `verified` - never floating @latest (npm-worm/Shai-Hulud surface). The existing omp marketplace plugins follow their marketplace and have no pin. Any new install surface, a new marketplace or plugin source included, needs a pin first. Update `verified` after testing a new release. upstream (optional) names where `docks-kit toolchain outdated` reads the newest release: npm package or GitHub repo releases with a tag prefix; results cache 24 h in ~/.docks-kit/kit.db; the report never installs or edits pins.\",\n \"tools\": {\n \"jq\": { \"kind\": \"check\", \"note\": \"optional operator CLI; EngineNative JSON handling does not invoke it\" },\n \"curl\": { \"kind\": \"check\", \"note\": \"installer transport for the Bun bootstrap on every host (install.sh on POSIX, install.ps1 on Windows); probed only when Bun is missing\" },\n \"git\": { \"kind\": \"check\", \"note\": \"omp plugin marketplaces (omp clones them) + kit checkout updates\" },\n \"npm\": { \"kind\": \"check\", \"note\": \"npm-global installer; `docks-kit update` uses it for an npm-installed kit\" },\n \"omp\": { \"kind\": \"check\", \"floor\": \"19.0.0\", \"verified\": \"19.0.0\",\n \"upstream\": { \"github\": \"can1357/oh-my-pi\", \"tagPrefix\": \"v\" },\n \"note\": \"Oh My Pi harness (https://github.com/can1357/oh-my-pi); upstream-owned. It updates through `omp update` or through the external manager that owns the install (for example Tern), and sync never installs or upgrades it. The floor is the oldest release the kit tested: 19.0.0 lists every model selector of the kit roles exactly, accepts every key of SoT/.omp/config.yml, and runs the bash approval order that cli/test/lib/ompBashPatterns.ts ports. Sync needs the CLI only for the marketplace and plugin passes; the file deploys proceed without it\" },\n \"bun\": { \"kind\": \"managed\", \"policy\": \"present\", \"floor\": \"1.4.4\", \"verified\": \"1.4.4\", \"pinnable\": true,\n \"upstream\": { \"github\": \"oven-sh/bun\", \"tagPrefix\": \"bun-v\" },\n \"note\": \"runtime for the docks-kit CLI; bootstrap installs the verified release (installer takes bun-vX.Y.Z); self-updates via `bun upgrade` when wanted. By owner decision (2026-09-25), the floor equals the verified pin and the CI Bun, and the checkout launchers refuse an older Bun. All three moved to 1.4.4 on 2026-10-22 for `bun check`\" },\n \"pi-intercom\": { \"kind\": \"pin\", \"via\": \"omp install\", \"verified\": \"0.14.0\",\n \"upstream\": { \"npm\": \"pi-intercom\" },\n \"note\": \"the cross-session messaging plugin ompSync installs with `omp install pi-intercom@<verified>` - pinned, never floating. Its broker runs under Bun because omp's flat plugin store cannot resolve the default `npx --no-install tsx` launcher\" }\n }\n}\n",
7
+ "SoT/toolchain.json": "{\n \"$comment\": \"Kit toolchain manifest - DATA only (versions, floors, policy); version probing and the doctor report live in cli/src/engine-native/toolchain.ts, and the one managed install lives in cli/src/engine-native/bun.ts bunBootstrap. kind: check (doctor visibility only) | managed (kit installs it when missing) | pin (no binary probe - a version pin for a package the kit installs through another tool, such as `omp install`; the required `via` names that tool in the doctor table). policy (managed only): present (install when missing, never upgrade). `verified` = last kit-tested version; `pinnable` marks a tool whose `verified` release the bootstrap can install by exact tag. Supply-chain stance: every kit-driven package install from npm, GitHub releases, or `omp install` is pinned to `verified` - never floating @latest (npm-worm/Shai-Hulud surface). The existing omp marketplace plugins follow their marketplace and have no pin. Any new install surface, a new marketplace or plugin source included, needs a pin first. Update `verified` after testing a new release. upstream (optional) names where `docks-kit toolchain outdated` reads the newest release: npm package or GitHub repo releases with a tag prefix; results cache 24 h in ~/.docks-kit/kit.db; the report never installs or edits pins.\",\n \"tools\": {\n \"jq\": { \"kind\": \"check\", \"note\": \"optional operator CLI; EngineNative JSON handling does not invoke it\" },\n \"curl\": { \"kind\": \"check\", \"note\": \"installer transport for the Bun bootstrap on every host (install.sh on POSIX, install.ps1 on Windows); probed only when Bun is missing\" },\n \"git\": { \"kind\": \"check\", \"note\": \"omp plugin marketplaces (omp clones them) + kit checkout updates\" },\n \"npm\": { \"kind\": \"check\", \"note\": \"npm-global installer; `docks-kit update` uses it for an npm-installed kit\" },\n \"omp\": { \"kind\": \"check\", \"floor\": \"19.0.0\", \"verified\": \"19.0.0\",\n \"upstream\": { \"github\": \"can1357/oh-my-pi\", \"tagPrefix\": \"v\" },\n \"note\": \"Oh My Pi harness (https://github.com/can1357/oh-my-pi); upstream-owned. It updates through `omp update` or through the external manager that owns the install (for example Tern), and sync never installs or upgrades it. The floor is the oldest release the kit tested: 19.0.0 lists every model selector of the kit roles exactly, accepts every key of SoT/.omp/config.yml, and runs the bash approval order that cli/test/lib/ompBashPatterns.ts ports. Sync needs the CLI only for the marketplace and plugin passes; the file deploys proceed without it\" },\n \"bun\": { \"kind\": \"managed\", \"policy\": \"present\", \"floor\": \"1.4.5\", \"verified\": \"1.4.5\", \"pinnable\": true,\n \"upstream\": { \"github\": \"oven-sh/bun\", \"tagPrefix\": \"bun-v\" },\n \"note\": \"runtime for the docks-kit CLI; bootstrap installs the verified release (installer takes bun-vX.Y.Z); self-updates via `bun upgrade` when wanted. By owner decision (2026-09-25), the floor equals the verified pin and the CI Bun, and the checkout launchers refuse an older Bun. All three moved to 1.4.5 on 2026-11-21 for its TLS, DNS, and HTTP security fixes\" },\n \"pi-intercom\": { \"kind\": \"pin\", \"via\": \"omp install\", \"verified\": \"0.14.0\",\n \"upstream\": { \"npm\": \"pi-intercom\" },\n \"note\": \"the cross-session messaging plugin ompSync installs with `omp install pi-intercom@<verified>` - pinned, never floating. Its broker runs under Bun because omp's flat plugin store cannot resolve the default `npx --no-install tsx` launcher\" }\n }\n}\n",
8
8
  "SoT/.omp/AGENTS.md": "# Global OMP guidance\n\n- Verify an unfamiliar or version-sensitive API or configuration against current official documentation before you use it.\n- When I ask for an assessment, report the findings and do not edit.\n- Docks plan reviews have standing cross-company authorization. Host security policy still applies.\n- Please remove all mannered prose.\n- `rewind` restores the conversation only. It does not restore files, git state, artifacts, or processes.\n\n## Asking me things\n\nAsk me only through `ask`, never in prose. Use `ask` before these steps:\n\n- An irreversible or outward action: delete or overwrite data that you did not create, force-push, rewrite history, drop tables, run migrations, rename in bulk, touch secrets, or publish a release, upstream PR, issue, or comment.\n- A choice between viable approaches whose tradeoffs I own: a schema, API, or protocol shape, a new dependency, or a new convention.\n- A fact that only I hold, or a request that contradicts the repository. Show the conflict.\n- A feature that the current structure cannot hold without a refactor. Propose the refactor before you write the feature.\n- A repository hook that fails on a problem that your change did not cause. Do not skip the hook.\n- A stop, removal, undeploy, or delete of a production resource, immediately before it. Keep such cleanups rare. A remote target is production unless it is named local, development, dev, test, homolog, homologation, staging, or preview.\n\nA settled plan Mode covers the routine plan-lifecycle writes in the resolved repository: the plan issue, plan edits, review comments, and each other issue or comment that the plan-lifecycle contract requires. A `plan-and-implement` Mode also covers the landing work: the push of the linked branch and the pull request. Every other issue, comment, release, or upstream pull request still needs an ask.\n\nA `yolo` invocation answers the routine asks of its plan run until its merge question, or until the grant check of the plan-lifecycle contract finds that its grant has ended. It does not cover destructive work, secrets, production systems, or a repository hook that fails; for a failed hook, follow the hook rule of the plan-lifecycle contract.\n\nA plan grant answers the asks that the Delegated decisions section of the plan-lifecycle contract lists as answered. Only trusted `Delegation grant:` and `Delegation revoked` comments give or end a grant. On the plan issue, the latest such comment decides, and a comment on a parent plan can end the grant of its child. The `Delegated:` line of the plan only mirrors that comment.\n\nA grant never answers a question that the contract keeps for me. Examples are the Mode, a non-local effect, the merge, a destructive action, secrets, production, a temporary workaround, and a fact that only I hold. Right before each delegated decision and each write that relies on the grant, run the grant check of the contract: read the latest authority comments of the plan and of its parent.\n\nWhen `ask` is not available, take the conservative reversible option. Put the question and your assumption in the final report.\n\n## Cleanup\n\nBefore your final answer, remove each resource that you created and that the task no longer needs. Follow the `workspace-hygiene` skill. Name each resource that you keep.\n\n## Output\n\n- Write Simplified Technical English in responses, documentation, comments, and interface text. Reply in my language.\n- Use the simplest precise term, and use it consistently. Expand an abbreviation at its first use. Explain a term when I ask.\n- Write complete sentences in active voice and simple tenses. In instructions, use the imperative, one action per sentence, and the condition first.\n- Do not use contractions, idioms, slang, humor, or rhetorical questions. Do not put more than three nouns together.\n- Keep procedural sentences to 20 words, descriptive sentences to 25 words, and paragraphs to one topic and six sentences.\n- Use vertical lists for complex information. Put a warning before its hazardous instruction.\n- Describe a thing in plain words before you name it. Give the term once, in parentheses. Prefer the short common word. Do not explain by metaphor alone.\n- Apply these rules in the language of the reply. The contraction ban applies only to English; elsewhere, follow the grammar of that language, and treat the word limits as approximate. For example, Portuguese \"do\" (de + o) and \"na\" (em + a) are required.\n",
9
9
  "SoT/.omp/config.yml": "cycleOrder:\n - smol\n - default\n - slow\n - fable\n - astra\n\nastGrep:\n enabled: true\n\ncheckpoint:\n enabled: true\n\ntask:\n agentModelOverrides:\n reviewer: \"@reviewer\"\n security-reviewer: \"@reviewer\"\n code-reviewer: \"@reviewer\"\n plan-reviewer: \"@reviewer\"\n agentServiceTierOverrides:\n reviewer: inherit\n security-reviewer: inherit\n code-reviewer: inherit\n plan-reviewer: inherit\n\nmodelRoles:\n smol: openai-codex/gpt-6-luna:medium\n designer: anthropic/claude-opus-5-5:high\n plan: anthropic/claude-opus-5-5:xhigh\n commit: openai-codex/gpt-6-luna:medium\n task: anthropic/claude-opus-5-5:high\n vision: anthropic/claude-opus-5-5:medium\n tiny: openai-codex/gpt-6-luna:low\n default: anthropic/claude-opus-5-5:high\n slow: anthropic/claude-opus-5-5:xhigh\n fable: anthropic/claude-fable-5-2:medium\n switch_fable: anthropic/claude-fable-5-2:medium\n astra: openai-codex/gpt-6.2-astra:xhigh\n reviewer: openai-codex/gpt-6.1-terra:high\n web: web/firecrawl\n\nmodelTags:\n fable:\n name: Fable 5.2\n switch_fable:\n name: Fable switch default\n hidden: true\n astra:\n name: GPT-6.2 Astra\n reviewer:\n name: Reviewer\n hidden: true\n\ndisplay:\n showTokenUsage: true\n\nretry:\n fallbackChains:\n default:\n - openai-codex/gpt-6.2-sol:high\n task:\n - openai-codex/gpt-6.2-sol:high\n vision:\n - openai-codex/gpt-6.2-sol:medium\n smol:\n - anthropic/claude-opus-5-5:low\n tiny:\n - anthropic/claude-opus-5-5:low\n commit:\n - anthropic/claude-opus-5-5:medium\n switch_fable: []\n fable:\n - openai-codex/gpt-6.2-astra:xhigh\n astra:\n - anthropic/claude-fable-5-2:medium\n reviewer:\n - anthropic/claude-opus-5-5:high\n web:\n - web/exa\n - web/perplexity\n - openai-codex/gpt-6-luna\n - web/parallel\n - web/zai\n - web/tinyfish\n - web/jina\n - web/kagi\n - web/tavily\n - web/brave\n - web/kimi\n - web/synthetic\n - web/ollama\n - web/searxng\n - web/startpage\n - web/duckduckgo\n - web/ecosia\n - web/google\n - web/mojeek\n - web/public\n\nbranchSummary:\n enabled: true\n\ndev:\n autoqa: false\n autoqaConsent: denied\n\ncodexResets:\n autoRedeem5h: \"no\"\n autoRedeemWeekly: \"no\"\n\nstartup:\n quiet: true\n\nbash:\n # First match wins. omp checks deny rules against the whole line and each\n # quote-stripped segment, so `rm -rf \"$HOME\"` matches `rm * $HOME`. `*`\n # matches any text, spaces and slashes included; no escape spells a literal\n # `*`.\n # The kit ships no prompt rule, because a subagent rejects every prompt.\n # A command that no deny rule matches runs under yolo, unless a prompt rule\n # that the user added matches it: a plain rm, git rm, git worktree remove,\n # gio trash, docks-kit scratch remove, git clean, git reset --hard, and\n # every git push that the denies below do not stop.\n # omp checks deny, then prompt, then its critical-command patterns, then\n # allow. A critical command that no deny or prompt rule matches runs under\n # yolo, so every rm shape that the critical check can flag is a deny.\n patterns:\n # Deny: rm of the home directory or the filesystem root, sudo before rm,\n # rm with an r or f option before an absolute path, recursive rm (bare, by\n # path, or after any word such as env, xargs, find -exec, or git), bulk\n # removal through find -delete, find -exec rm, and xargs rm, HOME\n # reassignment, a force push to main or master, and a $ or a backtick\n # after git push.\n - { match: \"rm /\", approval: deny }\n - { match: \"rm / *\", approval: deny }\n - { match: \"rm * /\", approval: deny }\n - { match: \"rm * / *\", approval: deny }\n - { match: \"rm ~\", approval: deny }\n - { match: \"rm ~ *\", approval: deny }\n - { match: \"rm * ~\", approval: deny }\n - { match: \"rm * ~ *\", approval: deny }\n - { match: \"rm ~/\", approval: deny }\n - { match: \"rm ~/ *\", approval: deny }\n - { match: \"rm * ~/\", approval: deny }\n - { match: \"rm * ~/ *\", approval: deny }\n - { match: \"rm $HOME\", approval: deny }\n - { match: \"rm $HOME *\", approval: deny }\n - { match: \"rm * $HOME\", approval: deny }\n - { match: \"rm * $HOME *\", approval: deny }\n - { match: \"rm $HOME/\", approval: deny }\n - { match: \"rm $HOME/ *\", approval: deny }\n - { match: \"rm * $HOME/\", approval: deny }\n - { match: \"rm * $HOME/ *\", approval: deny }\n - { match: \"rm ${HOME}\", approval: deny }\n - { match: \"rm ${HOME} *\", approval: deny }\n - { match: \"rm * ${HOME}\", approval: deny }\n - { match: \"rm * ${HOME} *\", approval: deny }\n - { match: \"rm ${HOME}/\", approval: deny }\n - { match: \"rm ${HOME}/ *\", approval: deny }\n - { match: \"rm * ${HOME}/\", approval: deny }\n - { match: \"rm * ${HOME}/ *\", approval: deny }\n - { match: \"* rm /\", approval: deny }\n - { match: \"* rm / *\", approval: deny }\n - { match: \"* rm * /\", approval: deny }\n - { match: \"* rm * / *\", approval: deny }\n - { match: \"* rm ~\", approval: deny }\n - { match: \"* rm ~ *\", approval: deny }\n - { match: \"* rm * ~\", approval: deny }\n - { match: \"* rm * ~ *\", approval: deny }\n - { match: \"* rm ~/\", approval: deny }\n - { match: \"* rm ~/ *\", approval: deny }\n - { match: \"* rm * ~/\", approval: deny }\n - { match: \"* rm * ~/ *\", approval: deny }\n - { match: \"* rm $HOME\", approval: deny }\n - { match: \"* rm $HOME *\", approval: deny }\n - { match: \"* rm * $HOME\", approval: deny }\n - { match: \"* rm * $HOME *\", approval: deny }\n - { match: \"* rm $HOME/\", approval: deny }\n - { match: \"* rm $HOME/ *\", approval: deny }\n - { match: \"* rm * $HOME/\", approval: deny }\n - { match: \"* rm * $HOME/ *\", approval: deny }\n - { match: \"* rm ${HOME}\", approval: deny }\n - { match: \"* rm ${HOME} *\", approval: deny }\n - { match: \"* rm * ${HOME}\", approval: deny }\n - { match: \"* rm * ${HOME} *\", approval: deny }\n - { match: \"* rm ${HOME}/\", approval: deny }\n - { match: \"* rm ${HOME}/ *\", approval: deny }\n - { match: \"* rm * ${HOME}/\", approval: deny }\n - { match: \"* rm * ${HOME}/ *\", approval: deny }\n - { match: \"*/rm /\", approval: deny }\n - { match: \"*/rm / *\", approval: deny }\n - { match: \"*/rm * /\", approval: deny }\n - { match: \"*/rm * / *\", approval: deny }\n - { match: \"*/rm ~\", approval: deny }\n - { match: \"*/rm ~ *\", approval: deny }\n - { match: \"*/rm * ~\", approval: deny }\n - { match: \"*/rm * ~ *\", approval: deny }\n - { match: \"*/rm ~/\", approval: deny }\n - { match: \"*/rm ~/ *\", approval: deny }\n - { match: \"*/rm * ~/\", approval: deny }\n - { match: \"*/rm * ~/ *\", approval: deny }\n - { match: \"*/rm $HOME\", approval: deny }\n - { match: \"*/rm $HOME *\", approval: deny }\n - { match: \"*/rm * $HOME\", approval: deny }\n - { match: \"*/rm * $HOME *\", approval: deny }\n - { match: \"*/rm $HOME/\", approval: deny }\n - { match: \"*/rm $HOME/ *\", approval: deny }\n - { match: \"*/rm * $HOME/\", approval: deny }\n - { match: \"*/rm * $HOME/ *\", approval: deny }\n - { match: \"*/rm ${HOME}\", approval: deny }\n - { match: \"*/rm ${HOME} *\", approval: deny }\n - { match: \"*/rm * ${HOME}\", approval: deny }\n - { match: \"*/rm * ${HOME} *\", approval: deny }\n - { match: \"*/rm ${HOME}/\", approval: deny }\n - { match: \"*/rm ${HOME}/ *\", approval: deny }\n - { match: \"*/rm * ${HOME}/\", approval: deny }\n - { match: \"*/rm * ${HOME}/ *\", approval: deny }\n - { match: \"sudo rm\", approval: deny }\n - { match: \"sudo rm *\", approval: deny }\n - { match: \"sudo * rm\", approval: deny }\n - { match: \"sudo * rm *\", approval: deny }\n - { match: \"sudo */rm\", approval: deny }\n - { match: \"sudo */rm *\", approval: deny }\n - { match: \"* sudo rm\", approval: deny }\n - { match: \"* sudo rm *\", approval: deny }\n - { match: \"* sudo * rm\", approval: deny }\n - { match: \"* sudo * rm *\", approval: deny }\n - { match: \"* sudo */rm\", approval: deny }\n - { match: \"* sudo */rm *\", approval: deny }\n - { match: \"*/sudo rm\", approval: deny }\n - { match: \"*/sudo rm *\", approval: deny }\n - { match: \"*/sudo * rm\", approval: deny }\n - { match: \"*/sudo * rm *\", approval: deny }\n - { match: \"*/sudo */rm\", approval: deny }\n - { match: \"*/sudo */rm *\", approval: deny }\n - { match: \"rm *-*r* /*\", approval: deny }\n - { match: \"rm *-*R* /*\", approval: deny }\n - { match: \"rm *-*f* /*\", approval: deny }\n - { match: \"rm *-*F* /*\", approval: deny }\n - { match: \"rm *--no-preserve-root*\", approval: deny }\n - { match: \"* rm *-*r* /*\", approval: deny }\n - { match: \"* rm *-*R* /*\", approval: deny }\n - { match: \"* rm *-*f* /*\", approval: deny }\n - { match: \"* rm *-*F* /*\", approval: deny }\n - { match: \"* rm *--no-preserve-root*\", approval: deny }\n - { match: \"*/rm *-*r* /*\", approval: deny }\n - { match: \"*/rm *-*R* /*\", approval: deny }\n - { match: \"*/rm *-*f* /*\", approval: deny }\n - { match: \"*/rm *-*F* /*\", approval: deny }\n - { match: \"*/rm *--no-preserve-root*\", approval: deny }\n - { match: \"rm *-r *\", approval: deny }\n - { match: \"rm *-r\", approval: deny }\n - { match: \"rm *-rf *\", approval: deny }\n - { match: \"rm *-rf\", approval: deny }\n - { match: \"rm *-fr *\", approval: deny }\n - { match: \"rm *-fr\", approval: deny }\n - { match: \"rm *-rv *\", approval: deny }\n - { match: \"rm *-rv\", approval: deny }\n - { match: \"rm *-vr *\", approval: deny }\n - { match: \"rm *-vr\", approval: deny }\n - { match: \"rm *-rfv *\", approval: deny }\n - { match: \"rm *-rfv\", approval: deny }\n - { match: \"rm *-rvf *\", approval: deny }\n - { match: \"rm *-rvf\", approval: deny }\n - { match: \"rm *-frv *\", approval: deny }\n - { match: \"rm *-frv\", approval: deny }\n - { match: \"rm *-fvr *\", approval: deny }\n - { match: \"rm *-fvr\", approval: deny }\n - { match: \"rm *-vrf *\", approval: deny }\n - { match: \"rm *-vrf\", approval: deny }\n - { match: \"rm *-vfr *\", approval: deny }\n - { match: \"rm *-vfr\", approval: deny }\n - { match: \"rm *-ri *\", approval: deny }\n - { match: \"rm *-ri\", approval: deny }\n - { match: \"rm *-ir *\", approval: deny }\n - { match: \"rm *-ir\", approval: deny }\n - { match: \"rm *-Ri *\", approval: deny }\n - { match: \"rm *-Ri\", approval: deny }\n - { match: \"rm *-iR *\", approval: deny }\n - { match: \"rm *-iR\", approval: deny }\n - { match: \"rm *-R *\", approval: deny }\n - { match: \"rm *-R\", approval: deny }\n - { match: \"rm *-Rf *\", approval: deny }\n - { match: \"rm *-Rf\", approval: deny }\n - { match: \"rm *-fR *\", approval: deny }\n - { match: \"rm *-fR\", approval: deny }\n - { match: \"rm *-Rv *\", approval: deny }\n - { match: \"rm *-Rv\", approval: deny }\n - { match: \"rm *-vR *\", approval: deny }\n - { match: \"rm *-vR\", approval: deny }\n - { match: \"rm *-Rfv *\", approval: deny }\n - { match: \"rm *-Rfv\", approval: deny }\n - { match: \"rm *-Rvf *\", approval: deny }\n - { match: \"rm *-Rvf\", approval: deny }\n - { match: \"rm *-fRv *\", approval: deny }\n - { match: \"rm *-fRv\", approval: deny }\n - { match: \"rm *-fvR *\", approval: deny }\n - { match: \"rm *-fvR\", approval: deny }\n - { match: \"rm *-vRf *\", approval: deny }\n - { match: \"rm *-vRf\", approval: deny }\n - { match: \"rm *-vfR *\", approval: deny }\n - { match: \"rm *-vfR\", approval: deny }\n - { match: \"rm *--recursive *\", approval: deny }\n - { match: \"rm *--recursive\", approval: deny }\n - { match: \"*/rm *-r *\", approval: deny }\n - { match: \"*/rm *-r\", approval: deny }\n - { match: \"*/rm *-rf *\", approval: deny }\n - { match: \"*/rm *-rf\", approval: deny }\n - { match: \"*/rm *-fr *\", approval: deny }\n - { match: \"*/rm *-fr\", approval: deny }\n - { match: \"*/rm *-rv *\", approval: deny }\n - { match: \"*/rm *-rv\", approval: deny }\n - { match: \"*/rm *-vr *\", approval: deny }\n - { match: \"*/rm *-vr\", approval: deny }\n - { match: \"*/rm *-rfv *\", approval: deny }\n - { match: \"*/rm *-rfv\", approval: deny }\n - { match: \"*/rm *-rvf *\", approval: deny }\n - { match: \"*/rm *-rvf\", approval: deny }\n - { match: \"*/rm *-frv *\", approval: deny }\n - { match: \"*/rm *-frv\", approval: deny }\n - { match: \"*/rm *-fvr *\", approval: deny }\n - { match: \"*/rm *-fvr\", approval: deny }\n - { match: \"*/rm *-vrf *\", approval: deny }\n - { match: \"*/rm *-vrf\", approval: deny }\n - { match: \"*/rm *-vfr *\", approval: deny }\n - { match: \"*/rm *-vfr\", approval: deny }\n - { match: \"*/rm *-ri *\", approval: deny }\n - { match: \"*/rm *-ri\", approval: deny }\n - { match: \"*/rm *-ir *\", approval: deny }\n - { match: \"*/rm *-ir\", approval: deny }\n - { match: \"*/rm *-Ri *\", approval: deny }\n - { match: \"*/rm *-Ri\", approval: deny }\n - { match: \"*/rm *-iR *\", approval: deny }\n - { match: \"*/rm *-iR\", approval: deny }\n - { match: \"*/rm *-R *\", approval: deny }\n - { match: \"*/rm *-R\", approval: deny }\n - { match: \"*/rm *-Rf *\", approval: deny }\n - { match: \"*/rm *-Rf\", approval: deny }\n - { match: \"*/rm *-fR *\", approval: deny }\n - { match: \"*/rm *-fR\", approval: deny }\n - { match: \"*/rm *-Rv *\", approval: deny }\n - { match: \"*/rm *-Rv\", approval: deny }\n - { match: \"*/rm *-vR *\", approval: deny }\n - { match: \"*/rm *-vR\", approval: deny }\n - { match: \"*/rm *-Rfv *\", approval: deny }\n - { match: \"*/rm *-Rfv\", approval: deny }\n - { match: \"*/rm *-Rvf *\", approval: deny }\n - { match: \"*/rm *-Rvf\", approval: deny }\n - { match: \"*/rm *-fRv *\", approval: deny }\n - { match: \"*/rm *-fRv\", approval: deny }\n - { match: \"*/rm *-fvR *\", approval: deny }\n - { match: \"*/rm *-fvR\", approval: deny }\n - { match: \"*/rm *-vRf *\", approval: deny }\n - { match: \"*/rm *-vRf\", approval: deny }\n - { match: \"*/rm *-vfR *\", approval: deny }\n - { match: \"*/rm *-vfR\", approval: deny }\n - { match: \"*/rm *--recursive *\", approval: deny }\n - { match: \"*/rm *--recursive\", approval: deny }\n - { match: \"* rm *-r *\", approval: deny }\n - { match: \"* rm *-r\", approval: deny }\n - { match: \"* rm *-rf *\", approval: deny }\n - { match: \"* rm *-rf\", approval: deny }\n - { match: \"* rm *-fr *\", approval: deny }\n - { match: \"* rm *-fr\", approval: deny }\n - { match: \"* rm *-rv *\", approval: deny }\n - { match: \"* rm *-rv\", approval: deny }\n - { match: \"* rm *-vr *\", approval: deny }\n - { match: \"* rm *-vr\", approval: deny }\n - { match: \"* rm *-rfv *\", approval: deny }\n - { match: \"* rm *-rfv\", approval: deny }\n - { match: \"* rm *-rvf *\", approval: deny }\n - { match: \"* rm *-rvf\", approval: deny }\n - { match: \"* rm *-frv *\", approval: deny }\n - { match: \"* rm *-frv\", approval: deny }\n - { match: \"* rm *-fvr *\", approval: deny }\n - { match: \"* rm *-fvr\", approval: deny }\n - { match: \"* rm *-vrf *\", approval: deny }\n - { match: \"* rm *-vrf\", approval: deny }\n - { match: \"* rm *-vfr *\", approval: deny }\n - { match: \"* rm *-vfr\", approval: deny }\n - { match: \"* rm *-R *\", approval: deny }\n - { match: \"* rm *-R\", approval: deny }\n - { match: \"* rm *-ri *\", approval: deny }\n - { match: \"* rm *-ri\", approval: deny }\n - { match: \"* rm *-ir *\", approval: deny }\n - { match: \"* rm *-ir\", approval: deny }\n - { match: \"* rm *-Ri *\", approval: deny }\n - { match: \"* rm *-Ri\", approval: deny }\n - { match: \"* rm *-iR *\", approval: deny }\n - { match: \"* rm *-iR\", approval: deny }\n - { match: \"* rm *-Rf *\", approval: deny }\n - { match: \"* rm *-Rf\", approval: deny }\n - { match: \"* rm *-fR *\", approval: deny }\n - { match: \"* rm *-fR\", approval: deny }\n - { match: \"* rm *-Rv *\", approval: deny }\n - { match: \"* rm *-Rv\", approval: deny }\n - { match: \"* rm *-vR *\", approval: deny }\n - { match: \"* rm *-vR\", approval: deny }\n - { match: \"* rm *-Rfv *\", approval: deny }\n - { match: \"* rm *-Rfv\", approval: deny }\n - { match: \"* rm *-Rvf *\", approval: deny }\n - { match: \"* rm *-Rvf\", approval: deny }\n - { match: \"* rm *-fRv *\", approval: deny }\n - { match: \"* rm *-fRv\", approval: deny }\n - { match: \"* rm *-fvR *\", approval: deny }\n - { match: \"* rm *-fvR\", approval: deny }\n - { match: \"* rm *-vRf *\", approval: deny }\n - { match: \"* rm *-vRf\", approval: deny }\n - { match: \"* rm *-vfR *\", approval: deny }\n - { match: \"* rm *-vfR\", approval: deny }\n - { match: \"* rm *--recursive *\", approval: deny }\n - { match: \"* rm *--recursive\", approval: deny }\n # Bulk removal: find -delete, find -exec rm, and xargs rm, in every position.\n - { match: \"find *-delete*\", approval: deny }\n - { match: \"*/find *-delete*\", approval: deny }\n - { match: \"* find *-delete*\", approval: deny }\n - { match: \"*-exec rm *\", approval: deny }\n - { match: \"*-exec */rm *\", approval: deny }\n - { match: \"*-execdir rm *\", approval: deny }\n - { match: \"*-execdir */rm *\", approval: deny }\n - { match: \"*-ok rm *\", approval: deny }\n - { match: \"*-ok */rm *\", approval: deny }\n - { match: \"*-okdir rm *\", approval: deny }\n - { match: \"*-okdir */rm *\", approval: deny }\n - { match: \"*xargs rm\", approval: deny }\n - { match: \"*xargs rm *\", approval: deny }\n - { match: \"*xargs * rm\", approval: deny }\n - { match: \"*xargs * rm *\", approval: deny }\n - { match: \"*xargs */rm\", approval: deny }\n - { match: \"*xargs */rm *\", approval: deny }\n - { match: \"HOME=*\", approval: deny }\n - { match: \"export HOME=*\", approval: deny }\n - { match: \"env HOME=*\", approval: deny }\n - { match: \"env * HOME=*\", approval: deny }\n - { match: \"git push --force origin main\", approval: deny }\n - { match: \"git push --force origin main *\", approval: deny }\n - { match: \"git push --force origin master\", approval: deny }\n - { match: \"git push --force origin master *\", approval: deny }\n - { match: \"git push -f origin main\", approval: deny }\n - { match: \"git push -f origin main *\", approval: deny }\n - { match: \"git push -f origin master\", approval: deny }\n - { match: \"git push -f origin master *\", approval: deny }\n # A $ or a backtick anywhere after git push: the matcher reads the text\n # before the shell expands it, so it cannot tell a branch name from +main\n # or --force. An unquoted value inside a word also splits into more words.\n # A deny, not a prompt: the agent reads the refusal and writes the ref\n # literally (git push -u origin HEAD). No person is asked.\n # The leading * also reaches a git push after a shell keyword such as do,\n # after a wrapper such as env, and after a path such as /usr/bin/git.\n - { match: \"*git push *$*\", approval: deny }\n - { match: \"*git push *`*\", approval: deny }\n # Allow: the macOS trash command.\n - { match: \"trash *\", approval: allow }\n",
10
10
  "SoT/.omp/intercom.json": "{\n \"brokerCommand\": \"bun\",\n \"brokerArgs\": []\n}\n",
@@ -339,4 +339,4 @@ export const GENERATED_PAYLOAD_PATHS = [
339
339
  "SoT/.omp/plugin/skills/zoom-out/SKILL.md"
340
340
  ] as const
341
341
 
342
- export const GENERATED_PAYLOAD_HASH = "33882cc46d363b278af525aa25cab9c4690c4f93e91dbce1a36ae287a34ee6b3"
342
+ export const GENERATED_PAYLOAD_HASH = "6de4a159d773ccfe547ef7724b8d91ea3603c3e8560016cb0b2276966001f464"
@@ -75,22 +75,19 @@ export interface KitHomeSources {
75
75
  }
76
76
 
77
77
  /**
78
- * Resolve DOCKS_KIT_HOME, then the nearest kit ancestor of the module,
79
- * executable, or working directory, then the executable directory. Running
80
- * installation sources take priority so an unrelated checkout cannot replace
81
- * the installation that is executing.
78
+ * Resolve DOCKS_KIT_HOME, then the nearest kit ancestor of the module, then
79
+ * the nearest kit ancestor of the working directory, then the executable
80
+ * directory. The module comes first so an unrelated checkout cannot replace
81
+ * the installation that is executing. The executable directory is the last
82
+ * resort: under Bun it holds no kit, so `update` stops with the error that the
83
+ * home is neither a git checkout nor a global package install.
82
84
  */
83
85
  export const resolveKitHome = (sources: KitHomeSources): string => {
84
86
  if (sources.env !== undefined && sources.env !== "") {
85
87
  return explicitKitHome(resolve(sources.env), sources.env);
86
88
  }
87
89
 
88
- return (
89
- findKitHome(sources.moduleDir) ??
90
- findKitHome(dirname(sources.execPath)) ??
91
- findKitHome(sources.cwd) ??
92
- dirname(sources.execPath)
93
- );
90
+ return findKitHome(sources.moduleDir) ?? findKitHome(sources.cwd) ?? dirname(sources.execPath);
94
91
  };
95
92
 
96
93
  export const kitHome = (): string =>
package/cli/src/main.ts CHANGED
@@ -39,7 +39,6 @@ const root = Command.make("docks-kit", {}, () =>
39
39
  yield* Console.log(
40
40
  "Run 'docks-kit --help' for full option listings (also: --wizard, --completions).",
41
41
  );
42
- yield* Console.log("No-Bun recovery path: use a platform release binary.");
43
42
  }),
44
43
  ).pipe(
45
44
  Command.withDescription(