[cixzhang]

Exact decision needed

Promote component:EmptyState from draft to current, recording EmptyState's shipped behavior on main today. No behavior, API, or output change.

Existing authority searched

• component:EmptyState on main (draft, template 3): the glance table, FR1–FR6, AV1–AV2, ORD1, PR1, AR1–AR3 (including the spec:AST-086 FR2 announcement), and the theming anatomy were re-verified against EmptyState.tsx and kept, rewritten as present-tense invariants in template 7.
• spec:AST-086 (current) owns the announcement the record's AR3 applies.
• pnpm specs:for packages/core/src/EmptyState/EmptyState.tsx: directory-wide architecture records.
• Overlapping open work: docs(knowledge): every component spec lives in docs/specs/components, one folder per component #9007 and feat(knowledge): check every specification in the repository as a knowledge record, and convert the native specs #8288 rebase on top of this record (docs(knowledge): every component spec lives in docs/specs/components, one folder per component #9007 moves component specs to docs/specs/components/; feat(knowledge): check every specification in the repository as a knowledge record, and convert the native specs #8288 migrates records to schema 5). This record keeps the colocated, schema-3 path main uses today.
• Open issues: none for EmptyState.

Decision

packages/core/src/EmptyState/EmptyState.spec.md: authority: current, approved_by: cixzhang, approved_at: 2026-10-31, owners unchanged, template 7, behavioral table headed "Invariant | Basis". The spec:AST-029/FR3 process link is dropped and spec:AST-009 added for accessibility-tree evidence.

Rejected alternatives

None.

Claim scope and non-goals

Covers only EmptyState as shipped on main. Message copy, icon meaning, and actions stay with the caller; heading order stays with the page. No new behavior is decided.

Evidence and implementation relationship

• FR1, FR3, FR4, AR2: slot, order, decorative-icon, empty-slot, and live-role tests; stable visual baseline core-emptystate--default.
• FR2, AR1: heading tests.
• AR3: EmptyState.announce.test.tsx.
• FR5, ORD1: ref, data-testid, and root-composition tests.
• FR6: compact and theming-target tests.

Writing rubric results

• R1 narration: the draft's "observational", "runtime remediation", "Draft requirements identify their basis…", and "verify" review-state cells are rewritten in the present tense.
• R2 research in the record: none.
• R3 evidence naming a change: none.
• R4 rejected alternatives over one line or outside a decision: none.
• R5 pull request or issue references remaining: none (searched # + digits, /pull/, /issues/).
• R6 ruled open questions still listing options: none; no open questions.

Scope

• This PR contains specification records only.
• It records observable behavior and preserves equivalent internal implementations.
• Any named internal mechanism is intentionally public, names its dependent caller/system, and explains why an equivalent implementation would not satisfy the contract: none.
• Verification states the evidence layer and failure signal without prescribing CI job/workflow topology.
• It records one intentional durable decision, not a rescue for a separable tagalong.
• The canonical knowledge owner, affected current claims, and overlapping open work are named; no ownership collision.
• Adjacent API, visual, accessibility, composition, and implementation facts remain outside scope unless this exact decision depends on them.
• Public text and artifacts contain no internal Meta context.

Validation

• pnpm check:knowledge: aligned
• Prettier: clean
• git diff --check: clean

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
astryx	Ready	Preview	Oct 31, 2026 12:14pm UTC

[astracat-bot]

AI review status for this pull request.

Review status	Updated
❓ Needs maintainer input (for maintainers only)	Oct 31, 2026, 12:21 PM UTC

[astracat-bot]

This record matches EmptyState as it ships, but it can't become current until an engineering owner approves its content at this head: FR1–FR6, AR1–AR3, ORD1, PR1 and the verification map with its named gaps. An engineering owner records that by commenting /approve-spec <full head SHA> on this pull request, and the author may do so as an engineering owner. Please make the fix below first, because any later commit to the record needs a fresh approval.

• The FR5/ORD1 verification row says the ref test catches a ref on another element, but forwards ref only checks for a div, so a ref placed on the text-group wrapper still passes it; name that gap in the row or assert that ref.current is the root.

[Automated review]

[astracat-bot]

This row credits the ref test with failing for "a ref on another element", but forwards ref only asserts that ref.current is an HTMLDivElement, and the text-group wrapper is a div too. Spreading the ref onto <AnnounceRenderedText> instead of the root type-checks and leaves all 23 EmptyState.test.tsx tests green; today only the announcement tests catch it, by side effect. Either add Gap: the ref test checks only that the ref is a div, not that it is the root. here, or tighten the test to expect(ref.current).toBe(container.firstElementChild).

[astracat-bot]

This record matches EmptyState as it ships and now names the ref gap, but it can't become current until an engineering owner approves its content: FR1–FR6, AR1–AR3, ORD1, PR1 and the verification map with its named gaps. An engineering owner records that by commenting /approve-spec <full head SHA> on this pull request, and the author may do so as an engineering owner. Please make the fix below first, because any later edit to the record needs a fresh approval.

• The FR5/ORD1 row credits the root-composition test for ORD1, but moving xstyle ahead of the component styles in EmptyState.tsx still passes every EmptyState test; add Gap: no test asserts that caller xstyle follows the component styles. to the row, or add a test with a conflicting caller xstyle.

[Automated review]

[astracat-bot]

This row also covers ORD1, but composes root props only checks that the caller's xstyle class is present. Moving xstyle ahead of styles.container in stylex.props (so a caller's gap or padding loses) keeps every EmptyState test green. Please add Gap: no test asserts that caller xstyle follows the component styles. here, or add a test with a conflicting caller xstyle.

[astracat-bot]

This record matches EmptyState as it ships and now names the xstyle-order gap, but it can't become current until an engineering owner approves its content: FR1–FR6, AR1–AR3, ORD1, PR1 and the verification map with its named gaps. An engineering owner records that by commenting /approve-spec <full head SHA> on this pull request, and the author may do so as an engineering owner. Please make the fix below first, because any later edit to the record needs a fresh approval.

• The FR2/AR1 and AR3 verification rows credit tests that stay green when the title's type style changes with its heading level or when EmptyState moves focus to its heading; add Gap: no check that the title keeps one type style at every heading level. and Gap: no test asserts that focus stays where it was when EmptyState appears. to those rows, or add the tests.

[Automated review]

[astracat-bot]

FR2 also promises the title keeps one visual type role at every heading level, but the heading tests only check the element, and the core-emptystate--default baseline renders level 3. Tying the title style to the level (for example (isCompact || headingLevel !== 3) && styles.titleCompact) leaves every EmptyState test green. Add Gap: no check that the title keeps one type style at every heading level., or a test that compares levels.

[astracat-bot]

AR3 also says EmptyState does not move focus, and nothing here checks it: a heading that focuses itself on mount passes every EmptyState test. Add Gap: no test asserts that focus stays where it was when EmptyState appears., or a test that keeps focus on a field while EmptyState mounts.

[astracat-bot]

This record matches EmptyState as it ships and now names every gap its tests leave, including the title's type style at every heading level and focus, so the record itself needs no further change. It can become current once an engineering owner approves its content at this head: FR1–FR6, AV1–AV2, AR1–AR3, ORD1, PR1, the theming anatomy and the verification map with its named gaps. An engineering owner records that by commenting /approve-spec <full head SHA> on this pull request, and the author may do so as an engineering owner; any later edit to the record needs a fresh approval.

[Automated review]

[cixzhang]

/approve-spec 552abbb