fix(meetings): Copy notes copies the open template report, not the Standard note

[Optic00]

Problem

With a generated template report open in MeetingDetail, the header "Copy notes" action still copied the Standard structured note. The clipboard silently disagreed with what was on screen.

Fix

• Extract the clipboard builder into app/renderer/src/lib/notesCopy.ts (pure, unit-tested): when a report is open it copies title + date/duration + that report's markdown; otherwise the Standard sections exactly as before (byte-identical output for the standard path).
• Disable "Copy notes" while a summary/report stream is on screen (streamPhase !== 'idle', all transient states) — same bug class: the body shows in-flux streamed text while the clipboard would get the old note.

Coverage

• Vitest unit tests for buildNotesCopyText (standard path, report path, empty-section omission, whitespace-only report).
• New T1 e2e spec copy-notes-report.t1.spec.ts driving the real pill switch + Copy notes action against a seeded meeting carrying a report. New STENOAI_E2E_SEED_REPORT seam in the mock IPC (env-gated so transcript-export.t1 keeps its report-less meeting), with a stateful set-active-report mock so the pill switch survives the post-mutation refetch like the real sidecar.

Full T1 suite 19/19, vitest 78/78, typecheck + lint clean.

Not changed (by design)

Template reports intentionally live in the <stem>_reports.json sidecar, not as standalone .md files (src/report_store.py) — "view containing folder" not showing a report md is the designed storage model, out of scope here.

---

Summary by cubic

Fixes “Copy notes” to copy the open template report (not always the Standard note), strips hidden reasoning blocks, and disables the action while streaming to avoid stale copies.

• Bug Fixes

  • Copies title + date/duration + the active report’s markdown; otherwise falls back to the Standard structured note.
  • Strips reasoning blocks (e.g., ) from both Standard summaries and report content before copying, matching what’s rendered.
  • Disables “Copy notes” when streamPhase !== 'idle' to prevent clipboard/display mismatches.

• Refactors

  • Extracted builder to app/renderer/src/lib/notesCopy.ts with unit tests.
  • Added e2e spec copy-notes-report.t1.spec.ts; mock IPC now supports STENOAI_E2E_SEED_REPORT and a stateful set-active-report (seeded report includes a block to verify stripping).

^{Written for commit 37926a7. Summary will update on new commits.}

[Optic00]

Heads-up on overlap with #317: that PR's latest revision also touches copyNotes (stripping reasoning blocks from the copied summary). This PR already incorporates that behaviour for both copy sources (Standard summary and open report content), so if #317 merges first the MeetingDetail.tsx conflict resolves by taking this branch's copyNotes; if this merges first, #317's copyNotes hunk becomes redundant. Details in #317 (comment).

[cubic-dev-ai]

1 issue found and verified against the latest diff

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="app/renderer/src/routes/MeetingDetail.tsx">

<violation number="1" location="app/renderer/src/routes/MeetingDetail.tsx:498">
P2: Copy notes can show a false success state when clipboard write fails, because the handler marks `copied` immediately instead of after a successful write. Matching the transcript copy pattern (or chaining `.then`) would keep feedback aligned with actual clipboard outcome.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

P2: Copy notes can show a false success state when clipboard write fails, because the handler marks copied immediately instead of after a successful write. Matching the transcript copy pattern (or chaining .then) would keep feedback aligned with actual clipboard outcome.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At app/renderer/src/routes/MeetingDetail.tsx, line 496:

<comment>Copy notes can show a false success state when clipboard write fails, because the handler marks `copied` immediately instead of after a successful write. Matching the transcript copy pattern (or chaining `.then`) would keep feedback aligned with actual clipboard outcome.</comment>

<file context>
@@ -474,36 +475,25 @@ function DetailContent({ meeting }: { meeting: Meeting }) {
+      },
+      activeReport,
+    );
+    void navigator.clipboard.writeText(text);
     setCopied(true);
     setTimeout(() => setCopied(false), 2000);
</file context>