Directories
¶
| Path | Synopsis |
|---|---|
|
Package buildpkg implements the `dockyard build` pipeline — the step that turns a Dockyard project into the shippable artifact (RFC §14).
|
Package buildpkg implements the `dockyard build` pipeline — the step that turns a Dockyard project into the shippable artifact (RFC §14). |
|
Package changelogx parses Dockyard's top-level CHANGELOG.md and extracts one version's section as plain Markdown (Phase 30 — V1 release engineering).
|
Package changelogx parses Dockyard's top-level CHANGELOG.md and extracts one version's section as plain Markdown (Phase 30 — V1 release engineering). |
|
cmd/changelogx
command
Command changelogx serves the release pipeline's CHANGELOG needs:
|
Command changelogx serves the release pipeline's CHANGELOG needs: |
|
Package cli is the cobra command tree for the dockyard CLI (RFC §9).
|
Package cli is the cobra command tree for the dockyard CLI (RFC §9). |
|
Package clidocs is the small helper that renders the dockyard CLI command tree as a Markdown page for the published documentation site (Phase 29 — docs/site/cli/index.md).
|
Package clidocs is the small helper that renders the dockyard CLI command tree as a Markdown page for the published documentation site (Phase 29 — docs/site/cli/index.md). |
|
cmd/clidocs
command
Command clidocs renders the dockyard CLI reference to a Markdown file.
|
Command clidocs renders the dockyard CLI reference to a Markdown file. |
|
Package codegen turns Go contract structs into downstream artifacts — the spine of Dockyard's contract-first property (P1, RFC §6.1).
|
Package codegen turns Go contract structs into downstream artifacts — the spine of Dockyard's contract-first property (P1, RFC §6.1). |
|
Package coveragecheck is the mechanical coverage gate (Phase 21.5).
|
Package coveragecheck is the mechanical coverage gate (Phase 21.5). |
|
cmd/coveragecheck
command
Command coveragecheck is the mechanical coverage gate's entry point: it reads a Go coverage profile and a threshold config, compares each package's statement coverage against its required band, prints a report, and exits non-zero on a shortfall (or on an unconfigured package).
|
Command coveragecheck is the mechanical coverage gate's entry point: it reads a Go coverage profile and a threshold config, compares each package's statement coverage against its required band, prints a report, and exits non-zero on a shortfall (or on an unconfigured package). |
|
Package devloop is the embedded fsnotify dev orchestrator behind the `dockyard dev` command (RFC §9.2).
|
Package devloop is the embedded fsnotify dev orchestrator behind the `dockyard dev` command (RFC §9.2). |
|
Package generate is the engine behind `dockyard generate` — the contract-first code generation verb (RFC §6, §9.1).
|
Package generate is the engine behind `dockyard generate` — the contract-first code generation verb (RFC §6, §9.1). |
|
Package inspector implements the host-side core of Dockyard's local inspector — the single test/debug surface for exercising an MCP server and its Apps without a real host (RFC §12).
|
Package inspector implements the host-side core of Dockyard's local inspector — the single test/debug surface for exercising an MCP server and its Apps without a real host (RFC §12). |
|
Package installpkg implements the `dockyard install` verb — registering a built Dockyard server with an MCP host (RFC §14).
|
Package installpkg implements the `dockyard install` verb — registering a built Dockyard server with an MCP host (RFC §14). |
|
Package manifest is the typed schema, loader, and structural validator for dockyard.app.yaml — Dockyard's control plane (RFC §4.2).
|
Package manifest is the typed schema, loader, and structural validator for dockyard.app.yaml — Dockyard's control plane (RFC §4.2). |
|
Package protocolcodec is Dockyard's single isolation seam for every MCP extension wire format.
|
Package protocolcodec is Dockyard's single isolation seam for every MCP extension wire format. |
|
Package releasebuild drives the Dockyard release pipeline — the step the `.github/workflows/release.yml` workflow runs on a `v*` tag push to produce the cross-compile artifacts attached to the GitHub Release (Phase 30 — V1 release engineering, RFC §14).
|
Package releasebuild drives the Dockyard release pipeline — the step the `.github/workflows/release.yml` workflow runs on a `v*` tag push to produce the cross-compile artifacts attached to the GitHub Release (Phase 30 — V1 release engineering, RFC §14). |
|
cmd/releasebuild
command
Command releasebuild drives Dockyard's V1 release pipeline — the step the `.github/workflows/release.yml` workflow runs on a `v*` tag push.
|
Command releasebuild drives Dockyard's V1 release pipeline — the step the `.github/workflows/release.yml` workflow runs on a `v*` tag push. |
|
Package runpkg implements the `dockyard run` verb — running a Dockyard project's MCP server on a chosen transport (RFC §14, §9.1).
|
Package runpkg implements the `dockyard run` verb — running a Dockyard project's MCP server on a chosen transport (RFC §14, §9.1). |
|
Package scaffold implements `dockyard new` — the no-template project scaffold (RFC §9.1, §10).
|
Package scaffold implements `dockyard new` — the no-template project scaffold (RFC §9.1, §10). |
|
Package skillcheck validates SKILL.md files against the agentskills.io Agent Skills specification (https://agentskills.io/specification).
|
Package skillcheck validates SKILL.md files against the agentskills.io Agent Skills specification (https://agentskills.io/specification). |
|
cmd/skillcheck
command
Command skillcheck validates a tree of Dockyard agent skills against the SKILL.md format (agentskills.io specification).
|
Command skillcheck validates a tree of Dockyard agent skills against the SKILL.md format (agentskills.io specification). |
|
Package testgate is the engine behind `dockyard test` — the contract + compliance gate (RFC §9.1, §9.4).
|
Package testgate is the engine behind `dockyard test` — the contract + compliance gate (RFC §9.1, §9.4). |
|
Package validate is the engine behind `dockyard validate` — the quality-gate verb (RFC §9.4).
|
Package validate is the engine behind `dockyard validate` — the quality-gate verb (RFC §9.4). |
Click to show internal directories.
Click to hide internal directories.