[bihius]

Prepares v0.1.0-beta.10, mirroring #380's file set.

• Version bumps: backend and log-shipper pyproject.toml (0.1.0b10) with their uv.lock, frontend package.json (0.1.0-beta.10), and the release/ kit pinned to v0.1.0-beta.10.
• uv lock rewrote only the two project version entries — no dependency, revision or wheel churn.
• Content since v0.1.0-beta.9 is one change, fix(backend): keep stick-tables through a reload that races the peers resync #381: Apply configuration now waits for the worker it is about to replace to become able to hand the stick-tables over before reloading. Without it, an Apply inside the outgoing worker's five-second resync window dropped every ban and rate-limit counter silently (git diff --name-only v0.1.0-beta.9..origin/main = that fix, its tests and docs).
• New ### v0.1.0-beta.10 upgrade notes:
  • bans and rate counters survive every Apply now: the beta.8 → beta.9 path that lost a ban in 5 of 8 applies keeps it 21 times out of 21 in a rapid Apply loop, and a fresh install 20 out of 20;
  • the two cases that still start the tables empty, stated explicitly: the first Apply after coming from v0.1.0-beta.8 or older (that worker has no peers section and cannot teach anything — an upgrade from v0.1.0-beta.9 does generate it, so it keeps them), and a restarted or recreated haproxy container;
  • docker-compose.yml and the seed haproxy/*.cfg are unchanged from beta.9, and no migrations: src/backend/alembic/ is untouched since beta.9, and .env gains no variables.
• Also tightened the "What an upgrade does not carry over" bullet, which attributed the first-Apply loss to any tag-only upgrade rather than to a v0.1.0-beta.8-or-older source.
• CHANGELOG: [0.1.0-beta.10] section and its compare link.

Gates: backend pytest clean, frontend type-check clean.

After merge: annotated tag v0.1.0-beta.10 on the merge commit; publish.yml builds both architectures, merges the manifest lists and creates the (non-prerelease, Latest) GitHub release with the kit asset.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.