fix(spec): make the two citations this branch rewrote resolve

`check-issue-citations` judges only what a change ADDS, and this branch
rewrote both lines, so both are ours to answer.

view.zod.ts: spell the citation bare. The qualified form named this
repository, which the classifier recognises — and then looks the number up
on a board the probe never asked for it, because the probe only fetches
unqualified citations. The target exists; the bare spelling is the grammar's
form for this repository and it now resolves.

component.zod.ts: the number this sentence carried is DELETED, probed with
`--probe-cause` (minted, gone from the board, 404 on the web endpoint too),
so no target resolves and none is guessed. The sentence now states that in
prose and names the live record — this block, and the pin-citation gate
whose header carries the same rule. The later paragraph's unchanged mention
is left as it stands on main.

Claude-Session: https://claude.ai/code/session_012GcsUbuqFGBibkEDMRC1eE
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

packages/spec/src/ui/component.zod.ts

@@ -2132,7 +2132,15 @@ export const ElementButtonPropsSchema = lazySchema(() => strictObject({
    * `lucide-react` directly — and the registration's two ranges both moved and
    * SHRANK, the input list having lost its per-input `label` and
    * `defaultValue` members. What each anchor asserts is re-stated below from
-   * the new tree, never inferred from the old one (#10274); the read point
+   * the new tree, never inferred from the old one — the re-READ discipline
+   * this block records, and which the later paragraph below still cites by
+   * number. ⚠️ That number does NOT resolve: objectstack issue 10274 was probed
+   * 2026-09-20 with `scripts/check-issue-citations.mjs --probe-cause` and came
+   * back minted, gone from the board and 404 on the web endpoint too — DELETED,
+   * not transferred. ⛔ No replacement number is guessed here: the live record
+   * of the discipline is THIS BLOCK, together with
+   * `check:objectui-pin-citations`, whose header states the same rule and whose
+   * refusal text enforces it. The read point
    * first MOVED rather than died on the earlier hop onto `9602dc820`, which is
    * why the anchors span a second
    * file):

packages/spec/src/ui/view.zod.ts

@@ -2951,7 +2951,7 @@ const FormFieldBaseSchema = lazySchema(() => {
    * tier. ⚠️ This is the re-read the previous revision of this block asked for:
    * objectui#9244 / objectui#9253 (objectui `bd09957380`, 2026-09-12) land
    * inside the `53ded82bf7...87af769e9` range, so the widest-tier-only
-   * under-span this block used to record (objectstack#17328: one cell of two at
+   * under-span this block used to record (#17328: one cell of two at
    * 720px) no longer reproduces at the pin this repo builds against.
    */
   span: z.enum(['auto', 'full']).default('auto').describe("Relative field width. 'auto' (default — omit it): the renderer sizes the field from its widget type × the current column count — at the pin this repo builds against (`.objectui-sha` = `87af769e9`), only textarea, markdown, html, richtext and repeater resolve to the full column count (repeater reaches it through the wide `field:grid` widget it maps to). 'full': resolves to the form grid's full column count. How far down the container-query tiers that span is emitted is the renderer's, not this key's: at that same pin the renderer emits one clamped col-span class per multi-column tier (`@md:col-span-2 @2xl:col-span-3` for a 3-column grid), so the field takes the whole row at every multi-column tier, not just the widest."),