Add sticky OS tabs across docs and courses (#14)

Standardize all OS-specific tab groups to use consistent
"macOS", "Linux", "Windows" labels so content.tabs.link
syncs selections across the site and persists via localStorage.
 Closes #13

Author: neuromechanist

.gitignore

@@ -34,12 +34,5 @@ node_modules/
 # Wrangler
 .wrangler/
 
-# Claude Code
-CLAUDE.md
-
-# Planning files
-plan.md
-ideas.md
+# Planning files (scratch only)
 scratch_notes.md
-research.md
-.context/

CLAUDE.md

@@ -0,0 +1,40 @@
+# OSC Documentation
+
+Documentation site for the Open Science Collective (OSC), built with MkDocs Material.
+
+## Two Documentation Sources
+
+This repo serves two independent MkDocs sites from two config files, each deploying to its own subdomain:
+
+| Config | docs_dir | Subdomain | Content |
+|--------|----------|-----------|---------|
+| `mkdocs.yml` | `docs/` | docs.osc.earth | OSC and OSA documentation |
+| `mkdocs-courses.yml` | `courses/` | courses.osc.earth | Course materials |
+
+Both share the `overrides/` directory for theme customizations.
+
+## Build and Serve
+
+```bash
+# Main docs
+uv run mkdocs serve                          # dev server (docs.osc.earth)
+uv run mkdocs build                          # build to site/
+
+# Courses
+uv run mkdocs serve -f mkdocs-courses.yml    # dev server (courses.osc.earth)
+uv run mkdocs build -f mkdocs-courses.yml    # build to site-courses/
+```
+
+## OS-Specific Tabs
+
+Both sites use `content.tabs.link` (Material for MkDocs), which syncs tab selections across the page and persists the choice in localStorage. For this to work, all OS tab groups must use exactly these labels:
+
+- `=== "macOS"`
+- `=== "Linux"`
+- `=== "Windows"`
+
+Never use combined labels like "macOS / Linux" or qualified labels like "macOS: Homebrew"; they break cross-group syncing.
+
+## Submodules
+
+- `osa/` -- the [OSA application repo](https://github.com/OpenScience-Collective/osa) (git submodule). Not part of the docs build; used for API reference generation when enabled.

courses/agentic-research/week-01.md

@@ -77,7 +77,9 @@ ls -la # List with details
 
 Package managers let you install software from the command line. Think of them as an app store for developer tools.
 
-=== "macOS: Homebrew"
+=== "macOS"
+
+    Install [Homebrew](https://brew.sh), the standard macOS package manager:
 
     ```bash
     /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
@@ -89,14 +91,22 @@ Package managers let you install software from the command line. Think of them a
     brew --version
     ```
 
-=== "Linux (Debian/Ubuntu) or WSL"
+=== "Linux"
 
     You already have `apt`. Update it:
 
     ```bash
     sudo apt update
     ```
 
+=== "Windows"
+
+    Your WSL Ubuntu terminal already has `apt` (see Step 1). Update it:
+
+    ```bash
+    sudo apt update
+    ```
+
 ### 3. Install Git and the GitHub CLI
 
 You need two command-line tools: `git` for version control and `gh` (the GitHub CLI) for interacting with GitHub.
@@ -107,7 +117,15 @@ You need two command-line tools: `git` for version control and `gh` (the GitHub
     brew install git gh
     ```
 
-=== "Linux or WSL"
+=== "Linux"
+
+    ```bash
+    sudo apt install git gh
+    ```
+
+=== "Windows"
+
+    In your WSL Ubuntu terminal:
 
     ```bash
     sudo apt install git gh
@@ -241,6 +259,21 @@ ssh-add ~/.ssh/id_ed25519
     # Select and copy the output manually
     ```
 
+=== "Windows"
+
+    In your WSL Ubuntu terminal:
+
+    ```bash
+    cat ~/.ssh/id_ed25519.pub
+    # Select and copy the output manually
+    ```
+
+    Or in PowerShell:
+
+    ```powershell
+    Get-Content ~\.ssh\id_ed25519.pub | Set-Clipboard
+    ```
+
 Then add it to GitHub:
 
 1. Go to [github.com/settings/keys](https://github.com/settings/keys)
@@ -371,13 +404,21 @@ If all of these work, you are ready for Week 2.
 !!! note "Install Claude Code"
     Before Week 2, install [Claude Code](https://claude.ai/claude-code):
 
-    === "macOS / Linux"
+    === "macOS"
 
         ```bash
         brew install claude-code
         ```
 
-    === "Official installer"
+    === "Linux"
+
+        ```bash
+        curl -fsSL https://claude.ai/install-cli | sh
+        ```
+
+    === "Windows"
+
+        In your WSL Ubuntu terminal:
 
         ```bash
         curl -fsSL https://claude.ai/install-cli | sh

docs/osa/cli-reference.md

@@ -365,8 +365,26 @@ osa ask -a hed "What is HED?" -o json | jq '.answer'
 
 ### Using with Environment Variable
 
-```bash
-export OPENROUTER_API_KEY=sk-or-v1-your-key
-osa ask -a hed "What is HED?"
-osa chat -a bids
-```
+=== "macOS"
+
+    ```bash
+    export OPENROUTER_API_KEY=sk-or-v1-your-key
+    osa ask -a hed "What is HED?"
+    osa chat -a bids
+    ```
+
+=== "Linux"
+
+    ```bash
+    export OPENROUTER_API_KEY=sk-or-v1-your-key
+    osa ask -a hed "What is HED?"
+    osa chat -a bids
+    ```
+
+=== "Windows"
+
+    ```powershell
+    $env:OPENROUTER_API_KEY = "sk-or-v1-your-key"
+    osa ask -a hed "What is HED?"
+    osa chat -a bids
+    ```

docs/osa/development.md

@@ -38,11 +38,29 @@ uv sync
 # Install pre-commit hooks
 uv run pre-commit install
 
-# Copy environment file
-cp .env.example .env
+# Copy environment file (see OS-specific command below)
 # Edit .env with your API keys
 ```
 
+=== "macOS"
+
+    ```bash
+    cp .env.example .env
+    ```
+
+=== "Linux"
+
+    ```bash
+    cp .env.example .env
+    ```
+
+=== "Windows"
+
+    ```powershell
+    Copy-Item .env.example .env
+    ```
+```
+
 ## Testing
 
 ### Guidelines

docs/osa/getting-started.md

@@ -30,9 +30,17 @@ osa init
 You'll need an [OpenRouter API key](https://openrouter.ai/keys). The setup will:
 
 1. Prompt for your API key
-2. Save it securely to `~/.config/osa/credentials.yaml` (permissions 600)
+2. Save it securely to your config directory (see paths below)
 3. Test the connection to the API
 
+Config directory by platform:
+
+| Platform | Path |
+|----------|------|
+| macOS | `~/Library/Application Support/osa/` |
+| Linux | `~/.config/osa/` |
+| Windows | `%APPDATA%\osa\` |
+
 Alternatively, pass the key directly:
 
 ```bash
@@ -63,10 +71,26 @@ osa ask -a hed "What is HED?" --api-key sk-or-v1-your-key
 
 Or set it via environment variable:
 
-```bash
-export OPENROUTER_API_KEY=sk-or-v1-your-key
-osa ask -a hed "What is HED?"
-```
+=== "macOS"
+
+    ```bash
+    export OPENROUTER_API_KEY=sk-or-v1-your-key
+    osa ask -a hed "What is HED?"
+    ```
+
+=== "Linux"
+
+    ```bash
+    export OPENROUTER_API_KEY=sk-or-v1-your-key
+    osa ask -a hed "What is HED?"
+    ```
+
+=== "Windows"
+
+    ```powershell
+    $env:OPENROUTER_API_KEY = "sk-or-v1-your-key"
+    osa ask -a hed "What is HED?"
+    ```
 
 ## For Developers (Server)
 
@@ -93,9 +117,23 @@ uv run pre-commit install
 
 Copy the example environment file:
 
-```bash
-cp .env.example .env
-```
+=== "macOS"
+
+    ```bash
+    cp .env.example .env
+    ```
+
+=== "Linux"
+
+    ```bash
+    cp .env.example .env
+    ```
+
+=== "Windows"
+
+    ```powershell
+    Copy-Item .env.example .env
+    ```
 
 Edit `.env` with your settings: