Make documentation visual qualification cover changed anchored surfaces

[rmcdaniel]

Problem

On the deployed Platform Conformance page at commit f62fa8d34f0ab13e2d5b4ca999047b28aba3f78f, navigating or scrolling to #public-manifests leaves a fragment of an earlier experiment summary control underneath the sticky navigation bar. The visible fragment receives no pointer input: rendered checks report 0 reachable points and a non-empty geometry.unreachable_controls set at 1440×900, 900×900, 390×844, and 1440×500.

The Public Manifests table and the new capacity schema catalog row render without clipping or horizontal page overflow, but the section state is still defective because a visible interactive control is occluded.

Acceptance criteria

• Navigating and programmatically scrolling to #public-manifests does not leave any ledger disclosure control partially visible beneath the sticky navigation bar.
• Rendered checks at desktop, intermediate, mobile, and short-height viewports report no unreachable controls, clipped controls or text, horizontal page overflow, browser errors, or console errors.
• The Public Manifests heading and capacity benchmark schema catalog entry remain visible and operable in the section-focused state.
• Stable 1.x remains the default documentation line and 2.0 remains an explicit prerelease route.

Delete when

Delete when the fix is deployed from main and live section-focused captures at all four viewport classes have an empty geometry.unreachable_controls set.

Consolidated scope

Anchor reachability, permalink visibility, sticky/floating overlap, and exact-route browser evidence are one rendered-documentation qualification contract.

#103: Make docs qualification consume reachability failures from section captures

Problem

Commit f62fa8d34f0ab13e2d5b4ca999047b28aba3f78f required rendered evidence focused on the changed #public-manifests state. The commit landed, but an exact live capture of that state exits unsuccessfully with a non-empty geometry.unreachable_controls report at every required viewport class.

The reachability collector is working; the missing protection is in change classification or evidence consumption. Screenshots showing the changed row were accepted without ensuring the associated reachability result was successful for the exact landed revision.

Acceptance criteria

• Customer-facing documentation changes that require a section-focused rendered state cannot satisfy qualification with screenshots alone; the corresponding machine report and capture exit status are required.
• Any non-empty geometry.unreachable_controls result fails qualification at desktop, intermediate, mobile, and short-height viewports.
• Evidence is bound to the exact candidate commit and required interaction or scroll state, so evidence from an earlier revision or a default first viewport cannot satisfy the check.
• A regression fixture representing an interactive disclosure partially occluded by sticky navigation proves the qualification path rejects the evidence.
• The corrected live Platform Conformance #public-manifests state passes the same qualification matrix without weakening overflow, clipping, console, or page-error checks.

Delete when

Delete when the negative fixture is rejected end to end and an exact-revision section-focused evidence matrix cannot be accepted while any required reachability report is failing.

#106: Keep Platform Conformance ledger permalink targets visible

Status Summary

The Executed Run Ledger exposes shareable hash links for tiers and experiments, but those links do not reliably leave the target visible. A direct desktop link to /docs/platform-conformance/#conformance-experiment-activities opens the disclosure while positioning the experiment heading and its permalink beneath the sticky navbar, making that control unreachable. The tier permalink is likewise clipped on narrow screens, and following an experiment permalink in-page can settle at the page top instead of the expanded target.

This makes exact conformance evidence difficult to share and navigate even though the underlying ledger content is present.

How to fix

Coordinate disclosure opening, router scroll restoration, and the sticky-header offset for tier and experiment hash targets. The target heading and its permalink must remain fully visible after direct navigation, in-page navigation, and browser history navigation.

Acceptance Criteria

• Direct tier and experiment hash URLs open the owning disclosure and land on the requested target.
• In-page tier and experiment permalinks land on the same visible target without returning to the page top.
• Browser back and forward navigation preserves the correct expanded target.
• Desktop, intermediate, mobile, and short-height evidence shows the target heading and permalink fully visible and reachable, with no new clipping, horizontal overflow, console errors, or unreachable controls.

Complete when all ledger hash-navigation paths satisfy these criteria on the public Platform Conformance page.

#107: Keep Server Config tables clear of the sticky page navigation

Problem

On the live 2.0 Server Config Reference, wide configuration tables extend beneath the sticky On this page rail. At 1440x900 and 1280x360, the Purpose and Legacy alias cells are obscured while the rail remains above them. The external-payload rows added in f615b2c are affected. Browser geometry reports a non-empty floating-element overlap even though document-level horizontal overflow is false.

At intermediate and mobile widths the page removes the right rail, but the table still needs an understandable responsive treatment so every cell remains discoverable without losing row context.

Acceptance criteria

• Wide reference tables remain inside the readable content region and never render beneath the sticky page-navigation rail.
• Every Variable, Default, Purpose, and Legacy alias cell remains reachable at desktop, intermediate, mobile, and short-height viewports.
• The external-payload rows can be read with their row context intact at each viewport.
• Browser evidence reports no overlapping floating elements, unreachable controls, clipped control text, or document-level horizontal overflow.
• Keep validation structural; do not couple tests to exact documentation prose.

Delete when

The live Server Config Reference passes the four-viewport checks above, including a section-scoped capture of the external-payload rows.

#108: Qualify changed documentation routes for floating-element overlap

Problem

The documentation visual qualification renders representative Platform Conformance routes rather than the routes changed by a landing. It also rejects horizontal overflow and unreachable controls but does not reject non-empty floating-element overlap. As a result, a Server Config Reference change can pass qualification while its wide table renders beneath the sticky On this page rail.

Acceptance criteria

• Visual qualification renders every materially affected documentation route or a justified route-specific state selected from the changed files.
• Table-heavy documentation changes exercise the affected table section at desktop, intermediate, mobile, and short-height viewports.
• The gate rejects unexpected floating-element overlap in addition to horizontal overflow and unreachable controls.
• A focused fixture proves that a sticky page-navigation rail covering table cells fails qualification.
• Evidence identifies the route, section or interaction state, viewport, geometry report, and screenshot that produced a failure.

Delete when

A change affecting the Server Config table cannot pass documentation qualification with the table/rail overlap reproduced by durable-workflow.github.io#107.