Fix core request pipeline stability

[RANGROO]

Summary

• stop unhandled physics_raw telemetry before it enters the dialogue/LLM pipeline
• move dynamic-profile batch processing out of Apache requests and into the core service queue
• sanitize memory full-text search terms and use the rechat origin line instead of control JSON
• safely handle structured equipment metadata and optional timeout/TTS globals
• add focused regression coverage for the corrected request paths

Root cause

Several core request paths assumed optional globals and scalar payload values were always initialized. Raw physics telemetry could also fall through without an extension handler, and dynamic-profile updates performed LLM work from the web request lifecycle. Rechat control JSON was passed directly into PostgreSQL to_tsquery, allowing syntax operators in metadata to produce malformed searches.

Impact

These changes prevent avoidable PHP warnings and connector errors, keep raw telemetry from producing LLM requests, prevent malformed memory searches, and allow dynamic-profile updates to continue asynchronously without holding the game request open.

Validation

• php vendor/bin/phpunit tests/CoreRequestStabilityTest.php (7 tests, 13 assertions)
• PHP syntax checks passed for all changed files
• git diff --check
• live physics_raw request returned X-CUSTOM-CLOSE in approximately 118 ms without connector errors
• deployed dynamic-profile worker consumed an invalid test queue job without invoking an LLM
• local HerikaServer UI returned HTTP 200 after deployment

Review notes

The unstable push guard requires a PR because this touches main.php, processor/comm.php, and service/processors/. It also reported overlap with open PRs #581 (main.php) and #568 (lib/data_functions.php), so this remains a draft pending conflict and semantic review.