[
    "NODE_EXTRA_CA_CERTS=",
    "REQUESTS_CA_BUNDLE=",
    "SSL_CERT_FILE=",
    "CLAUDE_CODE_USE_BEDROCK=",
    "AWS_REGION=",
    "AWS_ACCESS_KEY_ID=",
    "AWS_SECRET_ACCESS_KEY=",
    "AWS_SESSION_TOKEN=",
    "AWS_PROFILE=",
    "AWS_BEARER_TOKEN_BEDROCK=",
    "AWS_SSO_AUTH_REFRESH_CMD=",
    "ANTHROPIC_BASE_URL=",
    "ANTHROPIC_AUTH_TOKEN=",
    "ANTHROPIC_MODEL=",
    "DISABLE_PROMPT_CACHING=",
    "ANTHROPIC_BEDROCK_SERVICE_TIER=",
    "ANTHROPIC_DEFAULT_OPUS_MODEL=",
    "ANTHROPIC_DEFAULT_SONNET_MODEL=",
    "ANTHROPIC_DEFAULT_HAIKU_MODEL=",
    "ANTHROPIC_DEFAULT_FABLE_MODEL=",
    "CLAUDE_CODE_OAUTH_TOKEN=",
    "TRIPLE_C_CUSTOM_ENV=",
    "MISSION_CONTROL_ENABLED=1",
    "VPN_SUPPORT_ENABLED=0",
    "TRIPLE_C_PERMISSION_MODE=default",
    "CLAUDE_INSTRUCTIONS=global rules\nline two\n\n## Mission Control\n\nThe `/workspace/mission-control/` directory contains **Flight Control** — an AI-first development methodology for structured project management. Use it for all project work.\n\n### How It Works\n\n- **Mission Control is a tool, not a project.** It provides skills and methodology for managing other projects.\n- All Flight Control skills are installed as personal skills in `~/.claude/skills/` and are automatically available as `/slash-commands`\n- The methodology docs and project registry live in `/workspace/mission-control/`\n\n### When to Use\n\nWhen working on any project that has a `.flightops/` directory, follow the Flight Control methodology:\n1. Read the project's `.flightops/ARTIFACTS.md` to understand artifact storage\n2. Read `.flightops/FLIGHT_OPERATIONS.md` for the implementation workflow\n3. Use Mission Control skills for planning and execution\n\n### Available Skills\n\n| Skill | When to Use |\n|-------|-------------|\n| `/init-project` | Setting up a new project for Flight Control |\n| `/mission` | Defining new work outcomes (days-to-weeks scope) |\n| `/flight` | Creating technical specs from missions (hours-to-days scope) |\n| `/leg` | Generating implementation steps from flights (minutes-to-hours scope) |\n| `/agentic-workflow` | Executing legs with multi-agent workflow (implement, review, commit) |\n| `/flight-debrief` | Post-flight analysis after a flight lands |\n| `/mission-debrief` | Post-mission retrospective after completion |\n| `/daily-briefing` | Cross-project status report |\n\n### Key Rules\n\n- **Planning skills produce artifacts only** — never modify source code directly\n- **Phase gates require human confirmation** — missions before flights, flights before legs\n- **Legs are immutable once in-flight** — create new ones instead of modifying\n- **`/agentic-workflow` orchestrates implementation** — it spawns separate Developer and Reviewer agents\n- **Artifacts live in the target project** — not in mission-control\n\nproject rules\n\n## Flight Operations\n\nThis project uses **Flight Control** (bundled with Triple-C) for structured development.\n\n**Before any mission/flight/leg work, read these files in order:**\n1. `.flightops/README.md` — What the flightops directory contains\n2. `.flightops/FLIGHT_OPERATIONS.md` — **The workflow you MUST follow**\n3. `.flightops/ARTIFACTS.md` — Where all artifacts are stored\n4. `.flightops/agent-crews/` — Project crew definitions for each phase (read the relevant crew file)\n\n## Available Port Mappings\nThe following ports are mapped from the host to this container. Use these container ports when starting services that need to be accessible from the host:\n- Host port 8080 -> Container port 3000 (tcp)\n\n## Scheduled Tasks\n\nThis container supports scheduled tasks via `triple-c-scheduler`. You can set up recurring or one-time tasks that run as separate Claude Code agents.\n\n### Commands\n- `triple-c-scheduler add --name \"NAME\" --schedule \"CRON\" --prompt \"TASK\"` — Add a recurring task\n- `triple-c-scheduler add --name \"NAME\" --at \"YYYY-MM-DD HH:MM\" --prompt \"TASK\"` — Add a one-time task\n- `triple-c-scheduler list` — List all scheduled tasks, with a running/idle status column\n- `triple-c-scheduler remove --id ID` — Remove a task\n- `triple-c-scheduler enable --id ID` / `triple-c-scheduler disable --id ID` — Toggle tasks\n- `triple-c-scheduler status [--id ID] [--watch]` — Show what is running right now, and for how long\n- `triple-c-scheduler logs [--id ID] [--tail N]` — View execution logs\n- `triple-c-scheduler run --id ID` — Manually trigger a task immediately (streams its log)\n- `triple-c-scheduler notifications [--clear]` — View or clear completion notifications\n\n### Cron format\nStandard 5-field cron: `minute hour day-of-month month day-of-week`\nExamples: `*/30 * * * *` (every 30 min), `0 9 * * 1-5` (9am weekdays), `0 */2 * * *` (every 2 hours)\n\n### One-time tasks\nUse `--at \"YYYY-MM-DD HH:MM\"` instead of `--schedule`. The task automatically removes itself after execution.\n\n### Working directory\nUse `--working-dir /workspace/project` to set where the task runs (default: /workspace).\n\n### Checking results\nWhile a task is running, `triple-c-scheduler status` reports it with elapsed time — a log that has stopped growing is normal, because `claude -p` writes its answer only at the end, so use `status` rather than log silence to tell a slow run from a dead one. After tasks run, check notifications with `triple-c-scheduler notifications` and detailed output with `triple-c-scheduler logs`.\n\n### Timezone\nScheduled times use the container's configured timezone (check with `date`). If no timezone is configured, UTC is used.\n\n## Referring to files\n\nThe user can click a file path in this terminal to open it in a viewer (while a program holds the mouse: Shift+click, or Option+click on macOS). Paths relative to the project work. When you mention a file outside the project (for example in `/tmp`, including your scratchpad directory, or under `~`), print its full absolute path, not a shortened or relative one, so it can be opened.\n\n## Sandbox Mode\n\nThis container has Claude Code's bash sandbox enabled, managed by Triple-C\n(toggle it from the project's \"Sandbox mode\" switch in the Triple-C UI).\nBash commands run inside `bubblewrap` with filesystem and network isolation\n(`enableWeakerNestedSandbox` is on because we are inside Docker).\n\n### When a command fails because of sandbox restrictions\n\nTriple-C disables the `dangerouslyDisableSandbox` escape hatch\n(`allowUnsandboxedCommands: false`), so failing commands cannot bypass the\nsandbox at runtime. To make a blocked command work, edit\n`~/.claude/settings.json` and restart Claude Code:\n\n| Need | Setting |\n|---|---|\n| Write to a path outside the project (e.g. `~/.kube`) | Add to `sandbox.filesystem.allowWrite` |\n| Reach a new domain | Will prompt; or add permanently to `sandbox.allowedDomains` |\n| Run a specific tool entirely outside the sandbox | Add a glob (e.g. `\"docker *\"`) to `sandbox.excludedCommands` |\n\n### Docker commands\n\nThe `docker` CLI does not work inside the sandbox. If this project has\n\"Allow container spawning\" enabled in Triple-C and you need to run\n`docker` commands, add `\"docker *\"` to `sandbox.excludedCommands` in\n`~/.claude/settings.json`. Other tools known to be sandbox-incompatible\ninclude `watchman` — pass `--no-watchman` to `jest`.\n\n### Disabling sandbox mode\n\nDo not change `sandbox.enabled` in `settings.json` — Triple-C overwrites it\non every container start. To turn sandbox off, stop the container in\nTriple-C, flip the \"Sandbox mode\" switch off, then start the container.",
    "CLAUDE_CODE_NO_FLICKER=",
    "CLAUDE_CODE_ENABLE_AWAY_SUMMARY=",
    "CLAUDE_CODE_SUBPROCESS_ENV_SCRUB=0",
    "ENABLE_PROMPT_CACHING_1H=0",
    "CLAUDE_CODE_SETTINGS_JSON={\"autoScrollEnabled\":true,\"sandbox\":{\"allowUnsandboxedCommands\":false,\"enableWeakerNestedSandbox\":true,\"enabled\":true},\"showThinkingSummaries\":false}",
    "CLAUDE_CODE_SETTINGS_CLEAR=[\"awaySummaryEnabled\",\"effortLevel\",\"tui\",\"viewMode\"]",
]
