-
Notifications
You must be signed in to change notification settings - Fork 1
review: an author acknowledgment stops reading as unaddressed #367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
jwbron
wants to merge
2
commits into
main
Choose a base branch
from
agent/pra47-ack-rule
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| "review": minor | ||
| --- | ||
|
|
||
| An author acknowledgment stops reading as "unaddressed": the thread-reconciler now reports kept threads whose reply chain shows the author conceded the finding (will fix, TODO stands in) as `acknowledged`, code verifies the mechanical preconditions for each id against the staged reply chain (keep membership required, the PR author must actually have replied, bot replies never count, no staged author verifies nothing; whether the reply concedes rather than pushes back stays the reconciler's judgment), and the re-review recap counts those threads as "acknowledged (fix pending)" instead of unaddressed. An acknowledged blocking thread still renders visibly and still counts toward `keptBlockingCount`, so the flip gate is unchanged. The verified ids are recorded in `rereview.json`; nothing consumes them yet. | ||
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
issue (blocking, best-practice): Versioning: a workflow change must ship a changeset that bumps the
reviewpackage.workflows/review/README.md(the review-workflow-contract skill), Versioning, states the rule: "Published as git tags via the repo's changeset →utils/run-publish.tsrelease flow. A change to this workflow lands with a changeset bumping thereviewpackage; on release areview-v<major>.<minor>.<patch>tag (and a movingreview-v<major>tag) is cut at the real commit tree".The added changeset carries no package bump — its whole frontmatter is two consecutive delimiters:
That is an empty (no-op) changeset. I confirmed on the checkout that this is a divergence, not a house convention:
workflows/review/package.jsonis at"version": "1.17.1",.changeset/config.jsonhas an emptyignore: [](soreviewis not exempt), andworkflows/review/CHANGELOG.mdshows every prior comparable change shipping a real bump —1.17.0for the 👎-adjudication behavior change and1.16.0for thelinguist-generatednegation change, both of which are the same class of reviewer-behavior change as this one. This PR is squarely a behavior change to the shipped workflow: it adds anacknowledgedoutput to thethread-reconcilerprompt (workflows/review/review.md), a newverifiedAcknowledgedIdsverification path plus new recap wording (workflows/review/lib/rereview.ts), and newrereview.jsonartifact fields.Fix: give the changeset a package bump line, matching the minor-bump precedent set by
1.16.0/1.17.0for reviewer-behavior changes.A sketch, not a committable replacement:
review details
found by skill-auditor | also flagged by completeness