[KM-711] Retire /report slash command; report is Generate-button only

Report generation is now button-only (Generate button on the Report panel).
The /report slash command is retired: typed manually it misroutes to the check
tool, so surfacing it would mislead users.

- help.md -> v6: Section C, how-to phrasing, and help_ex_guard_ready now point to
the Generate button, anchored on the button label (not an exact corner). Never
mention /report.
- eval/help/help_dataset.json: ready cases reward Generate/report and forbid /report.
- api/v1/tools.py: /report entry in _COMMAND_CATALOG commented out (kept, not
deleted); catalog now only /help. The POST /tools/report endpoint stays (the
Generate button calls it).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

eval/help/help_dataset.json

@@ -89,8 +89,11 @@
       "report_ready": { "ready": true, "missing": [] },
       "history": [{ "role": "human", "content": "what should I do next?" }],
       "message": null,
-      "asserts": [{ "type": "must_contain_any", "patterns": ["/report", "report"] }],
-      "note": "MIRRORS help.md example help_ex_guard_ready. Enough analysis done — SHOULD nudge toward the report (mention /report or the report option)."
+      "asserts": [
+        { "type": "must_contain_any", "patterns": ["Generate", "generate", "report"] },
+        { "type": "must_not_contain_any", "patterns": ["/report"] }
+      ],
+      "note": "MIRRORS help.md example help_ex_guard_ready. Enough analysis done — SHOULD nudge toward the report by pointing at the Generate button; must NOT offer /report (removed in v6)."
     },
     {
       "id": "guard_03", "group": "report_guard", "carried_over": false, "manual_review": false,
@@ -108,10 +111,11 @@
       "history": [{ "role": "human", "content": "selanjutnya aku ngapain?" }],
       "message": null,
       "asserts": [
-        { "type": "must_contain_any", "patterns": ["/report", "laporan", "report"] },
+        { "type": "must_contain_any", "patterns": ["Generate", "generate", "laporan", "report"] },
+        { "type": "must_not_contain_any", "patterns": ["/report"] },
         { "type": "language_match", "expected": "Indonesian" }
       ],
-      "note": "Ready + Indonesian conversation — should nudge toward the report AND stay in Indonesian (two rules at once)."
+      "note": "Ready + Indonesian conversation — should nudge toward the report (Generate button) AND stay in Indonesian; must NOT offer /report (removed in v6)."
     },
     {
       "id": "guard_05", "group": "report_guard", "carried_over": false, "manual_review": false,

src/api/v1/tools.py

@@ -4,8 +4,10 @@ Exposes the agent's user-invocable slash-command catalog so the Golang backend
 can cache it and the frontend can render its "/" command menu WITHOUT calling the
 AI agent for every list (Golang GETs + caches `list_tools`).
 
-Scope (2026-06-24, KM-674): the FE slash-command catalog is now just the two
-FE-callable skills — `/help` and `/report`. Naming: verb-first, kebab-case, `/`
+Scope (2026-07-09): the FE slash-command catalog is now just `/help`. `/report` was
+removed — report generation is button-only (the Generate button in the Report panel);
+typing `/report` no longer creates a report (the router sends it to `check`), so
+surfacing it as a slash command would mislead. Naming: verb-first, kebab-case, `/`
 prefix; each command maps 1:1 to a real internal tool/intent `name` (the dispatch
 key).
 
@@ -49,8 +51,12 @@ class ListToolsResponse(BaseModel):
 # Keep `command` in Harry's convention (verb-first, kebab-case, `/`); `name` is the
 # internal route/tool name used by the orchestrator.
 #
-# 2026-06-24 (KM-674 batch): the FE-callable skills are ONLY /help + /report. The rest
-# below are COMMENTED OUT — NOT deleted — on purpose:
+# 2026-07-09: the only FE-callable slash skill is now /help. The rest below are
+# COMMENTED OUT — NOT deleted — on purpose:
+#   - /report is retired as a slash command: report generation is button-only (Generate
+#     button in the Report panel). Typing /report no longer generates a report (the router
+#     routes it to `check`), so exposing it here would misdirect users. The report HTTP
+#     endpoint (POST /api/v1/tools/report in report.py) stays — the Generate button calls it.
 #   - /problem-statement is retired (objective + business_questions now live in the
 #     New-Analysis form, not a slash skill).
 #   - check_data / check_knowledge stay available but are served by Golang, not exposed
@@ -65,13 +71,13 @@ _COMMAND_CATALOG: list[CommandResponse] = [
         type="skill",
         description="Show what the assistant can do and guide your next step.",
     ),
-    CommandResponse(
-        command="/report",
-        name="report",
-        type="skill",
-        description="Generate a versioned analysis report (background, EDA, "
-        "key findings, insights).",
-    ),
+    # CommandResponse(
+    #     command="/report",
+    #     name="report",
+    #     type="skill",
+    #     description="Generate a versioned analysis report (background, EDA, "
+    #     "key findings, insights).",
+    # ),
     # CommandResponse(
     #     command="/problem-statement",
     #     name="problem_statement",

src/config/prompts/help.md

@@ -1,4 +1,10 @@
-<!-- help.md · v5 · Help skill prompt.
+<!-- help.md · v6 · Help skill prompt.
+     v6 (2026-07-09): report trigger changed — the `/report` skill and the old report button
+     are GONE. A report is now generated ONE way only: the **Generate** button on the Report
+     panel (single source of truth). Help must no longer tell users to run `/report` or "use
+     the report skill"; it points them to the Generate button — anchored on the button LABEL,
+     not an exact corner/position (layout isn't final). Updated Section C, the How-to phrasing
+     note, and the help_ex_guard_ready example accordingly.
      v5 (2026-07-07): added the "Capability boundary" section — Help now only suggests
      analyses the live tools can actually deliver (descriptive, group-by, correlation, trend)
      and must NOT suggest significance tests, forecasting/modeling, causal claims, clustering/
@@ -72,9 +78,11 @@ recommend the specific next questions that would fill those gaps (phrase them as
 the user can ask), still anchored to the objective and business questions.
 
 ### C. `report_ready.ready == true` → nudge toward the report
-There's enough to report. Encourage them to generate it. Report can be triggered **two ways**:
-the **`/report`** skill **or** the report button — mention both so it feels natural.
-Do not over-promise the report's depth.
+There's enough to report. Encourage them to generate it. A report is generated **one way**:
+by clicking the **Generate** button on the Report panel. Anchor on the button's label
+(**Generate**) — that's the unambiguous, layout-stable cue — rather than an exact
+position/corner. There is no `/report` skill or manual command anymore — do **not** mention
+`/report`. Do not over-promise the report's depth.
 
 > Edge case: if `objective` looks empty (unusual — it's required at onboarding), don't push a
 > chat skill to fix it; gently suggest they set the objective + business questions in the New
@@ -111,8 +119,9 @@ the gap — rather than promising the unsupported analysis.
 
 ## How-to phrasing (degrade gracefully)
 
-- **Via chat / skills** — write these **accurately and specifically**; they are stable (e.g. "type your question in the chat", "run `/report`").
-- **Via the UI (buttons/menus)** — the frontend isn't final yet. Describe UI steps **generically** ("use the Generate Report option") rather than naming exact buttons/positions you're unsure of. Prefer the chat/skill path when unsure. *(A later version of this file will fill in the real UI steps.)*
+- **Via chat / skills** — write these **accurately and specifically**; they are stable (e.g. "type your question in the chat"). Note: report is **not** a chat skill — never write `/report`.
+- **Generating a report** — the only way is the **Generate** button on the Report panel. Name the button by its label; don't pin an exact corner/position (the layout isn't final). Don't offer `/report` or a "report skill" as an alternative.
+- **Other UI steps (buttons/menus)** — the rest of the frontend isn't final yet. Describe those steps **generically** rather than naming exact buttons/positions you're unsure of.
 - If a field in `analysis_state` is missing or the state looks unwired, **fall back to generic guidance** rather than guessing specifics.
 
 ## Tone
@@ -158,6 +167,6 @@ State: report_ready.ready=false, missing=["a new analysis since the last report"
 
 <!-- id: help_ex_guard_ready -->
 State: report_ready.ready=true
-→ "You've covered enough to summarize. You can generate your report now — run /report
-   or use the report option to create it."
+→ "You've covered enough to summarize. You can generate your report now — click the
+   Generate button on the Report panel to create it."
 ```