@starci/hfs 4.7.34 → 4.7.36

package/runtime/knowledge/hfs/slots.yaml

@@ -2396,9 +2396,9 @@ slots:
     presence: required
     tracked: tracked
     tier: foundation
-    # The app's i18n module: its catalogs and the one call of the repository's i18n factory. The next-intl stack (routing,
-    # navigation, request config) is written once per repository: in the i18n package (fe.package.i18n, `createAppI18n`)
-    # when the repository has one, else in the only app's module.
+    # The app's routing, request config and catalogs, or its adapter to the shared i18n factory. A single app
+    # owns createNavigation in fe.modules.routes, keeping this public entry safe for its proxy. Shared stacks
+    # belong to fe.package.i18n and expose a routing-only proxy entry separately from navigation.
     requires: [index.ts]
     tests: none
     rules: [FE_I18N_PLACEMENT, FE_I18N_CATALOG]

package/runtime/knowledge/ui/presentation/font.yaml

@@ -0,0 +1,101 @@
+schema: starci/knowledge-source@1
+id: ui.presentation.font
+title: Font presentation
+appliesTo:
+  - ui
+family: presentation
+purpose: Choose information rank and document semantics before typography. A heading establishes structure;
+  ordinary copy does not. The selected Grammar owns the concrete type scale, renderers, props, weights, line
+  heights and tracking under FE-RULE-OWNERSHIP. Applications compose that public contract and write
+  layout-only CSS.
+ownerVocabulary:
+  owners:
+    - name: The selected text renderer
+      meaning: Ordinary copy has no heading semantics
+      applicationWrites: The published semantic rank through the selected Grammar API
+    - name: The selected heading renderer
+      meaning: A heading declares its actual document position
+      applicationWrites: Its semantic level and any published emphasis treatment
+  notes: Information rank belongs to the application; its visual realization belongs to the selected Grammar. A
+    missing typography capability is a Grammar gap, never permission to override a component with application
+    typography CSS.
+guidance:
+  - id: weight
+    title: Weight
+    requirement: Weight refines an already chosen information rank. It does not create a hierarchy level or
+      substitute for a heading. Use only the selected Grammar's published weight treatment; its concrete
+      weights, defaults and renderer props belong to that family. Document structure remains meaningful when
+      weight or colour is removed.
+rules:
+  - id: FONT-1
+    title: Lowest supporting rank
+    governs: Supporting metadata remains subordinate while staying readable. The selected Grammar chooses its
+      exact size and treatment.
+    cases:
+      - id: case-1
+        when: Brief metadata remains understandable at the lowest supporting rank
+        owner: The selected text renderer
+        render: Compose its published supporting-copy treatment.
+      - id: case-2
+        when: A nested region has a label within an already titled section
+        owner: The selected heading renderer
+        render: Declare the nested region's actual document position; use the selected Grammar's corresponding recipe.
+    notThisRule: Ordinary sentences and important facts must not be demoted to the lowest supporting rank.
+  - id: FONT-2
+    title: Supporting reading rank
+    governs: A complete supporting line remains readable and visibly below ordinary reading copy.
+    cases:
+      - id: case-1
+        when: A complete supporting line such as a timestamp or short fact sits below normal body copy
+        owner: The selected text renderer
+        render: Compose the published supporting reading rank without reducing readability.
+      - id: case-2
+        when: A subordinate region is nested within a section
+        owner: The selected heading renderer
+        render: Keep its document nesting and published heading treatment aligned.
+    notThisRule: Do not shrink body copy to fit an undersized container; repair its layout.
+  - id: FONT-3
+    title: Ordinary reading rank
+    governs: Explanatory copy has the normal reading priority of its region. Its visual recipe comes from the
+      selected Grammar.
+    cases:
+      - id: case-1
+        when: Ordinary explanatory copy has normal reading priority
+        owner: The selected text renderer
+        render: Use the normal reading treatment supplied by the selected Grammar.
+      - id: case-2
+        when: A section has its own heading inside a page
+        owner: The selected heading renderer
+        render: Declare the section's structural position independently of its size.
+  - id: FONT-4
+    title: Page-heading rank
+    governs: The heading that names a page carries the primary structural rank of that document.
+    cases:
+      - id: case-1
+        when: The single heading names the whole page or route
+        owner: The selected heading renderer
+        render: Use the page-heading role and its published family treatment.
+    notThisRule: One document has one top-level page heading. A second page-heading role is a structural conflict.
+  - id: FONT-5
+    title: Leading-value emphasis
+    governs: The principal numeric value or short fact of a region may carry emphasis without acquiring heading
+      semantics.
+    cases:
+      - id: case-1
+        when: A leading metric or short value is the main fact of its region
+        owner: The selected text renderer
+        render: Use the family's published value-emphasis treatment while retaining text semantics.
+    notThisRule: Value emphasis is not decoration, sentence styling or an imitation of a heading.
+  - id: FONT-6
+    title: Display emphasis preserves structure
+    governs: A page introduction may use the selected Grammar's display treatment while preserving the heading's
+      actual semantic position.
+    cases:
+      - id: case-1
+        when: A page introduction needs marketing or landing emphasis
+        owner: The selected heading renderer
+        render: Apply the published display treatment while keeping the document outline unchanged.
+    notThisRule: A nested heading never gains a different outline position merely to obtain visual emphasis.
+doesNotDecide: |-
+  Which colour expresses the rank is [Tone](tone.yaml). How the line wraps, aligns, or truncates is
+  [Text flow](text-flow.yaml). How much room the text region gets is [Measure](measure.yaml).

