Some checks failed
validation / verify (push) Failing after 12s
- An Execution's files are written as each Deliverable is submitted, marked in_progress, so a killed process or one waiting for its user leaves them on disk. A write removes files an earlier write left that it no longer has. - A question about delivered work is answered from that Execution's solution guide by the reply writer; a question about the service is answered as before. Nothing is started for either. - Lessons: prove writes only for lessons the Skill holds; the Skill records the vendored Skill versions the lessons were read against, status names any that changed, and a test fails until they are reviewed. - Four more code patterns: Firestore, BigQuery, Eventarc and GKE. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
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.jsonsaysin_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.