feat: page-specific factor classification + best-page context (3.1.0)#48
Merged
Conversation
Sitemap and static cross-cutting rollups now classify each factor as sitewide, limited, or opportunity. Page-specific factors (FAQ, Definition Blocks) no longer float to the top of prioritizedFixes on a structurally-inflated "affected" count: a present-but-isolated factor becomes a scoped limited tune-up and an absent one a discretionary opportunity. Every cross-cutting issue and fix also carries bestScore/bestPageUrl so a gap reads as "propagate from the strongest page" rather than a bare "add it". Text/markdown reports gain status labels and a best-page column; schemaVersion bumped to 2.1 (additive), package to 3.1.0, with docs, CHANGELOG, and the skill updated to match. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…atters An opportunity factor is absent from every audited page, so the Prioritized Fixes line printing "best 0/100 on /" is noise (the Cross-Cutting section already suppresses it). Guard both the text and markdown formatters to skip the best annotation when status is opportunity, and add a formatter regression test covering both. Co-Authored-By: Claude Opus 4.8 <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 sitemap and static cross-cutting rollups now classify each factor as
sitewide,limited, oropportunity, so page-specific factors (FAQ, Definition Blocks) are no longer ranked as site-wide failures on a structurally-inflated "affected" count — a present-but-isolated factor becomes a scopedlimitedtune-up and an absent one a discretionaryopportunity. Every cross-cutting issue and fix also carriesbestScore/bestPageUrlso a gap reads as "propagate the template from the strongest page" rather than a bare "add it", and the text/markdown reports gain status labels plus a best-page column.schemaVersionis bumped to2.1(additive — existing fields unchanged) and the package to3.1.0, withdocs/, the CHANGELOG, and the AEO skill updated to match. It also wires the audited pages intobuildPrioritizedFixesfrom the static-audit path (the call site the new fourth argument missed, which otherwise leftlimitedfixes with an emptyaffectedPagesand a "present on 0 pages" summary), backed by an integration regression test.🤖 Generated with Claude Code