Add ACP cluster comparison report#12
Open
dutifulbob wants to merge 6 commits into
Open
Conversation
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.
Summary
The earlier manual ACP duplicate groups and the current
pr-search-cliissue clusters do not line up cleanly.This change adds a short report that compares them directly and states which grouping looks more faithful to the actual PRs.
It matters because we are likely going to keep updating this comparison as we refine the curated groups.
What Changed
The report compares the two earlier manual
prtagsgroups against the currentpr-search-clicluster output.It records the exact mismatches, then gives an objective read on which grouping looks more correct.
The main conclusion is that the manual
sessions_spawncluster looks better, while the/acpduplicate set is probably broader than either current narrow cluster.docs/2026-04-20-acp-cluster-comparison-report.mdprtagsgroupspr-search-clicluster resultssessions_spawncluster and broaden the/acpcluster to include#65248Testing
I only changed documentation here.
I ran the repository doc checks and whitespace check.
npx --yes @simpledoc/simpledoc@0.1.6 checkgit diff --checkRisks
The risk is low because this is only a report.
The only real risk is that the judgment in the report may need to change as we gather more evidence or update the clusters.
Follow-ups
We will likely keep updating this PR as the cluster comparison evolves.