fix: include story description in Telegram approval message (#39)

* feat: add Re-run Analysis button to project detail page

Adds POST /admin/ui/projects/{repo_slug}/rescan route that creates a
new onboarding run and enqueues it, then redirects to the live status
page — same flow as the wizard but without touching the Jira mapping.
Adds CSRF-protected button in the project detail page header.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* docs: add rescan route to CLAUDE.md API endpoints table

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* docs: update CLAUDE.md for monorepo detection, file landmarks, ambiguity check, rescan

- repo_profiler: document _scan_for_subdir_stacks() and monorepo detection
- claude_client: document file_landmark_map in arch tool, detect_epic_missing_specifics (Haiku), plan_epic_breakdown full-context params
- Capability Profiles: add Monorepo detection note
- Clarification Loop: add Missing specifics trigger (Epic) row
- Project knowledge injection: document file_landmarks bullet
- Dashboard: document Re-run Analysis button

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* fix: allow optional trailing text after APPROVE/REJECT/REGENERATE run_id

Users naturally append reason text (e.g. "REGENERATE 1 caption was wrong").
Align _APPROVAL_RE with _CLARIFICATION_RE which already supports this.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* feat: capture REGENERATE reason as epic memory for next planning run

When user sends "REGENERATE 1 <reason>", the trailing text is now stored
as an epic-scoped manual_note so Claude incorporates the feedback on the
regenerated breakdown instead of ignoring it.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* fix: include story description in Telegram approval message

Previously the approval message only showed story titles, so users had
no way to verify the specifics without checking the DB. Now each story
block includes its description (truncated at 300 chars) so the from/to
values and key details are visible before approving.

Also clarifies REGENERATE supports optional feedback text.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: suyog19

app/workflows.py

@@ -1995,10 +1995,19 @@ def epic_breakdown(run_id: int, issue_key: str, issue_type: str, summary: str) -
     request_planning_approval(run_id)
     set_run_waiting_for_approval(run_id)
 
-    story_lines = "\n".join(
-        f"  {i}. {item.get('title', '?')} [{item.get('confidence', '?')}]"
-        for i, item in enumerate(items, 1)
-    )
+    def _story_block(i: int, item: dict) -> str:
+        title = item.get("title", "?")
+        conf = item.get("confidence", "?")
+        desc = (item.get("description") or "").strip()
+        # Truncate long descriptions so the message stays readable
+        if len(desc) > 300:
+            desc = desc[:297] + "..."
+        line = f"  {i}. {title} [{conf}]"
+        if desc:
+            line += f"\n     {desc}"
+        return line
+
+    story_lines = "\n".join(_story_block(i, item) for i, item in enumerate(items, 1))
     extra = ""
     if assumptions:
         extra += "\nAssumptions:\n" + "\n".join(f"  - {a}" for a in assumptions)
@@ -2014,7 +2023,7 @@ def epic_breakdown(run_id: int, issue_key: str, issue_type: str, summary: str) -
         f"Reply with:\n"
         f"  APPROVE {run_id}\n"
         f"  REJECT {run_id}\n"
-        f"  REGENERATE {run_id}"
+        f"  REGENERATE {run_id} <optional feedback>"
     )
     send_message("epic_breakdown_proposed", "PENDING", approval_msg)
     logger.info("epic_breakdown: approval request sent to Telegram (run_id=%s)", run_id)