Remove stale OpenCode service-failure monitor entry on Vega #225

New issue

Open

opened 2026-09-12 19:49:24 +01:00 by nimmo · 0 comments

nimmo commented

2026-09-12 19:49:24 +01:00

Owner

Problem

The composed services.serviceFailureMonitor.services list for Vega still contains opencode, but the OpenCode web-server systemd service was removed in commit c7e0a683. Current source has no systemd.services.opencode implementation; the remaining OpenCode references are CLI/package configuration.

Because the failure-monitor module applies unitConfig.OnFailure with lib.genAttrs, a stale name can create or modify a unit definition that no longer corresponds to an owned service and makes monitoring coverage misleading. AGENTS.md also still says Vega posts failures for opencode.

Scope

Remove the stale Vega failure-monitor entry.
Update the corresponding AGENTS.md topology statement.
Evaluate Vega's composed monitored-service list and ensure every entry maps to an intentionally owned unit.
Add a small assertion or regression check if practical so retired service names cannot linger silently.

Acceptance criteria

opencode is absent from Vega's composed failure-monitor list.
Every remaining composed name maps to an intended unit.
AGENTS.md matches current coverage.
Appropriate evaluation/checks pass.

Discovered while verifying the Monitoring and Service Investigation runbook for wiki issue #222 at source commit 556df88494.

## Problem The composed `services.serviceFailureMonitor.services` list for Vega still contains `opencode`, but the OpenCode web-server systemd service was removed in commit c7e0a683. Current source has no `systemd.services.opencode` implementation; the remaining OpenCode references are CLI/package configuration. Because the failure-monitor module applies `unitConfig.OnFailure` with `lib.genAttrs`, a stale name can create or modify a unit definition that no longer corresponds to an owned service and makes monitoring coverage misleading. `AGENTS.md` also still says Vega posts failures for `opencode`. ## Scope - Remove the stale Vega failure-monitor entry. - Update the corresponding AGENTS.md topology statement. - Evaluate Vega's composed monitored-service list and ensure every entry maps to an intentionally owned unit. - Add a small assertion or regression check if practical so retired service names cannot linger silently. ## Acceptance criteria - [ ] `opencode` is absent from Vega's composed failure-monitor list. - [ ] Every remaining composed name maps to an intended unit. - [ ] AGENTS.md matches current coverage. - [ ] Appropriate evaluation/checks pass. Discovered while verifying the Monitoring and Service Investigation runbook for wiki issue #222 at source commit 556df88494686003b1c4f20c8e0b99b5afc16a6e.

nimmo added this to the Wiki Knowledge Architecture Rebuild milestone

2026-09-12 19:49:24 +01:00

nimmo added the

host:vega

project:wiki-rebuild

labels

2026-09-12 19:49:24 +01:00

nimmo referenced this issue

2026-09-12 19:51:47 +01:00

[Wiki 4/5] Rebuild operational runbooks and the engineering handbook #222

nimmo referenced this issue

2026-09-14 07:36:50 +01:00