Krzysztof kuhy Rudnicki 0717df646a Rebuild the command table on demand, and survive a tag whose file is gone ... The registry used to be built once, inline in build_bot, so every change to the data behind it -- a person tagged in the web UI, an alias, soon a command switched off from the management page -- meant restarting the unit. That is cheap and lossless, but it is a deploy step somebody has to remember, and a 21:37 report can land in the middle of it. Now the registration sequence lives in wiring.build_registry, and RegistryHolder runs it again on POST /_reload: the new table is built whole and swapped in with one assignment, never patched in place, so a duplicate trigger is found before anything the dispatcher reads has changed. Bad data (ConfigError, DuplicateTriggerError) keeps the previous table and answers 409 with the reason; a programming error still surfaces as a 500. scripts/reload.sh wraps it, with --code for the restart a Python change needs, and an optional command to type in testbot so "reloaded" means "answered". No Python hot-reload on purpose. The loader change is what makes deploying this safe: two rows in the live tags.json name files that are no longer in media/, and load_pack refused them, so the next restart would have looped on ConfigError. A stale tag is drift in a file a page edits mid-session, not a broken album -- it is now skipped with a warning naming it. A tag that reaches outside the album is still refused. pack_load.py split at the 250-line cap; pack_tags.py is the half whose checks are not all fatal. Proven offline in scripts/e2e.sh: !delta is unknown, a fifth person is tagged into the synthetic pack, scripts/reload.sh runs, and the same process posts delta's photo. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-09-04 10:14:39 +02:00
..
proofs	Rebuild the command table on demand, and survive a tag whose file is gone	2026-09-04 10:14:39 +02:00
scenarios	feat: no photo reaches the album from the chat until somebody approves it	2026-09-04 09:47:42 +02:00
__init__.py	feat: rewrite the bot so it runs, and gate it like the other repos	2026-08-29 13:05:42 +02:00
cli.py	feat: two commands that answer with somebody else's work	2026-08-31 21:32:07 +02:00
routes_account.py	feat: discover groups from the account, so adding the bot is the whole setup	2026-08-29 15:30:08 +02:00
routes_api.py	feat: add a photo to the album from the chat, tagged, stripped and verified	2026-08-31 11:20:00 +02:00
routes_control.py	feat: add a photo to the album from the chat, tagged, stripped and verified	2026-08-31 11:20:00 +02:00
routes_fixtures.py	feat: two commands that answer with somebody else's work	2026-08-31 21:32:07 +02:00
routes_groups.py	feat: discover groups from the account, so adding the bot is the whole setup	2026-08-29 15:30:08 +02:00
scenario.py	feat: add a photo to the album from the chat, tagged, stripped and verified	2026-08-31 11:20:00 +02:00
server.py	feat: discover groups from the account, so adding the bot is the whole setup	2026-08-29 15:30:08 +02:00
state.py	feat: add a photo to the album from the chat, tagged, stripped and verified	2026-08-31 11:20:00 +02:00