docbridge 0.10.0 → 0.11.0

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
 
@@ -33,17 +33,22 @@ Declare documentation patterns and at least one supported code language:
 }
 ```
 
-Supported language keys are `typescript`, `swift`, `dart`, and `rust`. A project can
-enable more than one language, each with its own patterns.
+Supported language keys are `typescript`, `swift`, `dart`, `rust`, and `go`. A
+project can enable more than one language, each with its own patterns.
 
 Each language accepts an optional `visibility` array. Omitting it uses the
 scanner default: TypeScript `public` and `protected` members, Swift `public`
-and `open`, Dart `public` only, Rust unrestricted `pub`. A declaration
-excluded by visibility is not an endpoint; an `@doc` on one is
+and `open`, Dart `public` only, Rust unrestricted `pub`, Go `exported`. A
+declaration 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.
+per-language rules, including Dart's leading-underscore privacy and Go's
+exported-name rule for methods.
 
-<!-- @code src/core/glob.ts#collectFiles -->
+The configuration has no `exclude` list and no glob negation. Narrow the
+positive patterns instead; for Go, `cmd/**/*.go` and `internal/**/*.go` scan
+fewer files than `**/*.go`, but `_test.go` files under them are still scanned.
+
+<!-- @code src/shared/glob.ts#collectFiles -->
 
 ## Excluded files
 

package/docs/user/getting-started.md

@@ -1,5 +1,5 @@
 ---
-description: Set up DocBridge in an existing TypeScript, Swift, Dart, or Rust project.
+description: Set up DocBridge in an existing TypeScript, Swift, Dart, Rust, or Go project.
 ---
 
 # Getting Started

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
 
@@ -72,6 +72,13 @@ void login(String email, String password) {}
 pub fn login(email: &str, password: &str) {}
 ```
 
+```go
+// Login starts the login flow.
+//
+// @doc docs/auth.md#login-flow
+func Login(email, password string) error { return nil }
+```
+
 Paths are relative to the configured root. An annotation on an unsupported or
 visibility-excluded declaration produces `unsupported_declaration`; the same
 declaration without an annotation is ignored.
@@ -114,7 +121,26 @@ 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 -->
+### Go declarations
+
+Supported forms are package-level functions, types (including aliases),
+constants, and variables, plus receiver methods and interface methods. The
+annotation goes in the declaration's doc comment, as `//` lines or one
+`/* */` block. Visibility defaults to `exported`; configure `unexported` to
+include unexported names. A method counts as exported only when both its name
+and its receiver or interface type name are exported. IDs use `.`
+qualification without type parameters, such as `AuthService.Login` and
+`List.Push` for `func (l *List[T]) Push`.
+
+Inside a `const (`, `var (`, or `type (` group, annotate the individual spec;
+an `@doc` in the comment above the group keyword, or above a spec that
+declares several names (`var a, b int`), is `unsupported_declaration` because
+it cannot name one endpoint. Struct fields, embedded fields, the `package`
+clause, imports, `init`, and `_` are not endpoints. The scanner is syntactic:
+`_test.go` files and `//go:build`-constrained files are scanned whenever the
+patterns match them.
+
+<!-- @code src/scan/markdown/markdown.ts#scanMarkdown -->
 
 ## Documentation to code
 
@@ -144,7 +170,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

@@ -30,7 +30,7 @@ delete it. See [Linking](linking.md) for its format.
 
 ## Scanner errors
 
-Swift, Dart, and Rust use packaged scanner workers. A
+Swift, Dart, Rust, and Go use packaged scanner workers. A
 `code_scanner_unavailable` diagnostic usually means the installed package
 lacks a binary for the current platform or the binary cannot execute.
 Reinstall the package first. If the platform is not supported, run DocBridge
@@ -41,9 +41,11 @@ converting it into a broken link. Check that the source parses with the
 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
+`code_parse_error` means a TypeScript, Swift, Dart, Rust, or Go source file has a
+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.10.0",
+  "version": "0.11.0",
   "description": "A CLI that links Markdown specifications and code declarations. Runs on Node.js and Bun.",
   "keywords": [
     "bun",

package/schemas/common-output.schema.json

@@ -44,7 +44,7 @@
         "target": { "type": "string" },
         "language": {
           "type": "string",
-          "enum": ["typescript", "swift", "dart", "rust"]
+          "enum": ["typescript", "swift", "dart", "rust", "go"]
         },
         "source": { "type": "string" },
         "message": { "type": "string" },

package/schemas/context-output.schema.json

@@ -35,7 +35,7 @@
           },
           "language": {
             "type": "string",
-            "enum": ["typescript", "swift", "dart", "rust"],
+            "enum": ["typescript", "swift", "dart", "rust", "go"],
             "description": "Code language for code context blocks."
           },
           "startLine": {

package/schemas/docbridge.schema.json

@@ -21,7 +21,8 @@
             "typescript": { "$ref": "#/$defs/typescriptEntry" },
             "swift": { "$ref": "#/$defs/swiftEntry" },
             "dart": { "$ref": "#/$defs/dartEntry" },
-            "rust": { "$ref": "#/$defs/rustEntry" }
+            "rust": { "$ref": "#/$defs/rustEntry" },
+            "go": { "$ref": "#/$defs/goEntry" }
           }
         },
         "docs": {
@@ -123,6 +124,28 @@
           }
         }
       }
+    },
+    "goEntry": {
+      "type": "object",
+      "additionalProperties": false,
+      "required": ["patterns"],
+      "properties": {
+        "patterns": {
+          "type": "array",
+          "minItems": 1,
+          "items": {
+            "type": "string",
+            "pattern": "\\.go$"
+          }
+        },
+        "visibility": {
+          "type": "array",
+          "items": {
+            "type": "string",
+            "enum": ["exported", "unexported"]
+          }
+        }
+      }
     }
   }
 }

package/schemas/graph-output.schema.json

@@ -31,7 +31,7 @@
           },
           "language": {
             "type": "string",
-            "enum": ["typescript", "swift", "dart", "rust"],
+            "enum": ["typescript", "swift", "dart", "rust", "go"],
             "description": "Code language for code nodes."
           },
           "location": { "$ref": "common-output.schema.json#/$defs/location" },

package/schemas/scanner-worker.schema.json

@@ -7,7 +7,7 @@
   "$defs": {
     "language": {
       "type": "string",
-      "enum": ["typescript", "swift", "dart", "rust"]
+      "enum": ["typescript", "swift", "dart", "rust", "go"]
     },
     "codeSymbol": {
       "type": "object",