Skip to content

docs: Report status rename: TODO β†’ NEEDS_REVIEW#91

Open
NikitaVr wants to merge 2 commits into
mainfrom
knowledge-update/report-status-rename-todo-needs-review-1780119788955
Open

docs: Report status rename: TODO β†’ NEEDS_REVIEW#91
NikitaVr wants to merge 2 commits into
mainfrom
knowledge-update/report-status-rename-todo-needs-review-1780119788955

Conversation

@NikitaVr

@NikitaVr NikitaVr commented May 30, 2026

Copy link
Copy Markdown
Contributor

Knowledge Update: Report status rename: TODO β†’ NEEDS_REVIEW

This PR was automatically generated from a knowledge base update.

Changes

  • Reports (concepts/reports.mdx): Updated report status flow to reflect TODO β†’ NEEDS_REVIEW rename
  • Review (getting-started/how-it-works/review.mdx): Updated report status terminology from TODO to NEEDS_REVIEW in the review process explanation

Knowledge Entry

Topic: Report status rename: TODO β†’ NEEDS_REVIEW
Added by: neri@chainpatrol.io
Date: 2026-05-30

Content:

The report status previously labeled "TODO" has been renamed to "NEEDS_REVIEW". Reports now move through: NEEDS_REVIEW (waiting in queue) β†’ IN_PROGRESS (actively being reviewed) β†’ CLOSED (review complete). Update any references in docs/explanations accordingly.

Original Message

replaced TODO with NEEDS_REVIEW


Auto-generated by the ChainPatrol Knowledge Agent


Note

Low Risk
Documentation-only wording change with no runtime, API, or security behavior impact.

Overview
Renames the report lifecycle label from TODO to NEEDS_REVIEW across customer-facing docs so terminology matches the product.

In concepts/reports.mdx, the overview info callout, status list, β€œWhat Happens Next,” and key takeaways now describe the queue state as NEEDS_REVIEW β†’ IN_PROGRESS β†’ CLOSED. In getting-started/how-it-works/review.mdx, the review overview info block adds the same report status flow alongside existing proposal decision text.

Reviewed by Cursor Bugbot for commit 8615dc9. Bugbot is set up for automated code reviews on this repo. Configure here.

@mintlify

mintlify Bot commented May 30, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
chainpatrol πŸ”΄ Failed – May 30, 2026, 5:44 AM

πŸ’‘ Tip: Enable Workflows to automatically generate PRs for you.

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