v0.1.6

Fix

• The master toggle and status line no longer scroll out of view. The popup was three elements in normal flow, so once the profile list overflowed, both the on/off control and the X/Y domains granted readout left the viewport (FINDING-022). The list now scrolls between a fixed header and a fixed footer. This was reached sooner than expected: v0.1.5's collision marker costs roughly 110px per card, so two colliding profiles could push Add profile below the fold at three profiles, not six. Verified against that exact configuration.

• Two refusal messages no longer describe a state that isn't happening. Saving a colliding profile, and importing a file containing a collision, both reused the wording written for the per-profile card marker — which reports that a stored profile is not applying (FINDING-026). Neither case is that: nothing had been saved, nothing had been imported, and on import the message could appear directly beneath cards that legitimately did say "Not applying". Both now describe the refused action and name what to change. The import message also stated the problem twice and ended in a double period; both are corrected. The card marker's wording is unchanged.

Change

• The subdomain migration notice now names its visual marker. It closes with "Click any underlined domain below to re-approve it", and domains carrying a pre-0.1.4 grant are the only ones underlined. No behaviour change; the notice was already correct, and this makes the domains it counts identifiable.

Notes

• No new permissions. The manifest is unchanged: declarativeNetRequestWithHostAccess and storage, with host access requested per-domain at grant time. No webRequest; the extension cannot read your traffic.
• v0.1.5's notes said the four-surface gap was "being addressed in the next release". This release does not close it. A colliding profile still shows a green domain dot, is counted in the "domains granted" total, and the status line still reads "applying" — the per-profile marker remains the only surface reporting the collision. Closing it means the status line and badge reporting how many profiles were skipped, which is new signal rather than corrected signal, so it is queued rather than patched.
• Known limit: with many profiles, a delete confirmation can render below the visible area, with nothing indicating that the popup continues below (FINDING-030). Not a regression — it was also off-screen before this release — but the pinned footer now reads as the end of the popup.
• Browser evidence for this release is in test/EVIDENCE.md (v0.1.6 — sitting E). Predictions were frozen before the browser opened (test/RUNBOOK-2026-09-04-v016.md); 12 of 13 were right, and the wrong one is recorded with its original wording.
• FINDING-023, a claim that domain chip tooltips never render, was withdrawn during this cycle as not reproducible. The tooltips render. The migration notice change above stands on its own merits.
• Selftest is 273 checks, 32 of them for this change. The new logic also passes a 31-mutation pass, re-runnable via test/mutate-collisions.py.
• Known open items are tracked in FINDINGS.md (024, 025, 027–031); none block this fix.