Skip to content

Latest commit

 

History

History
555 lines (475 loc) · 37.9 KB

native-presentation.md

File metadata and controls

555 lines (475 loc) · 37.9 KB

Git native presentation and navigation contract

Baseline inspected 2026-10-31: engine 07cf4a1, presentation c64a139, BusyMark ea47942 (feature/git-package), BusyFiles a1a6721 (Release/v0.0.1). All four trees were clean. The parent engineering policy applies; there are no repository-specific AGENTS.md files at this baseline. No engine change is planned.

One Linux implementation (2026-11-06)

The 2026-11-06 decision supersedes all earlier allowances for separate host Git layouts or native control geometry. The original 2026-10-31 baseline above is historical. The current baseline and action inventory are in one-git-ui.md. Both adapters extend the same YaruGitPresentation without visual overrides.

Git control category Shared owner used by both hosts
Application sidebar header/navigation Host workspace header and ordinary sidebar destination selector; typed GitSidebarView selects GitFeatureSidebar content
Buttons, input, checkbox, icon actions NativeGitActionButton, NativeGitTextEntry, NativeGitCheckbox, NativeGitIconAction
File/folder/status and reference rows NativeGitTreeRow, NativeGitRowSurface
Menus and glyph roles GitMenuRole and gitLinuxIcons; host only presents the native menu
Modal/history/date layout GitNativeDialog, shared history layout and native date fields
Comparison identity/tabs/navigation GitReview, GitReviewTabs, GitFeatureController, GitReviewContent, GitReviewSurface
Spacing, typography, colors, density and focus GitSpacing, GitSizes, GitTypography, GitPalette, NativeGitSurface in linux_native.dart

The shared modal frame clips its full-height reference sidebar to the official Yaru window radius through the public container clipBehavior API.

All rendering uses BusyStack-owned primitives and supported official pinned Yaru APIs. No upstream source is modified. Host document/browser lifetime, authorization, localization and system services remain application responsibilities. There is no alternate Commit/Log split workspace or mutable single preview. The canonical sidebar owns its end border inside its measured width. Host slot composition adds no extra separator width before shared comparison content; this keeps comparison toolbar coordinates identical across document/browser mounts. GitPalette.resolve owns the approved BusyMark neutral GTK/Yaru roles in both light and dark themes. It retains the active system accent and official Yaru high-contrast palette. Unrelated host editor/browser theme overrides cannot change Git text, surfaces or dialog control metrics. Actual same-fixture captures exposed a secondary-text mismatch inherited from the two app color schemes; regression tests perturb host colors/typography and measure resolved Git colors, painted controls and dialog text. Literal palette data is permitted only in the resolved shared ColorScheme factory; adversarial audits still reject controls hidden in that factory. Final installed-app visual acceptance remains required.

Tooltip overlays ignore pointer events and expose their description through the trigger's semantics. Empty messages create no overlay; unlinked targets do not paint a follower. The covered-row activation regression runs in both real host renderers, including an overlap assertion so the test cannot pass vacuously.

Action destinations to preserve

Capability Destination after integration
Working changes, staging, amend, message/templates/recent messages, commit/push Shared Commit sidebar in both main sidebar slots
Selected commit, parent, metadata, changed files Shared independent Git Log inspector, metadata before files
History graph, refs, filters, pagination, Go to, HEAD Shared full Git Log selection modal in both hosts
Branch/tag/commit context operations and ordered cherry-pick/revert History context menus and existing workflow dialogs
Ordinary staged/unstaged/historical file activation Independent shared comparison tabs in both content slots; BusyMark retains its document strip
File/hunk/line staging, search, navigation, wrapping and correspondence Existing shared comparison renderer and transaction paths
Index editing and three-way conflict resolution Existing guarded shared editors and native workflow surfaces
File history, blame, snapshots, revision comparison Existing history actions/workflow surfaces
Branches, clone/init, remotes/tags, network reviews Existing workflow menu and dialogs
Merge/rebase/cherry-pick, continuing operations, cancellation Existing workflow menu, operation banner and dialogs
Stash/worktrees/submodules/reset/revert/restore/recovery Existing workflow/context menus and dialogs
Trust, credentials, signing, hooks, failures Required host controls, native dialogs and notices

Selection and opening comparisons do not mutate repositories, save buffers or change drafts. Historical selection and comparison endpoints are immutable. Current-content actions retain the engine's reviewed snapshot preconditions. Evidence is recorded under the existing build/git-verification directories. This checklist describes required destinations, not completed acceptance.

Required provisioning and permanent checks

GitHost.presentation, its complete semantic glyph map and presentMenu are required. GitPresentation has no default. Missing scopes and glyphs fail clearly; a failed native menu service reports an operational error and never opens Flutter menu chrome. Native text selection menus use the host service while preserving the original controller, selection, composition and undo. BusyMark Git header/context menus use the native-required constructor of its existing header menu control. Generic menus with a Flutter fallback are rejected in Git source by resolved constructor/helper identity.

The resolved analyzer gate visits constructor calls and tear-offs, types and helper references, including prefixes and typedef aliases. It rejects all Material widget constructors (including controls not in the explicit helper/palette list), dialog/menu helpers, Material palette/icons and feature-created local palettes/themes. Every Git source is checked; there are no feature-file exceptions. A second resolved pass begins at each concrete host adapter root and follows first-party declarations across that host package transitively, so an approved-looking wrapper cannot conceal TextButton, IconButton, Material, InkWell, Dialog, or another prohibited control. Both complete host adapters and their reachable shared native surfaces are audited. The gate's own fixtures include forbidden aliased constructors, helpers, fallback paths, a wrapper-hidden control, and a legitimate primitive/Yaru implementation. Unresolved code and empty/missing input sets fail closed.

Both consumers run this gate over the shared sources they materialize and their Git integration sources. The source archives include the gate, its tests and the native contract fixture. Real host tests exercise all 26 workflow surfaces and both prompt kinds through each application's actual adapter in light/dark modes; fixture requests cannot authorize mutation. Existing tests retain the transaction, editor, graph, history and dismissal assertions. Runtime captures and native interaction acceptance remain separate from static compliance.

Font-family assignments in Git sources must reference the existing host catalog (GitTypography.monoFontFamily / monoFontFamilyFallback in the shared native implementation); shared views use GitPresentation.codeStyle. The analyzer resolves those exact symbols. A newly named feature constant is not an exception.

BusyMark Commit correction (2026-11-01)

The non-Git Writerside usage header in workspace_screen.dart uses BusyMarkHeaderIconButton; its semantic style explicitly uses the native rounded rectangle, including hover/pressed/disabled states. Git icon actions must use that flat treatment, including stage/unstage and Branches menus. BusyMarkCompactIconButton and its pill focus outline are not approved for Git. The non-Git Files tree uses BusyMarkSidebarTreeRow: Git change rows reuse that row, disclosure, indentation and native surface through the required host presentation contract. Branch records use the same row surface and spacing. Do not expand an allowlist or accept a golden to excuse circular Git actions.

BusyMark's Commit layout is the compact sidebar allocation: branch/path tooltip, Actions (including Refresh), then compact local tracking, then the tree. Commit and Commit and Push share a measured, spaced row. BusyFiles uses that same shared layout and retains descendant discovery. BusyMark alone requires the canonical opened workspace to equal the discovered working-tree root, at attachment and authoring-command boundaries. Untrusted Commit shows only the native trust screen; drafts remain owned by the session. All action destinations in the checklist above are retained by this correction.

The 2026-11-01 tracking correction requires one read-only engine contract bit: GitSnapshot.trackingCountsKnown distinguishes an omitted porcelain branch.ab (unavailable upstream object) from a measured +0 -0. Both previously became zero in the typed snapshot. Parser, background status and JSON handoff preserve this bit; old packets remain honestly unknown. Discovery, mutation/preconditions, Git invocations and transaction semantics are unchanged. BusyMark renders unknown counts as question marks with localized accessible descriptions.

Commit refinement (2026-11-01, graphical review)

The branch-management control uses BusyMark's neutral native inline action through BusyMarkGitActionButton. It remains an ordinary button opening the complete Branches modal, without copying the selector's interaction. Inline requests must not map to filled standard buttons. Resting fills, interaction states, localized truncation and actual modal/menu destinations are tested.

BusyMark's Commit repository menu contains Refresh and excludes its duplicate Branches entry. BusyMark invokes Git actions through controls and menus, with no Git action shortcuts. Both hosts consume these shared menu destinations. Workspace identity owns the full-path tooltip. The earlier branch-path-tooltip and standalone-Refresh mapping above is superseded by this refinement.

