2 Commits

Author	SHA1	Message	Date
Jon Chery	bee9d02f01	feat(P40): contract interpolation + environment JSON schema ... ---ci--- project: acdl phase: 40 milestone: v1.9 status: execute ---/ci--- Phase 40 — contract-interpolation (REQ-103, REQ-104, D-081): Interpolation: - core/contract_resolver.py: _expand_vars(value, context) recursively expands ${env.<field>} + ${contract.<field>} tokens (dotted paths supported, e.g. ${env.state_backend.bucket}). Unknown tokens raise ValueError (fail loud). Expansion is post-schema-validation, pre-IR-resolution. - resolve() accepts environment_override (D-088) — overrides the contract's environment field BEFORE schema validation so interpolation context is consistent. - env context loaded via _load_env (self-contained, works as script + package import); 'environment' alias for env 'name' so ${env.environment} resolves. Environment schema + bindings: - schemas/environment.schema.json (draft 2020-12): name, account_id, region, state_backend, network, runner_role_arn, autonomy, confidence_threshold. - core/environments/qa.json, prod.json, dr.json placeholder bindings (attested, thresholds 0.75/0.90/0.95, placeholder account_id with stderr warning at load). - core/environment_check.py: load(env_name) helper + placeholder warning. Sample contracts: - contracts/static-assets.yaml + microservice.yaml use acdl-${env.environment}-${contract.module}-${env.account_id}-${env.region} naming pattern (region + account id + environment). Tests: +35 (test_environment_schema.py, test_interpolation.py, test_sample_contracts_interpolate.py). 406 passed; run_ci.sh green; run_platform.sh --check-only green. Existing fixture-based tests preserved (instance.json static fixtures unaffected).	2026-07-23 04:30:30 +00:00
Jon Chery	4e495e5648	feat(P21): environments concept + onboarding scaffold (REQ-61) ... ---ci--- project: acdl phase: 21 milestone: v1.6 status: execute ---/ci--- Introduce platform-managed environments: a consumer does not provide an AWS account, VPC, subnet, S3 state bucket, or runner key. A named environment is a platform-owned bundle of account + network + state backend + IAM role (surfaced via ABAC), selected by name in the contract. Scaffold: - core/environments/dev.json (sample dev env definition) - core/environments/README.md (how envs are used + how to add one) - core/environment_check.py (reads a contract's environment field, looks up core/environments/<name>.json, prints a friendly onboarding prompt when none exists, exits non-zero) - scripts/run_platform.sh: Step 0 calls environment_check.py before contract validation; a missing env halts the pipeline with the onboarding prompt - tests/test_environment_check.py: 12 tests (dev bound, missing env -> onboarding prompt, onboarding message lists provisions, contract paths, wire-in, check-only still passes) Tests: 166 pass (154 + 12 new).	2026-07-22 18:24:02 +00:00