refactor(chat): remove the post-answer suggestion chips and the table that fed them

Measured use of the three chips above the composer was negligible. They
were also not what they appeared to be: the server looked up a fixed
triplet by session theme and passed it as metadata that overrode
anything the model produced, so the same ten hardcoded sets served every
user regardless of question or chart. That is a plausible reason nobody
pressed them.

Both copies of the per-theme table are gone, reply metadata narrows to
the session title, and the two parse entry points collapse into one now
that they return the same shape. The write schema still tolerates a
suggestions field so a client on the previous bundle does not lose its
message mid-deploy, and stored answers containing the legacy hidden
block are still stripped rather than shown raw.

Co-authored-by: Cursor <cursoragent@cursor.com>

frontend/src/app/api/consult/route.ts

@@ -469,14 +469,12 @@ export async function POST(request: Request) {
     try {
       const reply = parseAgentReply(
         rawTransformedText,
-        consultationTheme,
-        createConsultationReplyMetadata({ theme: consultationTheme, question: visibleQuestion }),
+        createConsultationReplyMetadata({ question: visibleQuestion }),
       );
       if (!reply.text) throw new Error("empty_agent_reply");
       const responseMessage = {
         role: "assistant" as const,
         text: reply.text,
-        suggestions: reply.suggestions,
         techniqueTruth,
         workflowReceipt,
         ...(agentExecutionReceipt ? { agentExecutionReceipt } : {}),