Git change rows use the shared Files-tree metrics with separate disclosure, file/folder icon, status and text slots. Entry actions are contextual in both hosts; no permanent stage/unstage or row Actions control is constructed.

BusyMarkCheckbox's labelled form uses official YaruCheckButton/YaruCheckbox, with its native geometry, state painting, label activation, focus and merged semantics. Existing unlabelled non-Git checkboxes remain unchanged. Amend uses this labelled form; its draft/transaction logic is untouched. Both hosts now use NativeGitCheckbox and the same amend layout.

The exclusive trust sidebar is concise. The native confirmation identifies the repository and distinguishes limited passive metadata from authorization of potentially executable hooks, filters, credential helpers and signing tools. Neither UI copy nor choosing trust authorizes a queued operation.

Interaction references consulted for this correction: GNOME buttons, menus, dialogs, checkboxes, and Git rev-parse. The pinned local Yaru checkbox/check-button APIs were inspected without changes. BusyMark's host components and the explicit product requirements remain the presentation authority; no upstream dependency or runtime pin changes apply.

Historical remediation evidence (2026-11-02)

The old host class names and mappings below record the earlier implementation. The shared ownership table above replaces their rendering owners; the behavioral requirements and recorded historical checks remain relevant.

The rendering chain is part of the contract, not a wrapper allowlist:

Git request BusyMark rendering path Observable rule
Commit details GitCommitDetails → GitHost.present (compact) → showBusyMarkModalDialog → BusyMarkGitDialogShell/YaruBorderContainer dialogWide maximum width, natural short-record height; only host-owned scrolling for long records
Selectable fields GitSelectableText → BusyMarkGitPresentation.selectable → SelectableRegion + Text with GitTextContextMenu exact original message, keyboard/context copy, no permanent Copy Text control
Context actions GitIconButton → BusyMarkGitPresentation.iconAction → BusyMarkHeaderIconButton → public YaruIconButton and external YaruFocusBorder flat resting state, native hover/press/focus/disabled states and separate row targets
Inline text actions GitButton.inline → BusyMarkGitActionButton → Flutter interaction primitives plus Yaru semantic tokens/focus native typography/geometry and neutral resting fill, with no first-party Material button construction
Commit controls standard/suggested GitButton → BusyMarkGitActionButton approved primary/secondary native treatment with no first-party FilledButton/ElevatedButton construction
Change rows GitChangeRow → BusyMarkSidebarTreeRow → BusyMarkSidebarRowSurface primitive pointer/focus/semantics surface plus Yaru focus border; no first-party Material/InkWell construction
Git branch glyph BusyMarkGlyphs.branch → official YaruIcons.share three-node graph native Yaru font/package; existing GTK branch-menu artwork remains first-party
Historical row actions GitHistoricalChangeTree → GitMenuButton(moreHorizontal) → host flat icon action/native menu horizontal contextual glyph, not the generic three-line primary-menu glyph

Commit Actions owns one Copy Commit Hash action (complete immutable ID) and View Commit Details. The inspector shows an abbreviated identity without dedicated Copy/Details icons. Details have labelled message, author, committer, commit, parent and reference fields. Full localized dates are normal text; exact timestamps remain in accessible tooltips. Parent identity is never fabricated at shallow boundaries. The complete message is selectable verbatim. The former whole-message Copy Text operation remains contextually available once as Copy Commit Message; it is distinct from copying selected text through the native text menu. Neither metadata copy operation mutates the repository.

The resolved audit follows constant IconData through imported host catalogs and aliases and rejects MaterialIcons. The host-chain pass resolves the entire BusyMark adapter rather than selected wrappers or methods. It rejects expanded/dynamic presentation of typed commit metadata, with forbidden and legitimate self-test examples. Actual host tests measure the painted BusyMarkGitDialogShell/Yaru surface rather than the full-window route wrapper, natural height, long-content reachability, native copying, all historical actions, glyphs and disjoint target geometry. Both hosts use the shared compact dialog/navigation; large history browsers and three-way editors retain expanded surfaces.

History selector and property mappings (2026-11-03)

The selector owns candidate browsing and explicit confirmation only. Its toolbar keeps message/author/path entries visible at every width. A measured wide row wraps into field and command rows at narrow widths or larger text sizes; the native overflow retains filter editors and secondary commands. Refresh and branch navigation form the adjacent command group. The menu retains Reset Filters, Go to Commit/Reference, HEAD, ordered cherry-pick and two-revision comparison. Commit-row context menus retain the historical Git operations and compact View Commit Details. There is no selector button opening the old 500px _detailPane() surface. Confirm/cancel and immutable comparisons are unchanged.

