docbridge 0.5.2 → 0.6.1

package/CHANGELOG.md

@@ -7,6 +7,43 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.6.1] - 2026-07-27
+
+### Changed
+
+- The related-gate CI recipe in `docs/integrations/ci.md` now derives the PR
+  changed-file list from the checkout (`git diff BASE...HEAD` with
+  `fetch-depth: 0`) and falls back to a retried GitHub API call. Outcomes are
+  reported as `clean`, `violation`, or `infra-error`, and the sticky comment
+  updates on every outcome (including infrastructure failure). Adopters who
+  copied the previous recipe must re-copy it and set `fetch-depth: 0` on the
+  checkout step; a shallow checkout breaks the new primary path.
+- Shipped Swift and Dart scanner executables are now named
+  `docbridge-swift-scanner` and `docbridge_dart_scanner`. Paths under
+  `dist/bin/<platform>/speclink-*` no longer exist; delete `chmod +x`
+  workarounds that hard-coded those names rather than updating the paths.
+
+### Fixed
+
+- Bundled Swift and Dart scanner binaries no longer have to be executable at
+  install time. Installers do not reliably preserve the executable bit on files
+  under `dist/bin/`, which made `docbridge check` fail on every Swift or Dart
+  project; DocBridge now restores the bit on its own bundled scanners when the
+  current process cannot execute them. Consumers can remove `chmod +x`
+  workarounds from their build recipes. When the bit cannot be restored, or when
+  the binary is executable but the filesystem refuses to execute it as a
+  `noexec` mount does, `code_scanner_unavailable` now names the cause and the
+  remedy instead of surfacing a bare spawn error.
+
+## [0.6.0] - 2026-07-13
+
+### Added
+
+- The npm package now runs on Node.js (>= 22) in addition to Bun: the CLI is
+  built for the Node target with a `#!/usr/bin/env node` shebang, so
+  `npx docbridge` works without installing Bun. Packaging smoke tests exercise
+  the CLI under both runtimes.
+
 ## [0.5.2] - 2026-07-12
 
 ### Fixed
@@ -185,7 +222,9 @@ Initial release of the SpecLink CLI.
 - `speclink check` command with `--root`, `--json`, and `--audit` options.
 - `speclink --version` (alias `-v`) and `speclink --help` (alias `-h`).
 
-[Unreleased]: https://github.com/salan70/docbridge/compare/v0.5.2...HEAD
+[Unreleased]: https://github.com/salan70/docbridge/compare/v0.6.1...HEAD
+[0.6.1]: https://github.com/salan70/docbridge/releases/tag/v0.6.1
+[0.6.0]: https://github.com/salan70/docbridge/releases/tag/v0.6.0
 [0.5.2]: https://github.com/salan70/docbridge/releases/tag/v0.5.2
 [0.5.1]: https://github.com/salan70/docbridge/releases/tag/v0.5.1
 [0.5.0]: https://github.com/salan70/docbridge/releases/tag/v0.5.0

package/README.md

@@ -13,10 +13,12 @@ files.
 
 ## Installation
 
-DocBridge is distributed as the `docbridge` npm package and is intended to run
-with Bun:
+DocBridge is distributed as the `docbridge` npm package and runs on Node.js
+(>= 22) and Bun:
 
 ```sh
+npx docbridge check
+# or
 bunx docbridge check
 ```
 
