MechaCat02 651fb27522 fix(analysis): emit Cancelled event + assert lock-release after cancel (0.87.13) ...

Two 0.87.4 follow-ups:

1. Cron tick: existing shutdown-on-cancel test now also asserts the
   advisory lock is re-acquirable after cancel-during-tick. Without
   this, a refactor moving `pg_advisory_unlock` under the cancel arm
   would ship green and break multi-replica safety.

2. Analysis worker: cancel-mid-dispatch left the dashboard banner stuck
   on the cancelled page until a later page overwrote it. Add a
   `Cancelled` AnalysisEvent variant, publish on the cancel-release
   branch, wire the analysis and admin overview dashboards to clear
   on it. Per-page chip rolls back from `analyzing` to `queued`.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-06-23 19:00:38 +02:00

..

migrations

fix(analyze-dedup): migration pre-dedup, force-collision upgrade, gate test (0.87.11)

2026-06-23 07:22:20 +02:00

src

fix(analysis): emit Cancelled event + assert lock-release after cancel (0.87.13)

2026-06-23 19:00:38 +02:00

tests

fix(analysis): emit Cancelled event + assert lock-release after cancel (0.87.13)

2026-06-23 19:00:38 +02:00

.dockerignore

bugfix: third-pass audit follow-ups (F1-F4 + dockerignore)

2026-05-17 00:13:14 +02:00

.gitignore

chore: initial project scaffold

2026-05-16 21:05:16 +02:00

Cargo.lock

fix(analysis): emit Cancelled event + assert lock-release after cancel (0.87.13)

2026-06-23 19:00:38 +02:00

Cargo.toml

fix(analysis): emit Cancelled event + assert lock-release after cancel (0.87.13)

2026-06-23 19:00:38 +02:00

Dockerfile

feat(crawler): system Chromium via CRAWLER_CHROMIUM_BINARY (0.45.0) (#2)

2026-05-31 15:47:47 +00:00