Fix apps-mcp agent behavior: localhost preference and deployment confirmation

Two key issues addressed:

1. Agent was opening deployed URLs instead of localhost when user asked to
   "open a dev copy" or see the app during development.

2. Agent was deploying too early without user confirmation.

Changes:
- apps.tmpl: Add localhost guidance and deployment confirmation requirement
- CLAUDE.md: Add "Deployment Procedures" section with pre-deployment checklist
- CLAUDE.md: Add "Local Development vs Deployed Apps" section with decision tree

The agent will now:
- Prefer localhost:8000 during active development
- Ask "Ready to deploy to [environment]?" before deploying
- Only use deployed URLs after deployment with user approval

Addresses feedback from PR #4045 discussion.

Author: keugenek

experimental/apps-mcp/lib/prompts/apps.tmpl

@@ -15,18 +15,43 @@ DATABRICKS APPS DEVELOPMENT
 
 invoke_databricks_cli 'experimental apps-mcp tools init-template --name my-app-name --description "My app description"'
 
+# Local Development
+
+⚠️ PRIMARY development workflow - run app locally:
+
+1. Navigate to app directory: cd ./your-app
+2. Start dev server: npm run dev
+3. Open in browser: http://localhost:8000
+
+⚠️ IMPORTANT: When user asks to "open the app", "see the app", or "open dev copy":
+- During development → ALWAYS use http://localhost:8000 (requires npm run dev to be running)
+- After deployment → Use deployed URL from bundle summary
+
+DO NOT suggest deployed URLs (staging/production) when user wants to test during development!
+
 # Validation
 
 ⚠️ Always validate your app before deploying to production:
 
 invoke_databricks_cli 'experimental apps-mcp tools validate ./your-app-location'
 
+This runs: npm install → build → typecheck → tests
+
 # Deployment
 
-⚠️ Use the deploy command which validates, deploys, and runs the app:
+⚠️ CRITICAL: NEVER deploy without explicit user confirmation!
+
+Deployment checklist (confirm with user BEFORE deploying):
+1. App has been validated successfully
+2. Local testing completed (npm run dev)
+3. User explicitly approved deployment
+
+⚠️ ALWAYS ask user: "Ready to deploy to [environment]?" before running deploy command.
+
+Once confirmed, use the deploy command:
 
 invoke_databricks_cli 'experimental apps-mcp tools deploy'
 
-# View and manage your app:
+After deployment, get the app URL:
 
 invoke_databricks_cli 'bundle summary'

experimental/apps-mcp/templates/appkit/template/{{.project_name}}/CLAUDE.md

@@ -37,6 +37,71 @@ TypeScript full-stack template powered by **Databricks AppKit** with tRPC for ad
 - Pre-commit: `npm run typecheck && npm run lint:fix && npm run format:fix && npm test`
 - Pre-deploy: `npm run build && npm start` (test locally) → `npm test`
 
+## Deployment Procedures
+
+**CRITICAL**: Deployment is a significant action that affects live environments. NEVER deploy without explicit user confirmation.
+
+### Before Deploying
+
+**ALWAYS** confirm with the user first by asking: "Ready to deploy to [environment]?"
+
+Pre-deployment checklist:
+1. ✅ App validated successfully (`databricks experimental apps-mcp tools validate .`)
+2. ✅ Local testing completed (`npm run dev` and manual verification)
+3. ✅ User explicitly approved deployment
+4. ✅ Code committed to git (recommended)
+
+### Deployment Commands
+
+```bash
+databricks bundle deploy              # Deploy app infrastructure
+databricks bundle run app            # Start the app
+databricks bundle summary            # Get deployed app URL
+```
+
+Or use the all-in-one command:
+```bash
+databricks experimental apps-mcp tools deploy  # Validates, deploys, and runs
+```
+
+**DO NOT** run deployment commands unless the user explicitly requests it or confirms when asked.
+
+## Local Development vs Deployed Apps
+
+**CRITICAL**: Understand the difference between local development and deployed environments.
+
+### During Development (Before Deployment)
+
+When the user asks to "open the app", "see the app", "view the app", or "open a dev copy":
+
+- ✅ **Use localhost**: `http://localhost:8000`
+- ✅ **Requires**: `npm run dev` must be running
+- ✅ **Purpose**: Hot reload, fast iteration, debugging
+
+**DO NOT** suggest deployed URLs (staging/production) during active development!
+
+### After Deployment
+
+Only after running `databricks bundle deploy && databricks bundle run app`:
+
+- ✅ **Use deployed URL**: Get from `databricks bundle summary`
+- ✅ **Purpose**: Production/staging environment, sharing with others
+
+### Decision Tree
+
+```
+User asks to "open the app" or "see the app"
+│
+├─ Has the app been deployed in this session?
+│  ├─ No  → Use http://localhost:8000 (start with `npm run dev` if needed)
+│  └─ Yes → Ask user which environment they want:
+│           • localhost (development)
+│           • deployed URL (production/staging)
+│
+└─ User explicitly says "localhost" or "local"
+   → Always use http://localhost:8000
+```
+
 ## App Naming Constraints
 
 App names must not exceed 30 characters total (including target prefix).