Initialize a new Hivemind-powered project workspace, establishing the target directories, files, and initial configuration schemas to bootstrap the execution lifecycle. @.opencode/references/hm-coordination-contracts.md The output directory structure and configurations feed directly into the harness validation tools: 1. **doctor command**: Evaluates whether all expected directories and gitkeep files exist. 2. **all downstream workflows**: Rely on these target paths (`.opencode/`, `.hivemind/`, `.planning/`) for caching, session persistence, and lineage tracking. **CRITICAL: Structure-only setup.** This workflow initializes the workspace layout and minimal configurations. It does NOT generate business logic or source code files. Any attempts to write code beyond default templates/configs must be deferred. Parse process arguments ($ARGUMENTS): - Target project path (positional). - `--scope` (project or global config path, default: project). - `--force` (overwrite existing configs if present). Establish the directory structure recursively: - `.opencode/agent/` - `.opencode/skill/` - `.opencode/command/` - `.opencode/workflows/` - `.opencode/references/` - `.opencode/templates/` - `.hivemind/state/` - `.hivemind/logs/` - `.planning/phases/` Write empty `.gitkeep` files inside every newly created folder to ensure directory tracking is registered in git. Write the base configurations: 1. **configs.json** under `.hivemind/` matching default schema constraints. 2. **configs.schema.json** generated from the active Zod schema engine. 3. Write initial `version.json` in `.hivemind/state/` documenting package details. Invoke the `doctor` diagnostic suite to check the initialized directory structure and config schema integrity. - All target folders successfully created. - `.gitkeep` files exist in every subfolder. - `configs.json` and `configs.schema.json` compiled and validated. - Doctor check passes with green exit code.