package/runtime/knowledge/ui/presentation/padding.yaml

@@ -0,0 +1,217 @@
+schema: starci/knowledge-source@1
+id: ui.presentation.padding
+title: Padding presentation
+appliesTo:
+  - ui
+family: presentation
+purpose: Resolve one owned content edge per boundary. Applications write layout insets only for boundaries
+  they own; a selected Grammar owns its components' internal insets and the values of its published scale.
+  FE-RULE-OWNERSHIP keeps these universal requirements separate from family recipes.
+ownerVocabulary:
+  owners:
+    - name: Application layout
+      meaning: The application owns this layout boundary
+      applicationWrites: Its one layout inset from the selected Grammar scale
+    - name: Selected Grammar component
+      meaning: The published component owns this boundary
+      applicationWrites: Compose its published API
+  notes: Every boundary has one inset owner. Reimplementing an owned component inset or overriding its internal
+    geometry violates that ownership. A missing component capability is repaired in the Grammar.
+guidance:
+  - id: side-contact
+    title: Side contact
+    requirement: Resolve each side from the boundary it meets. An outer edge takes the published content
+      clearance; a separator-facing side takes the published separator clearance; a side already owned by a
+      child adds no inset. Inline sides of peer bands align. The selected Grammar owns the exact values and
+      flush-band API.
+  - id: composite-insets
+    title: Composite insets
+    requirement: An asymmetric inset recipe composes published scale values. Each side has an explicit boundary
+      reason; the recipe introduces no new value. Preserve an existing recipe identity when its purpose is
+      unchanged, and declare a new recipe only for a distinct boundary relationship.
+  - id: axis-variants
+    title: Axis variants
+    requirement: An inset may apply to logical inline sides, block sides or one side independently. A narrower
+      declaration on the same element replaces its selected sides; padding on nested elements adds. Do not
+      introduce a wrapper merely to change a side that its owner already controls.
+rules:
+  - id: PADDING-0
+    title: No duplicate inset
+    governs: A boundary contributes no extra space when content or a child already owns its edge.
+    cases:
+      - id: case-1
+        when: A container only groups children that each carry their own boundary
+        owner: Application layout
+        render: Group without adding another inset.
+      - id: case-2
+        when: Surface bands run flush to the surface edge
+        owner: The surface component
+        render: Compose its published flush-band treatment.
+      - id: case-3
+        when: A list sits inside a panel or its rows own their own inset
+        owner: The list component
+        render: "Owner ruling 2026-10-25 (owner:panel-list-box-edge): the row box aligns with the panel content
+          edge, like the search field and tabs boxes. Content retains the vendor item inset and rounded
+          interaction background inside that box; the list keeps its vendor inset without negative-margin
+          bleed. Compose without padding wrappers. The selected Grammar supplies the panel-alignment API;
+          the universal FE canon reports stacked padding as FE_LIST_PANEL_PADDING."
+    notThisRule: The boundary protecting readable content keeps its one owned inset from the selected Grammar scale.
+  - id: PADDING-1
+    title: Minimal clearance
+    governs: Use the selected Grammar's smallest published inset where a deliberately tiny boundary nearly fits
+      its content.
+    cases:
+      - id: case-1
+        when: A compact marker or key floats over an application-owned canvas
+        owner: Application layout
+        render: Choose the smallest published inset that clears the marker content.
+      - id: case-2
+        when: A scroll region reserves room for focus visibility
+        owner: The scroll-region component
+        render: Compose the region; its focus clearance owns this inset.
+      - id: case-3
+        when: A short hint is attached to a control
+        owner: The hint component
+        render: Compose the hint; its internal inset stays with the component.
+  - id: PADDING-2
+    title: Compact clearance
+    governs: Use the published compact inset for an auxiliary boundary that needs clear but economical edge space.
+    cases:
+      - id: case-1
+        when: An auxiliary strip shares one inset on all sides
+        owner: Application layout
+        render: Apply the published compact inset once.
+      - id: case-2
+        when: A compact control bar sits above application-owned content
+        owner: Application layout
+        render: Keep its edge clearance and sibling gap as separate decisions.
+    notThisRule: Space between siblings belongs to the parent gap, not the boundary inset.
+  - id: PADDING-3
+    title: Dense content clearance
+    governs: Use the published dense inset for readable nested content and separator-facing band edges.
+    cases:
+      - id: case-1
+        when: A nested container owns a boundary distinct from its parent
+        owner: Application layout
+        render: Apply the published dense inset to that distinct boundary.
+      - id: case-2
+        when: A tab strip or secondary navigation needs inline clearance
+        owner: The navigation component
+        render: Compose its published inset API.
+      - id: case-3
+        when: A band side meets a separator inside a flush surface
+        owner: The selected Grammar recipe
+        render: Use its separator-facing clearance while retaining inline alignment.
+      - id: case-4
+        when: A metric cell or list row meets a separator
+        owner: The metric or list component
+        render: The separator-facing side uses its published dense clearance.
+    notThisRule: Repeating the same inset for the same boundary doubles it along the path from outer edge to content.
+  - id: PADDING-4
+    title: Readable content clearance
+    governs: Use the published content inset once at the boundary that protects readable content.
+    cases:
+      - id: case-1
+        when: An application section owns the distance from its border to its content
+        owner: Application layout
+        render: Apply the published content inset once.
+      - id: case-2
+        when: Content sits inside a card
+        owner: The card component
+        render: Compose the card; its content inset remains component-owned.
+      - id: case-3
+        when: A disclosure has a trigger and expanded panel
+        owner: The disclosure component
+        render: Compose the disclosure; its trigger and panel own their insets.
+      - id: case-4
+        when: An empty-state notice occupies a region
+        owner: The notice component
+        render: Compose the notice without adding its internal inset again.
+      - id: case-5
+        when: A fenced code block is displayed
+        owner: The code-block component
+        render: Compose the block without duplicating its content inset.
+      - id: case-6
+        when: A band side meets the outer edge of a flush surface
+        owner: The selected Grammar recipe
+        render: Use the published outer-edge content clearance.
+      - id: case-7
+        when: Inline sides of bands meet the same surface boundary
+        owner: The selected Grammar recipe
+        render: Use the same published inline inset on every band.
+  - id: PADDING-5
+    title: Generous section clearance
+    governs: A deliberately more spacious section uses its selected Grammar's published generous inset.
+    cases:
+      - id: case-1
+        when: A section deliberately uses equal generous clearance
+        owner: Application layout
+        render: Choose the published generous inset for that density.
+      - id: case-2
+        when: A tab frame owns page-level inline clearance
+        owner: The navigation component
+        render: Compose its published page-inset API.
+    notThisRule: Space between child sections is a gap, not a boundary inset.
+  - id: PADDING-6
+    title: Low-density region clearance
+    governs: A large, low-density region may use the selected Grammar's larger frame inset where its content
+      density calls for it.
+    cases:
+      - id: case-1
+        when: A large page region needs equal generous clearance
+        owner: Application layout
+        render: Choose its published larger frame inset.
+      - id: case-2
+        when: An empty or waiting region occupies most of the viewport
+        owner: Application layout
+        render: Give the region its own published frame clearance while its notice retains internal ownership.
+    notThisRule: A large frame inset is not the default for ordinary content boundaries.
+  - id: PADDING-7
+    title: Responsive inset follows its boundary
+    governs: A boundary keeps its meaning across widths. Its responsive inset follows adjacent published scale
+      steps. Separator-facing sides retain their separator clearance; block sides change only when the
+      boundary owns them.
+    cases:
+      - id: case-1
+        when: A decision surface gains room at a wider viewport
+        owner: The selected Grammar recipe
+        render: Step inline clearance to the adjacent published inset.
+      - id: case-2
+        when: That surface's outer-edge block sides gain room with it
+        owner: The selected Grammar recipe
+        render: Step only the block sides owned by the outer boundary.
+      - id: case-3
+        when: A side meets an internal separator
+        owner: The selected Grammar recipe
+        render: Keep the separator-facing clearance at both widths.
+    notThisRule: A separator-facing side does not step merely because the viewport widens.
+  - id: PADDING-8
+    title: Subordinate content indents at the inline start
+    governs: An inset that expresses nested hierarchy applies at logical inline start. The end edge remains
+      aligned with its parent so the reading measure stays available. The selected Grammar supplies the
+      indentation step and disclosure recipe.
+    cases:
+      - id: case-1
+        when: A disclosure body belongs under its trigger
+        owner: The disclosure component
+        render: Use its published leading indentation and unchanged trailing edge.
+      - id: case-2
+        when: A nested group belongs to a named parent row
+        owner: The group component
+        render: Use the selected Grammar's per-level leading indentation.
+    notThisRule: Indenting both sides reads as an inset block rather than subordinate content. A missing
+      disclosure capability is repaired in the Grammar.
+  - id: PADDING-9
+    title: Routed content owns its block inset
+    governs: A routed content region may step its block inset with the viewport while the page container retains
+      inline inset ownership. Its responsive values use adjacent published steps and never duplicate the page
+      edge.
+    cases:
+      - id: case-1
+        when: Routed content sits directly beneath the page shell
+        owner: Application layout
+        render: Apply its published responsive block inset; leave inline clearance with the page container.
+    notThisRule: Inline clearance on routed content duplicates the page-container edge and is refused.
+doesNotDecide: Space between siblings is Gap (gap.yaml), and external offsets are Margin (margin.yaml). The
+  selected Grammar owns page-container geometry, its closed inset scale and component recipes under
+  FE-RULE-OWNERSHIP; its playbook supplies the concrete values used in proof.

