init

To initialize a project configuration and architecture baseline, you can run an interactive or automated setup command that pre-discovers existing settings and generates the necessary configuration files. This establishes a stable architecture baseline before planning or execution begins.

The best way to import Git history into a pipeline configuration is to use the import-history flag during initialization. This allows the system to scan and integrate past commits into the project state file for ongoing work.

Yes, you can rescan a project to update rules and state files without losing existing configuration overrides. The rescanning process reuses settings from previous snapshots and project configs, updating the pipeline directory while preserving your specific rule presets.

Pipeline initialization works seamlessly with empty projects by applying built-in defaults and global configurations. You do not need pre-existing configuration files, as the process generates the required pipeline directory, config, and state files from scratch.

You can set up worker separation and apply rule presets during project configuration by using the interactive initialization mode. This mode generates or updates the rules file with project-specific overrides, ensuring proper worker separation settings.

Automated pipeline setup fails to read local defaults if the configuration file is missing or improperly formatted. The initialization process expects to read local defaults from a specific YAML config file in the user's home directory to properly apply standardized pre-checks.