Repository navigation
[Docs] Explain partial Slack history and recovery - #3677
Draft
roomote-community[bot] wants to merge 1 commit into
Draft
roomote-community[bot] wants to merge 1 commit into
roomote-community[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
No issues found. See session Reviewed the Slack guide addition against the bounded history reader, independent history/response-size continuations, and thread-reply recovery notes. The documentation matches the implementation. Current-head docs validation, lint, type checks, and tests passed in CI. Reviewed 8b83581 |
5 of 8 tasks
This branch has not been deployed
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.
Related issue
Daily documentation accuracy audit for 2026-11-05T03:00:36.542Z through 2026-11-06T03:00:36.542Z; no linked issue.
Why this PR exists
What changed
Explain partial Slack channel history, including potentially missing older messages and thread replies, independent continuation reads, deduplication, and recovery through narrower time ranges or specific thread links. This helps readers interpret incomplete summaries without assuming the requested range was fully read. No runtime behavior changes.
The audit reviewed all four PRs merged in the exact window: #3645 (
ad72e01b), #3674 (345f05ee), #3675 (7d56d859), and production promotion #3676 (7dc2847b). Behavior was traced through the Slack notifier, API lookup and response-size budget, and session/task tool contracts. The promotion also first shipped earlier #3646 and #3666; Slack discovery guidance is already included in the release docs, and the Copilot endpoint repair changes no user configuration. Existing GitHub docs correctly distinguish read-only task MCP from the authorized source-control write workflow.Compared fetched develop
7d56d859with shipped main/v1.20.17dc2847b; their trees differ only in the changelog. Open documentation PRs were checked for overlap. In particular, #3669's discovery correction is already present in the release and does not cover partial history.How it was tested
mise exec -- pnpm --filter @roomote/docs checkpassed: pinned Mintlify build validation and no broken links.mise exec -- pnpm --filter @roomote/docs check-cookbook-indexpassed: seven recipes current.git diff --checkpassed.pnpm lint/pnpm check-typeswere not run for this docs-only correction. Repository source and release history were audited; live production deployment state was not independently verified.Checklist
[Fix],[Feat],[Improve],[Refactor],[Docs], or[Chore]followed by a user-facing descriptionpnpm lintandpnpm check-typespass locallypnpm changeset