package/runtime/modules/kernel/failure-codes.yaml

@@ -2130,17 +2130,17 @@ FE_APP_SHELL_BOTTOM_TABS:
   meaning_vi: "Khung ứng dụng tại <file> đặt điều hướng trong thanh tab dưới thay vì Sidebar drawer."
   causes_vi:
     - "Cấu trúc shell không theo canon ứng dụng."
-  nextStep_vi: "Dùng hàng mở drawer bên dưới navbar và Sidebar presentation=\"drawer\"."
+  nextStep_vi: "Dùng hàng mở drawer bên dưới navbar và Sidebar presentation=\"drawer\" (R316; FE-RULE-OWNERSHIP: knowledge/patterns/fe/index.yaml; packages/eslint/grammar-starci/README.md)."
   owner: op-retry
   kind: check-finding
 
 FE_APP_SHELL_FRAME:
-  title: "The application frame is not a fixed WorkspaceShell"
+  title: "The application frame bypasses the selected Grammar shell"
   title_vi: "Khung ứng dụng không dùng WorkspaceShell cố định"
   meaning_vi: "Khung ứng dụng tại <file> không giao bố cục và cuộn cho WorkspaceShell."
   causes_vi:
     - "Cấu trúc shell không theo canon ứng dụng."
-  nextStep_vi: "Ghép khung ứng dụng bằng WorkspaceShell viewport=\"fixed\"."
+  nextStep_vi: "Ghép khung ứng dụng bằng WorkspaceShell viewport=\"fixed\" (R313; FE-RULE-OWNERSHIP: knowledge/patterns/fe/index.yaml; packages/eslint/grammar-starci/README.md)."
   owner: op-retry
   kind: check-finding
 
