docs+site: Nightjar brand, hosted service, infrastructure plan, saved site

Persists the branding/commercial/infrastructure work (previously only in chat and
on the live site) into version control.

What changed:
- docs/naming.md: due-diligence and the decision to brand the product Nightjar
  (OpenScribe domain/GitHub/trademark collisions; alternatives screened; why Nightjar).
- docs/hosted-service.md: the commercial model - plan tiers (Self-host / Cloud
  Starter / Cloud Pro / Private), indicative pricing, backend mapping, and the
  build-to-sell roadmap (metering, billing, provisioning, DPA).
- docs/infrastructure.md: backend infra plan. Primary option = self-host on the
  3x Minisforum MS-02 cluster (one with an RTX 3050 6GB) fronted by a Cloudflare
  Tunnel, with node roles, the 3050 capacity reality, caveats, and a Hetzner cloud
  fallback. Provision-later.
- site/: reproducible marketing-site source - block content for all 11 pages
  (rebranded to Nightjar), the navigation, the Contact Form 7 config (honeypot),
  the ApisCP SOAP helper (tools/apiscp.php, no secret), and a README on how the
  WordPress site is built and managed via the API.
- state/: DECISIONS (Nightjar rebrand, hosted service, MS-02 backend), PROJECT
  (brand + commercial section), TODO (rename decision, trademark, mailbox, pricing,
  hosted-service build, infra provisioning).

Why:
- User asked to save everything to the repo. Captures the product rebrand, the
  commercialisation plan, and the infrastructure decision so a cold session has the
  full picture.

Notes:
- The repo is still named `openscribe`; the product/brand is Nightjar. A full
  codebase rename is deferred (tracked in TODO + docs/naming.md).
- No secrets committed: the ApisCP API key is read from a local scratch file, never
  the repo.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

docs/hosted-service.md

@@ -0,0 +1,43 @@
+<!-- SPDX-License-Identifier: CC-BY-SA-4.0 -->
+# Nightjar hosted service (commercial)
+
+How 12 Hobbies Studio commercialises the open-source project: a managed backend so people
+can use Nightjar without self-hosting. The device and app stay open; the studio runs the
+transcription, summaries, storage and API.
+
+Status: **marketing site live, service in preparation.** No billing/signup yet; the site
+captures leads (register interest). Pricing below is **indicative**.
+
+## Plan lineup (live on the site)
+
+| Plan | Price (indicative) | AI backend | Notes |
+|------|--------------------|-----------|-------|
+| **Self-host** | Free, forever | your own | full source + docs, community support |
+| **Cloud Starter** | from GBP 6/mo | commercial API | 10 hrs audio/mo, 10 GB, email support |
+| **Cloud Pro** | from GBP 18/mo | commercial API | 40 hrs/mo, priority, 100 GB, team sharing |
+| **Private** | from GBP 39/mo | self-hosted open models | audio never touches a 3rd-party AI; DPA |
+
+The Cloud tiers use best-in-class commercial AI (cheap per-minute, good margin). The
+Private tier processes everything on our own hardware (see `docs/infrastructure.md`) for a
+privacy / sovereignty guarantee. All hosted data kept in the EU/UK.
+
+## Placeholders to confirm before launch
+
+- **Contact mailbox:** the site's forms/CTAs use `hello@12hobbies.studio` - create that
+  mailbox or change it.
+- **Real pricing + quotas:** the numbers above are indicative.
+- **Trademark clearance** for "Nightjar" (see `docs/naming.md`).
+
+## Roadmap to actually sell it (not built yet)
+
+- Metering (hours of audio, storage) per account.
+- Signup + billing (e.g. Stripe) wired to plan entitlements.
+- Provisioning: create a tenant, route jobs to the right backend (commercial vs Private
+  node), enforce quotas.
+- Provision the backend infra (`docs/infrastructure.md`) at first beta / paying users.
+- Data-processing agreement + retention policy for the Private tier.
+
+## Marketing site
+
+Built in WordPress on ApisCP (`howler.qsplace.co.uk`), served at
+`nightjar.12hobbies.studio`. Reproducible content and build notes are in `site/`.