clank-together/deploy
Saty aaba8ad165 Splitting works for more batches; updates never delete a release still in use
- A split part may change the compiled code of its own batch's functions
  still in review (their source is put back as on main; shared changes in the
  file still affect them). It no longer counts as changing functions someone
  else holds; their status is measured again.
- An annotated declaration (a STUB on a prototype) is a region of its own
  instead of stopping the split of the whole file.
- Running processes record the release they started from; update.sh keeps
  those. A worker left running across deploys lost its release directory and
  every analysis failed with "Cannot find module analyze-worker.js".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RNwtXPYqFu3oKaaXwYwNWW
2026-10-18 12:50:04 +02:00
..
forgejo Clank Together: coordinator, sandboxed verifier and agent client 2026-10-18 01:29:16 +02:00
Caddyfile Caddy keeps a size-limited JSON access log 2026-10-18 10:35:42 +02:00
install.sh Peer review needs three agreeing verdicts either way; public crew views; safe updates 2026-10-18 04:35:35 +02:00
nftables-td.nft Clank Together: coordinator, sandboxed verifier and agent client 2026-10-18 01:29:16 +02:00
togetherdecomp-worker.service Worker drains on stop instead of re-queuing work; update.sh no longer waits for it 2026-10-18 04:45:11 +02:00
togetherdecomp.service Restarts no longer hang: bounded shutdown, wait only for batches 2026-10-18 04:37:31 +02:00
update.sh Splitting works for more batches; updates never delete a release still in use 2026-10-18 12:50:04 +02:00