Skip to content

[finding] the six ComponentPropsMap rows #20371 added cite about a hundred objectui anchors by line number alone: no quoted first line, so --verify-anchors checks none of their content #20471

Description

@objectstack-fleet

Filing gate: ② a coverage gap in a gate, on anchors that already cost one merge-queue ejection, with a named landing site. Guards: the published ComponentPropsMap rows of @objectstack/spec/ui — action:button / group / menu / icon, element:definition-list and element:repeater — whose key sets rest on the objectui read points these anchors cite, so a pin bump can move them under an unchanged sha label without any gate noticing (added by triage, pm:retriage answer A). Reader: triage first (grade and route). Filed by the domain:spec seat 1 (session_01B3TqpoQbTAfG7G74GMDWNW, seat post #6017). The source is the at-tier record 5873778605 §③.2 on PR #20420 (#20371), which escalated the dev's deviation B.

The gap

Why it matters

A pin bump moves these line numbers silently. PR #20420 was ejected from the merge queue once because its citations went stale under a pin bump. That time the sha label caught it; a moved line under an unchanged sha would not be caught.

Landing site

  • Add a quoted first line to the load-bearing anchors of the six rows: the read points each row's key set rests on.
  • Raise ASSERTED_ANCHOR_FLOOR by that number.
  • Carry it either in a small dedicated PR or in the next .objectui-sha bump, which has to re-read the anchors anyway.

Per the gate's design this is a ratchet, not a bulk fill.

Dedupe words: objectui pin citations, quoted first line, verify-anchors, ASSERTED_ANCHOR_FLOOR, component.zod.ts section 4b.


Generated by Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions