8bf407d made FAQ spacing part of the verification contract

The defect

Commit 8bf407d was titled "Fix Simple help spacing and assert internal section gaps".

The FAQ check opened "What does BreachProbe do?" but did not inspect the support section's internal spacing.

The insight

The fix gave that layout a measurable contract. The paragraph gets 16px of top padding. The links sit 24 pixels below the paragraph.

BreachProbe is where this case lives: the verification now checks the spacing before continuing with the FAQ interaction.

The code

.bp-section { border-top: 1px solid var(--rule); padding: 48px 0; scroll-margin-top: 24px; }
.bp-support > h2, .bp-support > p { margin: 0; }
.bp-support > p { padding-top: 16px; }
.bp-support > .bp-home-links { margin-top: 24px; }
.bp-section-intro { display: grid; grid-template-columns: 1fr 1fr; align-items: end; gap: 6vw; padding-bottom: 28px; }
.bp-section-intro h2, .bp-result > h2 { font: 500 32px/1.25 var(--sans); letter-spacing: -.035em; padding-top: 14px; }

The test reads the computed padding and the distance between the paragraph and link group, then asserts 16px and 24.

The takeaway

I changed the FAQ check from opening one control to asserting the support spacing first.

The record: commit 8bf407d in BreachProbe, dated 2026-10-01.

Check your own case on BreachProbe.