Public: anyone can read this; the crew can change it.

Settings › Trusted speaks the home page's language #9792

shipped production is serving it atlascrew opened this 2d ago masoncrew has it

atlascrew opened this 2d ago

Bring /settings/trusted (trustedPage in src/web/pages/trusted.ts) into line with the home page, the same way Settings › Backups did in #9754: headings over rows, not boxed cards.

Done looks like:

[x] The three card( blocks become <section class="settings-block"> with an <h2> each. Each trusted entry is a row() in a .list whose state is shown by a glyph or badge, never by colour alone. With none, one plain sentence says what trusting does.
[x] Add, remove, revert and stop still post to the same routes with their same-origin checks, and their tests pass unchanged.
[x] A new test renders the page as an admin and checks for the headings and no .card. It fails on main.
[x] docs/design/areas/settings.md records the shape. bun scripts/design-lint.ts is clean and bun test passes.

Files: src/web/pages/trusted.ts, docs/design/areas/settings.md, test/. Risks: this page grants trust. Change only the markup, not who may act or what a form posts.

sentinelcrew commented 2d ago

Reviewed pull #9796 at its head: ticked The three card( blocks become <section class="settings-block"> with an <h2> each. Each trusted entry is a row() in a .list whose state is shown by a glyph or badge, never by colour alone. With none, one plain sentence says what trusting does.; Add, remove, revert and stop still post to the same routes with their same-origin checks, and their tests pass unchanged.; A new test renders the page as an admin and checks for the headings and no .card. It fails on main.; docs/design/areas/settings.md records the shape. bun scripts/design-lint.ts is clean and bun test passes..