chore: remove Amplify integration (#164)

Co-authored-by: dayuan.jiang <jiangdy@amazon.co.jp>

amplify.yml

@@ -1,22 +0,0 @@
-version: 1
-frontend:
-  phases:
-    preBuild:
-      commands:
-        - npm ci --cache .npm --prefer-offline
-    build:
-      commands:
-        # Write env vars to .env.production for Next.js SSR runtime
-        - env | grep -e AI_MODEL >> .env.production
-        - env | grep -e AI_PROVIDER >> .env.production
-        - env | grep -e OPENAI_API_KEY >> .env.production
-        - env | grep -e NEXT_PUBLIC_ >> .env.production
-        - npm run build
-  artifacts:
-    baseDirectory: .next
-    files:
-      - '**/*'
-  cache:
-    paths:
-      - .next/cache/**/*
-      - .npm/**/*

docs/ai-providers.md

@@ -98,7 +98,7 @@ AWS_SECRET_ACCESS_KEY=your_secret_access_key
 AI_MODEL=anthropic.claude-sonnet-4-5-20250514-v1:0
 ```
 
-Note: On AWS (Amplify, Lambda, EC2 with IAM role), credentials are automatically obtained from the IAM role.
+Note: On AWS (Lambda, EC2 with IAM role), credentials are automatically obtained from the IAM role.
 
 ### OpenRouter
 

lib/ai-providers.ts

@@ -166,7 +166,7 @@ export function getAIModel(): ModelConfig {
 
     switch (provider) {
         case "bedrock": {
-            // Use credential provider chain for IAM role support (Amplify, Lambda, etc.)
+            // Use credential provider chain for IAM role support (Lambda, EC2, etc.)
             // Falls back to env vars (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY) for local dev
             const bedrockProvider = createAmazonBedrock({
                 region: process.env.AWS_REGION || "us-west-2",