@@ -2155,6 +2155,38 @@ FE_BLOCK_PRODUCT_HOOK_DEFINITION:
   owner: other-op:interface.implement
   kind: check-finding
 
+FE_BUTTON_INTENT:
+  title: "Button variant is chosen by hand instead of by intent"
+  title_vi: "Variant của nút được chọn thủ công thay vì theo intent"
+  meaning_vi: "Button hoặc IconButton của ứng dụng thiếu intent, truyền variant, đặt nút xác nhận xoá ngoài hộp thoại xác nhận, có nhiều hơn một nút commit trong một lần render, hoặc đặt nút commit trong từng phần tử của danh sách."
+  causes_vi:
+    - "Truyền variant thay vì intent cho Button hoặc IconButton"
+    - "Đặt intent destructive với step confirm ngoài AlertDialog hoặc ConfirmDialog"
+    - "Đặt hai nút commit trong cùng một lần render hoặc một nút commit trong mỗi thẻ của danh sách"
+  nextStep_vi: "Khai báo intent (và step cho destructive) theo hệ quả của hành động, bỏ variant để Grammar tự suy ra, và chạy codemod button-intent cho các nút cũ."
+  owner: "op-retry"
+  kind: "check-finding"
+
+FE_BUTTON_INTENT_REQUIRED:
+  title: "A button has no declared intent"
+  title_vi: "Nút chưa khai báo intent"
+  meaning_vi: "Button hoặc IconButton tại <file> chưa nêu ý định của lệnh."
+  causes_vi:
+    - "Bỏ intent nên Grammar không có dữ kiện để chọn variant."
+  nextStep_vi: "Khai báo intent theo hệ quả và thứ hạng của lệnh trong quyết định (CTA-6)."
+  owner: op-retry
+  kind: check-finding
+
+FE_BUTTON_NO_VARIANT:
+  title: "An app button chooses a visual variant"
+  title_vi: "Nút ứng dụng tự chọn variant"
+  meaning_vi: "Button hoặc IconButton tại <file> truyền variant thay vì để Grammar suy ra từ intent và vị trí."
+  causes_vi:
+    - "Ứng dụng truyền variant trực tiếp hoặc qua props spread."
+  nextStep_vi: "Thay variant bằng intent theo hệ quả của lệnh (CTA-6)."
+  owner: op-retry
+  kind: check-finding
+
 FE_CALLBACK_SHAPE:
   title: "An auth callback performs more than code exchange and redirect"
   title_vi: "Callback xác thực làm thêm việc ngoài đổi mã và chuyển hướng"
@@ -2205,7 +2237,7 @@ FE_COMPONENT_API:
     - "Component nhận className từ ngoài"
     - "Khối kết nối không có bản trình bày thuần"
     - "Trạng thái dữ liệu tự chế thay vì qua SlotView"
-  nextStep_vi: "Sửa chữ ký component theo luật drawing và tách phần trình bày; op vừa tạo ra bản này sẽ được chạy lại để sửa theo lời nhắn của bộ kiểm tra."
+  nextStep_vi: "Sửa chữ ký component theo luật drawing và tách phần trình bày; op vừa tạo ra bản này sẽ được chạy lại để sửa theo lời nhắn của bộ kiểm tra (R92; FE-RULE-OWNERSHIP: knowledge/patterns/fe/index.yaml; packages/eslint/grammar-starci/README.md)."
   owner: op-retry
   kind: check-finding
 
@@ -2306,6 +2338,16 @@ FE_DANGEROUS_HTML:
   owner: op-retry
   kind: check-finding
 
+FE_DESTRUCTIVE_CONFIRM_IN_DIALOG:
+  title: "A destructive confirm is outside its confirmation dialog"
+  title_vi: "Lệnh xác nhận phá hủy nằm ngoài hộp thoại xác nhận"
+  meaning_vi: "Nút destructive confirm tại <file> không nằm trong nội dung AlertDialog hoặc ConfirmDialog cùng tệp."
+  causes_vi:
+    - "Đặt lần nhấn cuối ngoài hộp thoại hoặc trên trigger."
+  nextStep_vi: "Đặt confirm trong nội dung hộp thoại cùng tệp; trigger dùng step entry (CTA-6)."
+  owner: op-retry
+  kind: check-finding
+
 FE_EFFECT_CLEANUP:
   title: "What an effect starts, its cleanup releases"
   title_vi: "Effect khởi động thứ không được dọn"
