Add Overleaf-style LaTeX version history with automatic checkpoints and visual diffs#1
Closed
SmallSpider0 wants to merge 6 commits into
Closed
Conversation
Owner
Author
|
Closing this fork-local PR; recreating the stacked LaTeX version-history PR against ResearAI/DeepScientist instead. |
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.
Follow-up
Follow-up to ResearAI#101: Improve LaTeX workspace, SyncTeX jumps, and edit safety.
ResearAI#101 makes the LaTeX editor behave like a safer Overleaf-style local workspace: one project editor, multi-file source switching, SyncTeX PDF-to-source jumps, denser editor chrome, and protection against external source edits.
This PR builds on that foundation by adding the missing version-history layer for LaTeX manuscripts.
Problem
After ResearAI#101, the LaTeX editor is much safer for active editing, but it still lacks an Overleaf-like way to inspect and recover historical manuscript states.
This matters because LaTeX papers are often edited over long sessions by both users and AI/file tools. Without visual version history, restore actions are risky: users can create or restore versions, but cannot easily see what changed before deciding whether to roll back.
A local-first research workspace needs more than source editing and PDF preview. It also needs lightweight, trustworthy manuscript history so users can understand changes, compare archive points, and recover earlier states without losing work.
Solution
This PR adds Git-backed LaTeX version history scoped to the current LaTeX project folder.
Backend:
.dsstate while keeping Git as the durable source of truth.Frontend:
Test
Result:
Local deployment smoke check:
http://127.0.0.1:20999/api/health