Repository navigation
Let sites set their own site name; prepare 2.2.0 - #5
Merged
Merged
Conversation
Renaming the site in the title band failed verify at tier 2, so every rename needed a human --accept. The site-title region now declares ignoreTextOf: ["a.title-header"], which drops only the text inside the two title links before the golden comparison and keeps their elements, classes, and href pinned. Tier 1 still compares the text across pages, and a new tier 3 hasText requirement keeps either link from being emptied. Tier 2 now re-canonicalizes the recorded golden tree under the current region options, so goldens accepted with 2.1.0 keep passing after upgrade. Rules, skill, and user guide tell agents to change only the text, on every page, and to always propose a short form for the link shown below 480px. Co-Authored-By: Claude Opus 5.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
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.
Why
Changing a site's name in the title band failed
verify, because the golden baseline pins the region's text:The site name belongs to the site, so every rename needing a human
--acceptwas the wrong default.What changed
Gate (
checks/,contracts/)ignoreTextOf. Thesite-titleregion setsignoreTextOf: ["a.title-header"]. Tier 2 drops only the text inside those links. Their elements, classes andhref, and the rest of the band (includinga.title-logo), stay pinned. An added<span>/<img>or a changedhrefstill fails.hasText.site-title.brandingnow requires exactly one long and one short title link, each non-empty.--acceptcannot clear this.--accept. A test covers this.ignoreTextOfandhasText.Rules and docs
rules/00-canvas.mdhas a new section: "The site name is the one piece of chrome text you may change." Agents change only the text, on every page (or in the nav/header data file), and always propose a short form for the link shown below 480px, even when only a long name was given ("Decorator V5" → "V5", roughly 12 characters max).protected-regions.md,canvas-contract.md,checks/README.mdand the user guide. Compiled rule files andlibrary/tritonai/are regenerated.Release
package.jsonand.claude-plugin/plugin.json, with aCHANGELOG.mdentry.Reviewer notes
base.css(the short link shows atmax-width: 479pxand is 20px uppercase at ≤360px), not a measured limit.v2.2.0to trigger the npm publish.Testing
npm test: compile check, library check, and 122 tests passing. The 9 new tests cover a rename on every page, a mismatch between pages, an element added inside a title link, anhrefchange, an emptied link, and the 2.1.0 golden migration.🤖 Generated with Claude Code