Add Gherkin feature specs for editable tables, accumulation, and background processing

Three existing features were missing Gherkin scenarios for behaviors already supported by the codebase. Two new feature files cover cross-export deduplication and progressive streaming.

crm_card.feature: add 3 scenarios for editable payments, trips, and documents tables. The app already renders gr.Dataframe components with interactive=True (app.py:617-643) and the crm_tables presenter; these scenarios pin that contract.

dashboard.feature: add 2 scenarios for last-10-messages overview and chatbox Q&A. The app already has a chatbox wired to DashboardInteractor.stream() (app.py:588-603) which answers queries like 'a Maria ja pagou tudo?' using aggregated data.

accumulation.feature (new): 4 scenarios covering cross-export merge behavior. BuildCrmCard already deduplicates payments by (payer, amount, date), trips by locator, messages by (contact, text, timestamp), and preserves pipeline stage (build_crm_card.py:366-421). These scenarios document the merge invariants.

background_processing.feature (new): 3 scenarios for progressive UI updates. BuildCrmCard.process_streaming() yields snapshots at each stage (image, audio, documents, assemble, done) while the status panel updates alongside (build_crm_card.py:86-96, app.py:520-546). One scenario also asserts that the chatbox search remains independently usable during processing.

features/accumulation.feature

@@ -0,0 +1,27 @@
+Feature: Cross-export data accumulation
+  As the agency owner
+  I want to upload multiple exports for the same customer without duplication
+  So that the CRM card stays clean and complete
+
+  Scenario: Merge payments from two exports
+    Given a customer "Maria" with a payment of "R$ 1.000,00" from a previous export
+    When the user uploads a second export containing a payment of "R$ 500,00" and the same "R$ 1.000,00" receipt
+    Then the total payments include both unique amounts
+    And the duplicate "R$ 1.000,00" payment appears only once
+
+  Scenario: Merge trips from two exports
+    Given a customer with a trip "ABC123" from a previous export
+    When the user uploads a second export containing trip "ABC123" and a new trip "DEF456"
+    Then the customer card lists both trips
+    And trip "ABC123" appears only once
+
+  Scenario: Preserve existing pipeline stage
+    Given a customer at pipeline stage "TICKETING" from a previous export
+    When the user uploads a new export with no additional pipeline data
+    Then the pipeline stage remains "TICKETING"
+
+  Scenario: Merge contacts and fellow travelers
+    Given a customer "Ana" with contact "ana@email.com" from a previous export
+    When the user uploads a second export mentioning "Ana" as a fellow traveler of "Maria"
+    Then the customer "Ana" keeps the previous contact
+    And the customer "Ana" also has the new fellow-traveler relationship

features/background_processing.feature

@@ -0,0 +1,22 @@
+Feature: Background processing with progressive updates
+  As the agency owner
+  I want to see data appear gradually while processing
+  So that I never wait on a blank screen
+
+  Scenario: Show partial results as images are processed
+    Given a WhatsApp export with two receipt images and one ticket image
+    When the user uploads it
+    Then the payments table updates after each receipt is processed
+    And the trips table updates after the ticket is processed
+    And the interface remains responsive throughout
+
+  Scenario: Show progress status at each stage
+    Given a WhatsApp export with images, audio, and documents
+    When the user uploads it
+    Then a status message shows the current step
+    And the status updates through stages: images, audio, documents, assembly, done
+
+  Scenario: Search remains usable during processing
+    Given the system is currently processing a WhatsApp export
+    When the user types "quem ainda deve?" in the chatbox
+    Then the answer is returned immediately without waiting for processing to finish

features/crm_card.feature

@@ -21,3 +21,21 @@ Feature: Auto-built customer CRM card
     Given a conversation thread with voice notes
     When the user uploads it to the Space
     Then the timeline includes audio events with transcribed text
+
+  Scenario: View payments in editable table
+    Given a customer card with three payments
+    When the user views the payments tab
+    Then a table shows payer, amount, method, bank, and date columns
+    And the amount cell can be edited
+
+  Scenario: View trips in editable table
+    Given a customer card with two trips
+    When the user views the trips tab
+    Then a table shows locator, passengers, airline, total, and segment columns
+    And the total cell can be edited
+
+  Scenario: View documents in editable table
+    Given a customer card with documents for two passengers
+    When the user views the documents tab
+    Then a table shows passenger, document kind, and status columns
+    And the status cell can be edited

features/dashboard.feature

@@ -12,3 +12,13 @@ Feature: Cross-customer dashboard and search
     Given several processed customers
     When the user opens the overview
     Then the total money in, outstanding, and profit are shown
+
+  Scenario: Show recent messages across customers
+    Given several processed customers with messages
+    When the user opens the dashboard overview
+    Then the last 10 messages across all customers are shown
+
+  Scenario: Ask about customers via chatbox
+    Given several processed customers
+    When the user types "a Maria ja pagou tudo?" in the chatbox
+    Then the system answers based on the aggregated data