https://gitlab.synchro.net/main/sbbs/-/commit/35dc591dc72f62ac23cc6ded
Modified Files:
xtrn/bublbogl/install-xtrn.ini xtrn/chickendelivery/install-xtrn.ini xtrn/dicewarz2/install-xtrn.ini xtrn/druglord/install-xtrn.ini xtrn/fatfish/install-xtrn.ini xtrn/gooble/install-xtrn.ini xtrn/lemons/install-xtrn.ini xtrn/maze/install-xtrn.ini xtrn/oneliners/install-xtrn.ini xtrn/starstocks/install-xtrn.ini xtrn/startrek/install-xtrn.ini xtrn/synchronetris/install-xtrn.ini xtrn/syncwall/install-xtrn.ini xtrn/synkroban/install-xtrn.ini xtrn/synthkart/install-xtrn.ini xtrn/thirsty/install-xtrn.ini xtrn/uberblox/install-xtrn.ini xtrn/wordem/install-xtrn.ini
Log Message:
xtrn: stop 18 door installers skipping their JSON service registration

install-xtrn.js threads a single `done` flag through every one of its
installer loops (programs, [copy:], [ini:], [service:], [exec:] and
[eval:]), so `done = true` means "process no further installer items of
any kind" -- not "finished with this configuration file", which is what
these files evidently intended.

Eighteen doors carried it on the server-config [ini:] section that sits immediately before `!include install-json-service.ini`. That halted the installer before both the trailing [ini:json-service.ini:<code>] section
and the [service:JSON] section pulled in by the include, so the door
installed and reported success while its JSON data backend was never
registered at all.

Verified against a throwaway ctrl directory with [JSON] and the door
sections removed first: beforehand a successful install left ctrl/json-service.ini without the door's section; afterwards both that
section and ctrl/services.ini [JSON] are created.

zzt and avatar_chat also set `done`, but each on its file's final
section, where it changes nothing; those are left alone.

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

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net