@@ -24,8 +26,7 @@ The current release is
 [v0.5.0](https://github.com/salan70/docbridge/releases/tag/v0.5.0), published
 as `docbridge@0.5.0` on npm.
 
-The npm package is Bun-only; Node.js runtime compatibility is not part of the
-initial distribution. The package includes prebuilt Swift and Dart scanner
+The package includes prebuilt Swift and Dart scanner
 binaries for `darwin-arm64` and `linux-x64`. TypeScript and Markdown checks run
 without scanner binaries. Configured Swift or Dart projects on unsupported
 platforms report `code_scanner_unavailable` and name the supported platform
@@ -83,6 +84,7 @@ Add the backlink in the Markdown file:
 
 ```md
 <!-- @code src/auth/login.ts#login -->
+
 ## Login Spec
 
 Login flow specification.
@@ -227,6 +229,7 @@ public struct AuthService {
 
 ```md
 <!-- @code Sources/AuthService.swift#AuthService.login(email:password:) -->
+
 ## Login Spec
 ```
 
@@ -350,114 +353,14 @@ Exit code policy:
 - `1` when any error exists
 - `0` when there are only warnings or no diagnostics
 
-## Development
-
-### Prerequisites
-
-Recommended:
-
-- Nix
-- direnv
-
-The Nix development shell provides the tools used by this repository:
-
-- Bun
-- just
-- Git
-- Dart SDK
-
-If you do not use Nix, install Bun and just locally before running the project
-commands. Swift scanner development also requires a Swift 6 toolchain on
-`PATH`; CI installs Swift separately from Nix.
-
-### Setup
-
-Enable the development environment with direnv:
-
-```sh
-direnv allow
-```
-
-Or enter the Nix development shell manually:
-
-```sh
-nix develop
-```
-
-Install dependencies:
-
-```sh
-bun install --frozen-lockfile
-```
-
-Install repository Git hooks:
-
-```sh
-just install-git-hooks
-```
-
-If `just` is not on `PATH` yet, run:
-
-```sh
-nix develop -c just install-git-hooks
-```
-
-The pre-commit hook runs `just check` and `just test`.
-
-### Common Tasks
-
-Run common tasks with `just`:
-
-```sh
-just --list
-just check
-just check-example
-just check-swift-example
-just check-dart-example
-just check-fixture <code>
-just audit
-just related-gate
-just test
-just test-swift-scanner
-just test-dart-scanner
-just build
-just verify-dist
-```
-
-`just check`, `just test`, and `just build` are the default local and CI gates.
-`just test` includes TypeScript, Swift, and Dart end-to-end integration tests;
-the Swift and Dart scanner binaries must be built before those integration
-tests can spawn them. Scanner-native tests are mandatory in CI and are useful
-locally when changing worker code. `just verify-dist` builds confidence in the
-npm entry point by checking the Bun shebang, executable bit, `--version`,
-`--help`, and a TypeScript example check from `dist/index.js`.
-
-### Project Constraints
-
-Runtime:
-
-- Bun
-
-Language:
-
-- TypeScript
-- Swift scanner worker package
-- Dart scanner worker package
-
-Task runner:
-
-- just
-
-Environment loader:
-
-- direnv
+## Contributing
 
-Core dependencies should stay minimal. The CLI should primarily rely on Bun and
-the TypeScript Compiler API; Swift and Dart parser dependencies stay isolated
-inside their worker packages.
+See [CONTRIBUTING.md](CONTRIBUTING.md) for the pinned development environment,
+repository setup, testing matrix, commit convention, and pull request workflow.
 
 ## Documentation
 
+- Contributor guide: [CONTRIBUTING.md](CONTRIBUTING.md)
 - Japanese documentation: [docs/ja/README.md](docs/ja/README.md)
 - Specifications: [docs/specs](docs/specs)
 - v0.1 decisions: [docs/decisions/v0.1.md](docs/decisions/v0.1.md)
@@ -465,6 +368,7 @@ inside their worker packages.
 - v0.3 decisions: [docs/decisions/v0.3.md](docs/decisions/v0.3.md)
 - AI agent integration recipes: [docs/integrations](docs/integrations)
 - Commit message convention: [docs/contributing/commits.md](docs/contributing/commits.md)
+- Pull request convention: [docs/contributing/pull-requests.md](docs/contributing/pull-requests.md)
 - Testing convention: [docs/contributing/testing.md](docs/contributing/testing.md)
 
 ## Roadmap

package/dist/bin/darwin-arm64/SHA256SUMS

@@ -1,2 +1,2 @@
-d77294651a19f091422cc25d67131abfcf4de06d56a7e06116fed66a1ddf4097  speclink-swift-scanner
-9874f1a3e29f2c4ebf2ccd23d9d91e5bf74c9e6b0ca00a117b265418f7f12eb9  speclink_dart_scanner
+e5dc0117b9afe4e617fac20f9a8cf9797fa307f66d5a3f12e8ea6554639adce3  docbridge-swift-scanner
+8268ae8b1d3329a96ce30590c8f177b0c19ea1a887a458647e04d8d295c74a71  docbridge_dart_scanner

package/dist/bin/linux-x64/SHA256SUMS

@@ -1,2 +1,2 @@
-762934bad01b5a33a6b14ff22b579dcb03169436fb01a6a672ab30719c70c294  speclink-swift-scanner
-cfc22c423afaa1e42bef7c0c6b7de42fa54a3e11ca5baad518cd19e0c9c1258d  speclink_dart_scanner
+396d365794cb5c427817b358bb3d9f2280000cd33fe3fc7d6d5a772a29ebcae4  docbridge-swift-scanner
+b5de2b74d56c6d8c9f8edd859d4b0d8846ff32d8e1d50b6fa41683d9a310b9f5  docbridge_dart_scanner