* docs(self-hosting): AI runs on AWS Bedrock, not ANTHROPIC/OPENAI keys
A self-hoster followed SELF-HOSTING.md, set ANTHROPIC_API_KEY and
OPENAI_API_KEY, and found document interpretation dead (with a 30s
extraction-poll hang per upload). Neither key has been read since the
ai-chat / receipt-ocr / ai-categorization extensions were removed in
PR #157: all AI (document extraction and the assistant) goes through
Claude on AWS Bedrock via AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY.
- SELF-HOSTING.md, DOCKER.md, .env.example: document the Bedrock
credentials and model overrides; point plain-key support at #1406
- SELF-HOSTING.md: drop the receipts-bucket setup for the removed
receipt-ocr extension
- EXTENSIONS.md: replace removed extensions with live ones in trees
and examples; drop the AI-consent system claims (lib/extensions/
ai-consent.ts no longer exists); services-pattern example now uses
the real stripe/skatteverket services
- lib/init.ts: startup env warning now checks the AWS keys instead of
the two dead vars, so a misconfigured self-host logs the truth
Direct Anthropic API key support and pluggable providers: #1406.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* docs: address review, dedupe tree entry and match provider-chain claim to code
extractInvoiceFields bails without both static AWS keys, so only the
assistant client actually falls back to the credential provider chain.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---------
Co-authored-by: Jakob Wennberg <311770904+jakobwennberg-oss@users.noreply.github.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
