Container/runner/MCP lab polish (#41,#42,#45,#46) (#65)

Co-authored-by: claude <claude@jpaul.io> Co-committed-by: claude <claude@jpaul.io>
2026-06-22 17:21:16 -04:00
parent 6691755060
commit 315cb2c190
5 changed files with 51 additions and 15 deletions
@@ -222,7 +222,9 @@ a repo also works). If a real runner is too heavy right now, Track A alone satis
   (the same place your Module 14 `ci.yml` lives — for Actions-style forges that's
   `.github/`/`.forgejo/`/`.gitea/` under `workflows/`; the file comments tell you where). Commit and
   push. It runs the same lint-and-test as Module 14, then prints the runner's hostname, OS, user,
-   whether it looks ephemeral, and whether it can reach the public internet.
+   whether it looks ephemeral, and whether it can reach the public internet. The receipt step carries
+   `if: always()` so it still prints even when lint or test fail — a diagnostic shouldn't disappear on
+   a red build (the job still reports red). On GitLab CI the same idea is `when: always` on the job.

 2. **Read the receipt.** Open the job logs on your forge and read the `Where did this run?` step.
   You're now able to answer, for a real job, the question this module opened with: *whose computer