Replace JavaScript-only action links with semantic controls - #8978

…avigation panel controls

Move the reader sidenav and account-menu triggers onto the established button pattern.

These are the remaining navigation-panel variants, so they stay adjacent to the seed rather than becoming a second navigation change.

…ilter and export controls

Convert the filter and export panel triggers to semantic buttons while preserving their target wiring.

They use the same mechanical replacement as the seed and are grouped for one focused follow-up review.

…responsive control styling

Keep the converted main navigation trigger visually consistent in the responsive and dark-theme navigation styles.

The styling is derivative of the button migration, so it remains attached to that seed.

Replace the topbar mode trigger with a native button while keeping the existing Stimulus mode transition intact.

The topbar has a distinct interaction model, so its semantic conversion is reviewed separately from navigation triggers.

…search close controls

Convert the close controls used by the add URL and search modes to native buttons.

They complete the same topbar pattern and remain an adjacent fixup for focused review.

…ior and styling

Retain the close-button icon layout after the semantic element change.

This visual adjustment is inseparable from the converted topbar control and stays a fixup.

Convert the shared theme-selection actions to native buttons without changing the theme controller contract.

Theme selection is a separate control family and can be reviewed independently from topbar modes.

…heme controls

Apply the established theme-button pattern to reader-specific theme actions.

These controls share the seed behavior and remain grouped as its follow-up.

…lize dropdown behavior

Preserve dropdown, sidenav, and dark-theme styling for converted theme controls.

The style changes are derivative of the theme conversion and belong in its fixup block.

Convert the primary reader action control to a native button while retaining the existing disclosure wiring.

Reader actions have their own interaction surface, so this seed stays separate from topbar and theme controls.

…nd floating actions

Convert theme, share, and floating reader disclosures to the established button pattern.

These controls complete the same reader-action migration and remain together for a focused follow-up review.

…rt and print actions

Convert the remaining export and print reader actions to native buttons.

They use the seed pattern and stay in its fixup block instead of creating a second reader action story.

…-click protection

Remove Materialize keyboard handling that duplicates native button activation.

This is a compatibility correction to the reader button conversion and belongs with its seed.

Replace the initial configuration help trigger with a native button while preserving the tooltip controller contract.

Configuration help is a separate control family and is intentionally isolated for review.

…ooltip triggers

Apply the configuration-help button pattern to the remaining article-display tooltip triggers.

They are equivalent migrations, so this stays as the seed follow-up.

…-control dimensions

Keep tooltip icon alignment and line-height stable after the native button conversion.

The CSS adjustment is a direct completion of the configuration-help seed.

Add a repository-wide Twig anchor guard that rejects anchors without real destinations.

This establishes the semantic regression boundary after the button migrations; specialized invalid destinations follow as fixups.

…are fragment destinations

Reject bare hash destinations in Twig anchors.

This narrows the seed validation with one concrete invalid-link form, so it remains a fixup.

…ly the intentional bookmarklet

Reject JavaScript destinations while retaining the known static bookmarklet exception.

The exception refines the same anchor guard and belongs in its fixup block.