BaaRai 89ece8eb8d fix(bench): discover the challenge port dynamically and tear down on deploy failure ...

The suite does not use one container port: most challenges publish 8080
but some (051, 091, 100) publish 5000, and the adapter had 8080
hardcoded, so deploy failed on those and the failure happened before
the teardown block, leaving the challenge running.

- the host port now comes from the app container port mapping (any
  container port, via docker inspect), never from an assumed 8080
- the teardown finally now wraps the deploy as well: a failure halfway
  through deploy no longer leaves containers behind (--keep and
  --deploy-only still opt out)

2026-10-16 14:29:00 +02:00

..

benchmark

fix(bench): discover the challenge port dynamically and tear down on deploy failure

2026-10-16 14:29:00 +02:00

submission_review

feat: pre-submission report review (validate against program rules)

2026-10-12 08:09:57 +02:00

backup.sh

feat: built-in backup script (pg_dump with rotation, optional data archive)

2026-10-11 22:46:47 +02:00

posture_check.py

feat: refusal-posture probe for LLM profiles

2026-10-12 07:01:40 +02:00