feat(l10-token-engine): upgrade to v4.4.0 with security and payload hardening

[dcplatforms]

Upgraded L10 Token Engine to v4.4.0, hardened extractSiteId for nested metadata fallback, standardized DER_ALARM_REPORTED multi-key ISO extraction, expanded Zero-Trust JWT secret blocking in production, updated tests and verification scripts, and compiled WEEKLY_REPORT_SEPTEMBER_2026.md.

---

PR created automatically by Jules for task 1479892046039513202 started by @dcplatforms

---

Note

Medium Risk
Touches production JWT secret validation and Kafka-driven regional alarm routing that feeds reward penalties. Scope is small and additive, but mis-parsed ISO keys or overly aggressive secret blocking could affect auth or hardware-health scoring.

Overview
Bumps the Token Engine to v4.4.0 with three small hardening changes: nested site-id lookup, broader DER alarm ISO keys, and extra weak JWT secrets blocked in production.

extractSiteId now recurses into payload.metadata so nested L1 telemetry still resolves a site. The DER_ALARM_REPORTED consumer accepts isoRegion / iso / region in addition to iso_region, so regional Redis alarm counters (and hardware-health penalties) still increment when producers use alternate field names.

authenticateToken rejects change_in_production and development_secret when NODE_ENV === 'production'. Version strings are updated on /health, AI export source, and package.json. Tests and a static verify_l10_v4_4_0.js script cover the new checks.

^{Reviewed by Cursor Bugbot for commit 3f88380. Configure here.}

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.