fix(stop+stability): stop button interrupts live generation; classifier, prompt + preview pane improvements

Stop button fix:
- Plumb AbortSignal end-to-end: callVibnChat → Gemini SDK (config.abortSignal) / OpenAI fetch → executeMcpTool (/api/mcp fetch)
- Treat abort as clean user stop (not fatal error); partial reply persisted with '(stopped by user)'

Classifier fix:
- Add timeout/gateway/5xx/connection-error vocabulary to diagnose intent
- Prevents 'I get a gateway timeout' from falling through to feature_build (40 rounds) and looping

Prompt / agent behaviour:
- Render verification is now scope-aware: small edits stop at green healthCheck; no browser_console/curl audit on healthy server
- Sanitize stale '### Phase Checkpoint' walls from loaded history so old threads stop biasing new turns
- Next.js dev command updated to --no-turbopack for container stability (per-route lazy compile caused cold-start 503s)
- New public page prompt: agent checks middleware allowlist in the same turn
- Scope discipline and QA-tool gating carried forward from prior session

Code cleanup:
- Remove duplicate AgentPhase declaration (TS2440)
- Remove dead checkpoint emit branch and orphan 'checkpoint' phase value
- Remove unused MAX_TOOL_ROUNDS constant

Preview pane (build status):
- 4-state machine: initial-load / building (with elapsed timer) / build-failed / not-running
- pollMs 0 → 5 000ms so dev-server recovery and build completion auto-update without refresh
- anatomy route + use-anatomy type: inFlightBuild gains createdAt for elapsed timer

ai-new-thread.md

@@ -51,23 +51,35 @@ DO NOT treat `master-ai` as a single monorepo on Gitea. You must push changes in
 │                                             Remote 'coolify_agent_gitea' -> https://git.vibnai.com/mark/vibn-agent-runner.git
 ├── vibn-frontend/                        <-- Subfolder of master-ai. Pushes via:
 │                                             Remote 'coolify_gitea' -> https://git.vibnai.com/mark/vibn-frontend.git
-└── vibn-api/                             <-- Subfolder of master-ai. Pushes via:
-                                              Remote 'coolify_api_gitea' -> https://git.vibnai.com/mark/vibn-api.git
+├── vibn-api/                             <-- Subfolder of master-ai. Pushes via:
+│                                             Remote 'coolify_api_gitea' -> https://git.vibnai.com/mark/vibn-api.git
+└── vibn-telemetry-service/               <-- Subfolder of master-ai (Training Data Microservice). Pushes via:
+                                              Remote 'coolify_telemetry_gitea' -> https://git.vibnai.com/mark/vibn-telemetry-service.git
 ```
 
 ### Git Remotes Reference (Configured in `/Users/markhenderson/master-ai`):
-* `coolify_agent_gitea` : `https://git.vibnai.com/mark/vibn-agent-runner.git`
-* `coolify_gitea`       : `https://git.vibnai.com/mark/vibn-frontend.git`
-* `coolify_api_gitea`   : `https://git.vibnai.com/mark/vibn-api.git`
-* `gitea`               : `https://git.vibnai.com/mark/master-ai.git`  *(share-only: for a coworker's local setup; **builds do NOT use this**)*
-* `origin`              : `https://github.com/MawkOne/master-ai.git`  *(GitHub mirror)*
+* `coolify_agent_gitea`     : `https://git.vibnai.com/mark/vibn-agent-runner.git`
+* `coolify_gitea`           : `https://git.vibnai.com/mark/vibn-frontend.git`
+* `coolify_api_gitea`       : `https://git.vibnai.com/mark/vibn-api.git`
+* `coolify_telemetry_gitea` : `https://git.vibnai.com/mark/vibn-telemetry-service.git`
+* `gitea`                   : `https://git.vibnai.com/mark/master-ai.git`  *(share-only: for a coworker's local setup; **builds do NOT use this**)*
+* `origin`                  : `https://github.com/MawkOne/master-ai.git`  *(GitHub mirror)*
 
 **How deploys actually work:** `master-ai` is a single git repo. Each cloud app builds from its **own** Gitea
 remote, from the matching subfolder. To ship a change, commit in `master-ai`, then
-`git push <remote> HEAD:main` (e.g. `git push coolify_agent_gitea HEAD:main` for the runner), then trigger the
+`git push <remote> HEAD:main` (e.g. `git push coolify_telemetry_gitea HEAD:main`), then trigger the
 Coolify deploy for that app (see `VIBNDEV.md`). `vibn-code` is a nested submodule with its own `.git` — commit &
 push it via its own `origin`. Secret `.env*` files at the repo root are gitignored — never commit them.
 
+### Deploying the Telemetry Service manually via Coolify UI:
+Because Coolify's API strictly blocks the programmatic creation of GitHub/Gitea Apps, the Telemetry service must be linked manually once:
+1. Open [Coolify Dashboard -> vibn-infrastructure -> production](https://coolify.vibnai.com/project/f4owwggokksgw0ogo0844os0/environment/foskksoccksk0kc4g8sk88ok)
+2. Click **+ Add -> Application -> Private Repository (with Gitea)**.
+3. Select `vibn-telemetry-service` and branch `main`.
+4. Set Build Pack to `Dockerfile` and Ports Exposes to `4000`.
+5. Under Environment Variables, add `DATABASE_URL=postgresql://<user>:<password>@<host>/<database>`
+6. Deploy it, then add `TELEMETRY_SERVICE_URL=http://<the-new-coolify-url>:4000` to the `vibn-frontend` environments.
+
 ---
 
 ## 3. Key Tech Stacks & Development Tools