@@ -2348,6 +2390,16 @@ FE_ERROR_BOUNDARY_MISSING:
   owner: op-retry
   kind: check-finding
 
+FE_GRAMMAR_LAYOUT_ONLY:
+  title: "App surface paint violates layout-only composition"
+  title_vi: "Ứng dụng tự tô surface thay vì chỉ viết CSS bố cục"
+  meaning_vi: "Ứng dụng thêm lớp bg-surface thay vì dùng surface có nền của Grammar."
+  causes_vi:
+    - "Thêm lớp bg-surface vào phần tử do ứng dụng dựng"
+  nextStep_vi: "Giữ CSS ứng dụng chỉ lo bố cục và dùng SurfaceCard hoặc surface có nền khác của Grammar."
+  owner: "op-retry"
+  kind: "check-finding"
+
 FE_GRAPHQL_CONTRACT:
   title: "A front-end GraphQL document is one its back end serves"
   title_vi: "Tài liệu GraphQL của front end không khớp hợp đồng của back end"
@@ -2457,7 +2509,7 @@ FE_ICON_INLINE_SVG:
   causes_vi:
     - "Leaf Icon tự vẽ path hoặc SVG thay vì dùng Heroicons"
     - "Component vẽ SVG trực tiếp mà không phải leaf nhãn hiệu được khai báo"
-  nextStep_vi: "Thay glyph bằng Heroicons qua leaf Icon; nếu là nhãn hiệu, đặt nó trong leaf nhãn hiệu và khai báo đúng chủ của leaf."
+  nextStep_vi: "Thay glyph bằng Heroicons qua leaf Icon; nếu là nhãn hiệu, đặt nó trong leaf nhãn hiệu và khai báo đúng chủ của leaf (R286; FE-RULE-OWNERSHIP: knowledge/patterns/fe/index.yaml; packages/eslint/grammar-starci/README.md)."
   owner: op-retry
   kind: check-finding
 
@@ -2474,7 +2526,7 @@ FE_LIST_KEY:
 FE_LIST_PANEL_PADDING:
   title: "Panel list wrapper stacks horizontal content padding"
   title_vi: "Phần tử bọc danh sách trong panel cộng dồn padding ngang"
-  meaning_vi: "Ứng dụng thêm px-*, ps-* hoặc pe-* vào phần tử bọc ListBox của Grammar hoặc nhãn nhóm, khiến nội dung lệch khỏi mép panel."
+  meaning_vi: "Ứng dụng thêm padding ngang vào phần tử bọc ListBox của Grammar hoặc nhãn nhóm bên trong surface có nền, khiến nội dung lệch khỏi mép panel."
   causes_vi:
     - "Bọc ListBox bằng phần tử có padding ngang"
     - "Thêm padding ngang quanh nhãn nhóm của danh sách"
@@ -2488,7 +2540,7 @@ FE_NATIVE_FORM_CONTROL:
   meaning_vi: "`<tag>` thô ở `<file>`. Dùng renderer của grammar."
   causes_vi:
     - "Vi phạm luật R62: Không `<select>/<input>/<textarea>/<button>`, `<img>` thô và không thẻ cấu trúc thô (`<section>`, `<p>`, `<ul>`, `<h1>`...) ở tầng sản phẩm; dùng renderer grammar."
-  nextStep_vi: "Op vừa tạo ra bản này sẽ được chạy lại để sửa theo lời nhắn của bộ kiểm tra và mục của luật trong tiêu chuẩn HFS; nợ cũ cần quyết định thiết kế nên op không thêm ngoại lệ, chỉ tách hoặc chuyển về đúng chủ."
+  nextStep_vi: "Op vừa tạo ra bản này sẽ được chạy lại để sửa theo lời nhắn của bộ kiểm tra và mục của luật trong tiêu chuẩn HFS; nợ cũ cần quyết định thiết kế nên op không thêm ngoại lệ, chỉ tách hoặc chuyển về đúng chủ (R62; FE-RULE-OWNERSHIP: knowledge/patterns/fe/index.yaml; packages/eslint/grammar-starci/README.md)."
   owner: op-retry
   kind: check-finding
 
@@ -2508,17 +2560,17 @@ FE_NAVBAR_CLUSTER:
   meaning_vi: "Cụm navbar tại <file> không giữ thứ tự ngôn ngữ, giao diện, thông báo và tài khoản."
   causes_vi:
     - "Cấu trúc shell không theo canon ứng dụng."
-  nextStep_vi: "Ghép IconButton ngôn ngữ, Switch giao diện, IconButton chuông và AvatarButton theo đúng thứ tự."
+  nextStep_vi: "Ghép IconButton ngôn ngữ, Switch giao diện, IconButton chuông và AvatarButton theo đúng thứ tự (R315; FE-RULE-OWNERSHIP: knowledge/patterns/fe/index.yaml; packages/eslint/grammar-starci/README.md)."
   owner: op-retry
   kind: check-finding
 
 FE_NAVBAR_CONTROL_SIZE:
-  title: "A navbar control does not use the control size"
+  title: "A navbar control bypasses the selected Grammar control scale"
   title_vi: "Điều khiển navbar không dùng cỡ control"
   meaning_vi: "Điều khiển trong navbar tại <file> không khai báo cùng cỡ control của Grammar."
   causes_vi:
     - "Cấu trúc shell không theo canon ứng dụng."
