nebrius

Use when ESLint or Oxlint reports a violation from an `import-integrity/` rule, with messages like "must be imported in another file", "must be imported by non-test files", "does not point to a valid first party export", "is not listed in package.json", "Imports/reexports cannot form a cycle", "Test code should not be imported in production code", "Entry point exports should be not imported", or "Default import alias must not have the same name as a named export". Explains the correct fix for each rule, which obvious fixes are wrong, and when a violation needs a human decision instead of a code change.

Use when `legacy-lint-manager validate` fails, locally or in CI, with errors like "cannot be disabled", "New legacy entries cannot be added", "Duplicate legacy ID", "Unregistered legacy error", "Malformed legacy comment", "is not defined in the database", or "does not match ... the compare config". Also use when resolving a merge conflict on the legacy lint database file (default `legacy-lint.data.json`). Explains which failures mean fix-the-code, when to run validate --update, which resolutions are forbidden, and how to resolve database merge conflicts safely.