agessaman bf70594b41 fix: close the '*'-only flood_scopes bypass and schedule write race ...

A flood_scopes of "*" alone leaves scope_keys empty while setting
flood_scope_allow_global, and the loader already logs that as an active
allowlist. The handler gated on scope_keys alone, so that configuration
skipped authorisation entirely and admitted absent, uncorrelated and
TRANSPORT_FLOOD traffic. The gate now fires when either is set, so "*"
means global-only rather than everything.

The scheduled-message duplicate check ran outside the write lock inside
update_ini_values, so two concurrent creates for the same schedule could
both pass and the second silently replace the first instead of getting
the 409. Check and write are now one critical section, and delete is too.
Repaired the delete path's error handling while moving it, so an OSError
during the write is still a 500 rather than escaping.

2026-08-22 01:06:08 -07:00

..

__init__.py

Update configuration handling and validation for bot sections

2026-02-12 19:23:35 -08:00

test_flood_scope_reply.py

fix: close the '*'-only flood_scopes bypass and schedule write race

2026-08-22 01:06:08 -07:00

test_path_graph_integration.py

test: expanded test suite for v0.9.0 modules

2026-03-17 18:07:18 -07:00

test_path_resolution.py

test: expanded test suite for v0.9.0 modules

2026-03-17 18:07:18 -07:00

test_rf_scope_correlation.py

fix(path): never attribute an uncorrelated packet's route (#80)

2026-08-21 22:45:05 -07:00