docbridge 0.6.1 → 0.8.0

package/CHANGELOG.md

@@ -7,6 +7,135 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.8.0] - 2026-08-18
+
+### Added
+
+- The VS Code-compatible extension `salan70.docbridge` is published on Visual
+  Studio Marketplace.
+- Packaged user docs now cover linking workflow and semantic link review
+  (`docbridge docs show linking-workflow`, `docbridge docs show link-review`),
+  plus supported and unsupported `@doc` declaration forms, the heading-anchor
+  algorithm, and named link-authoring diagnostic codes.
+- Human-readable `docbridge check` output ends with a pointer to
+  `docbridge docs show troubleshooting`. `check --json` is unchanged.
+
+### Changed
+
+- `docbridge init` and `docbridge init-with-agent` install one skill,
+  `docbridge`, instead of the five companion skills. The skill routes adopt,
+  discover-and-link, annotate, review, and sync work; facts about the binary
+  come from `docbridge docs show`.
+
+### Fixed
+
+- `just package-vsix` bundles `vscode-languageclient` into the editor client.
+  Packaging with `--no-dependencies` previously omitted the module, so the
+  installed VSIX failed to activate.
+- `docs/user/annotations.md` no longer claims GitHub-style numeric suffixes for
+  duplicate headings. Duplicate anchors in one file are `duplicate_doc_anchor`.
+
+### Upgrading
+
+- Existing installs keep the five legacy skill directories
+  (`docbridge-adopt`, `docbridge-annotate`, `docbridge-link`,
+  `docbridge-review`, `docbridge-sync`) until `docbridge init --force` is run.
+  Review locally edited copies first. Symlinked skill directories are reported
+  and left untouched.
+
+## [0.7.0] - 2026-08-16
+
+### Added
+
+- Rust is a first-party code language. Configure `include.code.rust`, place
+  `@doc` in `///` / `//!` / `/** */` comments on modules, structs, enums, free
+  functions, and inherent `impl` methods, and check links with the bundled
+  `docbridge-rust-scanner` worker (same platforms as Swift/Dart). Default
+  visibility is `pub` only; set `visibility` to include `private` for
+  non-`pub` items. Canonical IDs use Rust path style (`Type::method`).
+- `docbridge docs list [--json]` and `docbridge docs show <name>` provide six
+  task-oriented, version-matched guides from the installed npm package, with
+  packed-package smoke coverage under Node.js and Bun.
+- CLI invocation errors now list valid commands, suggest close command names,
+  and include runnable command-specific recovery guidance. Missing check
+  configuration also points to `docbridge init` and `docbridge init-with-agent`.
+- TypeScript type members can be link endpoints, closing the last functional
+  asymmetry with Swift and Dart. `@doc` on a class method, property, getter,
+  setter, constructor, or static member, on an interface member, or on a member
+  of a type alias written directly as an object type literal resolves to a
+  type-qualified endpoint such as `AuthService.login`. Canonical IDs carry no
+  parameter signatures: overload groups and getter/setter pairs each describe
+  one member and collapse to one endpoint, and a collision — including a static
+  and an instance member of the same name — reports `duplicate_code_symbol`.
+  Only identifier-named members qualify, because a link target is
+  `file#fragment` with one `#` and no whitespace.
+- `include.code.typescript.visibility` accepts `public`, `protected`, and
+  `private`, defaulting to `public` and `protected`. It scopes type members
+  only; top-level declarations remain scoped by `export`.
+
+### Changed
+
+- Scanner worker request and response payloads now have a published JSON Schema,
+  and malformed nested worker output fails explicitly instead of degrading into
+  incomplete scan data. Graph and context output schemas share their diagnostic
+  definitions and are checked against real CLI output. The configuration schema
+  now matches the CLI's per-language suffix and visibility rules.
+- `docbridge context` and `docbridge graph --include-content` strip the common
+  leading indentation from an extracted declaration, so a type member reads at
+  its own level. Output for top-level declarations is unchanged.
+- A `@doc` on a TypeScript type member was previously collected by nothing and
+  silently ignored. It is now a real annotation, so an existing one can surface
+  link diagnostics — `invalid_link_target`, `doc_file_not_found`,
+  `doc_anchor_not_found`, `doc_backlink_not_found` — that were always latent,
+  and an annotation on a `private` member becomes `unsupported_declaration`.
+  `check --audit` output is unchanged: members never count as
+  `undocumented_symbol`.
+- `docbridge check --audit` reports `unlinked_doc_section`, a warning for
+  in-scope documentation sections that carry no `@code` annotation. It is the
+  documentation-side counterpart to `undocumented_symbol`, so the audit now
+  covers both directions of the link graph. Reporting is rolled up over the
+  heading tree: only the topmost heading of a fully unannotated subtree is
+  reported, and a heading is treated as annotated whenever a `@code` comment is
+  attached to it, even if that annotation fails to parse or resolve. Empty
+  headings create no anchor and are never reported, but they still close the
+  section before them, so a deeper heading following one is a separate region
+  rather than a suppressed descendant. Runs
+  without `--audit` are unaffected, and the diagnostic is a warning, so exit
+  codes do not change.
+
+### Fixed
+
+- Swift and Dart scanners now report malformed and duplicate `@doc` targets as
+  `invalid_link_target` and `duplicate_link`, matching TypeScript instead of
+  silently accepting or discarding the annotations.
+- `docbridge graph --include-content` no longer truncates a signature at an
+  object type. It cut the rendered text at the first `{`, which for
+  `login(options: { verbose: boolean })` produced `login(options: {}`. A
+  `signatureRange` already ends where the implementation body begins in every
+  language, so no body has to be cut out of it.
+- The VS Code extension manifest is version-aligned with the npm package again
+  (`0.4.1` had drifted from `0.6.1`), so a checkout of `main` is a valid input
+  to `just package-vsix`. Release Prepare now bumps both manifests through
+  `scripts/set-release-version.ts` and stages both in the release commit, so a
+  CLI release can no longer leave the extension version behind.
+- `just package-vsix` bundles the server the VSIX ships with `--target node`,
+  matching the npm build. The Bun-targeted bundle it built before still carried
+  a `#!/usr/bin/env node` shebang and crashed with `__require is not a function`
+  when the packaging flow's own `verify-dist` step executed it.
+
+### Removed
+
+- The agent-hook integration is gone from the product surface: the copyable
+  scripts under `examples/hooks/` and the hook recipes in
+  `docs/integrations/claude-code.md` and `docs/integrations/codex.md` no longer
+  ship. Wiring DocBridge into an agent's `PostToolUse`/`Stop` hooks covered only
+  the agents that read those configuration files; the documented guardrail is
+  now a Git `pre-commit` hook, which applies to every contributor and every
+  tool. Both integration documents survive as skill-installation guides,
+  `docbridge context` and `docbridge related --gate` are unchanged, and
+  `docbridge docs show agent-integration` describes the Git-hook shape instead.
+  Copies already installed in adopters' repositories keep working.
+
 ## [0.6.1] - 2026-07-27
 
 ### Changed
