The model pin takes the surface type, and the parser pin follows it - #167
Merged
Conversation
The model gained a tenth type. A surface is a place the company publishes that no script writes, and the instance now holds one, the LinkedIn profile, so the stage draws 125 entities in ten types where it drew nine. Nothing on the timeline moved: no experience changed, and the type carries no dates. The parser pin moves with it, from v0.15.0 to v0.16.0. That release is the one that added the type, and its parser is unchanged, so the pin catches up rather than changing what this site reads. The principles page rebuilt because its footer carries the pinned commit, and three cards re-rendered because their pages moved. Verified: npm run verify passes against a served copy; model:check, pages:check, design:check, pin:check, og:check after npm run og, test:og, test:build, test:dupes, conventions-check and conventions-sync check all pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
robertblust
force-pushed
the
model-repin-surface
branch
from
September 9, 2026 22:12
991288f to
51efd16
Compare
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 model gained a tenth type. A surface is a place the company publishes that no script writes, and the instance now holds one, the LinkedIn profile, so the stage draws 125 entities in ten types where it drew nine. Nothing on the timeline moved: no experience changed, and the type carries no dates.
The parser pin moves with it, from v0.15.0 to v0.16.0. That release is the one that added the type, and its parser is unchanged, so the pin catches up rather than changing what this site reads. The principles page rebuilt because its footer carries the pinned commit, and three cards re-rendered because their pages moved.
Worth knowing why the pin took two attempts. The first model commit could not be parsed at all: the surface entity was named LinkedIn, which resolved the
Wherecell of the profile's## Also atrow, flipped that table from data to references, and failed R4 on the GitHub row that resolves to nothing. The instance renamed the entity to LinkedIn profile, which is the better name and ends a collision that was structural rather than unlucky —## Also atlists places, and a surface named for a place is named for one of them. The parser fix that would make the collision impossible, a table whose declared columns carry no reference type being data by declaration, is named in two designs and not yet made.Verified: npm run verify passes against a served copy; model:check, pages:check, design:check, og:check after npm run og, test:og, test:build, test:dupes, pin:check, conventions-check and conventions-sync check all pass. The model page's card is the only one whose pixels moved; principles and timeline changed their stamps alone.
🤖 Generated with Claude Code