Bundle mission-control into Triple-C instead of cloning from GitHub

The mission-control (Flight Control) project is being closed upstream.
This embeds the project files directly in the repo under container/mission-control/,
bakes them into the Docker image at /opt/mission-control, and copies them into place
at container startup instead of git cloning from GitHub.

Also adds missing osc52-clipboard, audio-shim, and triple-c-sso-refresh to the
programmatic Docker build context in image.rs.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

container/mission-control/.claude/skills/init-project/README.md

@@ -0,0 +1,29 @@
+# Flight Operations
+
+This directory contains reference materials for the [Flight Control](https://github.com/anthropics/flight-control) development methodology.
+
+## Contents
+
+- **FLIGHT_OPERATIONS.md** — Quick reference for implementing missions, flights, and legs
+- **ARTIFACTS.md** — Project-specific configuration for how artifacts are stored
+- **agent-crews/** — Project crew definitions for each phase (who Mission Control works with)
+
+## For AI Agents
+
+When working on this project with Flight Control:
+
+1. Read `ARTIFACTS.md` to understand how this project stores missions, flights, and legs
+2. Read `FLIGHT_OPERATIONS.md` for the implementation workflow
+3. Read the relevant `agent-crews/*.md` file for crew definitions and prompts
+4. Check the artifact locations defined in `ARTIFACTS.md` for active work
+5. Follow the code review gate before marking any leg complete
+6. Update flight-log after each leg (location depends on artifact system)
+
+## Sync Behavior
+
+| File | Synced? | Notes |
+|------|---------|-------|
+| README.md | Yes | Updated via `/init-project` |
+| FLIGHT_OPERATIONS.md | Yes | Updated via `/init-project` |
+| ARTIFACTS.md | No | Project-specific, customize freely |
+| agent-crews/*.md | No | Project-specific, customize freely |