State and upgrades
Managed-file checksums, conflict detection, and the current upgrade policy.
State file
.stackiln/state.json records the state format, Stackiln version, preset, manifest hash, installed recipe versions and statuses, applied operations, and every managed file's owner and SHA-256 checksum.
Keep the state file committed. It contains no application secrets.
Changed managed files
A changed managed file is not automatically an error. It often means the product has correctly diverged from its generated starting point. The important rule is that later Stackiln operations must not silently overwrite it.
pnpm stackiln doctor ./my-product
Upgrades today
Automatic upgrade and conflict-proposal commands are not implemented. To adopt a newer Stackiln change, back up the product, generate a separate reference product with the same options, and review the relevant differences manually.
Do not replace a customised file solely because its owner is listed as base or a module.
Removing modules
Removal operations are not implemented. Recipe metadata still declares whether removal is stateless or requires archival so future tooling can produce a safe plan.