Adjust button hover

docs/figma-component-registry.md

@@ -30,6 +30,7 @@ Quick map from the Figma file **Community Rule System** (`agv0VBLiBlcnSAaiAORgPR
 ## Button conventions (Figma “Button” canvas)
 
 - **`buttons/Button/`** — **`Button.tsx`** + **`index.tsx`**. Variants (**filled**, **outline**, **ghost**, **danger**) and **`palette`** / **`size`** align with **`lib/propNormalization`**. **`href`** renders an `<a>` when not disabled.
+- **Interaction:** hover and focus change color/border (or opacity/shadow on cards) — they must not scale the control, because that enlarges the label. Reserve `active:scale-[0.98]` for press. Same rule for nav items (`MenuItem`) and cards (`Mini`, `Icon`, article thumbnails).
 - **`buttons/InlineTextButton/`** — tertiary inline **`<button>`** (underline, inherited typography) for in-paragraph controls—**not** primary actions.
 
 ## Control conventions (Figma [“Control”](https://www.figma.com/design/agv0VBLiBlcnSAaiAORgPR/Community-Rule-System?node-id=5944-58611) canvas)

docs/guides/ops-backend-deploy.md

@@ -225,10 +225,13 @@ maintenance window — after the final Cloudron backup (§5 phase 3 step
 ([CR-101](https://linear.app/community-rule/issue/CR-101/backend-decommission-legacy-communityrule-lamp-app))
 for operator recovery if manual lookup from the export is ever needed.
 
-**User discoverability:** link to the archive repo (or a release
-download) from the new app — footer, help page, or a static
-`/legacy-archive` page — so users looking for pre-cutover rules can
-find it without knowing Gitea exists.
+**No app-side surface.** The archive lives in the repo only. It exists
+for posterity and operator lookup, not end-user self-service — there is
+no footer link, help-page entry, or `/legacy-archive` page in the new
+app, and none is required to close
+[CR-102](https://linear.app/community-rule/issue/CR-102). Operators
+answering a "where did my rule go?" question point at the Gitea repo
+directly.
 
 ## 7. Old vs new deltas