Prioritize combat over routine logistics

[RANGROO]

Summary

• route major_damage through the existing combat event processor
• allow major_damage to enter the existing regular-memory event stream
• include canonical combat_start, combat_end, and major_damage rows in Combat history
• extend the existing event allowlist regression for major_damage

Scope

This PR only classifies and exposes the new combat event. It does not change bored conversations, prompt text, dynamic-profile history sizing, memory summarization instructions, schema defaults, or database migrations.

Validation

• php -l on every changed PHP file: passed
• php tests/memory_event_allowlist_regression.php: passed
• git diff --check: passed
• four runtime files hash-matched after local WSL sync
• runtime PHP lint and memory allowlist regression: passed
• local StobeServer HTTP endpoint: 200
• earlier prompt-default deployment was reverted to the original defaults in the local database

Companion

• Track combat lifecycle for autonomous dialogue STOBE#33

Deployment

• locally synced to /var/www/html/StobeServer from codex/combat-lifecycle at 4c8bb66
• configuration, logs, database content other than the two restored defaults, uploads, voices, portraits, and item images were preserved

Limits

• major_damage has not yet been confirmed end-to-end in game
• GitHub Actions does not reach repository tests because PostgreSQL client installation fails when libpq-dev and postgresql-common both own /usr/bin/pg_config