Jason Woltje
80c3680ccb
Rename the `rails/` directory to `tools/` for agent discoverability — agents frequently failed to locate helper scripts due to the non-intuitive directory name. Add backward-compat symlink `rails/ → tools/`. New tool suites: - Authentik: auth-token, user-list, user-create, group-list, app-list, flow-list, admin-status (8 scripts) - Coolify: team-list, project-list, service-list, service-status, deploy, env-set (7 scripts) - Woodpecker: pipeline-list, pipeline-status, pipeline-trigger (3 stubs) - GLPI: session-init, computer-list, ticket-list, ticket-create, user-list (6 scripts) - Health: stack-health.sh — stack-wide connectivity check Infrastructure: - Shared credential loader at tools/_lib/credentials.sh - install.sh creates symlink + chmod on tool scripts - All ~253 rails/ path references updated across 68+ files Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Mosaic Matrix Orchestrator Rail
Runtime-agnostic orchestration rail for delegating work to worker agents and enforcing mechanical quality gates.
Purpose
- Decouple orchestration from any single agent runtime feature set
- Persist state in repo-local
.mosaic/orchestrator/files - Emit structured events for Matrix transport and audit trails
- Enforce rails before marking tasks complete
Components
protocol/- JSON schemas for task/event payloadscontroller/mosaic_orchestrator.py- deterministic controller loopadapters/- runtime adapter guidance
Repo Contract
The controller expects this layout in each bootstrapped repo:
.mosaic/orchestrator/
config.json
tasks.json
state.json
events.ndjson
logs/
results/
Quick Start
From a bootstrapped repo:
~/.config/mosaic/bin/mosaic-orchestrator-matrix-cycle
~/.config/mosaic/bin/mosaic-orchestrator-run --once
~/.config/mosaic/bin/mosaic-orchestrator-drain
Continuous loop:
~/.config/mosaic/bin/mosaic-orchestrator-run --poll-sec 10
Sync from docs/TASKS.md to queue:
~/.config/mosaic/bin/mosaic-orchestrator-sync-tasks --apply
Set worker command when needed:
export MOSAIC_WORKER_EXEC="codex -p"
# or
export MOSAIC_WORKER_EXEC="opencode -p"
Publish new orchestrator events to Matrix:
~/.config/mosaic/bin/mosaic-orchestrator-matrix-publish
Consume Matrix task messages into tasks.json:
~/.config/mosaic/bin/mosaic-orchestrator-matrix-consume
Matrix Note
This rail writes canonical events to .mosaic/orchestrator/events.ndjson.
The Matrix transport bridge publishes those events into the configured control room
and can consume task commands from that room.
Task injection message format (room text):
!mosaic-task {"id":"TASK-123","title":"Fix bug","command":"echo run","quality_gates":["pnpm lint"]}