Ai/full autonomous flow (#359)

* Refactor bookkeeping error handling and introduce new error classes - Introduced new error classes for better error categorization: - JournalEntryNotBalancedError - FiscalPeriodNotFoundError - EntryDateOutsideFiscalPeriodError - JournalEntryNotFoundError - CannotReverseNonPostedError - CannotCorrectNonPostedError - EntryAlreadyReversedError - CurrencyRevaluationAlreadyExistsError - InvalidMappingResultError - BookkeepingDatabaseError - Updated existing functions in engine.ts and transaction-entries.ts to throw specific errors instead of generic ones. - Enhanced error response handling in get-error-message.ts to provide localized messages for new error types. - Added unit tests for new error classes and error handling functions to ensure correctness and coverage. * feat(ai): implement AI proposal application and persistence - Add apply.ts to handle the application of AI proposals, including match and booking steps. - Introduce persist.ts for inserting and managing AI requests and proposals, ensuring unique constraints. - Create re-validate.ts for validating proposals before acceptance, checking for stale conditions. - Define database migrations for ai_requests and ai_proposals tables, including constraints and indexes. - Enhance journal_entries with AI provenance tracking, linking entries to AI proposals. - Update categorization_templates to distinguish AI-corrected templates. - Add company settings for toggling AI flow and managing backfill processes. - Extend processing_history to include AI-related events for better tracking. * feat: add uncategorized transactions API and UI for transaction selection - Implemented a new API endpoint for fetching uncategorized transactions with pagination and filtering options. - Created ChangeTransactionDialog component for selecting alternative transactions based on AI proposals. - Developed ReceiptDetailDialog to display detailed information about receipts, including upload functionality. - Added TransactionDetailDialog for viewing transaction details with links to the transaction list. - Introduced receipt quality assessment logic to evaluate extracted receipt data. - Implemented feature flagging for the AI bookkeeping agent to control availability in different environments. * feat: add manual receipt extraction dialog and integrate AWS Textract for expense analysis - Added ManualExtractDialog component for user input when AI fails to extract receipt data. - Implemented ReceiptsList component to manage and display uploaded receipts, including upload and rescan functionalities. - Introduced Textract integration for analyzing expenses, extracting fields like total, vendor, and date. - Updated package.json to include @aws-sdk/client-textract dependency. * fix(ai): handle livsmedel VAT transition (12% → 6%) in booking prompt and re-validate guard Add date-aware guidance to BOOKING_SYSTEM_PROMPT for the temporary livsmedel VAT cut (Prop. 2025/26:55, 2026-04-01 to 2027-12-31), with restaurang/servering carve-out at 12%. Add a re-validate safety net that rejects clearly-stale rate labels for grocery-chain merchants relative to the entry date. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-27 10:32:15 +02:00
parent ab63da8324
commit 1af977950b
70 changed files with 9735 additions and 451 deletions
@@ -0,0 +1,106 @@
+import { NextResponse } from 'next/server'
+import { createClient } from '@/lib/supabase/server'
+import { ensureInitialized } from '@/lib/init'
+import { validateBody } from '@/lib/api/validate'
+import { ResolveRequestSchema } from '@/lib/api/schemas'
+import { requireCompanyId } from '@/lib/company/context'
+import { requireWritePermission } from '@/lib/auth/require-write'
+import { appendProcessingHistory } from '@/lib/processing-history/append'
+import { gateAgentInbox } from '@/lib/ai/feature-flag'
+import type { AIRequest, InvoiceInboxItem } from '@/types'
+
+ensureInitialized()
+
+/**
+ * POST /api/ai/requests/[id]/resolve
+ *
+ * Mark an open ai_request as resolved. The response body is stored on the
+ * row for audit, but the actual follow-up action (re-upload doc, pick a
+ * transaction manually, set a VAT rate) is wired through the existing
+ * domain endpoints — the UI calls those separately. This endpoint just
+ * closes out the request card.
+ */
+export async function POST(
+  request: Request,
+  { params }: { params: Promise<{ id: string }> }
+) {
+  const gate = gateAgentInbox()
+  if (gate) return gate
+
+  const supabase = await createClient()
+  const { data: { user } } = await supabase.auth.getUser()
+  if (!user) return NextResponse.json({ error: 'Unauthorized' }, { status: 401 })
+
+  const writeCheck = await requireWritePermission(supabase, user.id)
+  if (!writeCheck.ok) return writeCheck.response
+
+  const companyId = await requireCompanyId(supabase, user.id)
+  const { id } = await params
+
+  const validation = await validateBody(request, ResolveRequestSchema)
+  if (!validation.success) return validation.response
+  const { response } = validation.data
+
+  const { data: req } = await supabase
+    .from('ai_requests')
+    .select('*')
+    .eq('id', id)
+    .eq('company_id', companyId)
+    .maybeSingle()
+
+  if (!req) return NextResponse.json({ error: 'Not found' }, { status: 404 })
+  const typed = req as AIRequest
+  if (typed.status !== 'open') {
+    return NextResponse.json(
+      { error: 'Begäran är redan hanterad.', status: typed.status },
+      { status: 409 }
+    )
+  }
+
+  const { data: updated, error: updateError } = await supabase
+    .from('ai_requests')
+    .update({
+      status: 'resolved',
+      resolved_at: new Date().toISOString(),
+      resolved_by_user_id: user.id,
+      response_json: response ?? null,
+    })
+    .eq('id', typed.id)
+    .eq('status', 'open')
+    .select()
+    .maybeSingle()
+
+  if (updateError || !updated) {
+    return NextResponse.json({ error: 'Kunde inte uppdatera' }, { status: 500 })
+  }
+
+  // Audit.
+  try {
+    const { data: inbox } = await supabase
+      .from('invoice_inbox_items')
+      .select('correlation_id')
+      .eq('id', typed.subject_id)
+      .maybeSingle()
+    const item = inbox as Pick<InvoiceInboxItem, 'correlation_id'> | null
+    if (item?.correlation_id) {
+      await appendProcessingHistory({
+        companyId,
+        correlationId: item.correlation_id,
+        aggregateType: 'AIRequest',
+        aggregateId: typed.id,
+        eventType: 'AIRequestResolved',
+        payload: {
+          request_id: typed.id,
+          request_type: typed.request_type,
+          has_response: Boolean(response),
+        },
+        actor: { type: 'user', id: user.id },
+        occurredAt: new Date(),
+      })
+    }
+  } catch (err) {
+    console.error('[ai/requests/resolve] Failed to append AIRequestResolved:', err)
+  }
+
+  return NextResponse.json({ data: { request: updated } })
+}