docs: rebuild the technical documentation as architecture reference, not project history

.github/workflows/build.yml

@@ -46,7 +46,7 @@ jobs:
 
       # ponytail: STT is handled by the bundled whisper-stt-server (whisper.cpp
       # with native DTW token timestamps). No separate VAD model is fetched
-      # here. See docs/engineering/stt-spec.md for the full architecture.
+      # here. See technical-documentation/architecture/transcription-and-captions.md for the full architecture.
 
       - name: Build Windows app
         run: npm run build:win -- --publish never
@@ -77,7 +77,7 @@ jobs:
 
       # ponytail: STT is handled by the bundled whisper-stt-server (whisper.cpp
       # with native DTW token timestamps). No separate VAD model is fetched
-      # here. See docs/engineering/stt-spec.md for the full architecture.
+      # here. See technical-documentation/architecture/transcription-and-captions.md for the full architecture.
 
       - name: Build Windows Store package
         run: npm run build:win:store -- --publish never

.github/workflows/ci.yml

@@ -1,10 +1,13 @@
 name: CI
 
+# feat/ai-edition is a long-lived integration branch that PRs land on for
+# months at a time. Without it listed here, every one of those PRs merged with
+# no lint, no typecheck, no tests and no PR-title check.
 on:
   pull_request:
-    branches: [main]
+    branches: [main, feat/ai-edition]
   push:
-    branches: [main]
+    branches: [main, feat/ai-edition]
 
 jobs:
   lint:
@@ -23,6 +26,19 @@ jobs:
       - uses: ./.github/actions/setup
       - run: npx tsc --noEmit
 
+  docs:
+    name: Docs
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      # No ./.github/actions/setup: check-docs.mjs imports only node builtins,
+      # so npm ci would be a minute of install for nothing. Node 22 is here for
+      # import.meta.dirname (needs >= 20.11).
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 22
+      - run: npm run docs:check
+
   test:
     name: Test
     runs-on: ubuntu-latest

.gitignore

@@ -84,7 +84,7 @@ result-*
 
 # whisper.cpp DTW POC (tools/stt-eval/whispercpp-dtw-poc) — vendored engine
 # clone, downloaded GGML models, and generated build/results artifacts.
-# See docs/engineering/stt-whispercpp-dtw-poc-plan.md.
+# See technical-documentation/architecture/transcription-and-captions.md.
 /tools/stt-eval/whispercpp-dtw-poc/whisper.cpp/
 /tools/stt-eval/whispercpp-dtw-poc/build-cpu/
 /tools/stt-eval/whispercpp-dtw-poc/build-vulkan/

.harness/docs/architecture-overview.md

@@ -1,6 +1,6 @@
 # OpenScreen Architecture Notes
 
-Quick map of how the app fits together, for the Mavis reins. For deeper details, see `../docs/architecture/native-bridge.md` and `../docs/engineering/`.
+Quick map of how the app fits together, for the Mavis reins. For deeper details, see `../technical-documentation/architecture/native-bridge.md` and `../technical-documentation/engineering/`.
 
 ## Process layout
 

.harness/docs/git-workflow.md

@@ -41,7 +41,7 @@ All five must be green before merge. Native helper code is NOT covered by CI —
 
 ## Release flow
 
-Two `workflow_dispatch` workflows cut a release. Trunk-based on `main`, but **release branches freeze the RC codebase between cut and promote** (see § Release branches below). Both require the `OPENSCREEN_RELEASE_TOKEN` secret — see `docs/secrets.md`.
+Two `workflow_dispatch` workflows cut a release. Trunk-based on `main`, but **release branches freeze the RC codebase between cut and promote** (see § Release branches below). Both require the `OPENSCREEN_RELEASE_TOKEN` secret — see `technical-documentation/engineering/release-and-secrets.md`.
 
 ### Step 1: cut a release candidate
 

.harness/reins/openscreen-dev/agent.md

@@ -15,7 +15,7 @@ You are the generalist implementer for the OpenScreen project — a free, open-s
 ## How you work
 
 - Read `AGENTS.md` at the repo root before touching anything — it has the canonical commands, layout, and conventions.
-- When the change touches recording, IPC, or the native bridge, read `.harness/docs/architecture-overview.md` (start here), `docs/architecture/native-bridge.md` (deeper dive), and `docs/engineering/` (native helper roadmaps).
+- When the change touches recording, IPC, or the native bridge, read `.harness/docs/architecture-overview.md` (start here), `technical-documentation/architecture/native-bridge.md` (deeper dive), and `technical-documentation/engineering/` (native helper roadmaps).
 - TypeScript strict mode, Biome format (tabs, double quotes, 100-col). Run `npm run lint:fix` before committing.
 - For renderer-only iteration use `npm run build-vite`. For full packaging use `npm run build` (electron-builder, slow).
 - Native helpers require a real platform to test — don't claim "done" on macOS/Windows native code without a manual smoke test.

.harness/reins/openscreen-tester/agent.md

@@ -15,7 +15,7 @@ You are the test specialist for the OpenScreen project — a free, open-source s
 ## How you work
 
 - Read `AGENTS.md` at the repo root for commands and conventions.
-- Read `docs/tests/writing-tests.md` for the project's test style guide.
+- Read `technical-documentation/testing/writing-tests.md` for the project's test style guide.
 - Match the style of neighboring `*.test.<ext>` files in the same package — don't invent new patterns.
 - Unit tests: `npm run test` (Vitest, jsdom). Browser tests: `npm run test:browser` (needs `npm run test:browser:install` once). E2E: `npm run test:e2e` (Playwright).
 - E2E specs in `tests/e2e/windows-native-checklist.spec.ts` are Windows-only — gate with `test.skip` for other platforms rather than deleting.