Local Environment Control (bootstrap / doctor / reconcile)

Purpose

Make local development environments predictable and self-healing under the repo-env-contract SSOT model.

The env-localctl skill:

• •validates local requirements against the repo contract (env/contract.yaml)
• •checks that non-secret values and secret references exist for a chosen env
• •resolves secrets via approved mechanisms (never via chat)
• •generates a local env file (.env.local or .env.<env>.local)
• •produces redacted LLM context (docs/context/env/effective-<env>.json)
• •can compile to a custom env-file path (deployment machine) and optionally skip context

Hard precondition (SSOT mode gate)

Use the skill only when the project env SSOT mode is repo-env-contract.

To check the mode, read:

• •docs/project/env-ssot.json

If the project is not in the required mode, STOP.

If docs/project/env-ssot.json does not exist (first-time setup), run:

python3 -B -S .ai/skills/features/environment/env-contractctl/scripts/env_contractctl.py init --root .

Then re-run the local workflow.

When to use

Use when the user asks to:

• •"make my local env work" / "I can't boot the service locally"
• •sync local env after contract changes
• •diagnose missing env vars or secret access
• •regenerate .env.local deterministically

Avoid when:

• •you need to add/rename/deprecate variables (use env-contractctl)
• •you need to deploy/rotate secrets for staging/prod (use env-cloudctl)

Invariants

• •MUST NOT ask users to paste secrets into chat.
• •MUST NOT write secret values into evidence artifacts.
• •SHOULD write local secret material only to gitignored files (e.g., .env.local).
• •SHOULD set .env.local permissions to 0600.

Inputs

• •Contract: env/contract.yaml
• •Non-secret values: env/values/<env>.yaml (+ optional env/values/<env>.local.yaml for per-developer overrides)
• •Secret references: env/secrets/<env>.ref.yaml
• •Secret material: resolved via secret backends (e.g., mock file store, environment, or file reference)

Outputs (evidence + generated artifacts)

Evidence directory

Choose one evidence location (no secrets):

• •Recommended:
  • •dev-docs/active/<task-slug>/artifacts/env-local/
• •Otherwise:
  • •.ai/.tmp/env-local/<run-id>/

Evidence files (templates available in ./templates/):

• •00-prereq-check.md
• •01-auth-and-secrets-check.md
• •02-config-compile-report.md
• •03-connectivity-smoke.md
• •04-post-fix-summary.md

Generated artifacts

• •.env.local (default for dev) or .env.<env>.local
• •docs/context/env/effective-<env>.json (redacted; safe for LLM)
• •Custom env-file path when --env-file is provided (e.g. ops/deploy/env-files/<env>.env)

Steps

Phase 0 — Confirm scope and mode

1. •Confirm the user's intent is local bootstrap/diagnosis.
2. •Confirm env SSOT mode is repo-env-contract via docs/project/env-ssot.json.
   • •If not, STOP.
3. •Confirm target env for local run (default: dev).
4. •Confirm runtime target for policy rules (default: local; use ecs for deployment-machine compile).
5. •Choose evidence directory.

Phase A — Doctor (diagnose)

1. •Run a deterministic local doctor:

python3 -B -S .ai/skills/features/environment/env-localctl/scripts/env_localctl.py doctor --root . --env dev --out <EVIDENCE_DIR>/00-prereq-check.md

1. •If doctor reports missing non-secret values, use the minimal entry point:

• •Project-wide non-secret values: env/values/dev.yaml
• •Per-developer overrides (gitignored): env/values/dev.local.yaml

1. •If doctor reports missing secret material, use the minimal entry points:

• •Ensure secret ref exists: env/secrets/dev.ref.yaml
• •Provide secret material via an approved backend (never via chat)
  • •For tests/local demo: create env/.secrets-store/dev/<secret_name>

Phase B — Compile (generate .env.local)

1. •Compile and write .env.local and redacted context:

python3 -B -S .ai/skills/features/environment/env-localctl/scripts/env_localctl.py compile --root . --env dev --out <EVIDENCE_DIR>/02-config-compile-report.md

Deployment-machine compile (custom env-file, no context):

python3 -B -S .ai/skills/features/environment/env-localctl/scripts/env_localctl.py compile --root . --env staging --runtime-target ecs --workload api --env-file ops/deploy/env-files/staging.env --no-context --out <EVIDENCE_DIR>/02-config-compile-report.md

Phase C — Connectivity smoke (optional)

1. •If needed, run a light connectivity check (best-effort; safe; redacted):

python3 -B -S .ai/skills/features/environment/env-localctl/scripts/env_localctl.py connectivity --root . --env dev --out <EVIDENCE_DIR>/03-connectivity-smoke.md

Phase D — Reconcile (idempotent repair)

1. •If the local .env.local drifted, re-run compile (idempotent). Record 04-post-fix-summary.md.

Verification

• • SSOT mode is repo-env-contract
• • Doctor passes (no missing required keys)
• • .env.local generated and gitignored
• • No secret values written to evidence
• • docs/context/env/effective-<env>.json generated (redacted)
• • Central test suite passes: node .ai/tests/run.mjs --suite environment

Boundaries

• •MUST NOT modify env/contract.yaml in the env-localctl workflow.
• •MUST NOT perform cloud-side apply/rotate/decommission.
• •MUST NOT print or store secret values in logs/evidence.