Shared request Common native mapping in both hosts
Dense fields NativeGitTextEntry, titlebar-item minimum, scaled natural content height
Label/hint Dense placeholder with persistent semantic label; standard label above editor and separate hint
Prefix/suffix and contentPadding Logical start/end siblings; one native input boundary with requested directional insets
Multiline/vertical alignment Label above multiline content; supplied editor requests use top alignment
Disabled/read-only Disabled excludes pointer/focus and dims text; read-only preserves selection/focus/copy
Editing properties Original controller, focus, selection, composing range, undo/scroll controllers, line limits, direction and callbacks
Dense/action rows NativeGitRowSurface with shared GitSizes/GitSpacing, natural scaled height and semantic selected/enabled state
Row states Shared normal, selected, hover, pressed, focus and disabled treatments with official Yaru focus border
Entry actions Secondary click and Menu/Shift+F10; no permanent trailing action control; delayed replies bind the captured row
Non-entry trailing controls Separate sibling outside the row selection target
Choice expansion Full allocated width when requested; native checked menus for choices
Choice boundary Native surface owns boundary/focus without additional underline
Choice bars Shared native rendering for remaining transaction/editor choices; no Commit/Log workspace switcher
Progress Official unmodified Yaru progress controls
Tooltip, scrollbar, activation, notices Shared NativeGitTooltip, native scrollbars, focus/pointer primitives and semantic notice surfaces
Localized sizing/RTL Shared TextPainter uses active scale and direction, natural content height and directional insets
Menu positioning Pointer anchor or control bottom at logical start, passed to the host native service

Branch/reference entries use shared mouse and keyboard context menus without permanent action buttons in either host. Historical file, snapshot, remote, worktree and submodule rows use the same contextual contract. Diff semantic foregrounds come from the active official Yaru palette. Shared backgrounds are translucent treatments: word changes 20%, staged/unstaged 16%, conflict 24%; ordinary line backgrounds multiply the word treatment by 0.4 rather than replacing its opacity. The editor renderer consumes the supplied staged/unstaged/conflict treatment without making it opaque. Search uses the host accent background, active matches retain bold/underline, native selection retains its own treatment, and +/- line markers and labelled staging/conflict contexts retain non-color meaning.

Both hosts forward Git workflow feedback to showGitNotification. The shared window-local overlay owns the native surface, common geometry, message queue, dismissal, accessibility live region and lifetime cleanup. Host callbacks only apply their existing window/workspace lifetime guards and localization; neither host supplies notification widgets. This does not change the daemon's separate freedesktop background-operation notification contract or non-Git application feedback. The resolved native audit follows GitHost.notify through first-party helpers and State rendering lifecycles, rejects host-owned notification widget trees, and permits the shared renderer's supported official native controls.

The consumer contract tests execute actual adapters and inspect field/row sizes, requested icons, editing state, directional padding, disabled/read-only behavior, line and word rendering, and light/dark background contrast. Additional shared regressions cover selector routing, initial selection, confirmation/cancellation, branch glyphs and retained history actions. These assertions do not replace real native captures or the existing resolved-construction enforcement. Acceptance must report separately whether the test runner and native display were available.

Seven-sidebar consistency contract (2026-11-03)

This revision supersedes the earlier BusyMark sibling action-column and inline branch-button requirements. GitPresentation.entryActionPlacement is required: Both hosts declare contextMenu through YaruGitPresentation. Shared Commit and historical-file entries never construct permanent trailing controls. Branch and reference entries use contextual commands in both hosts. All existing entry action destinations remain in their context menus. View-level commands, disclosure controls, status markers and metadata remain visible in both hosts.

BusyMark change rows reuse Files' horizontal sidebar insets, depth base/step, disclosure slot/gap, row surface and scaled status extent. Historical tree roots start at depth zero. Tree and information-rich record entries share BusyMarkSidebarRowSurface for hover, pressed, selected, focus and disabled behavior; neither constructs first-party Material, InkWell, YaruListTile or an entry menu button. Standard TOC hierarchy uses the Files geometry. Record content uses natural single/secondary-line height, preserving clipboard previews and date-grouped history event information.

