blueprintlisted

# Blueprint ## Constraints - Apply `@rules/git/general.mdc` — branch, commit, and PR conventions below come from it. - Apply `@rules/compound-engineering/general.mdc` — the plan is durable memory the next agent reuses, not throwaway prose. - Apply `@rules/compound-engineering/general.mdc` *Assign the most relevant existing label when creating a tracker issue* for any tracker issue this plan creates or hands off to `@skills/create-issues-from-text/SKILL.md` to create. - Apply `@rules/laravel/architecture.mdc` when the project uses `pekral/arch-app-services`, so each step lands in the correct layer. - Plan only. Do not implement, commit, or push any step. - Output Markdown only. English only. - Every step must be one pull request: independently reviewable and mergeable on its own. - Break the objective into 3-12 steps. Fewer means it likely fits one PR; more means the objective is too broad and should be split first. - Each step must be executable cold by `@skills/resolve-issue/SKILL.md` or a fresh agent with no prior context. - Do not invent dependencies on tooling that may be absent. Degrade gracefully when GitHub CLI (`gh`) is missing. ## Use when - An objective clearly exceeds one pull request (a migration, a multi-layer feature, a cross-cutting refactor). - Work will span multiple sessions or multiple agents and needs a sequenced, resumable plan. - You need to know which parts can run in parallel and which must be sequential before starting. Do not use for single-PR tas