pipeline jobs never recieve status updates(?) from a spindle despite logs reporting success #253

hello, i'm testing our self-hosted spindle, and it seems that all recent jobs just don't get any status updates?

https://tangled.org/@melontini.me/spindle-knot-test-pls-ignore-thankies/pipelines all the jobs with the sand watch did get a spindle response and a job log (or a fail due some docker config tests)

e.g. this commit https://tangled.org/@melontini.me/spindle-knot-test-pls-ignore-thankies/commit/836591d42a119e7b200033a56677ed9efb08ba7c

{"kind":"control","content":"Configure Nix","step_command":"mkdir -p /etc/nix\necho 'extra-experimental-features = nix-command flakes' \u003e\u003e /etc/nix/nix.conf\necho 'build-users-group = ' \u003e\u003e /etc/nix/nix.conf"}
{"kind":"control","content":"Clone repository into workspace","step_id":1,"step_command":"git init\ngit remote add origin https://knot.synth.download/did:web:melontini.me/spindle-knot-test-pls-ignore-thankies\ngit fetch --depth=1 origin 836591d42a119e7b200033a56677ed9efb08ba7c\ngit checkout FETCH_HEAD"}
{"kind":"data","content":"Initialized empty Git repository in /tangled/workspace/.git/","stream":"stdout"}
{"kind":"data","content":"hint: Using 'master' as the name for the initial branch. This default branch name\nhint: is subject to change. To configure the initial branch name to use in all\nhint: of your new repositories, which will suppress this warning, call:\nhint:\nhint: \tgit config --global init.defaultBranch \u003cname\u003e\nhint:\nhint: Names commonly chosen instead of 'master' are 'main', 'trunk' and\nhint: 'development'. The just-created branch can be renamed via this command:\nhint:\nhint: \tgit branch -m \u003cname\u003e","stream":"stderr"}
{"kind":"data","content":"From https://knot.synth.download/did:web:melontini.me/spindle-knot-test-pls-ignore-thankies\n * branch            836591d42a119e7b200033a56677ed9efb08ba7c -\u003e FETCH_HEAD","stream":"stderr"}
{"kind":"data","content":"Note: switching to 'FETCH_HEAD'.\n\nYou are in 'detached HEAD' state. You can look around, make experimental\nchanges and commit th","stream":"stderr"}
{"kind":"data","content":"em, and you can discard any commits you make in this\nstate without impacting any branches by switching back to a branch.\n\nIf you want to create a new branch to retain commits you create, you may\ndo so (now or later) by using -c with the switch command. Example:\n\n  git switch -c \u003cnew-branch-name\u003e\n\nOr undo this operation with:\n\n  git switch -\n\nTurn off this advice by setting config variable advice.detachedHead to false","stream":"stderr"}
{"kind":"data","content":"HEAD is now at 836591d failed","stream":"stderr"}
{"kind":"control","content":"print cool envvar","step_id":2,"step_kind":1,"step_command":"echo $COOL_ENVVAR\n"}
{"kind":"data","content":"heelo!!","stream":"stdout"}