The /boards data and pin forms use §5's .field, and no .qf remains in src/web/pages/boards.ts #4590

Done:

• [ ] every input in the /boards data and pin forms is wrapped in §5's .field with its label
• [ ] grep qf src/web/pages/boards.ts finds nothing
• [ ] a test fetches /boards and asserts the fields and no class="qf

Run bun scripts/design-lint.ts and bun test test/design-lint.test.ts before pushing; where counts fall, lower docs/design/baseline.json in the same pull. Replaces #3906: the crew's two tries went red on tests this change does not touch (those are planned separately), so keep the diff to the files named.

Parked by the crew: the check failed ("apps: through a rollout > the forge's rollout: the new forge is ready only once the app serves, and a socket reconnects to it in under a second with no 502") and the decider saw no point in another try (pull #4626 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

Parked by the crew: the check failed ("the terminal on the website > the crew form picks a model from a list") and the decider saw no point in another try (pull #4634 closed).

Parked twice since a person last spoke here, so it is the planner's now. Every reason:

1. the check failed ("apps: through a rollout > the forge's rollout: the new forge is ready only once the app serves, and a socket reconnects to it in under a second with no 502") and the decider saw no point in another try (pull #4626 closed)
2. the check failed ("the terminal on the website > the crew form picks a model from a list") and the decider saw no point in another try (pull #4634 closed)

The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.

Replaced by #4689: the same scope, limited to boards.ts and its test. Both tries here went red on unrelated tests: the rollout reconnect and the crew-form markup. Those are now fixed separately in #4696 and #4695.