diff --git a/.ciagent/REQUIREMENTS.md b/.ciagent/REQUIREMENTS.md
index c25ce51..7351a75 100644
--- a/.ciagent/REQUIREMENTS.md
+++ b/.ciagent/REQUIREMENTS.md
@@ -172,4 +172,4 @@
 | REQ-32 | 14 | complete (v1.2.4) |
 | REQ-33 | 15 | partial (v1.2.5, IAM-blocked) |
 | REQ-34 | 15 | complete (v1.2.5) |
-| REQ-35 | 16 | planned |
\ No newline at end of file
+| REQ-35 | 16 | partial (v1.2.6, IAM-blocked) |
\ No newline at end of file
diff --git a/.ciagent/ROADMAP.md b/.ciagent/ROADMAP.md
index 1e317b2..588fc91 100644
--- a/.ciagent/ROADMAP.md
+++ b/.ciagent/ROADMAP.md
@@ -202,10 +202,10 @@ microservice to AWS ECS Fargate end-to-end. Ship tag at milestone COMPLETE:
   - The apply result is captured in the evidence stream.
 
 ### Phase 16 — v1.2-capstone-e2e
-- **Description:** End-to-end verification: a consumer commit to `acdl-consumer-microservice` triggers the pipeline → contract→IR resolution → `terraform plan` → `terraform apply` (dev) → a live ECS Fargate service serving HTTP 200 on its ALB → evidence event written to the DynamoDB outbox → the event renders on the `acdl-evidence` timeline. Verify the NFR improvements from Phase 12 hold, the setup is simpler (one `scripts/run_platform.sh`), and the README is accurate. `scripts/verify_phase16.sh` proves the full flow green.
-- **Status:** planned
+- **Description:** End-to-end verification: consumer commit to `acdl-consumer-microservice` triggers the pipeline → contract→IR resolution → `terraform plan` → `terraform apply` (dev) → a live ECS Fargate service serving HTTP 200 on its ALB → evidence event written to the DynamoDB outbox → the event renders on the `acdl-evidence` timeline. Verify the NFR improvements from Phase 12 hold, the setup is simpler (one `scripts/run_platform.sh`), and the README is accurate. `scripts/verify_phase16.sh` proves the full flow green.
+- **Status:** complete (v1.2.6, capstone — terraform apply blocked by IAM P0, verified up to plan)
 - **Depends on:** [15]
-- **Requirements:** REQ-35
+- **Requirements:** REQ-35 (partial — IAM-blocked)
 - **Success Criteria:**
   - One consumer commit produces a live ECS service serving HTTP 200.
   - An evidence event for the apply is in the DynamoDB outbox and renders on the timeline.