GitActionRow.onSecondaryTapUp reaches the actual host row. BusyMark requests row focus without invoking primary activation. Reference-row Menu/Shift+F10 uses the same native operation list and a direction-aware row anchor. The shared release-safe GitContextMenuKeys is also exported for existing BusyMark sidebar rows. Clipboard History retains collection-owned focus and forwards the keyboard context command to the selected record's native action; navigation and paste keys retain their original destinations. Menu dismissal restores live focus. No Flutter popup route is used when the native menu service is unavailable.

Commit's branch identity opens the complete original Branches modal. Git Log's selected subject is a neutral information row without activation, hover-button treatment or a semantic tap action. Its separate view-level Actions menu owns Select another commit… and all applicable commit commands. The menu opens the authoritative history selector, initialized from the inspector selection. Parent navigation remains secondary metadata with parent-specific comparisons, including merge parents. The commit hash is bounded so long references cannot displace the subject. Opening context menus causes no comparison activation or repository mutation. Commit menu mutation also revalidates session, snapshot and index identity after native dismissal; files that appeared after review are never added to a group.

The existing constructor gate is paired with BusyMark's resolved sidebar gate and actual host tests for geometry, states, keyboard release, native menu packets and side effects. Native packet probes replace only the transport in tests, and never render fake GTK menus. These assertions do not substitute for running the actual application and judging all seven populated sidebars. Restricted-session build/source results must remain separate from native and release acceptance.

Compact native Git navigation (2026-11-04)

GitButton.compact requests desktop toolbar/dialog insets without changing the Commit footer's default geometry. Standard New branch… and Date actions use native neutral push surfaces; Select this commit uses the suggested role; metadata parent navigation uses neutral inline treatment. Both hosts implement and measure the request. BusyMark uses the installed Yaru 10.2.0 public theme borders, titlebar-item minimum (34 logical pixels) and button radius. Dense fields have one themed border, one line of text and no permanent label row.

BusyMark text entry keeps EditableText's controller, focus, composition, undo, selection and editing callbacks. The public TextSelectionGestureDetectorBuilder and desktop selection controls provide pointer selection and native editing. The decorative placeholder and visible external label exclude semantics; the editor exposes one persistent accessible name. The shared exact-name contract runs through both actual host renderers for empty and populated fields. Informational sidebar surfaces register no no-op tap callback.

Branches uses explicit host spacing between flexible search and natural-size commands, wrapping the commands below search when measured labels need it. Repository basename and full-path tooltip preserve identity under the concise Branches title. Row metadata truncates on one line with complete tooltips. Content determines height up to 68% of the host's available screen; long lists scroll in that bound. A keyed controller preserves selection/composition across responsive rearrangement. Down moves from search into the reference focus scope; Up/Down traverse results and Menu/Shift+F10 opens the same native commands as secondary click. Selection itself never switches or merges a branch.

The inspector header is outside the entry-action placement policy: its information row has no trailing action; the adjacent menu is a view command. There is no duplicate commit selector or metadata Actions button. Commit hash, parents and explicit merge-parent comparisons remain in metadata/Changed Files. The full graph, filters, immutable comparison identity, cancellation/generation checks and reviewed mutation operations retain their existing implementations.

BusyMark's measured visual contract runs against production Branches and Log views in both themes, four locales, two widths and enlarged text. The same test fails all 19 cases on the original checkouts, including missing gaps, oversized controls, painted button surfaces, activating subjects and hidden filters. Source audit adversarial fixtures separately reject prohibited Material fallbacks and alias/wrapper escapes. Real GTK screenshots and sealed build receipts come from busymark/tools/git_native_smoke.py; human inspection remains required.

History's three primary filters also retain keyed editor subtrees while moving between the wide row and wrapped field group. This preserves the actual editor, focus node, selection, undo state and IME connection; retaining only controller text is insufficient. Shared and BusyMark regressions resize with a live composing range and assert the same editor/focus and complete editing value.

Git Log navigation correction (2026-11-05)

GitLogHeader, GitHistoryLayout, and GitReferenceRow are explicit required host requests. They do not change GitExpander in Rebase or other workflows. BusyMark supplies its existing native dialog titlebar, independent modal sidebar toggle, Files sidebar surface/tree rows, and dialog footer insets. The main filters belong inside the history pane. The modal retains reference search, selection, expansion and width when hidden. The title and sidebar toggle share one header row wherever their measured native text/control bounds fit. A second row is reserved for an actual overlap at very narrow or enlarged layouts; merely using the compact reference overlay does not create an extra header row. Narrow layouts open the same pane temporarily over the table; resizing does not retire a focused filter editor. Both hosts use this one modal grid, full-height reference sidebar, centered whole-modal title and padded confirmation footer.

