linting-alignment
Linting Alignment
Alignment is repository-policy-first: stay as close as current upstream behavior permits while preserving local rules that still protect a real project constraint. Treat configuration as an executable ownership graph, not a list of familiar package names.
Infer the authorized mode from the request:
- Review — inspect and report; leave the worktree unchanged.
- Align — inspect, make focused changes, and validate. This is the default when the user asks to update, fix, migrate, or configure the toolchain.
- Publish — align, then commit, push, or open a review only when the user explicitly requests that boundary.
1. Establish repository authority
Resolve the repository root, active branch, working-tree status, and applicable root and scoped agent instructions. Read the repository's code-style, contribution, dependency, generated-file, and validation guidance that governs the affected scope.
Identify existing user changes before running tools. Derive the package manager, workspace layout, supported runtimes, base branch, and requested publication boundary from repository evidence rather than convention.
Complete when: the governing policy, validation entry points, branch boundary, and every pre-existing dirty file are identified.