Directories
¶
| Path | Synopsis |
|---|---|
|
Package main hosts the `harbor` CLI binary.
|
Package main hosts the `harbor` CLI binary. |
|
init
Package harborinit ships the `harbor init` engine.
|
Package harborinit ships the `harbor init` engine. |
|
scaffold
Package scaffold implements the `harbor scaffold` engine — the template registry, the renderer, and the on-disk writer.
|
Package scaffold implements the `harbor scaffold` engine — the template registry, the renderer, and the on-disk writer. |
|
Command harbor-gen-protocol-docs emits the four generated Protocol contract-reference pages (`methods.md` / `events.md` / `errors.md` / `types.md`) into docs/site/protocol/ from the canonical single sources the Runtime compiles from (RFC §5):
|
Command harbor-gen-protocol-docs emits the four generated Protocol contract-reference pages (`methods.md` / `events.md` / `errors.md` / `types.md`) into docs/site/protocol/ from the canonical single sources the Runtime compiles from (RFC §5): |
|
harbor-mcptest-stdio is a minimal MCP stdio server used by the integration test.
|
harbor-mcptest-stdio is a minimal MCP stdio server used by the integration test. |
|
Command harbor-protocol-ts-lockstep emits the committed wire-surface manifest (web/console/src/lib/protocol/wire-manifest.gen.json) from the canonical Harbor Protocol single sources (RFC §5):
|
Command harbor-protocol-ts-lockstep emits the committed wire-surface manifest (web/console/src/lib/protocol/wire-manifest.gen.json) from the canonical Harbor Protocol single sources (RFC §5): |
|
Command harbor-protocol-ts-types emits a vendorable, external-client TypeScript wire-type module from the canonical Harbor Protocol single sources (RFC §5):
|
Command harbor-protocol-ts-types emits a vendorable, external-client TypeScript wire-type module from the canonical Harbor Protocol single sources (RFC §5): |
Click to show internal directories.
Click to hide internal directories.