-  nextStep_vi: "Đặt size=\"control\" trên từng điều khiển trong thanh."
+  nextStep_vi: "Đặt size=\"control\" trên từng điều khiển trong thanh (R314; FE-RULE-OWNERSHIP: knowledge/patterns/fe/index.yaml; packages/eslint/grammar-starci/README.md)."
   owner: op-retry
   kind: check-finding
 
@@ -2528,18 +2580,18 @@ FE_NAVBAR_CREATE:
   meaning_vi: "Navbar tại <file> chứa thao tác tạo mới thuộc nội dung trang."
   causes_vi:
     - "Cấu trúc shell không theo canon ứng dụng."
-  nextStep_vi: "Đưa thao tác tạo mới về trang sở hữu nó."
+  nextStep_vi: "Đưa thao tác tạo mới về trang sở hữu nó (R317; FE-RULE-OWNERSHIP: knowledge/patterns/fe/index.yaml; packages/eslint/grammar-starci/README.md)."
   owner: op-retry
   kind: check-finding
 
 FE_NESTED_VARIANT:
-  title: "Nested control or surface paint bypasses Grammar ownership"
-  title_vi: "Trường lồng hoặc nền surface vượt quyền sở hữu của Grammar"
-  meaning_vi: "Trường bên trong surface Grammar ép variant primary, hoặc ứng dụng tự tô nền bằng bg-surface thay vì dùng composition của Grammar."
+  title: "App variants bypass Grammar surface context"
+  title_vi: "Variant ứng dụng vượt qua context surface của Grammar"
+  meaning_vi: "Ứng dụng đặt variant tĩnh cho trường Grammar trên bất kỳ lớp nào, hoặc ép Tabs dùng primary trong surface có nền."
   causes_vi:
-    - "Truyền variant primary cho trường bên trong một surface"
-    - "Thêm lớp bg-surface vào phần tử do ứng dụng dựng"
-  nextStep_vi: "Dùng surface của Grammar và bỏ variant của trường lồng bên trong để Grammar tự cấp secondary."
+    - "Truyền variant tĩnh cho trường Grammar"
+    - "Ép Tabs dùng primary bên trong surface có nền"
+  nextStep_vi: "Bỏ variant để Grammar tự cấp mặc định theo context surface."
   owner: "op-retry"
   kind: "check-finding"
 
@@ -2566,6 +2618,16 @@ FE_NO_ALERT:
   owner: op-retry
   kind: check-finding
 
+FE_NO_COMMIT_IN_COLLECTION_ITEM:
+  title: "A collection item repeats a commit"
+  title_vi: "Phần tử danh sách lặp lại lệnh commit"
+  meaning_vi: "Một phần tử collection hoặc callback map tại <file> hiển thị nút commit."
+  causes_vi:
+    - "Mỗi hàng giành vai trò hành động chính của toàn màn hình."
+  nextStep_vi: "Dùng alternative cho hành động tiếp theo của hàng và giữ commit ở quyết định của màn hình (CTA-6)."
+  owner: op-retry
+  kind: check-finding
+
 FE_NO_TESTS:
   title: "Front end holds a test file, test tooling or a test dependency"
   title_vi: "Front end có tệp test, công cụ test hoặc thư viện test"
@@ -2801,6 +2863,16 @@ FE_SERVICE_ROLE_FORBIDDEN:
   owner: op-retry
   kind: check-finding
 
+FE_SINGLE_COMMIT_PER_RENDER:
+  title: "A component renders more than one commit"
+  title_vi: "Component hiển thị nhiều hơn một lệnh commit"
+  meaning_vi: "Một đường render của component tại <file> có nhiều nút commit cùng lúc."
+  causes_vi:
+    - "Nhiều lệnh cùng nhận thứ hạng hành động tiếp theo."
+  nextStep_vi: "Giữ một lệnh tiếp theo là commit và phân loại các lệnh còn lại theo hệ quả (CTA-6)."
+  owner: op-retry
+  kind: check-finding
+
 FE_SIZE_AND_STATE_BUDGET:
   title: "Hook and state budgets; no hand-written poll loop"
   title_vi: "Vượt ngân sách hook và state"
@@ -2855,6 +2927,16 @@ FE_STACK_CORE_MISSING:
   owner: op-retry
   kind: check-finding
 
+FE_STACK_FAMILY_LINT_MISSING:
+  title: "The front end installs canon-fe 9 without the selected Grammar family's lint package"
+  title_vi: "Front end dùng canon-fe 9 nhưng thiếu gói lint của họ Grammar đã chọn"
+  meaning_vi: "hfs.json chọn sides.fe.grammar (starci hoặc offset-pop) và front end khai báo @starci/eslint-canon-fe 9 trở lên, nhưng không manifest nào khai báo gói lint của họ đó; từ canon-fe 9 các luật component Grammar nằm trong gói này, thiếu gói thì các luật ấy không chạy."
+  causes_vi:
+    - "Nâng @starci/eslint-canon-fe lên 9 mà chưa thêm @starci/eslint-grammar-starci (Grammar StarCi) hoặc @starci/eslint-grammar-offset-pop (Grammar Offset Pop)."
+  nextStep_vi: "Thêm @starci/eslint-grammar-starci (hoặc @starci/eslint-grammar-offset-pop) cạnh @starci/eslint-canon-fe, ghép starciGrammarConfig({ hfs }) (hoặc offsetPopGrammarConfig({ hfs })) sau starciFeConfig({ hfs }) trong fe/eslint.config.mjs, hoặc chạy starci app sync."
+  owner: op-retry
+  kind: check-finding
+
 FE_STACK_FORBIDDEN:
   title: "A front end declares or imports a package or scoped package family forbidden by the stack"
   title_vi: "Front end dùng thư viện hoặc họ package bị fe-stack cấm"
