docs: update paths and version references for v1.2.0 monorepo structure

- Fix stale src/wolfwave/ paths → apps/native/wolfwave/ across getting-started and development guides
- Update example release tag from v1.0.0 → v1.2.0
- Fix landing page proof bar: macOS 14+ → macOS 26+

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

Author: nathanialhenniges

apps/docs/app/(home)/page.tsx

@@ -198,7 +198,7 @@ export default function HomePage() {
       {/* Proof bar */}
       <div className="border-y px-6 py-4" style={{ borderColor: "rgba(255,255,255,0.06)", backgroundColor: "rgba(255,255,255,0.02)" }}>
         <div className="mx-auto max-w-5xl flex flex-wrap items-center justify-center gap-3">
-          {["Free Forever", "macOS 14+", "No Account Needed", "~10MB", "Open Source"].map((pill) => (
+          {["Free Forever", "macOS 26+", "No Account Needed", "~10MB", "Open Source"].map((pill) => (
             <span
               key={pill}
               className="text-xs font-medium px-3 py-1 rounded-full"

apps/docs/content/docs/development.mdx

@@ -16,7 +16,7 @@ This guide covers everything you need to contribute to WolfWave.
 ## Setup
 
 1. Fork and clone the repository
-2. Copy `src/wolfwave/Config.xcconfig.example` to `src/wolfwave/Config.xcconfig`
+2. Copy `apps/native/wolfwave/Config.xcconfig.example` to `apps/native/wolfwave/Config.xcconfig`
 3. Set your Twitch Client ID and Discord Client ID in `Config.xcconfig`
 4. Open the project: `make open-xcode`
 5. Resolve dependencies: `make update-deps`
@@ -166,7 +166,7 @@ Or press **Cmd+U** in Xcode. The test target (`WolfWaveTests`) is a hosted unit
 
 ### Adding New Tests
 
-Test files are auto-discovered — just add `.swift` files to `src/WolfWaveTests/`. Use `@testable import WolfWave` to access internal types.
+Test files are auto-discovered — just add `.swift` files to `apps/native/WolfWaveTests/`. Use `@testable import WolfWave` to access internal types.
 
 ## CI/CD
 
@@ -192,8 +192,8 @@ Code signing, notarization, and DMG creation all happen in the release workflow.
 ### Triggering a Release
 
 ```bash
-git tag v1.0.0
-git push origin v1.0.0
+git tag v1.2.0
+git push origin v1.2.0
 ```
 
 This triggers the release workflow, which builds, signs, notarizes, and uploads the DMG to a draft GitHub Release. Once the workflow completes, review the draft and publish it.

apps/docs/content/docs/getting-started.mdx

@@ -25,10 +25,10 @@ cd WolfWave
 Copy the example configuration file:
 
 ```bash
-cp src/wolfwave/Config.xcconfig.example src/wolfwave/Config.xcconfig
+cp apps/native/wolfwave/Config.xcconfig.example apps/native/wolfwave/Config.xcconfig
 ```
 
-Open `src/wolfwave/Config.xcconfig` and set your keys:
+Open `apps/native/wolfwave/Config.xcconfig` and set your keys:
 
 ```
 TWITCH_CLIENT_ID = your_twitch_client_id_here
@@ -51,7 +51,7 @@ DISCORD_CLIENT_ID = your_discord_client_id_here
 ```bash
 make open-xcode
 # or
-open src/wolfwave.xcodeproj
+open apps/native/wolfwave.xcodeproj
 ```
 
 ## Build and Run
@@ -96,8 +96,8 @@ make notarize
 Pushing a version tag triggers the GitHub Actions release workflow, which creates a draft GitHub Release:
 
 ```bash
-git tag v1.0.0
-git push origin v1.0.0
+git tag v1.2.0
+git push origin v1.2.0
 ```
 
 After the workflow completes, build and notarize locally with `make prod-build && make notarize`, upload the DMG to the draft release, and publish it. Required secrets (`TWITCH_CLIENT_ID`, `DISCORD_CLIENT_ID`) must be configured in your repository's Actions secrets. See the [Development Guide](/docs/development) and [PUBLISH.md](https://github.com/MrDemonWolf/WolfWave/blob/main/PUBLISH.md) for the full release checklist.