feat: tell a node where a run came from

day01 commented

2026-08-11 21:58:44 +00:00

Owner

A node was handed a plan and nothing else. A plan says what to do and nothing about what it is being done to, so a job could not name its repository, its commit or the event that asked for it — and actions/checkout had nothing to check out.

Every run now records where it came from and which run it is, both written down with the run so a restart does not forget them or start numbering again. The assignment carries them to the node.

A pull request head sits on no branch this control plane knows, so its reference is the one the forge publishes it under.

A table created before this change has no honest value for either column, so they are added nullable and reading such a run back fails instead of inventing one.

A node was handed a plan and nothing else. A plan says what to do and nothing about what it is being done to, so a job could not name its repository, its commit or the event that asked for it — and `actions/checkout` had nothing to check out. Every run now records where it came from and which run it is, both written down with the run so a restart does not forget them or start numbering again. The assignment carries them to the node. A pull request head sits on no branch this control plane knows, so its reference is the one the forge publishes it under. A table created before this change has no honest value for either column, so they are added nullable and reading such a run back fails instead of inventing one.

day01 added 1 commit 2026-08-11 21:58:46 +00:00

feat: tell a node where a run came from

		Co-authored-by: Cursor <cursoragent@cursor.com>

day01 merged commit 7f19bdd298 into %!s()

2026-08-11 22:35:12 +00:00

day01 deleted branch feat/tell-a-node-where-a-run-came-from

2026-08-11 22:35:13 +00:00

feat: tell a node where a run came from #13