Repository navigation
chore(parity): bot store fetch present in max; --refresh checked again - #425
Merged
Merged
Conversation
…fresh checked again Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Task
P8 B8 follow-up: max-cli #329 mounts
bot store fetch; max #328 and tg #222 both carry the neutral--refreshhelp (0.109.0).What
bot store/bot store fetch(every option): in max, planned for tg (a Telegram bot has no history call yet).bot contacts show --refresh→allagain.Testing
vitest run src/parity,pnpm docs:checkgreen;main (max),main (tg)andwordingcheck both mains.🤖 Generated with Claude Code