fix: design harmonization on last features

features/activity_home_card_and_retention.feature

@@ -7,7 +7,7 @@ Feature: Recent activity card on Home and Retention card on Settings
   Background:
     Given the activity API (features/activity-log-backend.feature, activity-log-producers.feature, activity_screen.feature) and the settings retention fields already exist
     And this slice adds one field to the settings API, activity_next_cleanup_at, and wires the SPA to the existing endpoints; there is no other Go change
-    And the Home card and the Settings "Retention" card are the two items activity_screen.feature left out of scope; the spec of record is docs/design/screens/home.md ("Recent activity card") and docs/design/screens/settings.md ("Activity retention"), groups "Home card" and "Settings retention" of RenewCMS Screens Activity.dc.html
+    And the Home card and the Settings "Retention" card are the two items activity_screen.feature left out of scope; the spec of record is docs/design/screens/home.md ("Recent activity") and docs/design/screens/settings.md ("Activity retention"), groups "Home" and "Settings: Retention" of RenewCMS Screens Back-office.dc.html
     And both boards draw the existing cards as dashed placeholders, so neither card is pixel-compared and Vitest is the SPA coverage
     And "owner" and "admin" are the full Home view; any other or absent session role is the regular-user view
     And every new English string has a French entry in messages.ts

features/media_cleanup_spa.feature

@@ -18,10 +18,10 @@ Feature: Media cleanup in the SPA: Settings card, purge dialog and Media Duplica
       summary and try again." (stale fingerprint) or "A purge is already running." (busy)
     And "owner or admin" is session.role in ('owner', 'admin'); only those two roles exist, so any
       other role is a mocked value in tests
-    And /settings is the verified route of settings_page.feature; the Media cleanup card is its second
+    And /settings is the verified route of settings_page.feature; the Media cleanup card is its third
       card, below Version and Updates, 20 px under the previous card, in a page at most 720 px wide
     And the card is --ui-bg with a 1 px --ui-border, 20 px padding (16 px on mobile), 16 px gap, as
-      drawn in docs/design/source/SettingsFrame.dc.html
+      drawn in docs/design/source/AppFrame.dc.html
     And the components are Nuxt UI v4 only (UCard, USwitch, UInputNumber, UFormField, UAlert, UButton,
       UModal, USkeleton, useToast) and design tokens only
     And PurgeDuplicatesDialog is one component shared by the card and the Media Duplicates tab: props

features/media_cleanup_spa.qa.md

@@ -61,7 +61,7 @@ Amendments to existing specs, in the same change: `SettingsView.spec.ts` and the
 
 ## Visual (`task visual:check -- settings` and `task visual:check -- media`, desktop and mobile, light and dark)
 
-References: `docs/design/screens/settings.md` ("Media cleanup (second card)"), `docs/design/screens/media.md`, `docs/design/source/RenewCMS Screens Media cleanup.dc.html` and the frames `SettingsFrame.dc.html`, `MediaFrame.dc.html` (exact values). Add every state below to `web/visual/states.ts`, with the mocked `/v1` calls the state needs. The gate is hard: every capture within 10 %. Nothing is skipped: no state depends on the clock, because dates come from fixture timestamps (midday UTC, so the day is stable).
+References: `docs/design/screens/settings.md` ("Media cleanup (third card)"), `docs/design/screens/media.md`, `docs/design/source/RenewCMS Screens Back-office.dc.html` and the frames `AppFrame.dc.html`, `MediaFrame.dc.html` (exact values). Add every state below to `web/visual/states.ts`, with the mocked `/v1` calls the state needs. The gate is hard: every capture within 10 %. Nothing is skipped: no state depends on the clock, because dates come from fixture timestamps (midday UTC, so the day is stable).
 
 Board sample data to reuse:
 - Last purge fixture: `last_purge_at` 14 Jun 2026, merged 3, articles 5; "on" has 30 days and next 14 Jul 2026 (`next_purge_at` "2026-07-14T09:00:00Z").