PiCloud

Files

MechaCat02 73d3befb06 fix(manager-core): F-Q-009 promote dispatcher tick + async-exec timeout to env-overridable

TICK_INTERVAL (100ms) and ASYNC_EXEC_TIMEOUT (300s) were `const`. Every
other timing knob in the file (cron tick, queue reclaim, retry policy)
is env-overridable via TriggerConfig::from_env. Operators on a
constrained Pi or a busier instance could tune retries but not
dispatcher cadence.

Add env knobs:
- PICLOUD_DISPATCHER_TICK_INTERVAL_MS (default 100)
- PICLOUD_DISPATCHER_ASYNC_EXEC_TIMEOUT_SEC (default 300)

Read via tick_interval_from_env() / async_exec_timeout_from_env() at
dispatcher startup. Invalid values fall back with a tracing-warn.

AUDIT.md anchor: F-Q-009.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-06-07 21:04:13 +02:00

executor-core

fix(executor-core): F-P-014 thread-local LRU regex cache (128 entries)

2026-06-07 20:51:20 +02:00

manager-core

fix(manager-core): F-Q-009 promote dispatcher tick + async-exec timeout to env-overridable

2026-06-07 21:04:13 +02:00

orchestrator-core

fix(orchestrator-core): F-Q-006 + F-Q-010 InboxRegistry expect on poison

2026-06-07 20:52:05 +02:00

picloud

fix(manager-core): F-P-009 cache resolved Principals (60s TTL) in auth middleware