Sermo

Use when running safe Sermo validation or exploratory tests on remote Linux servers over SSH, using .env.ssh as the source of truth, local GOAMD64=v1 builds, staged all-host runs, temporary /tmp validation, or explicit remote installations under /etc/sermo. Covers active-services-only config, unsupported active-service reports, all safely discoverable host watches, dry-run deployments, storage under 5 percent free with 5G expand, fstab-backed local/network/USB mount units, Docker containers, libvirt/QEMU virtual machines, SMART daily, hdparm every 6h, Web UI on 0.0.0.0:9797 with startup/readiness/access timing, reusable scripts under scripts/remote-deploy, and safe alert/notification checks that must not execute hooks or alter server behavior.

Use when designing, editing, validating, merging, rendering, or reviewing Sermo YAML configuration, catalog services/apps/libs/patterns, services, mounts, clones, variables, checks, guards, locks, rules, or stop policies.

Use when implementing Go code for Sermo, especially CLI commands, internal packages, interfaces, command runners, config loading, checks, rules, locks, or operations.

Use when creating or reviewing Sermo Linux packaging, systemd units, OpenRC init scripts, Gentoo ebuilds, install paths, permissions, runtime directories, or service startup behavior.

Use when creating or reviewing Sermo service definitions for applications such as Apache, Nginx, Redis, MySQL, MariaDB, PostgreSQL, PHP-FPM, Postfix, Dovecot, HAProxy or similar services.

Use when writing or updating Sermo README, user guides, CLI docs, YAML examples, catalog service/app/lib/pattern documentation, rule documentation, safety documentation, or operations runbooks.

Use when adding or reviewing tests for Sermo, especially config resolution, backend detection, rule evaluation, locks, guards, process discovery, and safe operations.

Use for any Sermo change involving start, stop, restart, reload, resume, kill, signal, process matching, locks, preflight, guards, remediation rules, or automatic actions.

Use when implementing or reviewing Sermo process discovery, pidfile parsing, /proc traversal, cgroup usage, child process trees, residual process detection, or signaling policies.

Use when working on Sermo systemd/OpenRC integration, backend autodetection, service status normalization, systemctl/rc-service command behavior, or packaging service units.

Use when designing or implementing Sermo rules, condition trees, and/or/not logic, for cycles, within cycles, remediation actions, alerts, or guard rules.

Use when planning Sermo architecture, package boundaries, daemon/CLI design, config flow, or major feature sequencing. Do not use for small localized code edits.