docs: refresh installation and feature guides for v2.6.1 - #25
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
1 participant
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.
The Chinese and English READMEs still mixed older install and upgrade instructions with v2.6 features. This refresh documents stable v2.6.1, all six platform downloads, checksum verification, exact installed executable paths, and the v2.5.0 cutoff for in-app updates.
It also explains task-tree usage and totals, persisted accounting time zones, history/rebuild boundaries, session search and cost consistency, macOS service setup, and the current build/CI workflow. Earlier screenshots and acceptance records are labeled as historical and linked to the current demo and verification notes.
Validation: checked all local links and section anchors, rendered both documents through GitHub GFM (seven tables and twelve sections each), matched all seven download targets against the uploaded stable release assets, confirmed both price tables are unchanged, and ran
git diff --check. Only README.md and README.en.md change; no version bump or new binary release is needed.