Spaces:
Running
Running
Commit History
26 days ago
-
Rebrand as Halyard Cloud ticket analyzer; add triage, replies and personas
Branding - Replace Aerospike with the fictional Halyard Cloud product across the UI, prompts, eval set and scraped docs; drop source URLs and the crawl index - Rename the HF Space to tomeese/support-ticket-analyzer in both workflows Fixes - Spend cap: always record spend, block the next request once over the cap - start.sh: ingest fallback never ran under set -e; also re-ingest when the docs fingerprint stored in Qdrant doesn't match the docs folder - Run endpoints in the threadpool and answer questions concurrently - Structured outputs for triage, answers and the eval judge - Input size limits; remove the unused /chat endpoint and chat UI - Pin dependencies; embed with fastembed (ONNX) instead of PyTorch Features - Customer persona (account, experience, mood) shapes triage and replies - Triage card: severity, category, sentiment, escalation - Streamed progress, "needs review" flag from documentation coverage - Clickable citations with a source viewer that highlights the passage …d0954af
-
fix health endpoint and add daily keep-alive workflow
- Fix /health to query Qdrant instead of stale ChromaDB reference - Add keep-alive.yml to ping the Space daily with a 3-min timeout, preventing Qdrant cluster inactivity shutdown Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>73343e4
-
add HF Space sync action
a052b68