docs: record post-v1.12.0 work and what remains open - #154
Merged
Conversation
The roadmap had no unchecked items, which read as "nothing left to do". It was simply stale: six merged PRs were absent, one entry still described a feature PR as open after it had been merged, and none of the work done since the release appeared at all. That work did not come from this plan. It came from correcting the tool's stated purpose, which the review this roadmap derives from had misread. A note now says so at the top, so the derivation is not taken on trust, and the correction in REVIEW.md and the statement of purpose in AGENTS.md are pointed to as the things to read before planning further. Two items are recorded as genuinely open rather than left implicit: performance at scale is reasoned but never benchmarked, though "practical for large domain lists" is a claim the README makes; and the downstream consumer of these outputs will break on the format changes, since csp_matches went from prose to structured fields and three files gained new markers or columns. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
The roadmap had zero unchecked items, which reads as "nothing left to do". It was simply stale.
REVIEW.md— the review whose premise has since been corrected — with nothing to warn a reader of that.Changes
A note on its derivation. The plan came from a review that assessed the tool against a misread goal, treating cloud attribution as a supporting attribute rather than one of two co-equal products. The note points to the correction in
REVIEW.mdand the statement of purpose inAGENTS.mdas the things to read before planning further work.A "Since v1.12.0" section recording the six PRs, with the through-line stated plainly: the cloud-matching path is one of the tool1s two products and had never been assessed as such. It was discarding every field that made a match actionable, counting hosting-platform addresses as targets, and reporting a wildcard test that silently missed rotating pools. None of that was foreseen by the original review, because the review measured the wrong thing.
Two genuinely open items, rather than an empty list that implies completeness:
csp_matches_*.txtwent from prose to seven structured fields, two files gained aWILDCARD_ZONE|prefix, andtakeover_candidates_*.txtgained hop count and chain path.Documentation only.