✨ Transcript Saving - Auto-create PR to project repo after transcript ingestion (with summary + transcript file)

Goal

After Tiger ingests a transcript, auto-create a pull request to the relevant project repo containing a summary of the meeting and any associated action items extracted from the call.

Concept

• Tiger detects which project / repo the meeting relates to (from speakers, file naming, content)
• Generates a structured summary (decisions, action items, follow-ups)
• Opens a PR against the project repo with the transcript + summary added under a standardised path (e.g. meetings/2026-05-04-sprint-review.md)
• Optionally appends to the project's "meetings index" so the dashboard / onboarding page lists it

Acceptance criteria

1. Given a transcript file processed by Tiger, the system identifies a likely target repo (or surfaces top candidates if ambiguous)
2. A PR is opened (with appropriate auth) containing the transcript + summary, on a branch named for the date / meeting type
3. PR description references the meeting type, speakers, and primary decisions
4. Existing Tiger dashboard generation continues to work alongside the new PR-creation step (no regression)

Background — discussion

As per Calum in Sprint 10 Retro — "there could be a GitHub integration … after a transcript's recorded … then just go ahead and create a pull request … adding in a … transcript file. And maybe the entire dashboard also goes [into the repo]".

Calum at line 4021: "maybe that's another idea … later because it's a bigger change."

Out of scope

• Cross-repo linking / aggregation across projects (separate consideration)
• AI-generated PR review / approval (later)

Status

FLOATED — explicitly described as a "bigger change" and parking for later. Tracked in backlog for future prioritisation.

Start by tracing the transcript ingestion and existing dashboard-generation flow, using recordings/2026-05-04-Sprint-10-Review-Retro-Planning.vtt as the referenced example. Define how target-repository detection, authentication, summary generation, and PR creation fit together before implementation. Done means an ingested transcript can produce the required branch, PR contents, and description without regressing dashboard generation.