simone
f7eb7eec23
.planning/ documentava in dettaglio cio che era vecchio e per niente cio
che e in produzione: le fasi 11-22 (v2.1 e v2.2, chiuse a giugno) erano
ancora in phases/ mentre v1.0 e v2.0 stavano gia in milestones/, e il
lavoro degli ultimi due mesi - gate OTP e ciclo di vita dei retainer, cioe
quello che gira su hub.iamcavalli.net - non aveva nessuna cartella.
- phases/{11,12,14} -> milestones/v2.1-phases/, phases/{18..22} ->
milestones/v2.2-phases/. Ora phases/ contiene solo la milestone in
corso, che e quello che state.cjs conta per il progresso
- v2.1-ROADMAP.md ricostruito: era l'unica milestone senza archivio,
interrotta dal reset del 19/06 e mai chiusa formalmente
- v2.3-ROADMAP.md + v2.3-REQUIREMENTS.md: v2.3 e stata eseguita fuori dal
ciclo GSD, non esistono PLAN/SUMMARY per fase. L'archivio E la doc
- REQUIREMENTS.md riscritto per v2.4 con il backlog reale
- phases/13 e phases/26: SUMMARY ricostruiti da commit, migration e
STATUS.md. 26 e il primo numero libero
- research/: cancellate 4 varianti dello stesso PITFALLS e FEATURES/
SUMMARY, superati da PROJECT.md. Diverse anti-feature erano ormai
contraddette dai fatti (il Kanban e stato costruito in Phase 19,
l'email in v2.3, il time tracking esiste)
- cancellati UI-RULES.md e DESIGN-SYSTEM.md (CLAUDE.md li dichiara
superseded: impongono l'inverso della regola attuale) e HANDOFF.md,
fermo al 13/06
- SECURITY-*.md -> security/: audit chiuso, ma i report restano la doc di
cosa e stato ruotato e perche
- PROJECT.md/MILESTONES.md/ROADMAP.md allineati: milestone corrente v2.4,
sessione OTP 90gg non 30, migrazioni fino alla 0016
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2.2 KiB
Deferred Items — Phase 14 (crm-attio-style-fix)
Items discovered during execution that are out of scope for the current task/plan and deferred for future cleanup.
From Plan 14-01
-
src/app/admin/leads/actions.ts:54— pre-existing@typescript-eslint/no-explicit-anyerror onconst updateData: Record<string, any> = { updated_at: new Date() };insideupdateLead(). This function predates Phase 14 and is unchanged by 14-01 (Task 2 only appendsupdateLeadField/addLeadTag/removeLeadTag/renameLeadTagafter it).npx eslint src/app/admin/leads/actions.tsexits 1 solely due to this pre-existing line; the four new actions added in 14-01 introduce zero new lint errors/warnings. Fix: replaceRecord<string, any>with a properly typed partial update object (e.g.Partial<typeof leads.$inferInsert>or an explicit interface). -
src/lib/admin-queries.ts— pre-existing@typescript-eslint/no-unused-varswarnings (4x) for importssettings,ServiceCatalog,ProjectOffer,OfferPhaseService— these predate Phase 14 and are unrelated to thegetLeadsWithTags/getLeadFieldOptionsadditions in Task 1.
From Plan 14-03
| File | Lines | Issue | Reason Deferred |
|---|---|---|---|
src/components/admin/leads/SendQuoteModal.tsx |
39, 48 | @typescript-eslint/no-explicit-any on useForm<any>() and onSubmit(data: any) |
Pre-existing (not introduced by CRM-12's dead-branch removal). Attempted fix: typing useForm<AssignQuoteInput>() with AssignQuoteInput = z.infer<typeof assignQuoteSchema> (local schema has .optional()/.default() on generate_new) triggers a cascading zodResolver/Resolver<...> generic-incompatibility TS error (3 errors, TS2322/TS2345) between @hookform/resolvers/zod and react-hook-form@7.75's 3-generic Resolver type — same family of issue fixed for LeadForm.tsx's FormField in 14-03 Task 2, but here it surfaces in the resolver/schema layer (input vs output type divergence from .default()), not the FormField component. Resolving it would require either restructuring assignQuoteSchema's optional/default fields or adding resolver-boundary type assertions — out of scope for CRM-12 (isolated dead-code removal). |