Bug Description

Rule creation is completely broken in v3.13.0.

1. POST /api/rules returns 201 but nothing persists

POST with valid payload returns HTTP 201 with Content-Length: 0. Subsequent GET /api/rules returns [].

2. Rules payload rejected by validation

POST with rules returns: {"code":0,"result":"First value is not available for this server"}

3. YAML import rejects all input

POST /api/rules/yaml/decode returns {"code":0,"result":"Invalid input"} for all tested YAML formats.

4. Database inserts invisible to API

Inserting records directly into rule_group, collection, and rules tables (with correct foreign keys, isActive=1, useRules=1) results in data visible via SQL but not via API — even after container restart.

5. Community install endpoints 404

/api/rules/community/*/install returns 404.

Environment

• Maintainerr v3.13.0 (Docker: maintainerr/maintainerr:latest)
• Plex media server
• SQLite database

Impact

Complete blocker — no rules can be created through any path. Maintainerr is unusable for new setups or after rule cleanup.