@@ -222,7 +351,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.6.1...HEAD
+[Unreleased]: https://github.com/salan70/docbridge/compare/v0.8.0...HEAD
+[0.8.0]: https://github.com/salan70/docbridge/releases/tag/v0.8.0
+[0.7.0]: https://github.com/salan70/docbridge/releases/tag/v0.7.0
 [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

package/README.md

@@ -6,7 +6,7 @@
 
 Bring Markdown into the LSP world.
 
-DocBridge creates bidirectional links between TypeScript, Swift, or Dart code
+DocBridge creates bidirectional links between TypeScript, Swift, Dart, or Rust code
 and Markdown documentation, enabling LSP-like experiences such as Hover,
 Definition, References, and Diagnostics across implementation and specification
 files.
@@ -22,13 +22,13 @@ npx docbridge check
 bunx docbridge check
 ```
 
-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.
+See the npm badge above or
+[Releases](https://github.com/salan70/docbridge/releases) for the current
+version.
 
-The package includes prebuilt Swift and Dart scanner
+The package includes prebuilt Swift, Dart, and Rust scanner
 binaries for `darwin-arm64` and `linux-x64`. TypeScript and Markdown checks run
-without scanner binaries. Configured Swift or Dart projects on unsupported
+without scanner binaries. Configured Swift, Dart, or Rust projects on unsupported
 platforms report `code_scanner_unavailable` and name the supported platform
 keys.
 
@@ -40,9 +40,8 @@ Run first-time setup in the project root:
 bunx docbridge init
 ```
 
-For agent-guided adoption, install `docbridge-adopt` and print setup commands.
-The `docbridge-adopt` skill finishes adoption and installs the remaining
-DocBridge skills after scope is confirmed:
+For agent-guided adoption, install the `docbridge` skill and print setup
+commands. The skill routes adopt, link, review, and sync work:
 
 ```sh
 bunx docbridge init-with-agent
@@ -98,6 +97,16 @@ bunx docbridge check
 
 ## Usage
 
+Discover a command:
+
+```sh
+bunx docbridge --help
+bunx docbridge context --help
+```
+
+Every command accepts `--help` (alias `-h`) and prints its usage, when to use
+it, and its options on stdout.
+
 Check links:
 
 ```sh
@@ -124,7 +133,8 @@ bunx docbridge check --audit
 
 Audit diagnostics include:
 
-- `undocumented_symbol`
+- `undocumented_symbol` — in-scope code endpoints with no `@doc`
+- `unlinked_doc_section` — in-scope documentation sections with no `@code`
 
 List the linked counterparts of changed files:
 
@@ -193,7 +203,7 @@ Code <-> Documentation
 ```
 
 DocBridge links supported code declarations to Markdown sections. TypeScript is
-scanned in-process; Swift and Dart are scanned through bundled first-party
+scanned in-process; Swift, Dart, and Rust are scanned through bundled first-party
 worker packages.
 
 ## Supported Inputs
@@ -205,11 +215,15 @@ Supported code declarations:
 - TypeScript top-level exported declarations: `function`, `class`,
   `abstract class`, `interface`, `type`, `const`, `enum`, and supported
   `declare` / named default forms
+- TypeScript type members: class methods, properties, accessors, constructors,
+  and static members, plus interface and object-type-alias signatures
 - Swift public/open declarations and configured internal declarations:
   top-level and member types, functions, variables, constants, initializers,
   and extension members
 - Dart public declarations: top-level functions/variables, classes, enums,
   mixins, constructors, fields, accessors, methods, and extension members
+- Rust `pub` declarations (and configured non-`pub` with `visibility`):
+  modules, structs, enums, free functions, and inherent `impl` methods
 
 Supported Markdown elements:
 
@@ -217,8 +231,29 @@ Supported Markdown elements:
 - HTML comments
 - `@code` annotations attached to the next heading
 
-Swift and Dart use the same `@doc` and `@code` model. Their code fragments are
-the scanner-produced canonical IDs, so members are type-qualified:
+All four languages use the same `@doc` and `@code` model. Code fragments are
+the scanner-produced canonical IDs, so members are type-qualified.
+
+TypeScript member IDs carry no parameter signature; overload signatures and a
+getter/setter pair each collapse to one endpoint, and the constructor is
+`<Type>.constructor`. By default `public` and `protected` members are scanned;
+`private` members require `include.code.typescript.visibility`. Members are
+linkable but are never reported by `check --audit`.
+
+```ts
+export class AuthService {
+  /** @doc docs/auth.md#login-spec */
+  login(email: string, password: string): void {}
+}
+```
+
+```md
+<!-- @code src/auth/service.ts#AuthService.login -->
+
+## Login Spec
+```
+
+Swift, Dart, and Rust canonical IDs follow their own conventions:
 
 ```swift
 /// @doc docs/auth.md#login-spec
@@ -268,27 +303,26 @@ shape is intentionally invalid; migrate it to a `typescript` entry:
 }
 ```
 
-Swift and Dart projects must build their scanner workers in source checkouts
-before checking those languages. Run `just build-swift-scanner` for Swift and
-`just build-dart-scanner` for Dart, or use the native test recipes below.
+Swift, Dart, and Rust projects must build their scanner workers in source checkouts
+before checking those languages. Run `just build-swift-scanner` for Swift,
+`just build-dart-scanner` for Dart, and `just build-rust-scanner` for Rust, or
+use the native test recipes below.
 
 ## AI agent integration
 
 DocBridge's link graph is built to be consumed by AI coding agents:
 
 - [docs/integrations](docs/integrations) — recipes for Claude Code, Codex,
-  and CI: on-edit counterpart awareness with `docbridge context`, gate triage
-  with `docbridge related --gate`, and PR reporting.
-- [examples/hooks](examples/hooks) — copyable agent hook scripts implementing
-  those recipes.
-- [templates/skills](templates/skills) — distributable agent skills installed by
-  `docbridge init`; `docbridge init-with-agent` installs `docbridge-adopt`
-  first, then `docbridge-adopt` installs the companion skills:
-  `docbridge-annotate`, `docbridge-sync`, `docbridge-adopt`, `docbridge-link`,
-  and `docbridge-review`.
-
-This repository dogfoods the hooks and skills in its own guardrails under
-`.claude/`, `.codex/`, and `.agents/`.
+  and CI: gate triage with `docbridge related --gate`, counterpart content with
+  `docbridge context`, and PR reporting.
+- [templates/skills](templates/skills) — the distributable `docbridge` skill
+  installed by `docbridge init` and `docbridge init-with-agent`. Facts about
+  the binary live in `docbridge docs show`. Existing five-skill installs remain
+  until `docbridge init --force`.
+
+This repository dogfoods the skills under `.claude/` and `.agents/`, and keeps
+its guardrail in the Git `pre-commit` hook under `.githooks/` rather than in
+any agent's configuration.
 
 ## Editor support
 
@@ -304,24 +338,24 @@ options; the project root comes from the editor's `initialize` request.
 `docbridge check` is unchanged.
 
 A VS Code-compatible extension lives in [editors/vscode](editors/vscode). It
-packages the language server into a VSIX for VS Code and Cursor. The extension
-has not yet been published to VS Code Marketplace. Until the first Marketplace
-publication, stage the supported `dist/bin/darwin-arm64` and
-`dist/bin/linux-x64` scanner artifacts, then build and install the VSIX
-locally:
+packages the language server into a VSIX for VS Code and Cursor. Install
+[`salan70.docbridge`](https://marketplace.visualstudio.com/items?itemName=salan70.docbridge)
+from VS Code Marketplace. Bun must be available to the editor; set
+`docbridge.bunPath` if the GUI cannot find `bun` on `PATH`.
+
+Contributors can still stage the supported `dist/bin/darwin-arm64` and
+`dist/bin/linux-x64` scanner artifacts and build a local VSIX:
 
 ```sh
 just package-vsix
 just verify-vsix
 ```
 
-Install the generated file from `editors/vscode/.tmp/out/` with **Extensions:
-Install from VSIX...** in VS Code or Cursor. The first Marketplace publication
-is intentionally manual; the repository provides a publish command for that
-release process. Open VSX delivery is out of scope. Zed integration is tracked
-separately and is not yet implemented. MCP delivery is out of scope until a
-concrete consumer requires a long-lived tool server. Full LSP behavior is specified in
-[docs/specs/lsp.md](docs/specs/lsp.md).
+Registry publication remains manual (`VSCE_PAT=<token> just
+publish-vscode-extension`). Open VSX delivery is out of scope. Zed integration
+is tracked separately and is not yet implemented. MCP delivery is out of scope
+until a concrete consumer requires a long-lived tool server. Full LSP behavior
+is specified in [docs/specs/lsp.md](docs/specs/lsp.md).
 
 ## Diagnostics
 
@@ -339,6 +373,8 @@ Errors:
 - `duplicate_doc_anchor`
 - `duplicate_code_symbol`
 - `code_parse_error`
+- `code_scanner_unavailable`
+- `code_scanner_failed`
 - `file_read_error`
 
 Warnings:
@@ -347,6 +383,7 @@ Warnings:
 - `dangling_code_annotation`
 - `unsupported_declaration`
 - `undocumented_symbol` when `--audit` is enabled
+- `unlinked_doc_section` when `--audit` is enabled
 
 Exit code policy:
 
@@ -373,12 +410,11 @@ repository setup, testing matrix, commit convention, and pull request workflow.
 
 ## Roadmap
 
-Completed v0.1–v0.5 capabilities are documented above and in
+Completed v0.1–v0.6 capabilities are documented above and in
 [CHANGELOG.md](CHANGELOG.md).
 
 Remaining editor delivery work:
 
-- Publish the first verified VSIX to VS Code Marketplace
 - Follow-up automation for GitHub Release VSIX attachment and registry
   publishing after the manual flow is proven
 - Add a separate Zed integration path

package/dist/bin/darwin-arm64/SHA256SUMS

@@ -1,2 +1,3 @@
-e5dc0117b9afe4e617fac20f9a8cf9797fa307f66d5a3f12e8ea6554639adce3  docbridge-swift-scanner
-8268ae8b1d3329a96ce30590c8f177b0c19ea1a887a458647e04d8d295c74a71  docbridge_dart_scanner
+4b0ab3efbe865e9fb0cc48a6a0d37146c72a4255479e1c78c27b6c20e7e62604  docbridge-swift-scanner
+c764c46477f522c8a82b62e629ff69907c0511fbc58b005ee6eba04d0e08dbef  docbridge_dart_scanner
+a1b129d980c981a2d24f0c9682e614a9695d4e9f9b8174d61b0dacb3fc9e3c79  docbridge-rust-scanner

package/dist/bin/linux-x64/SHA256SUMS

@@ -1,2 +1,3 @@
-396d365794cb5c427817b358bb3d9f2280000cd33fe3fc7d6d5a772a29ebcae4  docbridge-swift-scanner
-b5de2b74d56c6d8c9f8edd859d4b0d8846ff32d8e1d50b6fa41683d9a310b9f5  docbridge_dart_scanner
+9b7f3eea8df6ec2a07bd243a46b149fe3468240c6e0293390dc58594140519de  docbridge-swift-scanner
+095c4c172da615be155bee15dcce7b99faaf2a8bb26f3cad3e0b17881495ddf2  docbridge_dart_scanner
+d89a1146ed10dcb01151ef5351a746862c3955286431c47f3cf91cf6639866ba  docbridge-rust-scanner