docs(init): validate v1.9 specification

---ci---
project: acdl
phase: 0
milestone: v1.9
status: specify
---/ci---

v1.9 scope (user-directed, 2026-07-23):
- Design doc refresh (hitl_matrix_design.md + audit_ledger_design.md)
- Contract interpolation (${env.<field>} + ${contract.<field>})
- Per-environment CI jobs (no environment field editing for promotion)
- Stub implementation (SoD, HITL gates, attestation matrix, Wiz, Kyverno)
- P1-1 adapter parameterization remediation

Requirements REQ-100..REQ-111 added to REQUIREMENTS.md.
PROJECT.md v1.9 objective + phase table (39-43) appended.
config.json milestone bumped to v1.9 (active).

.ciagent/PROJECT.md

@@ -296,6 +296,74 @@ and test each.
 Milestone COMPLETE gate: review → ship `v1.8.0` (feature milestone, next
 minor per run.md — v1.7 shipped `v1.7.0`) → audit.
 
+## Objective for Milestone v1.9 (active)
+
+Production-grade progression: contract interpolation, per-environment
+promotion without field editing, stub implementation, and P1-1
+remediation. The v1.8 milestone shipped encryption/deletion-protection by
+default, uptime, decommission, and engineering standards but left four
+gaps that v1.9 closes (user-directed, 2026-07-23):
+
+1. **Design doc refresh.** `core/hitl_matrix_design.md` and
+   `core/audit_ledger_design.md` are stale — both still describe the
+   v1.1 spike scope ("dev-only; HITL not exercised"; "spike scope =
+   hash chain + outbox write; Object Lock + JWS are v1.2"). v1.9 brings
+   them up to date with the shipped v1.8 platform and the v1.9 wiring.
+2. **Contract interpolation (variable expansion).** Contracts cannot
+   reference environment onboarding values today — bucket names, account
+   IDs, regions are hardcoded literals. v1.9 adds `${env.<field>}` and
+   `${contract.<field>}` expansion in the resolver, sourced from the
+   environment onboarding JSON. Naming patterns like
+   `acdl-${env.environment}-${contract.module}-${env.account_id}-${env.region}`
+   become expressible. The S3 bucket naming-pattern requirement is the
+   binding example.
+3. **Per-environment CI jobs (no field editing for promotion).** Today a
+   promotion dev → qa requires editing the `environment:` field in the
+   contract YAML. v1.9 ships a hybrid model: (a) per-environment contract
+   files (`.acdl/static-assets.dev.yaml`, `...qa.yaml`, etc.) and (b) an
+   `environment` `workflow_call` input on the reusable deploy workflow
+   that overrides the contract's environment at load time. There is one
+   CI job per environment, each pointing at its respective contract (or
+   the same contract + the env input). Promotion = running the matching
+   job; no field editing.
+4. **Stub implementation.** Identify and implement the stubbed
+   functionality: `separation_of_duties.route_halt_artifact` (logs only →
+   real SNS + outbox event); HITL qa/prod/dr pre-execution attestation
+   gates (only decommission SRE gates are wired today); the full
+   8-concern attestation matrix (offline-testable subset implemented;
+   operator-supplied concerns accept signed evidence artifacts); the Wiz
+   adapter (stub → real API client with graceful degrade); the Kyverno
+   adapter (fleshed out translator, still inactive for Terraform-only
+   stacks). The audit-ledger S3 Object Lock + JWS + async worker + DLQ +
+   daily checkpoints build-out is **deferred** to a future milestone
+   (D-076) — it requires non-offline-testable AWS infra (Object Lock
+   bucket, KMS signing key, SQS DLQ, Lambda worker).
+5. **Post-hoc requirement from previous milestones.** P1-1 from the v1.2
+   review (adapter ECS/ALB/VPC hardcoded defaults — `desired_count = 1`,
+   `launch_type = "FARGATE"`, `target_type = "ip"`,
+   `load_balancer_type = "application"`, `family = "app"`, `Name = ...`
+   — should be parameterized via the L1 interfaces, deferred to v1.3,
+   never implemented) is closed. The adapter becomes a thin translator;
+   the defaults move into `interface.json` inputs.
+
+The milestone also reconstructs `.ciagent/REVIEW.md`, which still holds
+v1.2 review content (v1.3–v1.8 reviews were not persisted). The v1.9
+review overwrites it with current milestone content; a note records the
+historical gap (no git-history rewrite).
+
+## Milestone v1.9 Phases
+
+| Phase | Name | Goal |
+|-------|------|------|
+| 39 | design-doc-refresh-and-p1-1-parameterization | Refresh `hitl_matrix_design.md` + `audit_ledger_design.md` to current. Move adapter ECS/ALB/VPC hardcoded defaults into L1 `interface.json` inputs (P1-1 closure). |
+| 40 | contract-interpolation | `${env.<field>}` + `${contract.<field>}` resolver expansion from environment onboarding JSON. Environment JSON schema. Sample contracts use naming patterns (region + account id + environment). |
+| 41 | per-environment-ci-jobs | Per-env contract files + `environment` workflow_call input on the deploy workflow. 1 CI job per environment (dev/qa/prod/dr), each pointing at its respective contract. HITL attestation gate structure wired (qa/prod/dr). |
+| 42 | stub-implementation | `route_halt_artifact` real (SNS + outbox). HITL qa/prod/dr attestation gates. 8-concern attestation matrix (offline-testable subset). Wiz real client. Kyverno translator fleshed out. |
+| 43 | verify-review-audit-complete | 4-layer verify. Multi-persona review. Audit. Complete v1.9 (tag `v1.9.0`, floating tags, `uses:` bump `@v1.6` → `@v1.9`). |
+
+Milestone COMPLETE gate: review → ship `v1.9.0` (feature milestone, next
+minor per run.md — v1.8 shipped `v1.8.0`) → audit.
+
 ## Requirements
 
 ### v1.0 (Prior milestone — the demo)