Skip to content

Add a button to regenerate meeting summaries - #27

Merged
tommusrhodus merged 2 commits into
a8cteam51:trunkfrom
SirDarcanos:fix/regenerate-summary
Nov 17, 2026
Merged

tommusrhodus merged 2 commits into
a8cteam51:trunkfrom
SirDarcanos:fix/regenerate-summary

Conversation

@SirDarcanos

Copy link
Copy Markdown
Contributor

Summary

Adds Regenerate summary to the Summary tab toolbar, so changing instructions in Settings no longer requires deleting summary.md by hand.

The action asks for confirmation, then generates a replacement using current instructions. The previous summary stays until a non-empty replacement succeeds. Transcript, notes, existing to-dos, and metadata remain unchanged. If the summary changes during generation, regeneration stops rather than overwriting those edits. Progress, errors, and retry are shown; regeneration controls are disabled without a transcript or while a job is already running.

Closes #24

Verification

  • swift build passed.
  • swift test: 92 tests across 23 suites passed.
  • Regression tests cover replacement, preservation of other files, changed instructions, generation failure, empty output, and intervening summary edits.
  • Independent Standards and Spec reviews completed. Their shared retry-state finding was corrected and the build/tests rerun.

Manual UI smoke testing is still outstanding, including confirmation/cancellation, busy/error/retry feedback, and missing-transcript states.

Validation details

Compared with trunk at 271c50b58ee0e7f41265406ba67e17f1ee975fb8: two Swift Testing test functions added; no existing tests removed or modified. Existing initial summary generation and retry coverage remains. The final build and all 92 tests passed after the retry-disabled-state correction. That narrow modifier correction was inspected by the implementation lead; the original independent reviews were not rerun. git diff --check passed. The committed files are content-identical to the final checked working tree.

README documents the new action and preservation behavior. No dependencies or CI jobs changed. Hosted CI has not yet been verified; duration/compute impact is unmeasured. The existing PR workflow builds, tests, and checks shell-script syntax. This PR contains no migrations, release tags, or installed-app updates. No private calendar or meeting data is included.

SirDarcanos and others added 2 commits November 17, 2026 07:43
Confirm summary replacement using current instructions, preserve existing content until success, and keep transcript, notes and to-dos unchanged.

Refs a8cteam51#24
…del only for that one

The Summary tab's toolbar has a Regenerate menu with Regenerate summary and
Regenerate to-dos. Each asks first, sends the model only the request for its
own part (the summary no longer pays for a to-dos pass it throws away), and
replaces only that file. Regenerating the to-dos replaces the whole list,
ticked and added ones included, as the confirmation says. Nothing is written
if the part was changed elsewhere meanwhile, or if the model's answer is empty
or unreadable; the notice says which part failed and Try again retries it.

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

Copy link
Copy Markdown
Contributor

Pushed 6f59e21 on top of this: Regenerate is now a menu with Regenerate summary and Regenerate to-dos, since to-do instructions can change in Settings too. Each one asks the model only for its own part. Before, regenerating the summary still ran the to-dos request and threw the result away. Regenerating the to-dos replaces the whole list, ticked and added ones included, and the confirmation says so.

Tested in a built copy against sample meetings and a stand-in model server: one request per regeneration, only the regenerated file changes, a failure leaves the old one in place, and Try again retries the same part.

Confirmation
While it runs
New to-dos
When the model can't be reached

@tommusrhodus
tommusrhodus merged commit ed59633 into a8cteam51:trunk Nov 17, 2026
2 checks passed
@SirDarcanos
SirDarcanos deleted the fix/regenerate-summary branch November 18, 2026 04:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add option to regenerate summaries

2 participants