Local Setup
Local Setup
Document verified steps for preparing a local development environment.
Status: Partial implementation reference — Code-confirmed; operational validation pending
Last reviewed: 2026-10-19
Scope
Prerequisites, configuration, startup, validation and troubleshooting without secrets. The source-confirmed baseline below covers part of this scope; remaining operational details are unknown.
Current implementation baseline
The project consists of sibling repositories; it is not a single Worker package. Worker CI selects Node.js 22 and pnpm 12.11.2. Read each repository’s package scripts and test configuration before running commands; the SDK uses npm scripts and the backup tool has its own Node SQLite requirement.
Declared local Worker ports are Registration 8787, Corpus 8788, Ingress 8789, Resources 8790, Events 8791 and MCP 8792. Local bindings/overrides are defined in each wrangler.jsonc; these declarations alone do not initialize D1 schemas, history identity, secrets or all service processes.
Evidence: Registration config, Corpus config, MCP local profile and test environments. Use disposable state and test identities. A complete six-service startup/seed runbook remains to be validated; no startup command was executed here.
Structured-payload setup reproducibility — unverified
The original implementation report, cited in the historical evidence record, states that its clean-build checks reused installed dependencies and did not establish a fresh registry installation from the lockfile. Preserve that as a historical limitation: it is not evidence that a clean setup succeeds or fails today. The Corpus workflow declares a frozen-lockfile installation, but a workflow definition is not an execution record.
No reviewed execution artifact establishes reproducibility of the complete Corpus setup from a clean environment. Acceptance requires a separately authorized, disposable environment without inherited node_modules, recorded source/lockfile revisions and runtime/package-manager versions, the dependency retrieval/cache conditions, exact setup/check commands and actual outputs, and isolated schema/lineage/service/test-setting prerequisites. The package scripts and test setup define relevant checks and initialization; this note neither runs them nor supplies operational credentials.
Accountable role to assign: Corpus development/tooling maintainer, with the release owner deciding whether the evidence is a release prerequisite. Until accepted, contributor clean-setup confidence and release reproducibility remain unverified; no blanket release-blocking decision is recorded. A later run must be dated and tied to its own environment/revisions and cannot authenticate the original implementation runs. See the obligation handoff.