@@ -2908,7 +2990,7 @@ FE_STYLE_TOKEN_ONLY:
     - "@media dùng breakpoint ngoài thang của grammar"
     - "brand.css thiếu cặp mềm của một tông trạng thái ở sáng hoặc tối, chữ mềm dưới 3:1 trên nền nhạt hoặc nền trang, --foreground dưới 4.5:1, hoặc giá trị màu không phân giải được"
     - "Component tô chữ hoặc icon bằng text-success, text-danger, fill-warning, stroke-info (tông đặc) thay vì text-<tông>-soft-foreground"
-  nextStep_vi: "Op interface.implement bỏ CSS riêng, dùng component và token của grammar; giá trị màu thương hiệu chỉ khai ở modules/brand/brand.css cho cả sáng và tối, đủ cặp mềm cho mọi tông trạng thái; chữ và icon trạng thái dùng text-<tông>-soft-foreground."
+  nextStep_vi: "Op interface.implement bỏ CSS riêng, dùng component và token của grammar; giá trị màu thương hiệu chỉ khai ở modules/brand/brand.css cho cả sáng và tối, đủ cặp mềm cho mọi tông trạng thái; chữ và icon trạng thái dùng text-<tông>-soft-foreground (R61; FE-RULE-OWNERSHIP: knowledge/patterns/fe/index.yaml; packages/eslint/grammar-starci/README.md)."
   owner: other-op:interface.implement
   kind: check-finding
 
@@ -3027,7 +3109,7 @@ FE_VENDOR_BOUNDARY:
     - "Dùng bộ glyph thứ hai ngoài họ heroicons (Phosphor, Lucide, Iconify...)"
     - "Dùng kích thước biểu tượng ngoài thang"
     - "Primitive thư viện ngoài dùng trực tiếp ở nhiều nơi"
-  nextStep_vi: "Dùng lá icon và chủ sở hữu primitive có sẵn; op vừa tạo ra bản này sẽ được chạy lại để sửa theo lời nhắn của bộ kiểm tra."
+  nextStep_vi: "Dùng lá icon và chủ sở hữu primitive có sẵn; op vừa tạo ra bản này sẽ được chạy lại để sửa theo lời nhắn của bộ kiểm tra (R93; FE-RULE-OWNERSHIP: knowledge/patterns/fe/index.yaml; packages/eslint/grammar-starci/README.md)."
   owner: op-retry
   kind: check-finding
 
@@ -4903,7 +4985,7 @@ RT_GENERATED_BLOCK_STALE:
 RT_GENERATED_DRIFT:
   title: "Generated copy drifted"
   title_vi: "Bản sao sinh tự động bị lệch"
-  meaning_vi: "Một bản sao sinh tự động trong packages/hfs/runtime, packages/eslint/be/runtime hoặc packages/eslint/fe/runtime khác với nội dung mà scripts/hfs/sync-runtime.mjs ghi ra từ nguồn duy nhất: thiếu, cũ, hoặc thừa tệp."
+  meaning_vi: "Một bản sao sinh tự động trong packages/hfs/runtime, packages/eslint/be/runtime hoặc packages/eslint/fe/runtime, packages/eslint/grammar-starci/runtime, packages/eslint/grammar-offset-pop/runtime khác với nội dung mà scripts/hfs/sync-runtime.mjs ghi ra từ nguồn duy nhất: thiếu, cũ, hoặc thừa tệp."
   causes_vi:
     - "Sửa một tệp nguồn được đóng gói mà quên chạy sync-runtime"
     - "Sửa tay một tệp trong thư mục runtime/ của gói"

package/runtime/modules/kernel/removed-vocabulary.yaml

@@ -8,6 +8,22 @@
 # a word to scan for).
 kinds: [config-key, bias-field, verb, flag, code, vocabulary, file]
 removed:
+  - id: fe-landmark-branch-inventory
+    kind: vocabulary
+    name: LANDMARK_BRANCHES
+    use: 'the selected Grammar lint package owns its component vocabulary; the universal FE canon exposes no component inventory'
+    since: 1.0.0-alpha.31
+  - id: fe-grammar-rule-namespace
+    kind: vocabulary
+    name: starci-fe Grammar component rules
+    match: 'starci-fe/(?:app-shell-frame|no-shell-bottom-tabs|navbar-control-size|navbar-cluster|no-navbar-create|no-raw-structural-element|no-heading-tag-outside-heading-component|status-text-uses-soft-foreground|vendor-primitive-has-named-owner|no-vendor-icon-outside-icon-leaf|heroicons-is-the-glyph-vendor|no-off-scale-glyph-size|no-icon-size-class|destructive-menu-entry-needs-danger-tone|no-decorative-icon-in-metric-cell|no-inline-svg-outside-brand-mark-leaf|no-fractional-step|no-hand-rolled-heading|no-unresolved-token-class|slot-status-through-slotview)\b'
+    use: 'the same rule id under starci-grammar/ from the selected Grammar lint package; FE-RULE-OWNERSHIP governs placement'
+    since: 1.0.0-alpha.31
+  - id: offset-pop-toaster-content-guidance
+    kind: vocabulary
+    name: toaster-clear-of-the-dock
+    use: 'toaster-clear-of-content in the Offset Pop playbook'
+    since: 1.0.0-alpha.31
   - id: cut-seam-command
     kind: flag
     name: cut-seam --command
