[M5-5] Migração de dados
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, node.js, postgresql, sqlite
Research direction
Start with ZAPFORGE_PLAN.md §4 and §9, then inspect the legacy data in luma_private.sqlite and luma_metrics.sqlite and the storage work in apps/lumabot. Confirm how the listed entities map to the new storage and how WhatsApp auth state is handled. Done means the data counts verify the migration and WhatsApp auth is migrated or a re-pairing procedure is documented, with all sub-issues complete.
Written by the indexing model from the issue text.
Description
Bridger · #M5-5 · Milestone M5 Luma + Dashboard · Pacote
apps/lumabot
Objetivo
Levar os dados do legacy para o storage novo sem perda.
Escopo
Cada item abaixo é uma sub-issue.
M5-5.1Script de migração dos bancos do legacy (luma_private.sqlite,luma_metrics.sqlite) para o storage novo (usuários, personas, lembretes, interações, métricas)M5-5.2Migração da sessão do WhatsApp (auth) ou procedimento de re-pareamento documentado
Critérios de aceite
- Usuários, personas, lembretes, interações e métricas migrados (verificado por contagem)
- Sessão do WhatsApp migrada ou procedimento de re-pareamento documentado
- Todas as sub-issues concluídas
DoD geral
Testes verdes; nenhum teste existente apagado/reescrito sem autorização; docs (COMO) atualizadas; ADR quando houver decisão arquitetural; changeset criado; Biome sem erros; benchmark sem regressão > 10% (a partir do M2).
Decisões relacionadas
- D14: StoragePort com SQLite e Postgres na v1; auth state no port
- D23: Migração incremental (legacy/)
- Tabela completa: BRIDGER_PLAN.md §4
Referência
- Dominant language
- JavaScript
- Stars
- 26
- Forks
- 6
- Avg merge
- 43m
- Merged PRs (30d)
- 137
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from murillous/LumaBot
-
area:plugin type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:plugin good first issue type:bug
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
area:plugin good first issue type:debt
Difficulty 3/5 1-2 days Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:plugin type:bug
Difficulty 3/5 1-2 days Newbie friendliness 54/100
Maintainers usually reply within 1 day
-
area:plugin type:feature
Difficulty 4/5 1-2 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
All issues in murillous/LumaBot
Similar issues
-
Place search spins forever when nominatim failsPossibly taken @jgt87 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
anvaka/city-roads#213 ·
-
mobile UX
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
jellyfin/jellyfin-web#8685 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
SchemaStore/schemastore#6535 ·
Maintainers usually reply within 1 day
-
enhancement good first issue helia storage tier-1
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
QMeshPy/distributed-quantum#53 ·
Maintainers usually reply within 1 day