templates/provider/ held copies of matrix-bot-baibot's LLM provider templates
(anthropic, groq, mistral, openai), added by accident with the role.
Nothing renders them and the variables they use are defined nowhere.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
baibot no longer has an image_generation.style setting for its OpenAI provider (it ignores it),
so matrix_bot_baibot_config_agents_static_definitions_openai_config_image_generation_style
is removed (and reported if still set).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
baibot now releases as CalVer tags (vYYYY.MM.DD.N); v2026.11.02.1 supports OpenAI's Realtime models for text-to-speech.
OpenAI shuts down tts-1, tts-1-hd and gpt-4o-mini-tts on 2027-01-06,
so the OpenAI agent now defaults to gpt-realtime-2.1-mini with the cedar voice (Realtime has no onyx).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The unit creates the container and attaches additional networks in later ExecStartPre steps.
Verify could inspect it in between and flakily fail the network contract assertion.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
claude-sonnet-4-5 retires on 2026-11-30. baibot now uses Anthropic API
version 2026-10-21, which rejects a temperature on every model, so
matrix_bot_baibot_config_agents_static_definitions_anthropic_config_text_generation_temperature
is removed (and reported if still set). The default max response tokens
go from 8192 to 16384, since thinking tokens count against them.
Needs the baibot release that moves to API version 2026-10-21.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
llama3-70b-8192 was shut down by Groq on 2025-08-30. Also point the
model list link at console.groq.com.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Root runs register-user and mas-cli from the bin path, and both scripts were owned by the matrix user.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Root runs register-user and s3-storage-provider's migrate (from a systemd timer) from bin paths under them.
Whoever owns a parent of a bin path could rename it (even a root-owned one) and put another in its place.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Whoever owns it could rename any service's directory (even a root-owned one) and put another in its place.
On Synology, the recursive chown now compares only the base path's gid (its uid is root's now) and runs before the base paths are ensured, so it doesn't undo their ownership.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This aligns gmessages, gvoice, linkedin, meta-instagram, meta-messenger
and slack with the upstream bridgev2 default (true), like ef6ad8cfa did
for mautrix-signal. The false value was a leftover from the pre-bridgev2
configs.
Fixes#5701
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The template still carried false from the pre-bridgev2 configuration.
bridgev2's example config and the mautrix-whatsapp role use true. With
false, double-puppeted Signal DMs never reach m.direct, so clients list
them outside the DM section and do not fall back to the contact's avatar.
Refs #5701
`matrix_synapse_workers_generic_worker_client_server_endpoints` and
`matrix_synapse_workers_generic_worker_federation_endpoints` dropped the
non-matching entries with `difference([none])`. ansible-core implements
`difference` as `list(set(a) - set(b))`, so the result follows Python's
per-process string hash seed and comes out in a different order on every
run.
The reverse-proxy companion renders these lists as nginx `location`
blocks, so its `conf.d/matrix-synapse-reverse-proxy-companion.conf`
changed, and the companion restarted, on every run, even with nothing
else to change.
`reject('none')` drops the same entries and keeps the order of
`matrix_synapse_workers_generic_worker_endpoints`. All these locations
point to the same upstream, so routing is unchanged.
With conditional restart (install-* tags), the homeserver entry for
Synapse fell through to `restart_necessary: true`, and the worker
entries carried no flag at all, which systemd_service_manager also
treats as "restart". Every install-all and install-service synapse
therefore restarted Synapse and all of its workers, even when nothing
had changed. Without workers, systemd also restarted most bridges and
bots, whose units require matrix-synapse.service.
Compute matrix_synapse_restart_necessary from the tasks that install
what Synapse runs: homeserver.yaml, the initial config and signing key,
the log config, labels and systemd service, the container image (pulled,
self-built or customized), each worker's config, labels and systemd
service, and the downloaded or cloned extension modules. Workers follow
the same decision, as they read the same files.
Synapse also mounts the appservice registration files written by other
roles. Add matrix_homeserver_app_service_registration_changed in
group_vars/matrix_servers, which checks the registered result of each
task installing one of the files listed in
matrix_homeserver_container_extra_arguments_auto, so that a changed
registration still restarts Synapse and its workers. The double-puppet
role did not register its result; it does now.
The Synapse image pull and three extension downloads all registered
their result as `result`. The downloads run first, so the pull's result
overwrote theirs before the restart decision could read them; they now
use role-prefixed names.
With Synapse workers enabled, inject_worker.yml appends each worker's
service to devture_systemd_service_manager_services_list_auto with
set_fact. That templates the whole list, including every service's
restart_necessary value, when the matrix-synapse role initializes, and
the resulting fact outranks group_vars. Services whose restart flag is
set after that point are then only started, not restarted, on install-*
runs even when their configuration changed. That includes the
matrix-synapse role's own reverse-proxy companion, Goofys and S3 storage
provider timer, and the services of every later role that sets a restart
flag (Element, Grafana, Prometheus, Traefik and others).
Collect worker services in matrix_synapse_worker_systemd_services_list
and append it to the auto list in group_vars/matrix_servers, like the
other entries there, so the list stays lazy.
Include inject_worker.yml once and loop inside each task instead of
including it once per worker. With 19 workers this cuts the step from
26.2 s to 5.3 s on ansible-core 2.20.1 (controller-only, one run). Also
fix two stream-writer failure messages that referenced the undefined
`item`, and report all missing worker properties in one message.
