Gen 2 migration Subtask 3: Decommission Gen 1, resume paused schema epic

Story Points: 2

# How?

Part of #292 (Amplify Gen 1 → Gen 2 Rebuild). Full detail in `.claude/plans/can-you-make-a-shimmying-crane.md`, Phase 6. Depends on the Phase 5 sub-issue (alpha cutover) completing its full bake period with the canary workflow green.

1. Remove `amplify/backend/*` (Gen 1 CloudFormation tree) and any now-unused Gen 1 CI steps.
2. Rename `amplify-gen2/` → `amplify/` (single atomic rename — this was the reason Gen 2 was built in parallel at a temporary path rather than in-place, to keep Gen 1 fully intact and deployable as a rollback path for the entire migration window).
3. Update any remaining path references (`backend-build.js`/`backend-build-gen2.js` split, docs, CLAUDE.md's description of the `amplify/` vs `amplify-gen2/` tree) to reflect the new single tree.

**Once this lands, resume the paused work**: the backend schema epic (#244 and subtasks #245/#247/#248, plus #258/#52/#51/#213) and the new-frontend plan, both paused pending this rebuild since it deliberately kept `ts-code/src` (business logic) untouched while the surrounding infra changed shape entirely.

Leia o plano de migração em `.claude/plans/can-you-make-a-shimmying-crane.md`, concentrando-se na Fase 6. Entenda as estruturas de diretórios atuais de `amplify/backend/` e `amplify-gen2/`. Verifique `backend-build.js` e `backend-build-gen2.js` em busca de referências a caminhos. O trabalho envolve excluir o diretório antigo do Gen 1, renomear o diretório do Gen 2 e atualizar todos os scripts de build e a documentação relacionados. Verifique se o canary workflow está verde antes de começar.

Escrita pelo modelo de indexação a partir do texto da issue.