sdlc-align

# sdlc-align The **window** check. Every other alignment gate in LoopSmith looks at one unit of work: `sdlc-plan-review` §4 holds a single plan to the north-star, and `sdlc-retro` asks what a single goal taught. Neither can see the shape of *twenty* goals, and that is where strategy actually drifts — no single decision violates the direction, but the trajectory has moved. **Read-only.** It produces a report and lets the user pick the reconciliation direction. It never edits the north-star, the goals, or any code. **Gate — a no-op without a north-star.** If `.sdlc/context/north-star.md` is absent, there is no stated direction to drift from: say so in one line and stop. (Drop-in projects skip this entirely, the same way `sdlc-plan-review` §4 does.) If it exists but states no priorities or bets, say that instead — the fix is `/sdlc-vision`, not a drift report. ## The window Default to everything since the previous report in `.sdlc/knowledge/align/`, or the last ~10 completed goals if there is none. State the window explicitly in the report; a finding is only as good as the span it was drawn from. Gather what actually shipped in it: - **Goals** — `.sdlc/goals/*.md` with `status: done` (local), or closed `sdlc:goal` issues (github). Include the parked ones too — `status: parked` locally, `sdlc:parked` on GitHub. Work that was started and abandoned still spent effort in a direction, and a *cluster* of parks on one theme is itself a drift signal: it usually means the back...