wikimedia · TodePond · Jun 23, 2026 · Jun 23, 2026 · Jun 24, 2026 · Jun 24, 2026
diff --git a/.agents/skills/protowiki-components/references/wrappers.md b/.agents/skills/protowiki-components/references/wrappers.md
@@ -219,6 +219,39 @@ Does **not** set `data-skin` / `data-theme` — pass those on content inside the
 </MobileWrapper>
 ```
 
+### Overlays inside MobileWrapper
+
+`MobileWrapper` provides `#mobile-wrapper-overlay` and
+`provide( 'CdxTeleportTarget', overlayEl )` (a template ref, not a selector
+string) so Codex popovers, bottom sheets, and dialogs teleport into a **fixed,
+viewport-height** layer aligned with the phone column (not the scrollable page
+height). Shared containment CSS lives in `src/styles/mobile-wrapper-overlays.css`.
+The overlay element must appear **before** the default slot so the ref is set
+before slot children mount.
+
+**`CdxPopover` bottom sheets:** Codex only uses bottom-sheet layout when the
+**browser viewport** is ≤639px. On wider viewports (typical desktop preview),
+`use-bottom-sheet` falls back to floating popover mode. Add
+`mobile-wrapper__sheet-popover` on the `CdxPopover` (teleport into the overlay
+root is fine) so `mobile-wrapper-overlays.css` keeps the sheet anchored to the
+bottom of the phone column:
+
+```vue
+<CdxPopover
+  v-model:open="open"
+  class="mobile-wrapper__sheet-popover"
+  use-bottom-sheet
+  :anchor="triggerRef"
+>
+  …
+</CdxPopover>
+```
+
+**Full-screen in-place dialogs** inside the frame: pass `render-in-place` to
+`CdxDialog` so it stays within the phone column instead of teleporting to
+`<body>`, then override the backdrop to `position: absolute` (it defaults to
+`fixed`, which would cover the whole browser viewport rather than the frame).
+
 ## Why these wrappers?
 
 The earlier draft of this repo had `ArticleLayout`, `ArticleBody`,

