Develop

[EfeDeveloper]

This pull request updates the month initialization logic and UI for the Dashboard and Gastos views to address issues with manual expenses and template-driven flows. The main goal is to ensure the "Iniciar mes" (Start Month) action is only shown when appropriate, and to provide clear, actionable feedback when users attempt to initialize a month without any templates. No backend or data model changes are made; all modifications are in UI logic and user feedback.

UI Logic & Behavior Updates:

• The top-level "Iniciar mes" action is now only visible if the current period has at least one expense, and is hidden in the empty month state. This applies to both Dashboard and Gastos views. [1] [2] [3] [4] [5]
• A new derived state, hasMonthInitializedFromTemplates, is added to the expense store to track whether any non-manual expenses exist for the period. This is used to control CTA visibility. [1] [2]

User Feedback Improvements:

• When users click "Iniciar mes" but have no templates, a toast/alert is shown instead of a persistent warning. This feedback is only triggered on click, not shown permanently in the UI. [1] [2] [3]
• Toasts are used for all feedback related to month initialization (success, warnings, errors), replacing the previous initMessage logic.

Documentation & Specification:

• Design, proposal, and spec documentation are updated to reflect the new requirements, rationale, and UI behavior for month initialization. This includes detailed scenarios and goals in Markdown files. [1] [2] [3] [4] [5]

Technical & Dependency Changes:

• The vue-sonner package is integrated for toast notifications, and its styles are imported in the main entry point. [1] [2]

These changes ensure a more intuitive and correct experience for users initializing months, especially when mixing manual and template-driven expenses.