get-tbd 0.2.1 → 0.2.2

package/dist/docs/guidelines/bun-monorepo-patterns.md

@@ -24,19 +24,19 @@ author: Joshua Levy (github.com/jlevy) with LLM assistance
 
 | Tool / Package | Version | Check For Updates |
 | --- | --- | --- |
-| **Bun** | 1.3.13 (1.3.14 too recent) | [bun.sh/blog](https://bun.sh/blog) — Runtime, bundler, package manager, test runner. Acquired by Anthropic (Dec 2025). **Pinned to 1.3.13 (2026-04-20) per the 14-day rule** — 1.3.14 (2026-05-13) is the **last Zig-based release** and the Rust rewrite merged to `main` 2026-05-14 (~960K lines, generated by Claude AI agents over ~6 days). New built-ins in 1.3.x: `Bun.Image` (Sharp replacement), experimental HTTP/3 in `Bun.serve()`, 7× faster warm installs via isolated linker global store, rewritten `fs.watch()` on Linux/macOS. Bump to 1.3.14 (or 1.4.x once it ships) once the 14-day window has elapsed. |
-| **TypeScript** | ^6.0.3 | [github.com/microsoft/TypeScript/releases](https://github.com/microsoft/TypeScript/releases) — **6.0.3 stable** (shipped 2026-03-23). TS 6.0 is the **last JavaScript-based release** and is positioned as a bridge to 7.0: `strict: true` is now the default, ESM is the default module system, and ~9 compiler settings flipped defaults. **TS 7.0 Beta** (Project Corsa, Go rewrite) shipped 2026-04-21 as `@typescript/native-preview` (binary: `tsgo`); claims ~10× type-check speed and ~3× less memory. TS 7.0 stable is expected mid-to-late 2026. Do not adopt `tsgo` for production builds yet. |
-| **Bunup** | ^0.16.31 | [npmjs.com/package/bunup](https://www.npmjs.com/package/bunup) — Build tool for TS libs. Still 0.x; 0.16.23 through 0.16.31 are bug-fix only (DTS alias fixes, workspace `onSuccess` fix, external/noExternal honoring). Pin to a specific minor version for stability. |
-| **Biome** | ^2.4.14 (2.4.15 borderline) | [biomejs.dev](https://biomejs.dev/) — Formatter + linter. **Pinned to 2.4.14 (2026-05-01) per the 14-day rule**; 2.4.15 (2026-05-09) is 13 days old today — bump on next refresh. v2.4 (Feb 2026) added experimental embedded snippet formatting (CSS/GraphQL in JS/TS template literals), 15 HTML accessibility lint rules enabled by default, and promoted 24 nursery rules to stable (Vue 3, Next.js, Qwik). |
-| **@changesets/cli** | ^2.31.0 | [github.com/changesets/changesets/releases](https://github.com/changesets/changesets/releases) — 2.31.0 latest. **Still no native Bun support**; `changeset version` does not resolve `workspace:*` references for Bun workspaces — workarounds below remain required. |
-| **bun-types** | ^1.3.13 | [npmjs.com/package/bun-types](https://www.npmjs.com/package/bun-types) — Type definitions for Bun runtime APIs. Track Bun version (pinned to 1.3.13 per the 14-day rule). |
-| **tryscript** | ^0.1.6 | [npmjs.com/package/tryscript](https://www.npmjs.com/package/tryscript) — Golden/CLI testing via Markdown test files. |
-| **flowmark** | latest | [github.com/jlevy/flowmark](https://github.com/jlevy/flowmark) — Markdown auto-formatter (via `uvx`). |
-| **publint** | ^0.3.20 (0.3.21 too recent) | [npmjs.com/package/publint](https://www.npmjs.com/package/publint) — **Pinned to 0.3.20 (2026-05-08) per the 14-day rule**; 0.3.21 (2026-05-13) is 9 days old today. Incremental: re-enabled TS/TSX file existence checks; `exports["default"]` support. |
-| **actions/checkout** | v6 | [github.com/actions/checkout/releases](https://github.com/actions/checkout/releases) — v6.0.2 (2026-01-09). Credentials now stored in `$RUNNER_TEMP` rather than `.git/config`; Node 24 runtime; requires runner ≥ 2.327.1. |
-| **oven-sh/setup-bun** | v2 | [github.com/oven-sh/setup-bun](https://github.com/oven-sh/setup-bun) — v2.2.0 (2026-03-14). Migrated to Node.js 24 runtime ahead of GitHub’s **2026-06-02 deadline** that forces all Node.js 20 actions to Node.js 24. |
-| **lefthook** | ^2.1.5 (2.1.7/2.1.8 too recent) | [github.com/evilmartians/lefthook/releases](https://github.com/evilmartians/lefthook/releases) — **Pinned to 2.1.5 (2026-04-06) per the 14-day rule**; 2.1.7 and 2.1.8 both shipped 2026-05-19 (3 days old). Patch-level since 2.1.1: dependency bumps and config-warning improvements. v2 still excludes regexp `exclude` and `skip_output` from v1. |
-| **npm-check-updates** | ^22.0.0 (22.2.0 too recent) | [npmjs.com/package/npm-check-updates](https://www.npmjs.com/package/npm-check-updates) — **Major version jump from 19 to 22.** **Pinned to 22.0.0 (2026-04-25) per the 14-day rule**; 22.2.0 (2026-05-12) is 10 days old today. Now pure ESM; named imports only (`import { run } from 'npm-check-updates'`); `.ncurc.js` with `module.exports` no longer works in `"type": "module"` projects (use `.ncurc.cjs`). **Critical for supply chain: now ships `--cooldown <days>` to refuse versions younger than the specified age.** See [Supply-Chain Mitigation](#supply-chain-mitigation). |
+| **Bun** | 1.3.13 (1.3.14 too recent) | [bun.sh/blog](https://bun.sh/blog)—Runtime, bundler, package manager, test runner. Acquired by Anthropic (Dec 2025). **Pinned to 1.3.13 (2026-04-20) per the 14-day rule**—1.3.14 (2026-05-13) is the **last Zig-based release** and the Rust rewrite merged to `main` 2026-05-14 (~960K lines, generated by Claude AI agents over ~6 days). New built-ins in 1.3.x: `Bun.Image` (Sharp replacement), experimental HTTP/3 in `Bun.serve()`, 7× faster warm installs via isolated linker global store, rewritten `fs.watch()` on Linux/macOS. Bump to 1.3.14 (or 1.4.x once it ships) once the 14-day window has elapsed. |
+| **TypeScript** | ^6.0.3 | [github.com/microsoft/TypeScript/releases](https://github.com/microsoft/TypeScript/releases)—**6.0.3 stable** (shipped 2026-03-23). TS 6.0 is the **last JavaScript-based release** and is positioned as a bridge to 7.0: `strict: true` is now the default, ESM is the default module system, and ~9 compiler settings flipped defaults. **TS 7.0 Beta** (Project Corsa, Go rewrite) shipped 2026-04-21 as `@typescript/native-preview` (binary: `tsgo`); claims ~10× type-check speed and ~3× less memory. TS 7.0 stable is expected mid-to-late 2026. Do not adopt `tsgo` for production builds yet. |
+| **Bunup** | ^0.16.31 | [npmjs.com/package/bunup](https://www.npmjs.com/package/bunup)—Build tool for TS libs. Still 0.x; 0.16.23 through 0.16.31 are bug-fix only (DTS alias fixes, workspace `onSuccess` fix, external/noExternal honoring). Pin to a specific minor version for stability. |
+| **Biome** | ^2.4.14 (2.4.15 borderline) | [biomejs.dev](https://biomejs.dev/)—Formatter + linter. **Pinned to 2.4.14 (2026-05-01) per the 14-day rule**; 2.4.15 (2026-05-09) is 13 days old today—bump on next refresh. v2.4 (Feb 2026) added experimental embedded snippet formatting (CSS/GraphQL in JS/TS template literals), 15 HTML accessibility lint rules enabled by default, and promoted 24 nursery rules to stable (Vue 3, Next.js, Qwik). |
+| **@changesets/cli** | ^2.31.0 | [github.com/changesets/changesets/releases](https://github.com/changesets/changesets/releases)—2.31.0 latest. **Still no native Bun support**; `changeset version` does not resolve `workspace:*` references for Bun workspaces—workarounds below remain required. |
+| **bun-types** | ^1.3.13 | [npmjs.com/package/bun-types](https://www.npmjs.com/package/bun-types)—Type definitions for Bun runtime APIs. Track Bun version (pinned to 1.3.13 per the 14-day rule). |
+| **tryscript** | ^0.1.6 | [npmjs.com/package/tryscript](https://www.npmjs.com/package/tryscript)—Golden/CLI testing via Markdown test files. |
+| **flowmark** | latest | [github.com/jlevy/flowmark](https://github.com/jlevy/flowmark)—Markdown auto-formatter (via `uvx`). |
+| **publint** | ^0.3.20 (0.3.21 too recent) | [npmjs.com/package/publint](https://www.npmjs.com/package/publint)—**Pinned to 0.3.20 (2026-05-08) per the 14-day rule**; 0.3.21 (2026-05-13) is 9 days old today. Incremental: re-enabled TS/TSX file existence checks; `exports["default"]` support. |
+| **actions/checkout** | v6 | [github.com/actions/checkout/releases](https://github.com/actions/checkout/releases)—v6.0.2 (2026-01-09). Credentials now stored in `$RUNNER_TEMP` rather than `.git/config`; Node 24 runtime; requires runner ≥ 2.327.1. |
+| **oven-sh/setup-bun** | v2 | [github.com/oven-sh/setup-bun](https://github.com/oven-sh/setup-bun)—v2.2.0 (2026-03-14). Migrated to Node.js 24 runtime ahead of GitHub’s **2026-06-02 deadline** that forces all Node.js 20 actions to Node.js 24. |
+| **lefthook** | ^2.1.5 (2.1.7/2.1.8 too recent) | [github.com/evilmartians/lefthook/releases](https://github.com/evilmartians/lefthook/releases)—**Pinned to 2.1.5 (2026-04-06) per the 14-day rule**; 2.1.7 and 2.1.8 both shipped 2026-05-19 (3 days old). Patch-level since 2.1.1: dependency bumps and config-warning improvements. v2 still excludes regexp `exclude` and `skip_output` from v1. |
+| **npm-check-updates** | ^22.0.0 (22.2.0 too recent) | [npmjs.com/package/npm-check-updates](https://www.npmjs.com/package/npm-check-updates)—**Major version jump from 19 to 22.** **Pinned to 22.0.0 (2026-04-25) per the 14-day rule**; 22.2.0 (2026-05-12) is 10 days old today. Now pure ESM; named imports only (`import { run } from 'npm-check-updates'`); `.ncurc.js` with `module.exports` no longer works in `"type": "module"` projects (use `.ncurc.cjs`). **Critical for supply chain: now ships `--cooldown <days>` to refuse versions younger than the specified age.** See [Supply-Chain Mitigation](#supply-chain-mitigation). |
 
 ### Reminders When Updating
 
@@ -44,7 +44,7 @@ author: Joshua Levy (github.com/jlevy) with LLM assistance
 
 2. **Update the table** with new versions and any relevant notes
 
-3. **Search and update code examples** — version numbers appear in:
+3. **Search and update code examples**—version numbers appear in:
 
    - GitHub Actions workflows (CI and Release sections)
 
@@ -56,24 +56,24 @@ author: Joshua Levy (github.com/jlevy) with LLM assistance
 
    - Appendices (complete examples)
 
-4. **Verify compatibility** — check that tools still work together
+4. **Verify compatibility**—check that tools still work together
 
 5. **Update the “Last Updated” date** at the top of the document
 
 6. **Review “Open Research Questions”** section for any resolved items
 
 7. **Honor the 14-day package-age rule** when bumping versions in code examples.
-   See [Supply-Chain Mitigation](#supply-chain-mitigation) — versions cited here should
-   be ≥14 days old at the time the table is updated, except where a clearly-noted
-   security exception applies.
+   See [Supply-Chain Mitigation](#supply-chain-mitigation)—versions cited here should be
+   ≥14 days old at the time the table is updated, except where a clearly-noted security
+   exception applies.
 
 * * *
 
 ## Executive Summary
 
 This research brief provides a comprehensive guide for setting up a modern TypeScript
-monorepo using the **Bun ecosystem** end-to-end — Bun as runtime, package manager,
-bundler (via Bunup), and test runner.
+monorepo using the **Bun ecosystem** end-to-end—Bun as runtime, package manager, bundler
+(via Bunup), and test runner.
 It serves as a direct comparison to the companion document on pnpm-based monorepos,
 covering the same architectural scope but using Bun-native tooling wherever possible.
 
@@ -83,7 +83,7 @@ building ESM (or dual ESM/CJS) outputs with TypeScript declarations, **Changeset
 (single-package repos) for versioning and release automation, **Biome** for formatting
 and linting, **publint** for package validation, and **lefthook** for git hooks.
 The architecture also covers Bun’s unique capability for **compiling standalone
-executables** — a native binary distribution path unavailable in the pnpm ecosystem.
+executables**—a native binary distribution path unavailable in the pnpm ecosystem.
 
 **Research Questions**:
 
@@ -123,7 +123,7 @@ research stock.
 
 ## Research Findings
 
-### 1. Package Manager & Workspace Structure
+### 1. Package Manager and Workspace Structure
 
 #### Bun Workspaces
 
@@ -141,13 +141,12 @@ research stock.
 
 - Supports `workspace:*` protocol for inter-package references
 
-- Does not use a content-addressable store like pnpm — installs are flat in
-  `node_modules`
+- Does not use a content-addressable store like pnpm—installs are flat in `node_modules`
 
 - Missing some pnpm features: no `pnpm deploy`, less strict `node_modules` (phantom
   dependencies possible)
 
-- **Notable**: Bun was acquired by Anthropic on 2025-12-02 — Anthropic’s first
+- **Notable**: Bun was acquired by Anthropic on 2025-12-02—Anthropic’s first
   acquisition. Bun powers Claude Code (which ships as a `bun build --compile`
   executable), the Claude Agent SDK, and other Anthropic AI tooling, signaling strong
   ongoing investment and maintenance.
@@ -354,7 +353,7 @@ Bun to directly import TypeScript source files, bypassing compiled output entire
 ```
 
 This means during development within the monorepo, Bun can consume TypeScript directly
-without a build step — a significant DX advantage over Node.js-based setups.
+without a build step—a significant DX advantage over Node.js-based setups.
 
 **Assessment**: This is a unique Bun advantage.
 During local development, packages can be consumed without building.
@@ -568,8 +567,8 @@ export default defineConfig([
 
 **Key details**:
 
-- Set `clean: true` only on the first config — subsequent configs must use
-  `clean: false` to avoid deleting earlier outputs.
+- Set `clean: true` only on the first config—subsequent configs must use `clean: false`
+  to avoid deleting earlier outputs.
 - CLI binaries typically don’t need `dts` since they aren’t imported by consumers.
 - The `banner` field adds the shebang line for direct execution.
 
@@ -634,7 +633,7 @@ has platform-specific issues.
 
 * * *
 
-### 4. Package Exports & Dual Module Support
+### 4. Package Exports and Dual Module Support
 
 #### Subpath Exports
 
@@ -690,7 +689,7 @@ This auto-generates:
 
 **Manual configuration** (if not using auto-exports):
 
-Identical to the pnpm research — use the same `exports` structure with `"types"` before
+Identical to the pnpm research—use the same `exports` structure with `"types"` before
 `"default"` in each condition block.
 
 **Bun export condition**: Optionally add a `"bun"` condition pointing to TypeScript
@@ -784,7 +783,7 @@ publint is runtime-agnostic.
 
 * * *
 
-### 7. Versioning & Release Automation
+### 7. Versioning and Release Automation
 
 #### Changesets (with Bun Workarounds)
 
@@ -904,7 +903,7 @@ No `tsx` dependency needed.
 **Details**:
 
 Bun ships with a built-in test runner that is API-compatible with Jest/Vitest.
-It is extremely fast — roughly 2x faster than Node’s built-in test runner and
+It is extremely fast—roughly 2x faster than Node’s built-in test runner and
 significantly faster than Jest or Vitest.
 
 **Key features**:
@@ -1062,7 +1061,7 @@ maintain.
 
 * * *
 
-### 9. Code Formatting & Linting
+### 9. Code Formatting and Linting
 
 #### Biome
 
@@ -1300,7 +1299,7 @@ jobs:
 ```
 
 **`biome ci` vs `biome check`**: Use `biome ci .` (via `"check:ci": "biome ci ."`) in CI
-workflows instead of `biome check .`. The `biome ci` command is stricter — it errors on
+workflows instead of `biome check .`. The `biome ci` command is stricter—it errors on
 formatting issues rather than just reporting them, and produces cleaner output for CI
 logs. Use `biome check --write .` for local development (auto-fixes issues) and
 `biome ci .` in CI (fails on any issue).
@@ -1315,7 +1314,7 @@ logs. Use `biome check --write .` for local development (auto-fixes issues) and
 | Lint + format | Separate `format:check` + `lint:check` | Single `biome check` |
 | Node.js setup | Required | Not required (Bun includes runtime) |
 
-**Assessment**: Bun CI is simpler — one setup action instead of two, and a single check
+**Assessment**: Bun CI is simpler—one setup action instead of two, and a single check
 command instead of separate format and lint steps.
 The text-based `bun.lock` (since Bun 1.2) is diffable in PRs, on par with
 `pnpm-lock.yaml`.
@@ -1391,7 +1390,7 @@ projects that prefer manual version control and want provenance guarantees.
 
 > **When to prefer this over Changesets (LLM-era note):** For a **single published
 > package**, Changesets’ main wins (multi-package coordination, per-PR changelog
-> accumulation) mostly evaporate while its ceremony stays — and Bun adds the extra
+> accumulation) mostly evaporate while its ceremony stays—and Bun adds the extra
 > `workspace:*` workarounds above.
 > When releases are cut by an agent/maintainer who assembles notes from clean
 > conventional commits at release time (see a release-notes template), tag-triggered
@@ -1473,11 +1472,11 @@ jobs:
 
 **Release process with tag-triggered workflow**:
 
-1. `bun run changeset` — create changeset
+1. `bun run changeset`—create changeset
 2. Commit the changeset file
-3. `bun run changeset version` — bumps versions, updates CHANGELOG
+3. `bun run changeset version`—bumps versions, updates CHANGELOG
 4. Commit the version bump
-5. `git tag vX.X.X && git push --tags` — triggers the release workflow
+5. `git tag vX.X.X && git push --tags`—triggers the release workflow
 
 **Key advantages over Changesets Action**:
 
@@ -1514,7 +1513,7 @@ timing. The Changesets Action remains simpler for projects that prefer full auto
 
 * * *
 
-### 11. Git Hooks & Local Validation
+### 11. Git Hooks and Local Validation
 
 #### Lefthook with Biome
 
@@ -1724,7 +1723,7 @@ This is a unique advantage that the pnpm ecosystem does not offer natively.
 
 npm-check-updates (`ncu`) works with Bun.
 The main difference is using `bun install` instead of `pnpm install` after updates.
-**All upgrade commands must honor the 14-day package-age rule** — see
+**All upgrade commands must honor the 14-day package-age rule**—see
 [Supply-Chain Mitigation](#supply-chain-mitigation) for the rationale and exception
 process. `ncu` v22+ ships a native `--cooldown` flag that enforces this directly.
 
@@ -1795,7 +1794,7 @@ Distribution options are identical:
 
 1. **GitHub Packages** (recommended for teams)
 
-2. **Direct GitHub install**: `bun add github:org/repo` — Bun has limited support for
+2. **Direct GitHub install**: `bun add github:org/repo`—Bun has limited support for
    monorepo subdirectory installs (lagging behind pnpm)
 
 3. **Local linking**: `bun link` works similarly to `pnpm link`
@@ -1825,13 +1824,13 @@ in core library code if the library needs to work in Node.js environments.
 Supply-chain hardening applies to **every repo, not just new monorepos**, so the full
 policy and hands-on enforcement now live in a standalone guideline:
 **`tbd guidelines supply-chain-hardening`**. It covers the cross-ecosystem 14-day
-cool-off plus the Node/pnpm/Bun specifics — lifecycle-script allowlists, lockfile
+cool-off plus the Node/pnpm/Bun specifics—lifecycle-script allowlists, lockfile
 discipline, `npm-check-updates --cooldown 14`, the CI audit gate, and the
 `check-package-age` pre-push guard.
 Deeper background and the named-incident watch list:
 <https://github.com/jlevy/supply-chain-hardening>.
 
-**Bun specifics**: Bun blocks lifecycle scripts by default — extend the allowlist via
+**Bun specifics**: Bun blocks lifecycle scripts by default—extend the allowlist via
 `trustedDependencies` in `package.json`, run `bun audit` in CI with
 `bun install --frozen-lockfile`, and commit `bun.lock`. Bun has no native release-age
 gate yet, so enforce the 14-day cool-off with `bunx npm-check-updates --cooldown 14`.
@@ -1911,13 +1910,13 @@ gate yet, so enforce the 14-day cool-off with `bunx npm-check-updates --cooldown
 7. **Use `bun publish` per package** instead of `changeset publish` to ensure proper
    workspace resolution.
 
-8. **Run CLI from source with `bun`** directly — no need for `tsx` or any TypeScript
+8. **Run CLI from source with `bun`** directly—no need for `tsx` or any TypeScript
    execution wrapper.
 
 9. **Consider `bun --compile`** for distributing CLI tools as standalone executables,
    especially for users who don’t have Node.js or Bun installed.
 
-10. **Use `bun test`** for testing — fake timers are now supported (v1.3.4+). Switch to
+10. **Use `bun test`** for testing—fake timers are now supported (v1.3.4+). Switch to
     Vitest only if you need test isolation, browser mode, or sharding.
 
 11. **Keep the root `package.json` private** with `"private": true` and only workspace
@@ -1934,23 +1933,23 @@ gate yet, so enforce the 14-day cool-off with `bunx npm-check-updates --cooldown
 15. **Add the `"bun"` export condition** to let Bun consumers import TypeScript source
     directly, bypassing compiled output.
 
-16. **Use dynamic git-based versioning** for dev builds — the pattern works identically
+16. **Use dynamic git-based versioning** for dev builds—the pattern works identically
     with Bun, and `bun` replaces `tsx` for script execution.
 
-17. **Use `biome ci`** in CI workflows instead of `biome check` — it’s stricter and
+17. **Use `biome ci`** in CI workflows instead of `biome check`—it’s stricter and
     produces cleaner output for CI logs.
 
 18. **Consider ESM-only output** for Bun-native CLI tools and packages targeting modern
     Node.js (>=22). Only add CJS if specific consumers require it.
 
-19. **Use flowmark** for Markdown formatting in pre-commit hooks — Biome does not format
+19. **Use flowmark** for Markdown formatting in pre-commit hooks—Biome does not format
     Markdown, and consistent Markdown formatting improves documentation quality.
 
-20. **Add golden/CLI tests** with `tryscript` alongside `bun test` for CLI tools — they
+20. **Add golden/CLI tests** with `tryscript` alongside `bun test` for CLI tools—they
     catch regressions in help text, output formatting, and argument parsing.
 
 21. **Consider tag-triggered OIDC releases** as an alternative to the Changesets GitHub
-    Action — they provide npm provenance attestation and automatic GitHub Releases.
+    Action—they provide npm provenance attestation and automatic GitHub Releases.
 
 * * *
 
@@ -2000,7 +1999,7 @@ gate yet, so enforce the 14-day cool-off with `bunx npm-check-updates --cooldown
    `@typescript/native-preview` (binary `tsgo`). Claims ~10x type-check speed and ~3x
    less memory; passes 95%+ of the test suite.
    Available in Visual Studio 2026 18.6 Insiders by default.
-   **Do not adopt for production builds yet** — wait for stable (expected mid-to-late
+   **Do not adopt for production builds yet**—wait for stable (expected mid-to-late
    2026). May change the DTS generation landscape for Bunup and tsdown once stable.
 
 9. **Bunup maturity**: Bunup is iterating rapidly (0.16.31 as of May 2026, up from 0.4.x
@@ -2024,7 +2023,7 @@ gate yet, so enforce the 14-day cool-off with `bunx npm-check-updates --cooldown
     `--audit-level=<low|moderate|high|critical>` and `--json` output.
     Should be a required CI check (see
     [Supply-Chain Mitigation](#supply-chain-mitigation)). A `bun audit signatures`
-    equivalent to npm’s signature verification has not yet shipped — monitor.
+    equivalent to npm’s signature verification has not yet shipped—monitor.
 
 * * *
 
@@ -2112,7 +2111,7 @@ testing features.
 
 - [publint Documentation](https://publint.dev/docs/)
 
-### Guides & Articles
+### Guides and Articles
 
 - [Building a TypeScript Library in 2026 with Bunup](https://dev.to/arshadyaseen/building-a-typescript-library-in-2026-with-bunup-3bmg)
 
@@ -2304,10 +2303,10 @@ testing features.
   [Supply-Chain Mitigation](#supply-chain-mitigation) policy.
   Newer releases may exist (`@biomejs/biome` 2.4.15, `lefthook` 2.1.8,
   `npm-check-updates` 22.2.0) but were too fresh at the time of this document update.
-- `"check:ci": "biome ci ."` uses `biome ci` (stricter than `biome check` — errors on
+- `"check:ci": "biome ci ."` uses `biome ci` (stricter than `biome check`—errors on
   formatting issues)
 - `bun run --filter '*' <script>` delegates to each workspace package
-- The `@changesets/changelog-github` dependency is optional — use
+- The `@changesets/changelog-github` dependency is optional—use
   `"changelog": "@changesets/cli/changelog"` in `.changeset/config.json` for a simpler
   built-in changelog generator
 - `npm-check-updates` v22+ is pure ESM. Add `--cooldown 14` to every invocation per the
@@ -2406,7 +2405,7 @@ testing features.
 
 - `"organizeImports": { "enabled": true }` →
   `"assist": { "actions": { "source": { "organizeImports": "on" } } }`
-- `"vcs"` configuration is new — enables `.gitignore`-based file exclusion
+- `"vcs"` configuration is new—enables `.gitignore`-based file exclusion
 - `"files.ignoreUnknown": true` prevents errors on unsupported file types
 - `"files.includes"` with negation patterns replaces the old `"files.ignore"` array
   (both still work, but `includes` with negation is more flexible)
@@ -2629,7 +2628,7 @@ export default defineConfig([
 }
 ```
 
-### Appendix G: Case Study — craft-agents-oss (Real-World Bun Monorepo)
+### Appendix G: Case Study—craft-agents-oss (Real-World Bun Monorepo)
 
 **Repository**:
 [lukilabs/craft-agents-oss](https://github.com/lukilabs/craft-agents-oss) (Apache 2.0,
@@ -2678,7 +2677,7 @@ craft-agents-oss/
 
 **1. Source-Level Exports (No Build Step for Internal Consumption)**
 
-All internal packages export TypeScript source directly — no `dist/` directory:
+All internal packages export TypeScript source directly—no `dist/` directory:
 
 ```json
 // packages/shared/package.json — 27 subpath exports
@@ -2745,10 +2744,10 @@ Changesets entirely for a private monorepo that distributes as a single Electron
 
 Instead of Biome, this project uses ESLint with 4 custom rules:
 
-- `no-direct-navigation-state` — enforces navigation state abstraction
-- `no-localstorage` — prevents browser localStorage usage (Bun incompatible)
-- `no-direct-platform-check` — enforces platform detection abstraction
-- `no-hardcoded-path-separator` — enforces cross-platform paths
+- `no-direct-navigation-state`—enforces navigation state abstraction
+- `no-localstorage`—prevents browser localStorage usage (Bun incompatible)
+- `no-direct-platform-check`—enforces platform detection abstraction
+- `no-hardcoded-path-separator`—enforces cross-platform paths
 
 This demonstrates that ESLint’s custom rule ecosystem remains valuable for
 domain-specific architectural constraints that Biome cannot yet replicate.
@@ -2797,7 +2796,7 @@ The source-level exports pattern and TypeScript build scripts are directly appli
 The hybrid esbuild/Vite approach is more relevant for Electron/full-stack apps than for
 pure library packages where Bunup would be simpler.
 
-### Appendix H: Case Study — clam (Published Bun CLI Monorepo)
+### Appendix H: Case Study—clam (Published Bun CLI Monorepo)
 
 **Repository**: [jlevy/clam](https://github.com/jlevy/clam) (MIT, shell-like interface
 for Claude Code and other agents)
@@ -2866,7 +2865,7 @@ export default defineConfig([
 ```
 
 Separate configs for library (with DTS) and CLI binary (with shebang, dependency
-bundling, no DTS). ESM-only output — no CJS.
+bundling, no DTS). ESM-only output—no CJS.
 
 **2. Tag-Triggered OIDC Release with npm Provenance**
 
@@ -2897,7 +2896,7 @@ new Biome 2.x `"assist"` API for import organization.
 The base config enables `isolatedDeclarations: true` (as recommended), but the package
 overrides it to `false` because its types are complex enough to require the full
 TypeScript compiler for DTS generation.
-This is a valid pattern — enable in the base, override in packages that need it.
+This is a valid pattern—enable in the base, override in packages that need it.
 
 #### What This Repo Uses