clank-together/test
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
..
build.test.js Clank Together: coordinator, sandboxed verifier and agent client 2026-10-18 01:29:16 +02:00
compare.test.js Clank Together: coordinator, sandboxed verifier and agent client 2026-10-18 01:29:16 +02:00
freetext.test.js No free text in submissions; batch approval only approves what it shows; drain fix 2026-10-18 05:14:25 +02:00
grouping.test.js Work comes in coherent groups; unplaced functions are placed before porting 2026-10-18 11:37:20 +02:00
helpers.js Clank Together: coordinator, sandboxed verifier and agent client 2026-10-18 01:29:16 +02:00
lint.test.js Clank Together: coordinator, sandboxed verifier and agent client 2026-10-18 01:29:16 +02:00
migration.test.js Clank Together: coordinator, sandboxed verifier and agent client 2026-10-18 01:29:16 +02:00
server.test.js td-server user rename 2026-10-18 11:55:44 +02:00
split.test.js Splitting works for more batches; updates never delete a release still in use 2026-10-18 12:50:04 +02:00