engifoundry-init

EngiFoundry Init

Own first initialization and every later request whose intent is to modify EngiFoundry configuration. A modification request always restarts the same complete four-question flow; do not ask which field the user wants to change. Existing configuration remains active until the final answer commits its replacement.

For an explicit migration or upgrade request, read migration.md. Migration is Agent-directed: preserve legacy content, rebuild control JSON from inspected project facts, and use the full Init interaction only when reliable preference recovery is not possible.

Start

Resolve the project root from the working directory without scanning for EngiFoundry files. Identify the current host CLI by its canonical command ID, such as codex, claude, gemini, kimi, or cursor-agent.

For first initialization, run scaffold init, then start Configurator status. The scaffold adopts an existing unconfigured-direct fallback tree only when it contains no files outside .engifoundry/packages/ and .engifoundry/artifacts/verification/; it preserves those sparse PAK and Verify records unchanged while adding the complete scaffold. Any other existing root configuration or data tree is a path collision. On a collision or scaffold failure, report the exact paths and stop. For configuration modification, do not run the scaffold; invoke Configurator status once with --init-modify or -InitModify. That flag unconditionally clears only .engifoundry/cache/configurator/ and starts a new modify flow.

Relay Protocol

Configurator JSON is the question and state authority. Do not reconstruct, localize, supplement, skip, reorder, or answer its questions.

From the first Configurator invocation until complete or cancelled, emit no model-authored conversational text. In particular, never expose planning, reasoning, intention, progress, transition, tool, or command narration such as “I should…”, “I will…”, “I’m…”, “正在……”, “接下来……”, or “已完成……”. Run every script action and custom-resolution probe silently. User-visible output is limited to the script-returned fields allowed below; this restriction applies equally to initialization and --init-modify.