docbridge 0.9.0 → 0.10.1

package/docs/README.md

@@ -57,6 +57,7 @@ with the specification for the interface whose exact contract you need:
 - [Testing](contributing/testing.md)
 - [Commit messages](contributing/commits.md)
 - [Pull requests](contributing/pull-requests.md)
+- [Releasing](contributing/releasing.md)
 - [Self-audit baseline](contributing/self-audit.md)
 - [Dogfooding review, September 2026](reports/2026-09-dogfooding-review.md)
 

package/docs/user/automation.md

@@ -34,8 +34,8 @@ docbridge init-with-agent --agent-target codex
 Use `claude` or `both` for the other supported targets. The command installs
 the skill and prints the next command or prompt; it does not launch an agent.
 
-<!-- @code src/core/context.ts#context -->
-<!-- @code src/core/related.ts#related -->
+<!-- @code src/query/context.ts#context -->
+<!-- @code src/query/related.ts#related -->
 
 ## Editing workflow
 

package/docs/user/commands.md

@@ -13,7 +13,7 @@ Use the narrowest command for the question you need to answer.
 The first argument selects a command. Global `--help` and `--version` are
 handled before project scanning, while each command validates its own options.
 
-<!-- @code src/core/resolver.ts#check -->
+<!-- @code src/query/check.ts#check -->
 
 ### `check`: validate the project
 
@@ -22,7 +22,7 @@ annotations, targets, reciprocal links, and the optional link manifest. Add
 `--audit` to include warnings for undocumented code declarations and unlinked
 Markdown sections. Add `--json` for machine-readable diagnostics.
 
-<!-- @code src/core/related.ts#related -->
+<!-- @code src/query/related.ts#related -->
 
 ### `related`: find counterpart files
 
@@ -36,7 +36,7 @@ git diff --name-only | docbridge related --stdin
 set. It identifies review obligations; it does not decide whether the
 counterpart actually needs an edit.
 
-<!-- @code src/core/context.ts#context -->
+<!-- @code src/query/context.ts#context -->
 
 ### `context`: read counterpart content
 
@@ -49,7 +49,7 @@ docbridge context src/auth.ts
 The default Markdown output is suitable for an agent prompt. `--json` returns
 structured contexts, diagnostics, and a summary.
 
-<!-- @code src/core/graph-output.ts#graph -->
+<!-- @code src/query/graph-output.ts#graph -->
 
 ### `graph`: inspect link structure
 

package/docs/user/configuration.md

@@ -8,7 +8,7 @@ DocBridge loads `docbridge.config.json` from the project root supplied by
 `--root`, or from the current directory by default. Paths and glob patterns are
 interpreted relative to that root.
 
-<!-- @code src/core/config.ts#loadConfig -->
+<!-- @code src/config/config.ts#loadConfig -->
 
 ## Loading configuration
 
@@ -43,7 +43,7 @@ excluded by visibility is not an endpoint; an `@doc` on one is
 `unsupported_declaration`. See `docbridge docs show linking` for the
 per-language rules, including Dart's leading-underscore privacy.
 
-<!-- @code src/core/glob.ts#collectFiles -->
+<!-- @code src/shared/glob.ts#collectFiles -->
 
 ## Excluded files
 

package/docs/user/linking.md

@@ -32,7 +32,7 @@ Use `docbridge check --audit` to find unlinked sections and undocumented public
 symbols. Audit diagnostics are candidates for judgment, not instructions to
 link every item.
 
-<!-- @code src/core/links.ts#parseLinkTarget -->
+<!-- @code src/model/link-target.ts#parseLinkTarget -->
 
 ## Target grammar
 
@@ -114,7 +114,7 @@ to include non-`pub` items. Trait definitions and implementations, macros,
 constants, statics, unions, and extern blocks are not endpoints. IDs use `::`
 qualification, such as `TypingEngine::advance`.
 
-<!-- @code src/core/markdown.ts#scanMarkdown -->
+<!-- @code src/scan/markdown/markdown.ts#scanMarkdown -->
 
 ## Documentation to code
 
@@ -144,7 +144,7 @@ numeric suffixes.
 Each direction is validated independently, so a resolving target can still
 report a missing backlink. Run `docbridge check` after every edit.
 
-<!-- @code src/core/link-manifest.ts#loadLinkManifest -->
+<!-- @code src/config/link-manifest.ts#loadLinkManifest -->
 
 ## Declare links in a manifest
 

package/docs/user/troubleshooting.md

@@ -42,8 +42,10 @@ project's own toolchain, then reproduce with the smallest configured file
 set.
 
 `code_parse_error` means a TypeScript, Swift, Dart, or Rust source file has a
-syntax error. DocBridge extracts no links or symbols from that file, so fix the
-syntax before judging link diagnostics that involve it. Unlike
+syntax error. The diagnostic points at the first error the language's parser
+found and includes the parser's message. DocBridge extracts no links or symbols
+from that file, so fix the syntax before judging link diagnostics that involve
+it. Unlike
 `code_scanner_failed`, the worker ran correctly; the source itself did not
 parse.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "docbridge",
-  "version": "0.9.0",
+  "version": "0.10.1",
   "description": "A CLI that links Markdown specifications and code declarations. Runs on Node.js and Bun.",
   "keywords": [
     "bun",
@@ -33,17 +33,9 @@
     "LICENSE"
   ],
   "type": "module",
-  "scripts": {
-    "docbridge": "bun run src/cli/index.ts",
-    "check": "bun run src/cli/index.ts check",
-    "check:example": "bun run src/cli/index.ts check --root examples/typescript",
-    "test": "bun test",
-    "build": "bun build src/cli/index.ts --outdir dist --target node"
-  },
   "devDependencies": {
     "@types/bun": "^1.3.14",
     "ajv": "^8.20.0",
-    "markdown-it": "15.0.1",
     "oxfmt": "0.57.0",
     "oxlint": "1.73.0",
     "typescript": "^5.9.0"