@@ -401,3 +417,16 @@ removed:
     use: 'the release tag is always <release.tagPrefix><package.json version>; delete the key'
     since: 1.0.0-alpha.31
     match: '\btagMatchesVersion\b'
+
+  - id: grammar-surfacecard-manual-layer
+    kind: vocabulary
+    name: SurfaceCard manual depth and unpainted frame
+    use: 'SurfaceCard derives its depth from the painted parent surface; use an unpainted layout container for grouping and a bounded SurfaceCard for a painted face'
+    since: 1.0.0-alpha.31
+    match: 'SurfaceCard[^\r\n>]*\s(?:depth=|frame="frameless")'
+  - id: grammar-dropdown-negative-tone
+    kind: vocabulary
+    name: DropdownMenuItem negative tone
+    use: 'DropdownMenuItem.tone uses neutral or danger; destructive commands use danger'
+    since: 1.0.0-alpha.31
+    match: 'DropdownMenuItem(?:Tone|\.tone)[^\r\n]*["'']negative["'']'

package/runtime/modules/kernel/roles.yaml

@@ -84,7 +84,7 @@ rulings:
   critic-coverage: "Who judges each op's product is declared once, in the required judge field of its contract (modules/kernel/op-judges.yaml): machine, critic, owner or next-leg, never nobody. An independent Critic of another provider, on the frontier tier, runs for drawing (inside the op) and, run by the runtime at settle, for scope.define, business.decide and architecture.decide (modules/kernel/critic.yaml coverage); the op-judge check holds that table and the contracts to each other."
   debug-is-time-boxed: "Debug is a time-boxed auditor of role conformance for the stabilisation phase, bound to a chat session; the runtime is self-sufficient, every edge case Debug meets becomes a rule plus an edge-case entry, and the loop is set up no more once the end condition of the debug role holds."
   updating-the-runtime: "The runtime tree can be updated while workflows run, and no running workflow conflicts with the update. What a change asks of each role is declared once in modules/kernel/revision-scope.yaml and checked against the tree. A change that concerns no role costs no seat anything. A live seat is updated in place by default: woken once per revision change, even with an empty menu, with exactly the changed files that concern it, it reads and attests them (one wake, never a second for the same revision; several commits deployed together are one change). A seat is replaced by a fresh one that boots from the stores only when a rule of its contract was removed or reversed (a line deleted or modified in its declared contract files; a commit may declare an edit wording-only, and the declaration holds only for a file that keeps its structure), when the files its launch prompt is built from changed, or when it is already due for rotation (the revision change folds into that replacement). A replacement happens at the seat's next yield, never in the middle of a decision. An Op is neither updated nor restarted inside an attempt: it keeps the rules of its admission, the next try and the next Critic run are admitted under the new rules, and only guards bite at once. The engine restarts only for the files its process loaded, derived from its import graph; every other command is a new process that reads the tree."
-  debug-fix-lanes: "A runtime defect Debug catches is fixed at once, never queued behind another: Debug splits it by independent cause and opens one fix lane per cause in the same turn, each in its own clone with the files it may touch named, so the lanes run in parallel; each lane's fix reaches the host as soon as `starci runtime verify` prints `verified <sha>` for it (the check, the package clean-test and the scaffold e2e on one commit; the line of `npm run check` alone runs no test and is never the report), through `starci runtime deploy --from <clone>` (one verified revision change; never a hand fast-forward of the live checkout followed by a hand restart). Nothing a lane found is left listed as later: it is fixed in that round or handed to another lane opened then. The fixes of a day are consolidated into one release cut at the end of that day."
+  debug-fix-lanes: "A runtime defect Debug catches is fixed at once, never queued behind another: Debug splits it by independent cause and opens one fix lane per cause in the same turn, each in its own clone with the files it may touch named, so the lanes run in parallel; each lane's fix reaches the host as soon as `starci runtime verify` prints `verified <sha>` for it (the check, the package clean-test and the scaffold e2e on one commit; the line of `npm run check` alone runs no test and is never the report), through `starci runtime deploy --from <clone>` (one verified revision change; never a hand fast-forward of the live checkout followed by a hand restart). Nothing a lane found is left listed as later: it is fixed in that round or handed to another lane opened then. A verified fix ships as its own release wave, the next alpha.N.M, as soon as it is green (owner ruling release-waves)."
   debug-replay-before-done: "A fix for a defect found on a live host is done when the runtime change that handles it (the contract, prompt, policy row, gate, guard or code) and its edge-case entry (found: live, the rule that now handles it) land on one commit and starci runtime verify is green on that commit. The runtime has no specs of its own (owner ruling no-runtime-specs): no runtime spec or replay spec is written; an entry may name a package spec or the scaffold e2e that already covers it."
   debug-channels: "Debug speaks only through runtime channels (starci supervisor tell; a durable ruling to a Kernel through the Supervisor's notify), never by typing into a seat's terminal, and never to an Op or a Critic."