Pseudo-function style for new/empty frontend surfaces

[MarkusNeusinger]

Follow-up to the frontend pseudo-function style pass on branch claude/consistent-pseudo-function-style-G5I1a. The branch covered existing buttons, tooltips and the .find() prompt. A few surfaces either don't exist yet or are currently plain text and could be styled to match the brand once built.

Proposal

Surface	Current	Proposed
404 page headline	plain text (if it exists)	page.miss() or route.notFound()
Footer links	plain text	.about(), .contact(), .license()
Empty filter state	"no matches"	results.empty() + .reset() as the clear-filters action
Keyboard-help (?) overlay	—	help.keys() as title
Library-card hover CTA	arrow icon only	.explore() label
RSS / subscribe (if added)	—	feed.subscribe()
Copy-link on spec detail	—	.share()

Risks

• Low — most of these surfaces don't exist yet; this is a convention-before-build issue.
• The 404 page and empty-state exist somewhere — verify current content before writing the PR, don't silently overwrite copy.

Scope suggestion

Can be a tracking issue split into smaller PRs per surface, or a single PR that ships the ones already in the codebase. Contributors: good first issue once the style guide §7.4.1 is merged — just translate labels.