fix(dashboard): introduce ACE Fleet in the About section, and unbreak the rail anchors

[contactacefleetdev]

Description

The About banner described the sidecar to a reader who has no way of telling it apart from the company: someone arriving through the open-source repo saw "ACE Sidecar — local developer observability" and nothing about the platform it is a slice of. It now names ACE Fleet, says what the proxy does, and places the sidecar as one open-sourced vertical of it. The pills followed the headline: LOCAL-FIRST and ZERO-CLOUD OVERHEAD are true of this page but read as claims about Fleet in that position, which inverts what Fleet is, so they are now DROP-IN PROXY and CUT AI BILLS. The outbound link opens in a new tab rather than dropping the reader out of their dashboard.

Separately, the rail's "Common questions" pointed at #s11 and landed on Live Stream. The link was a symptom: the questions section was numbered 10, the same as Session Time, so the page carried two id='s10' — invalid, and a fragment jump resolves to whichever comes first. The tail also ran 11, 13, 10, 12 in document order. Renumbered to follow the order the sections are emitted in — Prometheus 13 to 12, Common questions 10 to 13, About 12 to 14 — with the rail, the About CTA and three docstrings that had drifted to other numbers updated to match. Every rail target now resolves to the section it names.

Button styling came along with the banner, since the CTA sits inside it: spacing between glyph and label moves from a margin on the arrow to gap on the flex container, which is what lets the arrow slide on hover; word-break:break-all is dropped so "acefleet.dev" cannot split mid-word; and the links gain a :focus-visible ring, having previously been unreachable to indicate by keyboard.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Verification

Describe the tests and checks performed to verify changes:

• pytest passes cleanly.
• python -m build and twine check dist/* pass.
• E2E test script scripts/e2e_test.py passes.

Checklist

• My code follows the code style of this project.
• I have updated documentation where necessary.
• I have updated CHANGELOG.md with my changes.