diff --git a/cli/package.json b/cli/package.json
index a7a6cb1..9b3817d 100644
--- a/cli/package.json
+++ b/cli/package.json
@@ -1,6 +1,6 @@
 {
 	"name": "@bproxy/cli",
-	"version": "0.9.0",
+	"version": "0.9.1",
 	"private": true,
 	"type": "module",
 	"bin": {
diff --git a/docs/internal/plans/phases/11-extension-popup-compliance.md b/docs/internal/plans/phases/11-extension-popup-compliance.md
new file mode 100644
index 0000000..a1a9a28
--- /dev/null
+++ b/docs/internal/plans/phases/11-extension-popup-compliance.md
@@ -0,0 +1,176 @@
+---
+title: "Phase 11: Extension popup compliance and presentation"
+status: complete
+date: 2026-06-23
+---
+
+## Phase 11: Extension popup compliance and presentation
+
+**Motivation:** The extension popup was functional but too minimal for first-run clarity and Chrome Web Store review. It needed to explain what bproxy is, show version/protocol metadata, link to docs and privacy information, and present pairing state more clearly without turning the popup into a dashboard.
+
+**Source decisions:**
+
+- [ADR-001](../../decisions.md#adr-001-default-instrumentation-strategy--read-mode) — programmatic injection only
+- [ADR-011](../../decisions.md#adr-011-extension-token-bootstrap-via-popup-driven-pairing) — popup-driven pairing
+- [ADR-016](../../decisions.md#adr-016-web_accessible_resources-default-deny) — no WAR by default
+- [ADR-017](../../decisions.md#adr-017-sensoractuator-boundary) — popup remains a thin pairing surface, not a dashboard
+- [ADR-024](../../decisions.md#adr-024-no-arbitrary-page-eval-and-no-scroll-target-inference) — no extra control/eval surface
+- [ADR-025](../../decisions.md#adr-025-security-scanner-findings-are-remediated-in-code) — compliance changes land in code/tests
+
+---
+
+## Scope shipped
+
+| # | Deliverable | Outcome |
+|---|-------------|---------|
+| 1 | Popup markup/style redesign | Shipped |
+| 2 | Version and protocol metadata rendering | Shipped |
+| 3 | Footer links (docs, license, credits) | Shipped |
+| 4 | Paired/unpaired state presentation | Shipped |
+| 5 | Privacy policy page for CWS | Shipped |
+| 6 | Store listing manifest description | Shipped |
+| 7 | Popup test updates | Shipped |
+
+Out of scope remained unchanged:
+- No session counts, tab counts, recent activity, or operator dashboard UI
+- No options page
+- No new permissions or `web_accessible_resources`
+- No strategy, selector repair, retries, or fallback chains in the popup
+
+---
+
+## Major changes
+
+### Popup UI rewrite
+
+`extension/src/entrypoints/popup/index.html` was redesigned into a compact single-column utility layout with:
+- inline cable icon + product name
+- subtitle: `Human-in-the-loop browser bridge for AI agents.`
+- explicit pairing status line above the form
+- pairing help text
+- footer metadata and outbound links
+
+The popup stayed fully static in HTML/CSS for presentation:
+- inline styles only
+- no external assets
+- native form semantics preserved
+- no new runtime permissions or WAR entries
+
+### Pairing-state presentation
+
+`extension/src/entrypoints/popup/main.ts` now:
+- reads local bootstrap state from `chrome.storage.local`
+- renders `Not paired` vs `Paired with local daemon`
+- shows a gray or green status dot
+- updates status immediately after successful pairing
+
+Important honesty rule preserved: "Paired" means a valid local bootstrap record exists; it does not claim the daemon is currently reachable.
+
+### Version and protocol metadata
+
+The popup now renders:
+- `Extension ${VERSION}`
+- `Protocol ${PROTOCOL_VERSION}`
+
+Both values come from `@bproxy/shared`.
+
+### Footer links and attribution
+
+The popup footer now includes static external links to:
+- documentation
+- privacy page
+- MIT license
+- GitHub repository (icon link)
+
+Attribution is shown as plain text: `Created by Dim Kharitonov`.
+
+### Re-pair UX follow-up
+
+After manual review, the paired-state submit button was clarified:
+- unpaired: `Pair extension`
+- paired: `Re-pair with new code`
+
+This matches actual architecture behavior: entering a new valid pairing code replaces the stored bootstrap and reconnects the background worker with a fresh extension token.
+
+### Manual presentation tweak after review
+
+After loading the built extension in Chrome, popup spacing was increased to improve visual separation from the page behind it:
+- outer padding increased
+- major section spacing increased
+
+This was a presentation-only adjustment; no behavioral changes.
+
+### Manifest and privacy materials
+
+- `extension/wxt.config.ts` manifest description was updated to CWS-safe wording:
+  - `Companion extension for bproxy. Connects Chrome to a local bproxy daemon for explicit human-in-the-loop browser actions.`
+- `docs/public/privacy.md` was rewritten as a short factual privacy policy page for `/privacy/`
+
+### Tests
+
+Added `extension/src/entrypoints/popup/__tests__/presentation.test.ts` to cover:
+- title/subtitle/copy
+- footer metadata and links
+- attribution and GitHub link
+- paired/unpaired view-model behavior
+- version/protocol rendering fallback behavior
+
+Existing pairing-flow tests remained intact.
+
+---
+
+## Files changed
+
+| Package | File |
+|---|---|
+| extension | `src/entrypoints/popup/index.html` |
+| extension | `src/entrypoints/popup/main.ts` |
+| extension | `src/entrypoints/popup/__tests__/presentation.test.ts` |
+| extension | `wxt.config.ts` |
+| docs/public | `privacy.md` |
+
+No changes were required in `shared/`, `service/`, `cli/`, the background SW, content scripts, or the protocol wire shape.
+
+---
+
+## Shipped outcome
+
+The popup now presents bproxy as a clear pairing utility instead of a bare form:
+- product identity and purpose are visible immediately
+- pairing state is visible immediately
+- version/protocol metadata is available for support/debugging
+- documentation/privacy/license/credits are one click away
+- paired users see `Re-pair with new code`, which matches the actual token-rotation flow
+
+This improved first-run clarity and CWS readiness without expanding the popup into an operator surface or violating the extension's sensor/actuator boundary.
+
+---
+
+## Validation
+
+Validated during implementation:
+- `pnpm --filter @bproxy/extension typecheck`
+- `pnpm --filter @bproxy/extension test`
+- `pnpm docs:build`
+- `pnpm check`
+- `pnpm --filter @bproxy/extension build`
+
+Manual verification in Chrome confirmed:
+- updated layout and spacing render correctly
+- paired/unpaired states display correctly
+- successful pairing updates the status line
+- paired state shows `Re-pair with new code`
+- footer links open correctly
+
+---
+
+## Deferred / rejected
+
+| Item | Reason |
+|---|---|
+| Session/tab/activity dashboard in popup | Rejected for this phase; daemon remains the authority and popup is not an operator dashboard |
+| WebSocket live connection state in popup | Deferred; badge already covers transport state |
+| Options page | Explicitly out of scope |
+| Store icons/screenshots/promo assets | Deferred; non-code store assets |
+| Dark mode | Deferred; no requirement for this increment |
+| Localization | Deferred; English-only for now |
diff --git a/docs/internal/solution/extension-popup-compliance.md b/docs/internal/solution/extension-popup-compliance.md
new file mode 100644
index 0000000..cdb9889
--- /dev/null
+++ b/docs/internal/solution/extension-popup-compliance.md
@@ -0,0 +1,249 @@
+---
+title: Extension Popup Compliance and Presentation
+---
+
+Solution note for making the bproxy Chrome extension popup clearer, more transparent, and easier to review against Chrome Web Store expectations.
+
+**Decisions that constrain this:** [ADR-001](../decisions.md#adr-001-default-instrumentation-strategy--read-mode) (programmatic injection only), [ADR-011](../decisions.md#adr-011-extension-token-bootstrap-via-popup-driven-pairing) (popup-driven pairing), [ADR-016](../decisions.md#adr-016-web_accessible_resources-default-deny) (no WAR by default), [ADR-017](../decisions.md#adr-017-sensoractuator-boundary) (extension is sensor/actuator only), [ADR-024](../decisions.md#adr-024-no-arbitrary-page-eval-and-no-scroll-target-inference) (no eval / no scroll inference), and [ADR-025](../decisions.md#adr-025-security-scanner-findings-are-remediated-in-code) (security findings remediated in code).
+
+## Inputs
+
+- Current popup screenshots show a minimal pairing form with title, pairing-code input, pair button, and one status sentence. It is functional, but too terse for a user or reviewer to understand scope, authorship, version compatibility, license, or where to read more.
+- Current extension spec: [public extension solution](../../public/solution/extension.md).
+- Current public documentation URL: <https://dimdasci.github.io/bproxy/>.
+- Current root package metadata: version `0.9.0`, license `MIT`, description `Human-in-the-loop browser proxy for AI agents.`
+- Current protocol version source: `shared/src/version.ts` exports `PROTOCOL_VERSION = 2`.
+- Current license file: [`LICENSE`](../../../LICENSE). User-facing credits use `Dim Kharitonov`.
+
+## Chrome Web Store requirements observed
+
+Chrome's policy pages use five themes that apply directly to this popup and listing.
+
+| Theme | Requirement | Source |
+|---|---|---|
+| Be honest | Extension functionality should be clearly disclosed to users, with no surprises. | [Program Policies — Chrome Web Store Principles](https://developer.chrome.com/docs/webstore/program-policies) |
+| Be useful / quality | Extensions should have a narrow, understandable purpose and a respectful user experience. Persistent UI should help the current task and avoid distraction. | [Quality guidelines](https://developer.chrome.com/docs/webstore/program-policies/quality-guidelines) |
+| Minimum functionality | Extension must provide real utility, not just launch/link to another site. | [Minimum Functionality](https://developer.chrome.com/docs/webstore/program-policies/minimum-functionality) |
+| Permission minimality | Request the narrowest permissions needed for implemented features; do not future-proof permissions. | [Use of Permissions](https://developer.chrome.com/docs/webstore/program-policies/permissions) |
+| Data transparency and handling | Disclose collection/use/sharing of user data, and handle auth/user data securely. | [Disclosure Requirements](https://developer.chrome.com/docs/webstore/program-policies/disclosure-requirements), [Handling Requirements](https://developer.chrome.com/docs/webstore/program-policies/data-handling) |
+| Limited Use | Use of collected data must be limited to the disclosed single purpose. No transfer to third parties except for providing/improving that purpose, legal compliance, or security. An affirmative compliance statement must appear on a website belonging to the extension — but this applies specifically to extensions that access Google user account data via OAuth/Google APIs. Extensions that only use Chrome platform APIs (tabs, scripting, storage, etc.) for local functionality and do not collect or transmit user data are not subject to this requirement. | [Program Policies — Limited Use](https://developer.chrome.com/docs/webstore/program-policies/policies#limited_use) |
+| Listing requirements (mandatory) | Submissions missing a description, icon, or screenshots are **rejected**. Privacy field declarations must be accurate and consistent with the privacy policy and actual extension behavior. | [Program Policies — Listing Requirements](https://developer.chrome.com/docs/webstore/program-policies/policies#listing_requirements) |
+| Listing metadata (quality) | Provide a detailed description, graphics, homepage URL, support URL, and content rating/details. | [Complete your listing information](https://developer.chrome.com/docs/webstore/cws-dashboard-listing), [Creating a great listing page](https://developer.chrome.com/docs/webstore/best-listing) |
+| Code readability (MV3) | Full functionality must be easily discernible from submitted code. No obfuscation, no remote logic execution. Minification is allowed. | [Program Policies — Code Readability Requirements](https://developer.chrome.com/docs/webstore/program-policies/policies#code_readability_requirements) |
+
+## Presentation goal
+
+The popup should answer four questions immediately:
+
+1. **What is this?** The Chrome-side piece of bproxy: a local, human-in-the-loop browser bridge for AI agents and agentic systems.
+2. **What does it do?** Pairs this Chrome profile with the local bproxy daemon so an agent can request explicit browser actions through the user's real browser session.
+3. **Who made it and under what terms?** Created by Dim Kharitonov, MIT licensed.
+4. **Where can I verify details?** Documentation, license, and credits links.
+
+Avoid decorative product-dashboard language. Do **not** introduce badges, chips, gradients, icon clutter, or trend-driven UI elements. The popup should feel like a small browser utility: restrained, readable, explicit.
+
+## Proposed popup content
+
+```text
+bproxy
+Human-in-the-loop browser bridge for AI agents.
+
+Status: Not paired
+
+Pairing code
+[ VQE7-KNBM              ]
+[ Pair extension ]
+
+Run `bproxy service start` and paste the one-time code shown by the daemon.
+
+Extension 0.9.0 · Protocol 2
+Documentation · License · Credits
+Created by Dim Kharitonov · MIT
+```
+
+When paired:
+
+```text
+Status: Paired with local daemon
+```
+
+When pairing fails, preserve the existing specific error messages and codes, but keep them below the form and use plain text color treatment only.
+
+## Required metadata
+
+The popup should render these values from source-of-truth constants where practical:
+
+| Field | Value / source | Notes |
+|---|---|---|
+| Extension version | `VERSION` from `@bproxy/shared` or WXT/manifest package version | Must match release package version. |
+| Protocol version | `PROTOCOL_VERSION` from `@bproxy/shared` | Useful for daemon/extension mismatch support. |
+| Documentation | `https://dimdasci.github.io/bproxy/` | Use a normal external link. |
+| License | MIT, linked to repository license or docs license page | Link target can be GitHub `LICENSE` until a docs page exists. |
+| Credits | Created by Dim Kharitonov | Link to repository or credits section/page. |
+
+## Copy requirements
+
+Use copy that is transparent without over-explaining internals:
+
+- Product subtitle: `Human-in-the-loop browser bridge for AI agents.`
+- Purpose text: `This extension pairs Chrome with your local bproxy daemon so AI agents and agentic systems can request explicit browser actions while you stay in control.`
+- Human-control sentence: `You handle logins, CAPTCHAs, consent screens, and final submits.`
+- Pairing help: `Run bproxy service start and paste the one-time code shown by the daemon.`
+- Success text: `Paired with local daemon. You can close this popup.`
+- Footer: `Created by Dim Kharitonov · MIT`
+
+Avoid claims such as "undetectable", "bypass", "stealth", "anti-bot", or anything suggesting circumvention. The public framing should remain human-in-the-loop browser control, not evasion marketing.
+
+## Layout requirements
+
+- Use one compact column, about `340px` to `380px` wide.
+- Keep native form semantics: real `form`, `label`, `input`, `button`, and `output aria-live="polite"`.
+- Use text hierarchy, spacing, and a thin divider for clarity.
+- Links live in a simple footer: `Documentation · License · Credits`.
+- No badge/chip components.
+- No external fonts or remote assets.
+- No options page is required for this increment.
+
+## Compliance notes for manifest and listing
+
+The popup cannot carry all compliance burden. Store listing and privacy fields should also disclose:
+
+- bproxy is a companion extension for a local daemon/CLI.
+- It can read page text/structure and perform explicit browser actions only after pairing.
+- It stores pairing bootstrap material in Chrome extension storage.
+- It communicates with `ws://127.0.0.1:9615/ws` / `http://127.0.0.1:9615/pair/claim` only for local daemon pairing/control.
+- Broad host access exists because the user/agent may work on arbitrary pages; this must be justified in listing/privacy text.
+- Permission rationale:
+  - `tabs`: route actions to tabs and manage user-requested tab actions.
+  - `scripting`: programmatically inject the isolated content script on first command.
+  - `webNavigation`: track top-level navigation state for session/page identity.
+  - `alarms`: background service-worker keepalive/reconnect scheduling.
+  - `storage`: persist bootstrap token and bounded session diagnostics.
+  - `<all_urls>`: support user-selected pages across the web.
+
+### Limited Use — does not apply to bproxy
+
+The Limited Use affirmative statement requirement applies to extensions that access Google user account data via OAuth/Google service APIs (Gmail, Drive, Calendar, etc.). bproxy does not use any Google account APIs. It uses only Chrome extension platform APIs (`tabs`, `scripting`, `webNavigation`, `storage`, `alarms`) for local functionality.
+
+The extension does not collect user data:
+
+- Page content is read on demand and passed to a localhost daemon on the same machine — nothing leaves the user's device.
+- The only persisted value is the pairing bootstrap token in `chrome.storage.local`.
+- No browsing history, page content, or user activity is stored or transmitted externally.
+
+In the CWS privacy fields, the correct declaration is: **"This extension does not collect user data."** No Limited Use disclosure page is needed.
+
+### Privacy policy page
+
+The CWS dashboard requires a privacy policy URL. The page should be published on the docs site at `https://dimdasci.github.io/bproxy/privacy/` and state in plain English:
+
+- The extension does not collect, store, or transmit any user data.
+- It reads page content only when an agent sends a command, and passes it to a daemon running on the same machine (`127.0.0.1`).
+- Nothing leaves the user's device. There is no remote server, no analytics, no telemetry.
+- The only value the extension persists is a pairing token in Chrome's local storage, used to authenticate the connection to the local daemon.
+- The extension communicates exclusively with `localhost:9615`. It never contacts any external service.
+
+Keep it short. No legal boilerplate. No "we may update this policy" padding. Just the facts about how it works and why there is nothing to disclose.
+
+### Listing mandatory assets
+
+The store will **reject** submissions that are missing any of:
+
+- A non-blank detailed description.
+- A 128×128 px store icon.
+- At least one 1280×800 px (or 640×400 px) screenshot.
+
+Screenshots should show the popup in both unpaired and paired states. A third screenshot may show a terminal with `bproxy service start` output to illustrate the pairing flow.
+
+### Privacy fields consistency
+
+The CWS developer dashboard privacy fields must:
+
+- Accurately declare what user data is collected (page text/structure read on demand, pairing token stored locally).
+- State that data is not transferred to any third party.
+- Be consistent with the privacy policy text and actual extension behavior.
+
+If privacy field declarations contradict the privacy policy or observed behavior, the extension may be removed from the store.
+
+### Code readability (MV3)
+
+bproxy already satisfies this requirement:
+
+- Source maps are preserved in production output (`sourcemap: true` in `wxt.config.ts`).
+- No obfuscation; code is minified only.
+- No remote logic execution — all functionality is self-contained in the extension package.
+- No `eval()`, no `<script>` tags pointing to external resources.
+
+No action needed, but this should be verified on each release build.
+
+The manifest description should stay clear and non-promotional. Candidate wording:
+
+> Companion extension for bproxy. Connects Chrome to a local bproxy daemon for explicit human-in-the-loop browser actions.
+
+## Store listing assets
+
+No custom artwork is planned. All graphics derive from existing assets.
+
+| Asset | Requirement | Source | Action |
+|---|---|---|---|
+| Store icon | 128×128 px PNG | `assets/brand/cable.svg` (Lucide cable icon, 24×24 SVG) | Render at 128×128 on a solid background |
+| Screenshot ×1–5 | 1280×800 px | None yet | Capture popup in unpaired and paired states; optionally a terminal showing `bproxy service start` |
+| Small promo tile | 440×280 px | `assets/bproxy-hero.png` (1571×1001, aspect ≈1.57:1) | Resize/crop — aspect ratio is nearly exact |
+| Marquee promo tile | 1400×560 px (optional) | `assets/bproxy-hero.png` | Needs wider recomposition; defer unless featuring is pursued |
+
+### Dashboard fields
+
+| Field | Value |
+|---|---|
+| Homepage URL | `https://dimdasci.github.io/bproxy/` |
+| Support URL | `https://github.com/dimdasci/bproxy/issues` |
+| Category | Developer Tools |
+
+### Blocked by
+
+- Screenshots require the popup code changes from this solution to be implemented first.
+- Privacy policy page must be published on the docs site before submission (simple "no data collected" page).
+
+## Session and tab visibility check
+
+The extension does **not** currently know authoritative bproxy session state.
+
+What it has today:
+
+- Forwarded daemon requests include `session` and `target.tabId`, so the extension trace can record which sessions/tabs were involved in actions that actually reached the extension.
+- `chrome.storage.session` contains operational caches (`session:dedupe`, `session:injectedTabs`, `session:trace`, and `session:pins`), but these are not a session registry.
+- The action badge only shows connection state: disconnected, connecting, connected, or error.
+
+What it deliberately does not have today:
+
+- `session.create`, `session.list`, `session.bind`, `session.unbind`, `session.resume`, `session.close`, `tab.list`, `debug.last`, and `debug.status` are daemon-local and excluded from extension forwarding.
+- The daemon owns generated session ids, logical tab handles, tab ownership, pause state, nick scoping, and the session→Chrome-tab map.
+- The extension cannot safely reconstruct active sessions by enumerating Chrome tabs. That would leak operator-opened tabs and violate the daemon-owned logical-tab boundary.
+- The popup has no daemon bearer token and no nick; it only stores the extension bootstrap token used for the WebSocket.
+
+Conclusion: the popup can honestly show pairing/connection state, but it cannot currently show "active sessions" or "tabs per session" as an authoritative value.
+
+Decision: **discard the dashboard request**. Do not add session counts, tab counts, per-session lists, recent-activity panels, or an operator status surface to the extension popup. Keeping the extension simple preserves the daemon-owned session boundary and avoids creating an unscoped operator API surface that would conflict with [ADR-030](../decisions.md#adr-030-agent-nickname-session-scoping).
+
+If session visibility becomes necessary later, it must start with a separate ADR/design for a daemon-supplied operator summary. It is explicitly out of scope for this popup polish.
+
+## Implementation plan
+
+1. Update `extension/src/entrypoints/popup/index.html` styles and markup only; keep the existing TypeScript flow in `main.ts` thin.
+2. Import `VERSION` and `PROTOCOL_VERSION` in popup DOM code and render them into footer fields.
+3. Add external links using `target="_blank"` and `rel="noreferrer"`.
+4. Keep existing pairing validation/error handling in `pairing.ts` unchanged unless tests require DOM-selector updates.
+5. Do not add session/tab counts, recent activity, or dashboard UI; this request is intentionally discarded.
+6. Add/adjust popup tests to assert visible metadata and stable user-facing copy.
+7. Confirm `pnpm --filter @bproxy/extension test` and relevant typecheck pass.
+
+## Acceptance criteria
+
+- Popup clearly states what bproxy is before the user pairs.
+- Popup shows extension version and protocol version.
+- Popup links to documentation, license, and credits.
+- Popup identifies creator and MIT license in plain text.
+- Popup does not show active session counts, tab counts, recent activity, or dashboard-like status.
+- Pairing success/error behavior remains unchanged.
+- No strategy, selector repair, modal solving, fallback chains, or page interaction logic is added to the popup or extension.
+- Manifest/listing copy remains honest and does not imply bypassing anti-bot systems.
diff --git a/docs/public/index.md b/docs/public/index.md
index 02bef16..5e7f2c8 100644
--- a/docs/public/index.md
+++ b/docs/public/index.md
@@ -2,9 +2,13 @@
 title: bproxy
 ---
 
+<img src="./assets/bproxy-hero.png" alt="bproxy hero illustration: three robot agents on the left connect through a terminal and a shield to a stack of browser tabs on the right, all framed inside a computer monitor. Caption reads 'bproxy: paired browsing for humans and agents.'" width="900">
+
 ## Why this exists
 
-Most of my work is information research, analysis, and synthesis. Agents are good at the routine part — collecting data, transforming it, distilling patterns — but they need browser access to do it, and the services I use (Google, authenticated feed sites, Medium) actively detect automation.
+Most of my work is information research, analysis, and synthesis. Agents are good at the routine part — collecting data, transforming it, distilling patterns — but they need browser access to do it. Many services detect automation and use their terms of service to restrict it.
+
+I think "automation" is overloaded. At the extreme, I am already sitting at a laptop, using an operating system and a browser to access a service — is that not automation too? I am not trying to scrape service content at scale. I want to automate the copy-paste and routine navigation that are a natural part of desktop research.
 
 I have two options:
 
diff --git a/docs/public/privacy.md b/docs/public/privacy.md
new file mode 100644
index 0000000..eda6c3d
--- /dev/null
+++ b/docs/public/privacy.md
@@ -0,0 +1,28 @@
+---
+title: Privacy Policy
+---
+
+## bproxy Extension Privacy Policy
+
+The bproxy Chrome extension does not collect, store, or transmit any user data.
+
+**What the extension does:**
+- Reads page content only when an AI agent sends a command through the local daemon.
+- Passes page content to a daemon running on the same machine (`127.0.0.1`).
+- Nothing leaves your device. There is no remote server, no analytics, no telemetry.
+
+**What the extension stores:**
+- A pairing token in Chrome's local storage, used to authenticate the WebSocket connection to the local daemon.
+- Bounded session diagnostics (request trace, dedupe cache) in Chrome's session storage, cleared when the browser closes.
+
+**Network communication:**
+- The extension communicates exclusively with `localhost:9615` (`ws://127.0.0.1:9615/ws` and `http://127.0.0.1:9615/pair/claim`).
+- It never contacts any external service.
+
+**Permissions rationale:**
+- `tabs`: route actions to specific tabs and manage tab lifecycle.
+- `scripting`: programmatically inject the content script on first command.
+- `webNavigation`: track top-level navigation for page identity.
+- `alarms`: background service-worker keepalive scheduling.
+- `storage`: persist bootstrap token and session diagnostics.
+- `<all_urls>`: support user-directed actions on any page.
diff --git a/extension/package.json b/extension/package.json
index 6026ea7..99692d6 100644
--- a/extension/package.json
+++ b/extension/package.json
@@ -1,6 +1,6 @@
 {
 	"name": "@bproxy/extension",
-	"version": "0.9.0",
+	"version": "0.9.1",
 	"private": true,
 	"type": "module",
 	"scripts": {
diff --git a/extension/src/content/__tests__/reads.test.ts b/extension/src/content/__tests__/reads.test.ts
index d981551..95cf653 100644
--- a/extension/src/content/__tests__/reads.test.ts
+++ b/extension/src/content/__tests__/reads.test.ts
@@ -230,14 +230,17 @@ describe("read actions", () => {
 	});
 
 	it("links returns capped: true when page has more than MAX_COLLECTION_CAP links", () => {
-		// MAX_COLLECTION_CAP is 2000 — create 2001 links to trigger the cap
+		// MAX_COLLECTION_CAP is 2000 — create 2001 links to trigger the cap.
+		// Each element gets a unique id so createStableSelector resolves on the
+		// first candidate (#id), avoiding O(n²) path-selector probing in the
+		// fake querySelectorAll implementation.
 		const page = doc(
 			el("html", {
 				children: [
 					el("body", {
 						children: Array.from({ length: 2001 }, (_, i) =>
 							el("a", {
-								attrs: { href: `https://example.com/${i}` },
+								attrs: { id: `lk${i}`, href: `https://example.com/${i}` },
 								text: `L${i}`,
 							}),
 						),
diff --git a/extension/src/entrypoints/popup/__tests__/presentation.test.ts b/extension/src/entrypoints/popup/__tests__/presentation.test.ts
new file mode 100644
index 0000000..17b7f3d
--- /dev/null
+++ b/extension/src/entrypoints/popup/__tests__/presentation.test.ts
@@ -0,0 +1,90 @@
+import { readFileSync } from "node:fs";
+import { PROTOCOL_VERSION, VERSION } from "@bproxy/shared";
+import { describe, expect, it } from "vitest";
+import type { PairingBootstrap } from "../../../background/storage";
+import { formatVersionInfo, getConnectionStatusViewModel } from "../main";
+
+const html = readFileSync(new URL("../index.html", import.meta.url), "utf8");
+
+function expectLink(label: string, href: string): void {
+	const hrefPattern = href.replace(/[.*+?^${}()|[\]\\]/g, "\\$&");
+	expect(html).toMatch(
+		new RegExp(
+			`<a[^>]*href="${hrefPattern}"[^>]*target="_blank"[^>]*rel="noreferrer"[^>]*>${label}</a>`,
+		),
+	);
+}
+
+function bootstrap(overrides: Partial<PairingBootstrap> = {}): PairingBootstrap {
+	return {
+		extensionToken: "tok-123",
+		wsUrl: "ws://127.0.0.1:9615/ws",
+		protocolVersion: PROTOCOL_VERSION,
+		issuedAt: 100,
+		expiresAt: 10_000,
+		nonce: "nonce-1",
+		...overrides,
+	};
+}
+
+describe("popup presentation", () => {
+	it("renders title, subtitle, status line, and stable pairing controls", () => {
+		expect(html).toContain("<title>bproxy</title>");
+		expect(html).toContain("Human-in-the-loop browser bridge for AI agents.");
+		expect(html).toContain('id="connection-status"');
+		expect(html).toContain('id="pair-form"');
+		expect(html).toContain('id="code"');
+		expect(html).toContain('id="submit"');
+		expect(html).toContain("Pair extension");
+		expect(html).toContain('id="status"');
+		expect(html).toContain(
+			"Run <code>bproxy service start</code> and paste the one-time code shown by the daemon.",
+		);
+	});
+
+	it("renders footer metadata, links, and attribution", () => {
+		expect(html).toContain('id="version-info"');
+		expectLink("Documentation", "https://dimdasci.github.io/bproxy/");
+		expectLink("Privacy", "https://dimdasci.github.io/bproxy/privacy/");
+		expectLink("MIT", "https://github.com/dimdasci/bproxy/blob/main/LICENSE");
+		expect(html).toContain("Created by Dim Kharitonov");
+		expect(html).toContain('aria-label="bproxy on GitHub"');
+		expect(html).toContain('href="https://github.com/dimdasci/bproxy"');
+	});
+});
+
+describe("formatVersionInfo", () => {
+	it("renders shared version metadata", () => {
+		expect(formatVersionInfo()).toBe(`Extension ${VERSION} · Protocol ${PROTOCOL_VERSION}`);
+	});
+
+	it("falls back to empty values without throwing", () => {
+		expect(formatVersionInfo(null, null)).toBe("Extension · Protocol");
+	});
+});
+
+describe("getConnectionStatusViewModel", () => {
+	it("renders gray not-paired state when no bootstrap exists", () => {
+		expect(getConnectionStatusViewModel(null, 5_000)).toEqual({
+			text: "Not paired",
+			tone: "muted",
+			submitLabel: "Pair extension",
+		});
+	});
+
+	it("renders gray not-paired state when bootstrap is expired", () => {
+		expect(getConnectionStatusViewModel(bootstrap({ expiresAt: 4_000 }), 5_000)).toEqual({
+			text: "Not paired",
+			tone: "muted",
+			submitLabel: "Pair extension",
+		});
+	});
+
+	it("renders green paired state when bootstrap is present and fresh", () => {
+		expect(getConnectionStatusViewModel(bootstrap(), 5_000)).toEqual({
+			text: "Paired with local daemon",
+			tone: "ok",
+			submitLabel: "Re-pair with new code",
+		});
+	});
+});
diff --git a/extension/src/entrypoints/popup/index.html b/extension/src/entrypoints/popup/index.html
index a949075..a77f1bc 100644
--- a/extension/src/entrypoints/popup/index.html
+++ b/extension/src/entrypoints/popup/index.html
@@ -3,80 +3,230 @@
 	<head>
 		<meta charset="UTF-8" />
 		<meta name="viewport" content="width=device-width, initial-scale=1.0" />
-		<title>bproxy pairing</title>
+		<title>bproxy</title>
 		<script type="module" src="./main.ts"></script>
 		<style>
+			:root {
+				--c-text: #1a1a1a;
+				--c-muted: #555;
+				--c-ok: #167a30;
+				--c-error: #a4262c;
+				--c-bg: #fff;
+				--space-xs: 4px;
+				--space-sm: 8px;
+				--space-md: 12px;
+				--space-lg: 16px;
+			}
+
 			body {
-				font-family: system-ui, sans-serif;
+				box-sizing: border-box;
+				margin: 0;
+				width: 380px;
+				min-width: 340px;
+				max-width: 380px;
+				padding: calc(var(--space-lg) * 2);
+				background: var(--c-bg);
+				color: var(--c-text);
+				font-family: system-ui, -apple-system, sans-serif;
+				font-size: 13px;
+				line-height: 20px;
+			}
+
+			h1,
+			p {
 				margin: 0;
-				padding: 12px 16px;
-				min-width: 260px;
 			}
+
 			h1 {
-				font-size: 14px;
-				margin: 0 0 8px;
+				display: flex;
+				align-items: center;
+				gap: var(--space-sm);
+				font-size: 16px;
+				line-height: 24px;
+				font-weight: 600;
+			}
+
+			.subtitle,
+			.help,
+			footer {
+				color: var(--c-muted);
+			}
+
+			.subtitle {
+				margin-top: var(--space-xs);
 			}
+
+			.connection-status {
+				display: flex;
+				align-items: center;
+				gap: var(--space-sm);
+				margin-top: calc(var(--space-md) * 2);
+				color: var(--c-text);
+			}
+
+			.section {
+				margin-top: calc(var(--space-md) * 2);
+				padding-top: calc(var(--space-md) * 2);
+				border-top: 1px solid #ddd;
+			}
+
 			form {
 				display: flex;
 				flex-direction: column;
-				gap: 8px;
+				gap: var(--space-sm);
 			}
-			section {
-				margin-top: 12px;
-				padding-top: 12px;
-				border-top: 1px solid #e2e2e2;
+
+			label,
+			input,
+			button,
+			output,
+			code,
+			footer {
+				font: inherit;
+				line-height: 20px;
 			}
+
 			label {
-				font-size: 12px;
-				color: #555;
-			}
-			label.inline {
-				display: flex;
-				align-items: center;
-				gap: 8px;
-				color: #111;
+				color: var(--c-text);
 			}
+
 			input[type="text"] {
-				font: inherit;
-				padding: 6px 8px;
-				border: 1px solid #ccc;
+				padding: var(--space-sm);
+				border: 1px solid #ddd;
 				border-radius: 4px;
+				color: var(--c-text);
+				background: var(--c-bg);
 			}
+
 			button {
-				font: inherit;
-				padding: 6px 8px;
-				border: 1px solid #888;
+				padding: var(--space-sm);
+				border: 1px solid var(--c-muted);
 				border-radius: 4px;
-				background: #f4f4f4;
+				background: transparent;
+				color: var(--c-text);
 				cursor: pointer;
 			}
+
 			button:disabled {
 				opacity: 0.6;
 				cursor: progress;
 			}
+
+			.help {
+				margin-top: calc(var(--space-md) * 2);
+			}
+
+			code {
+				font-family: ui-monospace, SFMono-Regular, Menlo, Consolas, monospace;
+			}
+
 			#status {
-				font-size: 12px;
-				margin-top: 8px;
-				min-height: 1.2em;
+				display: block;
+				margin-top: var(--space-sm);
+				min-height: 20px;
+			}
+
+			#status:empty {
+				min-height: 0;
 			}
+
 			#status[data-state="success"] {
-				color: #167a30;
+				color: var(--c-ok);
 			}
+
 			#status[data-state="error"] {
-				color: #a4262c;
+				color: var(--c-error);
+			}
+
+			#status[data-state="pending"],
+			#status[data-state="idle"] {
+				color: var(--c-muted);
 			}
-			#status[data-state="pending"] {
-				color: #555;
+
+			footer p + p {
+				margin-top: var(--space-xs);
+			}
+
+			a {
+				color: inherit;
+				text-decoration: underline;
+			}
+
+			.credits {
+				display: flex;
+				align-items: center;
+				gap: var(--space-sm);
+			}
+
+			.github-link {
+				display: inline-flex;
+				align-items: center;
+				justify-content: center;
 			}
 		</style>
 	</head>
 	<body>
-		<h1>bproxy pairing</h1>
-		<form id="pair-form" autocomplete="off">
-			<label for="code">Pairing code</label>
-			<input id="code" name="code" type="text" inputmode="text" autocapitalize="characters" spellcheck="false" required />
-			<button id="submit" type="submit">Pair</button>
-		</form>
-		<output id="status" data-state="idle" aria-live="polite"></output>
+		<header>
+			<h1>
+				<svg
+					aria-hidden="true"
+					xmlns="http://www.w3.org/2000/svg"
+					width="20"
+					height="20"
+					viewBox="0 0 24 24"
+					fill="none"
+					stroke="currentColor"
+					stroke-width="2"
+					stroke-linecap="round"
+					stroke-linejoin="round"
+				>
+					<path d="M17 19a1 1 0 0 1-1-1v-2a2 2 0 0 1 2-2h2a2 2 0 0 1 2 2v2a1 1 0 0 1-1 1z" />
+					<path d="M17 21v-2" />
+					<path d="M19 14V6.5a1 1 0 0 0-7 0v11a1 1 0 0 1-7 0V10" />
+					<path d="M21 21v-2" />
+					<path d="M3 5V3" />
+					<path d="M4 10a2 2 0 0 1-2-2V6a1 1 0 0 1 1-1h4a1 1 0 0 1 1 1v2a2 2 0 0 1-2 2z" />
+					<path d="M7 5V3" />
+				</svg>
+				<span>bproxy</span>
+			</h1>
+			<p class="subtitle">Human-in-the-loop browser bridge for AI agents.</p>
+			<p id="connection-status" class="connection-status"></p>
+		</header>
+
+		<section class="section">
+			<form id="pair-form" autocomplete="off">
+				<label for="code">Pairing code</label>
+				<input id="code" name="code" type="text" inputmode="text" autocapitalize="characters" spellcheck="false" required />
+				<button id="submit" type="submit">Pair extension</button>
+			</form>
+			<p class="help">Run <code>bproxy service start</code> and paste the one-time code shown by the daemon.</p>
+			<output id="status" data-state="idle" aria-live="polite"></output>
+		</section>
+
+		<footer class="section">
+			<p id="version-info"></p>
+			<p>
+				<a href="https://dimdasci.github.io/bproxy/" target="_blank" rel="noreferrer">Documentation</a>
+				·
+				<a href="https://dimdasci.github.io/bproxy/privacy/" target="_blank" rel="noreferrer">Privacy</a>
+				·
+				<a href="https://github.com/dimdasci/bproxy/blob/main/LICENSE" target="_blank" rel="noreferrer">MIT</a>
+			</p>
+			<p class="credits">
+				<span>Created by Dim Kharitonov</span>
+				<a
+					class="github-link"
+					href="https://github.com/dimdasci/bproxy"
+					target="_blank"
+					rel="noreferrer"
+					aria-label="bproxy on GitHub"
+				>
+					<svg aria-hidden="true" xmlns="http://www.w3.org/2000/svg" width="16" height="16" viewBox="0 0 24 24" fill="currentColor">
+						<path d="M12 .297a12 12 0 0 0-3.797 23.387c.6.111.82-.261.82-.577v-2.234c-3.338.726-4.042-1.609-4.042-1.609-.546-1.387-1.333-1.757-1.333-1.757-1.089-.745.083-.73.083-.73 1.205.084 1.839 1.237 1.839 1.237 1.07 1.833 2.807 1.303 3.492.996.108-.775.419-1.304.762-1.604-2.665-.303-5.466-1.332-5.466-5.931 0-1.311.469-2.382 1.236-3.221-.124-.303-.535-1.524.117-3.176 0 0 1.008-.322 3.301 1.23a11.5 11.5 0 0 1 6.008 0c2.291-1.552 3.297-1.23 3.297-1.23.654 1.652.243 2.873.119 3.176.77.839 1.234 1.91 1.234 3.221 0 4.61-2.805 5.625-5.479 5.921.431.371.815 1.102.815 2.222v3.293c0 .319.216.694.825.576A12.003 12.003 0 0 0 12 .297" />
+					</svg>
+				</a>
+			</p>
+		</footer>
 	</body>
 </html>
diff --git a/extension/src/entrypoints/popup/main.ts b/extension/src/entrypoints/popup/main.ts
index 25df41a..14dcde1 100644
--- a/extension/src/entrypoints/popup/main.ts
+++ b/extension/src/entrypoints/popup/main.ts
@@ -1,4 +1,5 @@
-import { bootstrapItem } from "../../background/storage";
+import { PROTOCOL_VERSION, VERSION } from "@bproxy/shared";
+import { bootstrapItem, type PairingBootstrap } from "../../background/storage";
 import { type PairingErrorCode, type PairingResult, runPairing } from "./pairing";
 
 // Thin DOM wiring for the popup. Real flow logic lives in small helpers:
@@ -23,6 +24,17 @@ const STATUS_FRIENDLY: Record<PairingErrorCode, string> = {
 	PAIR_NOTIFY_FAILED: "Paired, but failed to wake the background worker. Try reopening the popup.",
 };
 
+export interface ConnectionStatusViewModel {
+	text: string;
+	tone: "muted" | "ok";
+	submitLabel: string;
+}
+
+interface PopupInitDeps {
+	storage: { getValue(): Promise<PairingBootstrap | null> };
+	now: () => number;
+}
+
 function $<T extends HTMLElement>(id: string): T {
 	const el = document.getElementById(id);
 	if (!el) throw new Error(`#${id} not found in popup DOM`);
@@ -30,14 +42,84 @@ function $<T extends HTMLElement>(id: string): T {
 }
 
 function setStatus(state: "idle" | "pending" | "success" | "error", text: string): void {
-	const status = $<HTMLDivElement>("status");
+	const status = $<HTMLOutputElement>("status");
 	status.dataset["state"] = state;
 	status.textContent = text;
 }
 
+export function formatVersionInfo(
+	version: unknown = VERSION,
+	protocolVersion: unknown = PROTOCOL_VERSION,
+): string {
+	const versionText = typeof version === "string" ? version : "";
+	const protocolText =
+		typeof protocolVersion === "number" || typeof protocolVersion === "string"
+			? String(protocolVersion)
+			: "";
+	const extensionPart = `Extension ${versionText}`.trimEnd();
+	const protocolPart = `Protocol ${protocolText}`.trimEnd();
+	return `${extensionPart} · ${protocolPart}`;
+}
+
+export function getConnectionStatusViewModel(
+	bootstrap: PairingBootstrap | null,
+	now: number,
+): ConnectionStatusViewModel {
+	if (
+		bootstrap &&
+		typeof bootstrap.extensionToken === "string" &&
+		bootstrap.extensionToken.length > 0 &&
+		typeof bootstrap.expiresAt === "number" &&
+		bootstrap.expiresAt > now
+	) {
+		return {
+			text: "Paired with local daemon",
+			tone: "ok",
+			submitLabel: "Re-pair with new code",
+		};
+	}
+	return {
+		text: "Not paired",
+		tone: "muted",
+		submitLabel: "Pair extension",
+	};
+}
+
+function renderVersionInfo(text: string): void {
+	$<HTMLSpanElement>("version-info").textContent = text;
+}
+
+function createStatusDot(tone: ConnectionStatusViewModel["tone"]): SVGSVGElement {
+	const svg = document.createElementNS("http://www.w3.org/2000/svg", "svg");
+	svg.setAttribute("aria-hidden", "true");
+	svg.setAttribute("width", "8");
+	svg.setAttribute("height", "8");
+	svg.setAttribute("viewBox", "0 0 8 8");
+
+	const circle = document.createElementNS("http://www.w3.org/2000/svg", "circle");
+	circle.setAttribute("cx", "4");
+	circle.setAttribute("cy", "4");
+	circle.setAttribute("r", "4");
+	circle.setAttribute("fill", tone === "ok" ? "var(--c-ok)" : "var(--c-muted)");
+	svg.append(circle);
+
+	return svg;
+}
+
+function renderConnectionStatus(model: ConnectionStatusViewModel): void {
+	const status = $<HTMLParagraphElement>("connection-status");
+	status.replaceChildren(createStatusDot(model.tone), document.createTextNode(model.text));
+	$<HTMLButtonElement>("submit").textContent = model.submitLabel;
+}
+
 function renderResult(result: PairingResult): void {
 	if (result.ok) {
-		setStatus("success", "Paired. You can close this popup.");
+		renderConnectionStatus({
+			text: "Paired with local daemon",
+			tone: "ok",
+			submitLabel: "Re-pair with new code",
+		});
+		setStatus("success", "Paired with local daemon. You can close this popup.");
 		return;
 	}
 	const friendly = STATUS_FRIENDLY[result.code];
@@ -75,9 +157,23 @@ async function onSubmit(ev: SubmitEvent): Promise<void> {
 	}
 }
 
-document.addEventListener("DOMContentLoaded", () => {
-	$<HTMLFormElement>("pair-form").addEventListener("submit", (ev) => {
-		void onSubmit(ev);
+export async function initializePopup(
+	deps: PopupInitDeps = {
+		storage: bootstrapItem,
+		now: () => Date.now(),
+	},
+): Promise<void> {
+	renderVersionInfo(formatVersionInfo());
+	const bootstrap = await deps.storage.getValue().catch(() => null);
+	renderConnectionStatus(getConnectionStatusViewModel(bootstrap, deps.now()));
+	setStatus("idle", "");
+}
+
+if (typeof document !== "undefined") {
+	document.addEventListener("DOMContentLoaded", () => {
+		$<HTMLFormElement>("pair-form").addEventListener("submit", (ev) => {
+			void onSubmit(ev);
+		});
+		void initializePopup();
 	});
-	setStatus("idle", "Enter the one-time code issued by the daemon.");
-});
+}
diff --git a/extension/wxt.config.ts b/extension/wxt.config.ts
index 91b7f9b..6e797c2 100644
--- a/extension/wxt.config.ts
+++ b/extension/wxt.config.ts
@@ -24,7 +24,8 @@ export default defineConfig({
 	}),
 	manifest: {
 		name: "bproxy",
-		description: "Browser proxy companion extension for bproxy daemon.",
+		description:
+			"Companion extension for bproxy. Connects Chrome to a local bproxy daemon for explicit human-in-the-loop browser actions.",
 		permissions: ["tabs", "scripting", "webNavigation", "alarms", "storage"],
 		host_permissions: ["<all_urls>"],
 		action: {
diff --git a/package.json b/package.json
index 21debc4..5db23f6 100644
--- a/package.json
+++ b/package.json
@@ -2,8 +2,8 @@
 	"name": "bproxy",
 	"private": true,
 	"type": "module",
-	"version": "0.9.0",
-	"description": "Browser proxy for code agents.",
+	"version": "0.9.1",
+	"description": "Human-in-the-loop browser proxy for AI agents.",
 	"license": "MIT",
 	"packageManager": "pnpm@9.15.0",
 	"scripts": {
diff --git a/scripts/release-package.json b/scripts/release-package.json
index 3d2c56e..44a1b1f 100644
--- a/scripts/release-package.json
+++ b/scripts/release-package.json
@@ -1,7 +1,7 @@
 {
 	"name": "@dimdasci/bproxy",
 	"version": "VERSION_PLACEHOLDER",
-	"description": "Browser proxy for code agents — control your real Chrome from CLI.",
+	"description": "Human-in-the-loop browser proxy for AI agents — use your real Chrome session via a localhost daemon and extension.",
 	"license": "MIT",
 	"homepage": "https://dimdasci.github.io/bproxy/",
 	"bugs": {
diff --git a/service/package.json b/service/package.json
index 0fa3973..6bc1fc1 100644
--- a/service/package.json
+++ b/service/package.json
@@ -1,6 +1,6 @@
 {
 	"name": "@bproxy/service",
-	"version": "0.9.0",
+	"version": "0.9.1",
 	"private": true,
 	"type": "module",
 	"bin": {
diff --git a/shared/package.json b/shared/package.json
index ffbfb63..8a68743 100644
--- a/shared/package.json
+++ b/shared/package.json
@@ -1,6 +1,6 @@
 {
 	"name": "@bproxy/shared",
-	"version": "0.9.0",
+	"version": "0.9.1",
 	"private": true,
 	"type": "module",
 	"exports": {
diff --git a/shared/src/version.ts b/shared/src/version.ts
index 73029a6..4eaa82c 100644
--- a/shared/src/version.ts
+++ b/shared/src/version.ts
@@ -6,7 +6,7 @@
  */
 
 /** Current bproxy package version (semver). */
-export const VERSION = "0.9.0";
+export const VERSION = "0.9.1";
 
 /** Protocol version for the daemon↔CLI↔extension wire format. */
 export const PROTOCOL_VERSION = 2;
diff --git a/skills/bproxy/SKILL.md b/skills/bproxy/SKILL.md
index 426180c..4b91477 100644
--- a/skills/bproxy/SKILL.md
+++ b/skills/bproxy/SKILL.md
@@ -9,7 +9,7 @@ description: >-
 compatibility: Node >=24, bproxy installed (npm install -g @dimdasci/bproxy), daemon running, extension paired
 license: MIT
 metadata:
-  version: "0.9.0"
+  version: "0.9.1"
 ---
 
 # bproxy
diff --git a/views/astro.config.mjs b/views/astro.config.mjs
index ca5fc53..282fdc7 100644
--- a/views/astro.config.mjs
+++ b/views/astro.config.mjs
@@ -144,6 +144,7 @@ export default defineConfig({
 				},
 			],
 			components: {
+				Footer: "./src/components/Footer.astro",
 				PageFrame: "./src/components/PageFrame.astro",
 			},
 			customCss: ["./src/styles/custom.css"],
diff --git a/views/package.json b/views/package.json
index 4a323eb..55815f6 100644
--- a/views/package.json
+++ b/views/package.json
@@ -1,7 +1,7 @@
 {
 	"name": "@bproxy/views",
 	"private": true,
-	"version": "0.9.0",
+	"version": "0.9.1",
 	"type": "module",
 	"scripts": {
 		"dev": "astro dev",
diff --git a/views/public/assets/bproxy-hero.png b/views/public/assets/bproxy-hero.png
new file mode 120000
index 0000000..e2e8968
--- /dev/null
+++ b/views/public/assets/bproxy-hero.png
@@ -0,0 +1 @@
+../../../assets/bproxy-hero.png
\ No newline at end of file
diff --git a/views/src/components/Footer.astro b/views/src/components/Footer.astro
new file mode 100644
index 0000000..d86919e
--- /dev/null
+++ b/views/src/components/Footer.astro
@@ -0,0 +1,33 @@
+---
+import DefaultFooter from "@astrojs/starlight/components/Footer.astro";
+import pkg from "../../package.json";
+
+const version = pkg.version;
+---
+
+<DefaultFooter />
+
+<p class="bproxy-site-meta">
+	bproxy v{version} ·
+	<a href="https://github.com/dimdasci/bproxy/blob/main/LICENSE" target="_blank" rel="noopener noreferrer">
+		MIT License
+	</a>
+	· © Dim Kharitonov
+</p>
+
+<style>
+	.bproxy-site-meta {
+		margin: 0 auto 1.5rem;
+		font-size: var(--sl-text-xs);
+		color: var(--sl-color-gray-3);
+		text-align: center;
+	}
+
+	.bproxy-site-meta a {
+		color: inherit;
+	}
+
+	.bproxy-site-meta a:hover {
+		color: var(--sl-color-white);
+	}
+</style>