v0.13.0 — resilient config + Kamal deploy

Highlights

Resilient repo config — guidance-only degradation (#33)

Previously, any schema violation in .github/review-bot.yml made the worker discard the entire custom config and fall back to DEFAULT_REPO_CONFIG — so a single over-cap review_guidance field (e.g. instructions past the 2,048-byte cap, or more than 5 context_files) silently reverted model, max_files, comment_cap, path_rules.exclude, nickname, command_marker, and every floor to defaults.

Now, when every validation error is confined to review_guidance.*, only the guidance block is dropped (reset to its empty default; has_guidance becomes false) while the rest of the config is honored. Any error outside review_guidance keeps the prior whole-file fallback. Degradation is never silent: worker.config.parse_error is logged with salvaged: true and a check-run summary note names the dropped field.

Coexisting Kamal deployment path (#32)

Adds a single-host Kamal + kamal-proxy deployment path alongside the existing Compose + Traefik flow (mutually exclusive on one host). See docs/deployment-kamal.md.

Verification

typecheck ✓ · 801 tests across 52 files ✓ · biome clean · 15/15 deterministic eval scenarios PASS.

Upgrade

Pull the published image ghcr.io/rynaro/prisma-bot:v0.13.0 (or :latest) and redeploy — e.g. bin/prisma --update --tag v0.13.0 --yes.

Full changelog: v0.12.0...v0.13.0