teatea-pension/.trellis/tasks/archive/2026-07/07-09-ai-fee-frontend/implement.md

AI Presentation And Fee Workspace Implementation Plan

1. AI Surface Audit

• Confirm the visible elder analysis path has no external provider call.
• Replace technical knowledge retrieval and failure-history wording with product-facing copy.
• Keep analysis history, refresh/generate behavior, citations, and permission redaction intact.
• Add or adjust focused assertions for user-visible AI copy where practical.

2. Fee Domain

• Add billing types, labels, currency helpers, status derivation, and summary calculations.
• Add realistic initial resident statements with itemized fees and payments.
• Add unit tests for amount totals, payment application, and status derivation.

3. Fee Workspace UI

• Build overview metrics, search, filters, and responsive statements table.
• Build statement detail with charge items and payment history.
• Build charge registration and payment registration flows with validation.
• Build receipt and invoice actions with state updates and visible feedback.

4. Routing And Navigation

• Add scoped and unscoped billing routes with authentication and admission:manage gating.
• Add 费用管理 and a Lucide icon to the operations navigation.
• Verify workspace breadcrumbs and organization-scoped links resolve correctly.

5. Validation

• Run focused billing and AI tests.
• Run pnpm lint.
• Run pnpm type-check.
• Run pnpm test.
• Run pnpm build.
• Start the development server and smoke-test AI and billing flows in the browser at desktop and mobile widths.
• Check browser console errors, text clipping, dialog geometry, and interactive state updates.

Risk And Rollback Points

• Keep the billing domain isolated so removal does not affect persisted modules.
• Do not change Permission, role seed, schema, or migrations for the frontend-only workspace.
• Reuse admission:manage; changing authorization is out of scope.
• Do not alter AI API response shapes or stored analysis records.