flights_web/docs/superpowers/phase-1/rename-pass-plan.md

A1 rename-pass rework plan

Trigger. Phase 0 assumption A1 — "customer's standard remote-frontend module template" — resolves to a directory layout that differs from the one this repo uses.

Scope. Move/rename directories inside src/ to match the customer template. Update import paths only at the five frozen public barrels (see frozen-barrels.md). Do not restructure feature internals.

Preconditions.

• The frozen-barrel rule has been enforced since 1A-1 (Task 11) and 1A-3 ESLint rules are passing on main.
• Customer template document is in hand and reviewed for explicit directory conventions.

Steps (to be fleshed out when A1 resolves).

1. Create a target-layout scratch file mapping current path → new path for every file under src/.
2. Run the rename as a single automated pass (git mv) inside an isolated worktree.
3. Update tsconfig.json paths aliases if the top-level segments change.
4. Update vitest.config.ts aliases to match.
5. Update the five barrel files — this is the only hand-edit needed for consumer code.
6. Run pnpm typecheck && pnpm lint && pnpm test — green before commit.
7. Run all Phase 1 exit-gate checks (from master plan) — green before PR.
8. Single commit: Rename src/ layout to match customer module template (A1).

Escape valve. If the rename touches more than the five barrels, something violated the frozen-barrel rule between 1A-1 and now. Fix the violation first (move the cross-boundary import through a barrel), then retry the rename.

Owner. This task is attached to 1A-1's exit gate and fires on A1 resolution, whether that happens during Phase 1 or early Phase 2.