v1.9.2 — Config backup: 413 fix + claw_agents in backups

Two bugs in the config-backup skill's full backup, fixed.

Fixed

• 413 Payload Too Large — once the DB grew to ~19 MB, the base64 backup body (~25 MB) blew past the file-bridge's hardcoded 25 MB Express limit, so automatic backups had been failing since ~2026-06-01. The file-bridge now gzips backups at rest (transparent compress: true flag — downloads and Seafile forwards decompress on the fly, no breaking change), and the body limit derives from MAX_FILE_SIZE_MB (20 → 200) instead of a hardcoded value.
• Persona/config silently missing from backups — TABLE_DEFS/SCOPES/UPSERT_TABLES still named the table agents, so since the Issue #35 rename every full backup wrote claw_agents: 0 rows. Now corrected; restore adds a legacy agents → claw_agents alias so pre-#35 backups still restore.

Validated

Live on the VPS: 19.0 MB / 11372-row full backup with claw_agents: 19 rows, uploaded without 413 and forwarded to Seafile (19.2 MB). End-to-end: DB → file-bridge (gzipped at rest) → Seafile (plain JSON).

Upgrade

git pull && ./setup.sh --force, then reinstall the config-backup skill (now n8n-claw-templates@6089521, v1.2.0). No breaking changes to stored files.

Full notes in CHANGELOG.md.

🤖 Generated with Claude Code