Consume weighted search answers and suppress dead chips

docs/modules/ui/search-zero-learning-primary-entry.md

@@ -29,6 +29,7 @@
 - Place `Did you mean` directly below the input because it is an input correction, not a result refinement.
 - Remove explicit `Find / Explain / Act` controls.
 - Remove the explicit scope toggle chip.
+- Remove manual result-domain refinements from the primary flow; the server should rank the current page first and render any cross-scope overflow as a secondary section instead.
 - Remove the recovery panel.
 - If top results are close in score, compose one short summary across them.
 - If one result is clearly dominant, present that answer first and then cards.
@@ -58,10 +59,12 @@
 ### Suggestion viability
 - Suggestions must be validated against the current corpus before rendering.
 - Knowledge/domain emptiness should be detectable so the UI can suppress invalid chips.
+- Empty-state contextual chips and page-owned common-question chips should preflight through the backend viability endpoint before they render.
 - Live Playwright coverage must assert that every surfaced suggestion returns visible results.
 
 ## Phase map
 - Phase 1: FE primary-entry consolidation and removal of explicit search controls.
 - Phase 2: AdvisoryAI implicit scope weighting, answer blending, and suggestion viability.
 - Phase 3: FE consumption of overflow results and executable suggestion contracts.
+  - Implemented on 2026-03-07: backend `contextAnswer` is now preferred over frontend heuristics, overflow renders as a secondary result section, and suggestion viability preflight suppresses dead chips before they are shown.
 - Phase 4: Live Playwright reliability matrix with corpus preflight and chip-success guarantees.