Skip to content

chore(parity): max's store group is in both tools; store's old --since and --max-pages go - #347

Merged
leemour merged 1 commit into
mainfrom
chore/parity-store-both
Oct 1, 2026
Merged

leemour merged 1 commit into
mainfrom
chore/parity-store-both

Conversation

@leemour

@leemour leemour commented Oct 1, 2026

Copy link
Copy Markdown
Owner

Task

Close the store rows #333 left planned.

Why

max's main moved onto the shared store group (max-cli #307), so the rows can say both tools have it.

What

  • Every store row and option planned by T6 → both.
  • store fetch|export --since and store fetch --max-pages rows go; --max-pages leaves the catalogue (no command has it). --since stays: other commands use it.
  • docs/dev/STANDARD.md re-rendered; changelog under "Changed — may break callers".

Testing

  • pnpm lint && pnpm typecheck && pnpm test && pnpm docs:check — 719 tests pass.
  • max's main build piped into this build's dist/parity/bin.js max: no differences. tg's main: the Parity workflow on this PR.

Reviewed against the review checklist — §A for a docs PR, §B for code.

🤖 Generated with Claude Code

…and --max-pages go

max's main moved onto the shared store group (max-cli #307). store reindex
is max's until tg takes cli-messaging 0.97.0; --page-size's default is each
messenger's own, as its note says.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@leemour
leemour force-pushed the chore/parity-store-both branch from 727dd7f to ef1602a Compare October 1, 2026 20:50
@leemour
leemour merged commit d092a89 into main Oct 1, 2026
9 checks passed
@leemour
leemour deleted the chore/parity-store-both branch October 1, 2026 22:50
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.

1 participant