diff --git a/.agents/skills/protowiki-wikitab/SKILL.md b/.agents/skills/protowiki-wikitab/SKILL.md
diff --git a/.agents/skills/protowiki-wikitab/references/state-and-storage.md b/.agents/skills/protowiki-wikitab/references/state-and-storage.md
@@ -0,0 +1,117 @@
+# State and storage
+
+Wikitab splits persistence into three layers. Keep them separate — do not fold
+feed cache into user config, and do not persist transient view state.
+
+## Authoritative config (`wikitab-config-v*`)
+
+User preferences for this browser profile live in
+[`data/wikitabConfig.ts`](../../../../src/prototypes/wikitab/data/wikitabConfig.ts).
+
+- Storage key: `wikitab-config-v1` (bump the suffix on breaking shape changes)
+- API: `loadWikitabConfig()`, `saveWikitabConfig()`, `patchWikitabConfig()`
+- Each field is normalized on read and write (unknown section ids dropped, etc.)
+
+**Grow one field at a time.** Add a property to `WikitabConfig`, a default in
+`DEFAULT_WIKITAB_CONFIG`, and a line in `normalizeConfig`. Do not pre-build a
+wikita-lite-style mega schema — the old prototype's 772-line `urlStateSchema.ts`
+is the anti-pattern.
+
+Current fields:
+
+- `pinnedSectionIds` — most recently pinned first
+- `hiddenSectionIds` — section ids hidden from the home feed and skipped for
+  fetching (`useWikitabHiddenSections.ts`)
+- `hiddenArticleTitleKeys` — normalized article titles hidden from Trending on
+  the home feed (`useWikitabHiddenArticles.ts`)
+- `dismissedActivityRevids` — Activity-tab revision ids permanently dismissed
+  via the card ellipsis menu (`useWikitabDismissedActivity.ts`)
+
+## Cache-only feed storage (`wikitab-feed-cache-v*`)
+
+[`data/feedCache.ts`](../../../../src/prototypes/wikitab/data/feedCache.ts) caches
+the full daily feed — all six sections (Trending, In the news, Did you know,
+Active discussions, On this day, Birthdays) — under a UTC-day key. Nothing here
+is authoritative — clearing it must only ever cost one refetch.
+
+A new-tab page opens dozens of times a day; caching the daily feed is both fast
+and good API etiquette. Writing today's entry evicts older days.
+
+**Active discussions TTL** — the discussions slice carries
+`sliceFetchedAt.discussions` (epoch ms). `readCachedSectionSlice('discussions')`
+and `readCachedFeed()` treat the slice as a miss after **5 minutes**
+(`DISCUSSIONS_TTL_MS`). Other slices remain on the UTC-day key. Legacy entries
+without a timestamp are treated as stale. `persistPartialFeed()` stamps the time
+when a non-empty discussions slice lands.
+
+**Ordered home load** (`index.vue` → `refreshHomeModulesInOrder` →
+`useWikitabFeed.loadSection`) reads and writes through the same cache:
+
+- `prepareForOrderedLoad()` hydrates `feed.value` from `readCachedFeed()` when
+  the day key hits, marking cached sections as already fetched via
+  `readCachedSectionSlice()` (so stale discussions are not marked fetched).
+- Each `loadSection` call reads its slice via `fetchWikitabSectionFeed` (cache
+  before network) and patches localStorage via `persistPartialFeed()` after each
+  non-empty slice lands. Empty slices are not cached so a later open can retry.
+- `feed/featured` is deduped in-memory per UTC day when Trending, News, and DYK
+  load separately on a cache miss (`getFeaturedPayload` in
+  `fetchDailyFeed.ts`).
+- `fetchDailyFeedProgressive()` refetches discussions only when the rest of the
+  day cache hits but discussions exceeded the TTL.
+
+Skip caching when Trending is still empty (early UTC) so the next tab open can
+retry. `?nocache=1` bypasses reads and writes.
+
+**DYK / In the news** — both are "current day only" in the Wikifeeds API. DYK
+normally updates once at ~00:00 UTC; enwiki can switch to twice daily (~00:00 and
+~12:00 UTC) during nomination backlog. UTC-day cache is sufficient for normal
+days; no separate TTL unless parity with the midday rotation is needed later.
+
+## Cache-only Daily reads storage (`wikitab-daily-reads-cache-v*`)
+
+[`data/dailyReadsCache.ts`](../../../../src/prototypes/wikitab/data/dailyReadsCache.ts)
+caches the loaded card list plus `hasMore` under `{ day, savedFingerprint }`.
+Refetch only when that key misses (saved pages changed, UTC day rolled, or first
+visit) and a Daily reads render is triggered via `refreshHomeSavedModules()` —
+not on every save during the session. Only the first batch loads on refresh;
+additional cards fetch on Show more. Same `?nocache=1` bypass as the feed cache.
+
+## Cache-only Suggested edits storage (`wikitab-suggested-edits-cache-v*`)
+
+[`data/suggestedEditsCache.ts`](../../../../src/prototypes/wikitab/data/suggestedEditsCache.ts)
+mirrors Daily reads: `{ day, savedFingerprint, items, hasMore }`. Same refresh
+cadence via `refreshHomeSavedModules()` and the Saved-module snapshot. Resumable
+partial loads — `hasMore: true` lets `loadMore()` recreate the Contribute feed
+with `seenPageidsFromCards()` so cached cards are not duplicated.
+
+## Transient component state
+
+Revealed page counts (`useSectionReveal`: `reserved` / `ready`) stay in memory
+only. A new tab opens fresh every time; persisting scroll/reveal depth would add
+complexity with little benefit.
+
+## URL
+
+Wikitab does **not** use the URL for user preferences. A browser new-tab URL is
+fixed — pin state would never survive between opens if it lived in query params.
+
+The sole Wikitab-specific URL escape hatch is **`?nocache=1`**, read inline in
+`feedCache.ts` to force a feed refetch when developing against the loading
+contract.
+
+ProtoWiki-global params (`?theme=`, `?skin=`) are unrelated — they are resolved
+onto `<html>` at boot by [`src/theme.ts`](../../../../src/theme.ts) and
+[`protowiki-skins`](../protowiki-skins/SKILL.md).
+
+## Legacy migration
+
+On first load, if stored config has empty `pinnedSectionIds` and the URL still
+carries `?pinned=trending,dyk`, those ids are imported into config and the param
+is stripped via `history.replaceState`.
+
+## Cross-tab sync
+
+`useWikitabPinned.ts`, `useWikitabHiddenArticles.ts`, and
+`useWikitabDismissedActivity.ts` listen for the `storage` event on
+`WIKITAB_CONFIG_STORAGE_KEY` so pin / hide / dismiss changes in one tab update
+open tabs.
diff --git a/AGENTS.md b/AGENTS.md
@@ -71,6 +71,7 @@ trailing **Inside ProtoWiki** section.
 | [`protowiki-theme`](.agents/skills/protowiki-theme/SKILL.md)                       | Light / dark theming; per-component theme overrides                      |
 | [`protowiki-deploy`](.agents/skills/protowiki-deploy/SKILL.md)                     | GitHub Pages deploy, PR previews, base path, fork setup, SPA 404         |
 | [`protowiki-update-codex`](.agents/skills/protowiki-update-codex/SKILL.md)         | Upgrading Codex: bump packages, diff upstream docs, sync skills + tokens |
+| [`protowiki-wikitab`](.agents/skills/protowiki-wikitab/SKILL.md)                   | Wikitab new-tab page: section registry, no-jump loading contract, reveal-more paging |
 
 ### Codex (design system)
 

diff --git a/index.html b/index.html
@@ -3,7 +3,10 @@
   <head>
     <meta charset="UTF-8" />
     <link rel="icon" type="image/svg+xml" href="%BASE_URL%images/ProtoWiki.svg" />
-    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+    <meta
+      name="viewport"
+      content="width=device-width, initial-scale=1.0, viewport-fit=cover"
+    />
     <title>ProtoWiki</title>
   </head>
   <body>