craft-install

Run the install flow, which infers applicable stacks from pyproject.toml, package.json, and tsconfig.json, presents what each profile level enables, and writes the rendered configuration only after an explicit yes. There is no default level; the choice is always confirmed.

Each level binds a different number of properties and rules, with the manifest reporting rule counts, how many declare an automatic fix, and how many properties remain unenforced. Strict binds more properties that standard leaves unenforced.

Yes, a React profile needs six ESLint plugins added as dev dependencies using the package manager command named by the control register for the repository's lockfile. Python needs none because ruff ships every selected rule.

It stops when a pin is malformed or ahead of the manifest, when a select key or config file is owned by someone else, or when a later configuration file in the search order would override the write. Every refusal writes nothing and reports the exact condition.

A second run compares the pinned version against the manifest, the file bytes against the rendered artefact, and current stack inference against the stamp. When all three agree it writes nothing; differences are reported rather than silently overwritten.

No, it only writes rule selections into configuration the linter already reads; enforcement and wiring of lint gates belong to the control register. It also writes an unenforced residue file listing properties no linter can decide.