Repository navigation
spec(AST-112): keep the package's shape; move the rest to its owners - #13029
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
AI review status for this pull request.
|
This was referenced Nov 19, 2026
Contributor
|
/approve-spec 459e440 |
imdreamrunner
force-pushed
the
spec/ast-112-slim
branch
from
November 20, 2026 01:58
336d83b to
04486d1
Compare
Contributor
Author
|
/approve-spec 69fc687 |
imdreamrunner
marked this pull request as ready for review
November 20, 2026 02:01
This branch was successfully deployed
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.
spec:AST-112keeps only the React Native package's shape: the package set, the two layers and their dependency rules, default linking, where native code lives, the public entries, the capability shape, building on core, the build system, the release train, the evidence bar, accessibility, and where each native piece lives. Everything else moves to the record onmainthat owns it, or is removed. A new draft record,spec:AST-142(React Native commands), takes theastryx rnCLI.Exact decision needed
Whether
spec:AST-112's claims move to the newspec:AST-142and tospec:AST-140, or leave the record, as listed under Decision. Every moved decision keeps its decider and date.Existing authority searched
spec:AST-112andspec:AST-140onmain(both draft records), including the runtime-boundary edits that merged in spec(AST-112): runtime boundaries #12998.spec:AST-112claim (FR6, FR8, FR13, FR16, FR17, FR18, FR21, FR22, FR23, DEC-15, and FR4's public-API line).spec:AST-114,spec:AST-042andarchitecture:cli-surface, which the CLI's Current-state entries amend;spec:AST-114's Non-goals cite the moved FR13 and OQ5.spec:AST-140follow-ups) has merged; this branch is rebased on it and keeps its text.spec:AST-112here.surfaceon Button and IconButton):spec:AST-082DEC-2's Current-state entry stays as onmain.Decision
docs/specs/AST-112-react-native-foundation/spec.md(spec:AST-112):spec:AST-140; FR17; the Platform asks section; FR5's line on names.does not export; FR18 (gesture arbitration) and FR21 (glass and materials), each with its verification row; FR2's two router lines; FR7's group table and the line that introduces it; the Current-state entry on the group records. References to FR6 and FR8 now point tospec:AST-140FR3 and FR5 (DEC-4 tospec:AST-140DEC-5). FR8's canary note stays as a line under FR7.main, other thanspec:AST-142, which this pull request adds. Pointers to removed claims are dropped (FR2's recognizer line, FR5's router line and the./controlsline, DEC-9, and the end of thespec:AST-082DEC-2 entry); FR20's coexistence pointer citesspec:AST-140/FR9.@astryxdesign/cli,spec:AST-114×3,spec:AST-042,architecture:cli-surface), and the./commandslines of FR2 and FR5 move to the newspec:AST-142as FR1, DEC-1, OQ1, OQ2, FR1's row and its Current-state impact. DEC-1 keeps Decider: imdreamrunner, 2026-11-17. FR1 ofspec:AST-112keeps one line: the React Native commands are theastryx rngroup, whichspec:AST-142specifies; FR5 keeps a one-line pointer for the./commandsentry.affects_architectureandaffects_consumer_docsmove with them.spec:AST-140DEC-6 already decides it. Its FR4 requirement lines becomespec:AST-140FR9 lines that cite DEC-6, with their two verification rows. The library's code now meets its five gap lines, so they do not move; FR9 gains one gap line for what remains: VideoView's full-screen presentation on iOS uses React Native'sModal.spec:AST-140as DEC-10 and an FR9 line (Decider: imdreamrunner, 2026-11-19). The code now meets its gap line, so the gap line does not move.spec:AST-140states are removed: FR2's motion line (spec:AST-140FR6, which gains the line's clause that the feel followsspec:AST-107andspec:AST-108), and FR2's third-party coexistence line (spec:AST-140FR9, which gains its compatibility test, its haptics library and its inset agreement, and their failures in FR9's verification row). FR2 keeps "no third-party native dependency". FR4's public-API line and DEC-15 move tospec:AST-140FR9 and DEC-9 (Decider: imdreamrunner, 2026-11-17), and FR4's public-API check moves to FR9's first verification row.main: DEC-9 (without pointers to removed claims), DEC-10 and itsIntland unsupported-platform lines, DEC-18 and its non-goal, FR23, DEC-20 (Decider: cixzhang, 2026-11-18) and thespec:AST-017FR27 entry, and thespec:AST-082DEC-2 Current-state entry (Decider: cixzhang, 2026-11-18) without its pointer to the removed FR21.docs/specs/AST-140-react-native-platform-code/spec.md(spec:AST-140): FR6 gains the motion-feel clause; FR9 gains the moved lines, the VideoView gap line, DEC-9 and DEC-10, and three verification rows. It drops its citations ofspec:AST-112FR18 and FR22 and of the group records: the "Platform group records" section, the group-record line under "Related records", the Current-state line on the group records, and thespec:AST-130citations in FR4 and FR5; the Intent and "Why this exists" lines keep their rule without the pointer. DEC-15's citation points to DEC-9. The branch is rebased onmainafter #12988, whose text is kept where the two met (the Verification table).docs/specs/AST-114-bases/spec.md(spec:AST-114): its Non-goals line on React Native platform commands citesspec:AST-142FR1 and OQ1 instead ofspec:AST-112FR13 and OQ5.docs/specs/AST-142-react-native-commands/spec.md(spec:AST-142, new, draft, owners [imdreamrunner]): theastryx rngroup, as moved. It is a separate record because the commands are a CLI surface: they followspec:AST-114,spec:AST-042andarchitecture:cli-surface, and a CLI change no longer edits the package record.Open drafts
The open drafts state the removed claims in their own records: #12562 (gesture arbitration), #12557, #12817 and #12820 (glass and
surface), #12554 (the router) and #12596 (the lab start). Citation-only updates went to #12867, #12850, #12838, #12834, #12822 and #12686 (FR10 for web parity), #12555 (FR5 for internal views), and #12553, #12552 and #12551 (spec:AST-140FR9 and DEC-9 for public platform API).Drafts that cite
spec:AST-112FR21 forrenderkeep those lines for their ownrenderfixes.Rejected alternatives
None recorded in the records.
Claim scope and non-goals
Only the moves and removals above. The contracts bullet, OQ2, OQ3 and OQ8 stay. No moved rule changes its content.
Evidence and implementation relationship
The records are specifications only and have no implementation in this pull request.
Writing rubric results
Rejected:lines.spec:AST-142OQ1 and OQ2 andspec:AST-112OQ2, OQ3, OQ7 and OQ8 are unanswered and keep their options.FRn gap:form.Scope
Validation
node scripts/check-knowledge.mjs: knowledge templates and records are aligned (exit 0), here and on each open draft above.--checkclean on every changed record.git diff --check: clean.