Repository navigation
feat: add recovery summary to session history export - #46
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Exported session Markdown now includes a recovery summary for non-empty selections. It counts messages from you and Pi, counts completed, failed and running tool calls, and lists distinct tool names in first-use order. Empty exports keep their existing shape.
Part of #4
Closes #45
Verification
bun install --frozen-lockfilepassed with the pinned mise toolchain, Node 22.23.0 and Bun 1.3.14.mise run buildpassed, includingbun run lint,bun run typecheck,bun run test:unit(84 tests),bun run test:integration(46 tests), main/preload compilation and Vite bundling.summarises tool outcomes and distinct tools in first-use order,handles an empty selection and a blank title, andwrites the full conversation with context and tool input.bun run test:e2epassed all 43 tests across five files (151.65 seconds). The previous loopback sandbox block was cleared with the required desktop/loopback access.Proof
Capture methods (a), (c) and (d) succeeded. E2E output is saved locally at
.tmp/proof/pr-46-e2e.log. The inspected session-history screenshot at.tmp/proof/pr-46-history.pngis supporting evidence of the existing Export surface, not a picture of the exported summary. The terminal capture below comes from the realsessionExportMarkdownfunction at PR head3491ef2125d2ca3866cf6483740ada61f909a225. Local scratch captures are.tmp/proof/pr-46-build.logand.tmp/proof/pr-46-export.txt; they are not committed. The visible change is exported text, with no new in-app surface.Gaps
This slice summarises exported text. In-app recovery summaries, folder-to-folder archive relocation and a migration wizard remain outside this slice. The Vite build reports its existing large-chunk warning, and e2e logs SVG property warnings. Neither failed a gate. All requested verification gates passed; no environment gaps remain for this run.