Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@assets/js/custom.js`:
- Around line 10-39: Add a guard to only hijack plain left-clicks: inside the
document.addEventListener('click', (e) => { handler, after you compute const
link = ... and confirm link exists, early-return if the click is not a simple
left-click by checking e.button !== 0 || e.metaKey || e.ctrlKey || e.shiftKey ||
e.altKey (also consider returning if link.target === '_blank'), so modified
clicks or clicks meant to open in new tab/window are left to the browser; leave
the rest of the logic (using details, preventDefault, stopImmediatePropagation,
and programmatic navigation via window.location.href) unchanged.

In `@assets/scss/common/_components.scss`:
- Around line 42-58: Remove the empty lines inside the .section-desc-box rule
that are triggering stylelint's declaration-empty-line-before (specifically
remove the blank line before the font-size declaration and the blank line before
the width declaration), keeping all declarations consecutively grouped; edit the
.section-desc-box block in assets/scss/common/_components.scss (the selector
.section-desc-box) to eliminate those extra blank lines so the rule has no empty
lines between declarations.
- Around line 62-65: Define a new CSS custom property --desc-box-border-dark in
_variables-custom.scss alongside the other desc-box tokens (matching the dark
visual spec), then update the dark-mode override for the .section-desc-box
selector to include border: var(--desc-box-border-dark); (you can reference the
existing .toc-box dark-mode behavior for the exact placement and pattern).

In `@assets/scss/common/_pages.scss`:
- Around line 31-35: Replace selectors that rely on :first-child (e.g.,
.docs-content h1:first-child and the similar selectors around lines 51-54) with
type-based pseudo-class matching so the first heading is targeted even when
breadcrumbs or banners precede it; specifically, change the selector usage to
use :first-of-type for h1 (and the corresponding heading levels in the other
selectors) so .docs-content h1:first-of-type (and the analogous selectors) will
match the first heading of that type regardless of preceding elements like
main/breadcrumb or version-banner.
- Around line 42-46: The rule always shifts .ocm-section-page even when no
sidebar exists; restrict the desktop padding to only pages that sit next to the
sidebar by scoping the media query rule to when .docs-sidebar is present (e.g.
replace the selector inside the `@media` (min-width:1200px) block with a
sibling/ancestor selector such as .docs-sidebar + .ocm-section-page or
.docs-sidebar ~ .ocm-section-page so padding-left: 3.8rem only applies when
.docs-sidebar is rendered).

In `@layouts/_partials/sidebar/render-section-menu.html`:
- Around line 35-38: The current logic initializes $linkContent with
$node.Page.LinkTitle then overwrites it with $node.Name, which causes Name to
take precedence and prevents LinkTitle customizations from showing; update the
fallback order so LinkTitle wins: initialize $linkContent from $node.Name (or
use a conditional) and then, if $node.Page.LinkTitle is set, assign $linkContent
= $node.Page.LinkTitle (or implement if/else that uses $node.Page.LinkTitle when
present, otherwise $node.Name) — look for the variables $linkContent,
$node.Page.LinkTitle and $node.Name in render-section-menu.html and swap the
assignment logic accordingly.

---

Outside diff comments:
In `@assets/scss/common/_header-custom.scss`:
- Around line 198-204: The rule block for selectors .btn-link, .nav-link,
.header-github-pill, .mode-toggle uses the mixin `@include` navbar-control-reset;
but violates stylelint declaration-empty-line-before — add a single blank line
after the mixin include inside that rule so there is an empty line between the
include and the following height declaration (i.e., ensure `@include`
navbar-control-reset; is followed by one blank line, then height: 32px
!important;).

---

Nitpick comments:
In `@config/_default/module.toml`:
- Line 129: The comment above the module pin is out of date: the toml now
contains version = "v0.2.0" but the doc note still says “dev: uses latest”;
update that nearby comment block to state that the module is pinned to v0.2.0
(or otherwise reflect the pinned import) so the documentation matches the actual
version string (search for version = "v0.2.0" and edit the surrounding comment
text).