eforge-init

# /eforge:init <!-- parity-skip-start --> Initialize eforge in this project. This setup configures an agent runtime profile and post-merge validation commands. You can use an existing local- or user-scope profile from any supported harness, or create a new project profile. When creating a new profile from this flow, the generated profile uses the Pi harness for all tiers, then creates it under `eforge/profiles/` and activates it. Also writes `eforge/config.yaml` for team-wide settings (postMergeCommands, etc.). <!-- parity-skip-end --> ## Welcome Before starting Step 1, print this welcome message to the user verbatim: > Welcome to eforge — an agentic build system that turns plans into code. You stay close to the code (planning, decisions) while eforge implements, blind-reviews, and validates in the background. > > This setup configures your agent runtime profile and post-merge validation commands. Then proceed to Step 1. ## Workflow ### Step 1: Determine postMergeCommands Inspect the project to figure out the right `postMergeCommands`: 1. Read `package.json` (if it exists) and note which scripts are available (e.g. `install`, `type-check`, `typecheck`, `test`, `build`, `lint`) 2. Detect the package manager from lockfiles: `pnpm-lock.yaml` -> pnpm, `yarn.lock` -> yarn, `package-lock.json` -> npm, `bun.lockb` -> bun 3. Build a suggested command list. Always start with the install command, then add validation scripts in order: type-check, test, build. For example: `["pn...