Doc Bridge v1.3.0 — deterministic handoffs for VitePress, Starlight, Nextra, and Nx

Coding agents can read a repository and still make the wrong change. Documentation pages do not automatically tell an agent which package owns the work, which paths are safe to edit, or which checks prove the result.

Doc Bridge turns that scattered context into one deterministic handoff:

{
  "startHere": "docs/for-agents/packages/auth.md",
  "editRoots": ["packages/auth"],
  "checks": ["pnpm --filter @demo/auth test"],
  "humanDoc": "/docs/guides/auth"
}

Version 1.3.0 extends that bridge to more of the documentation and monorepo stacks JavaScript teams already use.

What is new

• VitePress: maps configured content roots, clean URLs, index pages, prefixes, and declarative exclusions.
• Astro Starlight: maps content roots, explicit slugs, drafts, index pages, and partial-file exclusions.
• Nextra: maps content or src/content, contentDirBasePath, index routes, and deterministic route collisions.
• Nx: discovers static project metadata and available test or lint targets from workspace manifests.

Why this is different

The adapters do not import documentation frameworks, execute next.config, load themes, run Nx plugins, or evaluate project code. They read bounded declarative files and produce the same handoff contract already used by the CLI, MCP server, and CI gates.

The core path still requires no LLM, provider account, hosted service, or API key. A model can consume the result, but it does not decide repository ownership or invent the validation command.

Try it now

npx -y @agentskit/doc-bridge@1.3.0 demo --text

Then start from the example closest to your repository:

• Nx: examples/nx-monorepo.config.ts
• VitePress: examples/vitepress-only.config.ts
• Astro Starlight: examples/starlight-only.config.ts
• Nextra: examples/nextra-only.config.ts

Documentation: https://doc-bridge.agentskit.io/?utm_source=github_release&utm_medium=owned&utm_campaign=docbridge_adapters_1_3_0

Source: https://github.com/AgentsKit-io/doc-bridge

npm: https://www.npmjs.com/package/@agentskit/doc-bridge/v/1.3.0

Provenance: https://registry.npmjs.org/-/npm/v1/attestations/@agentskit%2fdoc-bridge@1.3.0

Full changelog: v1.2.6...v1.3.0

If a route does not match your real documentation site, open an issue with the smallest reproducible layout. Suggestions, critical feedback, adapter contributions, and stars are welcome.

Doc Bridge v1.2.6 — deterministic handoffs for Claude Desktop

Agents should not have to guess which package they may edit, where the relevant documentation lives, or which checks prove a change is safe.

Doc Bridge turns repository docs, ownership metadata, and human documentation into deterministic handoffs that work from the CLI, MCP, and CI. Its core runs locally without an LLM, API key, hosted service, or model-provider dependency.

What ships in 1.2.6

• Claude Desktop MCP Bundle: the release includes doc-bridge-1.2.6.mcpb, exposing eight read-only tools behind an explicit project configuration boundary.
• Executable repository handoffs: agents receive startHere, allowed editRoots, required checks, and the matching human documentation instead of guessing.
• Secure release recovery: dependency overrides now work with pnpm 11, with patched Next.js, Sharp, and brace-expansion versions. The release gate completed with no known vulnerabilities.
• Two installation paths: use the npm package for CLI, CI, and custom MCP clients, or the MCPB artifact for the Claude Desktop connector workflow.

Try the deterministic path

npm i -D @agentskit/doc-bridge@1.2.6
npx ak-docs demo --text

Then configure a repository:

npx ak-docs init
npx ak-docs index
npx ak-docs query package example --agent

The packaged bundle currently declares macOS compatibility. Its manifest, privacy boundary, archive inventory, and all eight read-only tools passed automated validation; installation verification inside Claude Desktop remains the next distribution gate.

Artifact integrity

• doc-bridge-1.2.6.mcpb — SHA-256 9136d4a487b44f0a56731fac89d880525ad5e216d376940dff949477cd741905
• npm provenance — SLSA attestation

Documentation: doc-bridge.agentskit.io
Implementation: PR #69
Full changelog: v1.2.5...v1.2.6

If your repository has a workflow Doc Bridge cannot express yet, open an issue with the handoff you expected. That feedback directly shapes the next contracts and adapters.

v1.2.2 — seven-product properties + ecosystem llms block

What's new

• Ecosystem contract accepts 4- or 7-product properties[] projections
• Export formatEcosystemLlmsBlock for a shared llms.txt ecosystem section
• Unit coverage for the shared formatter

Includes #45.

v1.1.1

What's Changed

• ci: publish verified stable releases with provenance by @EmersonBraun in #32
• chore: prepare Doc Bridge 1.1.1 by @EmersonBraun in #33

Full Changelog: v1.1.0...v1.1.1

v1.1.0 — Documentation Standard v1

Doc Bridge 1.1.0 ships the stable, HITL-approved Documentation Standard v1.

Highlights:

• deterministic seven-required/two-recommended conformance profile
• JSON and human-readable CLI reports with actionable remediation
• auditable approved exceptions
• generated llms.txt freshness enforcement
• canonical AgentsKit ecosystem manifest and claims validation
• static JS/TS configuration parsing without code execution
• bounded, symlink-safe documentation traversal
• upstream contract parity in CI

Validation: 187 tests, 90.45% statement coverage, build, package dry run, packaged smoke, conformance dogfood, and upstream parity.