# Step 28 — Housekeeping (2026-10-10) Small things found during the runs of 2026-10-09. Not run with real models unless said. ## Files are written as an Execution goes An Execution's folder was written only when it ended, so a killed process, or an Execution left waiting for its user, left nothing on disk. - Each time a Deliverable is submitted, the folder is written with what exists, and `execution.json` says `in_progress`. The end of the Execution writes it again with its final status. - An in-progress Execution is refused as a Baseline, as any Execution that did not complete is. - Because the folder is now written more than once, a write removes the files an earlier write recorded and this one does not have. Without that, a Terraform file removed in a Revision would have stayed beside the files that replaced it. Only files the Execution itself wrote are removed. Tests: `tests/execution/test_outputs_as_it_goes.py` (2). ## Four more code patterns `skills/google-cloud-iac-patterns/` gains Firestore, BigQuery, Eventarc and Google Kubernetes Engine, 18 in all. Each validates against `hashicorp/google` 8.6.0 in `tests/test_iac_patterns.py`. ## The two explainer pages Both now describe the opt-in to published Terraform modules.