docs: add interactive GitHub Pages landing site

.github/workflows/pages.yml

@@ -0,0 +1,37 @@
+name: Deploy GitHub Pages
+
+on:
+  push:
+    branches: [main]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: pages
+  cancel-in-progress: true
+
+jobs:
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v5
+
+      - name: Setup Pages
+        uses: actions/configure-pages@v5
+
+      - name: Upload site
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: docs
+
+      - name: Deploy
+        id: deployment
+        uses: actions/deploy-pages@v4

AGENTS.md

@@ -32,6 +32,7 @@ macOS Tahoe 26-only Swift Package (SPM executable → SwiftUI app) that imports
 
 - Version/build is in **AppVersion.swift** (single source; `Scripts/build-app.sh` parses it for Info.plist — update **both** `shortVersion` and `buildNumber` or the script exits 1).
 - Release order matters: in one commit, bump AppVersion.swift **and** add the `## <version>` section to CHANGELOG.md, push it, then push tag `v<version>` pointing at that commit. release.yml's changelog extraction exits 1 if the section is missing, and the Info.plist version comes from AppVersion.swift — tagging a commit without either publishes the wrong version or fails the run (a moved tag is the only recovery). Release zips `dist/AerialDrop.app` as `AerialDrop-<version>-macOS.zip`.
+- The Pages site hardcodes the current version as a no-JS/offline fallback: bump `v1.1.3` in `docs/index.html` (hero terminal output, `#expectVersion`, unzip commands, release chip) and the `applyRelease("v1.1.3", …)` fallback in `docs/app.js` in the same commit as AppVersion.swift, or visitors whose release fetch fails see a stale version. `Assets/icon.svg` and `docs/assets/icon.svg` must stay byte-identical, and `docs/assets/icon.png` must be regenerated from it when the art changes.
 
 <!-- code-review-graph MCP tools -->
 ## MCP Tools: code-review-graph

README.md

@@ -1,6 +1,7 @@
 # AerialDrop
 
 [![CI](https://github.com/YapWH1208/AerialDrop/actions/workflows/ci.yml/badge.svg)](https://github.com/YapWH1208/AerialDrop/actions/workflows/ci.yml)
+[![Website](https://img.shields.io/badge/website-yapwh1208.github.io%2FAerialDrop-0a84ff)](https://yapwh1208.github.io/AerialDrop/)
 
 AerialDrop imports your own videos into macOS Tahoe's native Aerial (wallpaper) catalogue, so custom videos play as screen savers and lock screen wallpapers using Apple's own playback pipeline — no helper processes, no app-managed player.
 
@@ -93,6 +94,7 @@ Every manifest write is backed up automatically first: backups live under `aeria
 
 ## Documentation
 
+- [Website](https://yapwh1208.github.io/AerialDrop/) — interactive landing page (source: `docs/`, published to GitHub Pages)
 - [ARCHITECTURE.md](ARCHITECTURE.md) — processing pipeline
 - [TESTING.md](TESTING.md) — manual test procedure
 - [CHANGELOG.md](CHANGELOG.md) — release history