working-with-lacquer

Exit 3 means a lacquer-managed file was edited locally and sync would clobber it. Either upstream the change to the lacquer repo, add the file to `[project].exclude` with a reason if the project owns it, or run `lacquer sync --force` to take the lacquer's version.

Exit 6 means the project runs a stack that `.lacquer.toml` does not declare, leaving that toolchain with no hooks, CI, or CLAUDE region. Run `lacquer adopt` to record the stack additively, then `lacquer sync`, or exclude the path if it is deliberately unmanaged.

Add the path to `[project].exclude` in `.lacquer.toml` with a required `reason` field, plus an `until` date if the exclusion is temporary. An expired `until` becomes a hard audit failure with exit 4, and exclusions matching nothing the lacquer ships are flagged as stale.

Use `exclude` when one project genuinely owns a single managed file. Use `[project].retired` with `since` and `reason` when the whole project is over: it stops scheduled workflows and Dependabot while keeping PR CI, lint configs, and hooks syncing so the repo still audits clean.

Create a roster TOML file listing each project's name and path, then run `lacquer fleet --roster fleet.toml` for a summary or add `--json` for a diffable snapshot. It exits 4 if any project would fail its own audit and highlights expiring exemptions and multiply-excluded paths.

A `[baseline.relax]` entry requires both `until` and `reason`, and an expired entry is a hard failure with exit 4 by design. Either meet the baseline standard or update the entry with a new justified date rather than removing the expiry, which would redefine the standard.