The selected subject is neutral information with complete tooltip/semantics. Select another commit is a dedicated icon immediately before Commit Actions, with the host's normal spacing. It is absent from the menu. Commit Actions still owns full details, exact hash/message copying and all commit workflows. Historical status markers occupy their own shared slot beside Files-quality icons at every text scale; root files start at hierarchy depth zero. Selection/comparison ownership is unchanged. The confirmation footer is outside the table scroll area and uses the native lg inset on every side, including logical end in RTL.

Pinned Yaru 10.2.0's public YaruDateTimeEntry constructor has no decoration or label override; its build always supplies MaterialLocalizations.dateInputLabel. Its controller is a nullable DateTime ValueNotifier. BusyMark therefore uses its existing native BusyMarkGitTextEntry composition with a single external label, compact localized hint, native editing menu, clear action and explicit field/action spacing. MaterialLocalizations.formatCompactDate preserves the locale's displayed date. Strict parsing and the placeholder use the pinned Intl locale date pattern. Parsing ignores invisible direction-format marks and accepts both the locale's native digits and ordinary keyboard digits; field order, separators and calendar-date validation remain strict. This avoids requiring Arabic users to type invisible CLDR marks or follow a stock hint with a different field order. The controller value and IME composition are untouched. An invisible reserved clear-control slot keeps empty and populated fields the same height. These corrections were established by inspecting the native images and are covered by actual-host input/geometry tests. Blank input remains absent; both valid dates are required to save. The accepted date bounds and inclusive UI end/exclusive history-query upper bound are unchanged. No Yaru, Flutter, engine, SDK or dependency source/version is changed.

The actual-host regressions measure native surfaces, header centering, search and row insets, tree/status geometry, separated main filters, retained state, footer bounds, RTL/narrow/scaled layouts and date editing/validation/save/cancel. Four strengthened geometry checks were run first against the original source; all four failed. Native shipping-binary captures and source receipts are recorded under BusyMark's build/git-verification/2026-11-05-navigation. Widget and native desktop acceptance remain separate; screenshots must be inspected.

Interaction references consulted: GNOME header bars, sidebars, lists, text fields, menus, dialogs, keyboard, accessibility, and official pinned Flutter source/API documentation for constraints, Focus, EditableText/controllers, ModalRoute dismissal, Semantics and Directionality.

Semantic Actions and comparison geometry

View-level menus request GitMenuRole.viewActions; dynamic repository and selected-commit menus request GitIconButton.actions. Callers cannot override their icon. GitGlyph.actions is mapped once by gitLinuxIcons to the approved Yaru three-bar menu artwork in both hosts. Entry menus request entryContext; display and checked choice menus retain separate roles. The source inventory test enumerates every production menu, including remote, worktree, snapshot, and historical-file contexts. The resolved symbol audit rejects direct overflow artwork in feature controls.

GitButton.toolbar and GitButton.diffInline distinguish compact toolbar and inline region actions from ordinary/suggested push actions. Required native toolbarMetrics drive shared width measurement and overflow allocation, rather than guessed icon widths. The shared renderer owns the Actions caption and compact Log content insets. The shared modal centers its title across the entire surface; its narrow overlay retains the confirmation footer outside the overlay.

test/support/actions_presentation_contract.dart runs in both applications' actual theme/control adapters. It checks artwork, native hit geometry, semantic names, RTL menu anchoring, complete menu transport, keyboard activation and reentrant opening. tool/check_consumer_consistency.py checks equal approved pins, byte-identical archives, required consumer tests/audits and duplicate shared workflow declarations. Run it after refreshing both source archives.

The final semantic change passed all 418 shared UI tests with the controlled Git executable and supervisor configured. Native application and release acceptance remain separate from this package result.

Both consumer gates now audit the resolved first-party host rendering chain and run the cross-consumer pin/archive check. Both hosts consume the exact same shared button, field and typography implementation through Widgets focus, pointer, EditableText and native tooltip primitives; official Yaru remains unmodified. Material control constructions hidden behind host wrappers remain prohibited.

