Bundlekit

Standalone local MCP for docs-hub bundle IR:

• split / merge / check / normalize bundles
• render design Markdown
• validate legacy-dynamics YAML
• sync owned docs skills on init

Package is independent of Hubdocs, ArtifactGraph, and CodeGraph. They remain optional accelerators; missing optionals use the documented fallback and measurable bundlekit.missing-optional event contract.

Install

# from a local checkout (dev)
cd /path/to/bundlekit
pnpm install
pnpm build
pnpm link --global   # optional

cd /path/to/docs-hub
bundlekit init

Linux installer (after the repo is published):

curl -fsSL https://raw.githubusercontent.com/raintr91/bundlekit/main/install.sh | bash

Init

cd <docs-hub>
bundlekit init

The TTY wizard runs in three steps:

1. choose agents (detected agents are pre-selected; choosing none is valid)
2. optionally configure installed Hubdocs and/or ArtifactGraph toolkits (none means skip and add them later)
3. when Cursor and machine-local repo maps are present, wire cross-repo CodeGraph servers now or defer to platform-dna codegraph:wire

Bundlekit never downloads another toolkit implicitly. A selected optional toolkit that is not installed is reported as deferred without failing init. CodeGraph wiring is owned and performed by Platform DNA, not reimplemented inside Bundlekit.

Writes/updates:

• project-local MCP configs for the agents selected by the wizard
• owned skills/extracts/rules under .cursor/ (commit-worthy; not ignored wholesale)
• exact machine-local ignore entries (.bundlekit/, legacy-repos.local.json, platform-repos.local.json, written agent MCP paths such as .cursor/mcp.json)
• both machine-local map skeletons when missing (never overwrite member content)
• repo-only legacy-repos.json + example for optional brownfield evidence
• Bundlekit CLI aliases in package.json without replacing existing scripts
• no portable platform-repos*.json: that config is Platform DNA-owned

Configure repo maps (/configure-repo-maps)

After init, fill machine-local checkouts with natural language — do not hand-edit JSON. Prefer the Platform DNA skill when that toolkit is installed; Bundlekit ships a thin copy for independence. /legacy-spec Gaps when a legacy root is missing hand off here.

Platform example (writes platform-repos.local.json):

docs = base-docs ở ~/ws/base-docs; portal admin ở ~/ws/portal; api core ở ~/ws/api

Legacy example (writes legacy-repos.local.json, key legacy-*):

legacy ERP cũ ở D:\legacy\erp, key legacy-erp

For CI, use bundlekit init --yes; detected agents and the only supported lane (docs) are selected automatically, optional toolkits and CodeGraph are skipped by default. Use --with=hubdocs,artifactgraph (or --with=none) and --codegraph|--no-codegraph for explicit automation. --target, --type, --location, and --project-root remain available.

Tools

Tool	Purpose
bundle_split	*.bundle.yaml → ir/*
bundle_merge	ir/* → bundle
bundle_check	split drift check
bundle_split_all	batch split
bundle_normalize	normalize gen
docs_render / docs_render_common	design MD only
legacy_dynamics_validate	legacy dynamics schema

Owned skills

/spec · /update-spec · /update-spec-legacy · /legacy-spec · /configure-repo-maps · /bqa-grill-docs · /dev-grill-docs · /grill-with-docs

Lifecycle

The primary commands are:

bundlekit init                          # install in this docs hub
bundlekit deinit                        # remove this hub's owned harness + local MCP
bundlekit uninstall                     # preview global/all removal from anywhere
bundlekit uninstall --yes               # all tracked hubs + local/global MCP + CLI
bundlekit prune                         # dry-run
bundlekit prune --yes                   # delete only unmodified stale files

Interactive deinit/uninstall preview and confirm. Non-TTY runs are dry-runs unless --yes is passed. init records each destination in the XDG state ledger and records managed-file hashes in .bundlekit/install-manifest.json. Use bundlekit uninstall --discover <dir> to find installs created before the ledger existed.

Customized files and package scripts are preserved and reported. Bundlekit removes legacy-repos.json only when it created the file and its recorded hash is unchanged. Shared MCP/extract registries are unmerged without deleting other toolkits' entries. prune remains stale-only.

See mcp-package.json for tool/harness API compatibility.

Docs

• docs/INIT.md
• docs/INSTALL.md
• docs/LEGACY-DYNAMICS.md