docs(audit): verify the project board now that the scope is available - #50
Merged
Merged
Conversation
The Milestone 2 close-out recorded the project board as unverified: a user-level Projects v2 board needs the `project` scope, which the token in use at the time did not carry. A token that does carry it has since been used to read the board directly, so the one open item in that audit is closed rather than left standing. Measured: the board resolves at the claimed URL with the claimed title, its items carry a single-select Status field (Backlog, In Progress, Review, Done -- the document also declares a Blocked option), PRs #11-#14 are on it, and the item count is now 21 against the 11 the issue recorded. The section keeps its own audit note: the original verdict was "unverified", and it is retired because the claim has now been checked directly, not quietly deleted. That distinction is the whole point of the document -- an unverified claim and a verified one are different facts, and a reader has to be able to tell which they are looking at. Refs #15
|
Warning Review limit reachedNext included review available in 16 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
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.
Refs #15 (closed) — a follow-up to the Milestone 2 close-out audit.
The audit recorded one claim it could not check: the project board, because reading a
user-level Projects v2 board needs the
projectscope and the available credentialsdid not carry it. The audit said so explicitly rather than assuming the board existed.
That scope is now available, so the claim has been read directly:
Cladistics Development";
Backlog,In Progress,Review,Done— and the milestone document also declares aBlockedoption;same direction the audit found for the test counts.
Verdict: holds. All three open PRs merged ahead of this one, and the two main CI
runs carrying the R-probe fix and the audit have completed green (19:21 and 29:18).
The section keeps a note that its verdict was originally "unverified" and is retired
because the claim was subsequently checked. An unverified claim and a verified one are
different facts; a reader should be able to tell which they are looking at, and the
record of having said so is worth keeping rather than editing away.