The non-Git Files/TOC/Outline/History row foundations also have a geometry audit. Its explicit sidebarGeometry scope includes complete widget construction/build chains, while generic deferred application feedback stays host-owned. Git inputs retain the default full rendering/service scope, including GitHost.notify and stateful feedback helpers. Resolved Git presentation/shared-package roots cannot select the geometry-only scope; adversarial cases cover both boundaries.

Named native action and focus ownership, 2026-11-06

A Git action exposes its name, button role, enabled state, focus and activation on one semantic node. Actual AT-SPI inspection found that the custom text-action renderer put those flags on an unnamed parent while Focus/GestureDetector exposed a named panel child. This affected enabled toolbar/inline/footer actions, not just their widget class names. Both real host contracts reproduce that split. The shared renderer now owns the complete node, suppresses only redundant inner focus/gesture annotations, and retains real keyboard, pointer and accessible actions. Disabled actions have no focus/tap action. GitActivation and row focus use the same ownership rule without replacing the native tree/table roles.

Git modal close controls retain the official unmodified YaruWindowControl's pixels and pointer behavior. One shared wrapper supplies its localized button name, state and keyboard/accessibility focus/activation. Both history's owned header and the other Git dialog headers consume that wrapper. No host-specific Git fix or upstream modification is involved. The common action/history contracts check these properties in both consumer themes; final native AT-SPI inspection and installed-application acceptance remain required.

Supported APIs: FocusableActionDetector.includeFocusSemantics, Semantics, and the actual pinned Flutter 3.47.5/Yaru 10.2.0 sources. Do not infer an original tooltip rectangle's cause from this independently reproduced accessibility defect.

History toggle semantic ownership

The neutral reference-sidebar toggle keeps its accessible toggled state, focus and activation on the same named node. The shared history layout merges the state wrapper and native action through the public MergeSemantics widget. A named parent with an actionable but unnamed child is not an accessible action. The shared historyToggleSemanticsContract dispatches through the semantic owner in both themes and in both actual host adapters; native AT-SPI activation remains an independent installed-application gate. Do not restore selected/accent painting to provide this state or alter third-party semantics implementations.

Pointer activation of a standard Git action preserves the previous keyboard focus owner, matching the approved BusyMark secondary control. Do not force focus on mouse press or hide keyboard/semantic focus to remove an outline. The host contract exercises actual mouse gestures on TargetPlatform.linux, compares against the approved control, and verifies Tab/Enter focus and return. Touch-only widget input cannot qualify desktop pointer-focus behavior.

Reference results use the public parent-scope traversal edge for Tab/Shift+Tab. Their explicit Up/Down commands cycle eligible results in the inherited public traversal-policy order. Search composition remains with its editor, and toolbar arrows do not enter the reference scope. A results-only closed loop traps native Tab before Date, Actions and the history table; the shared and actual-host contracts cover both traversal boundaries as well as local arrow wraparound.

Sidebar identity and focus

NativeSidebarHeader uses Local History's body-medium title, a secondary body-small context line, directional 12 px content insets, 8 px vertical insets, 2 px title/context gap, and 8 px action gaps. Titles and contexts elide within the available width. No context widget means no reserved second line. Context may retain a view-specific selector; Git branch/commit identities are plain text. Commit and Log have separate selection actions immediately before Actions.

NativeFocusIndicator observes supported Flutter pointer and keyboard events, without consuming them or changing focus ownership/global highlight strategy. Pointer activation hides keyboard emphasis; the next keyboard event restores it, including on an already focused row. The pinned upstream Yaru border paints a two-pixel inside outline using NativeFocusStyle's foreground semantic role at 65% opacity (opaque in high contrast). Input fields keep their focused border for pointer editing too. Selection, hover, pressed state and accent roles remain independent. Upstream source is unmodified. See the maintained host rendered property tests and actual native evidence; a component name alone is insufficient.

The focus boundary includes NativeGitIconAction, the keyboard-accessible native window-close wrapper, NativeGitCheckbox and choice-bar radios. Each keeps the upstream Yaru control and transfers its decoration through the public hasFocusBorder API. NativeFocusIndicator is the only first-party constructor of YaruFocusBorder. Its editing role permits an input's pointer focus without turning ordinary pointer-selected rows into keyboard-emphasis targets.

Sidebar context occupies the upstream Yaru title-bar item minimum extent. Its text is centered for informational and interactive contexts alike; selectors keep their native hit targets. The title-to-context-container gap remains 2.