feat(ansible): version-sync role for agentic-os hook blocks (warn on drift + missing rules) #277

Open
opened 2026-06-08 21:51:37 +00:00 by coilysiren · 0 comments
Owner

What

Author an ansible role that converges every workspace repo's managed agentic-os hook block, so version drift and missing rules stop accumulating silently. This is the fleet-rollout half of the code-comments cleanup (catalogue built 2026-06-08, per-repo content issues filed in each repo).

Why

The 2026-06-08 sweep found the fleet spread across agentic-os revs from v0.6.0 to v0.16.0, with code-comments enforcement varying by pin (YAML enforcement only landed in v0.14.0). Several repos never listed - id: code-comments in their managed block at all. The drift is invisible until someone runs a sweep by hand.

Scope

  • Converge each repo's managed agentic-os rev toward the latest release.
  • Ensure the managed hook block lists the expected rule set, including code-comments.
  • Warn, do not fail, on version drift (repo pinned below latest).
  • Warn, do not fail, on a missing expected rule (rule absent from the managed block).
  • Both signals at warning level so the role reports the gap without blocking convergence runs.

Note - trivially-tiny repos folded in here

Eight repos carry only 2 hand-written .coily/coily.yaml comment lines each after the managed-marker false-positive is removed (tracked in the agentic-os issue): gauntlet, luca, atmosphere, factorio-mods, message-ops, scoop-bucket, sirens-discord-ops, coilysiren. They did not get their own content issue. When this role bumps their pin and code-comments starts enforcing YAML, the hook will surface those two lines on the next commit. Fix inline then.

Done when

  • an ansible role converges managed aos revs and rule sets across the workspace
  • the role emits warning-level output on version drift and on missing expected rules
## What Author an ansible role that converges every workspace repo's managed agentic-os hook block, so version drift and missing rules stop accumulating silently. This is the fleet-rollout half of the code-comments cleanup (catalogue built 2026-06-08, per-repo content issues filed in each repo). ## Why The 2026-06-08 sweep found the fleet spread across agentic-os revs from v0.6.0 to v0.16.0, with `code-comments` enforcement varying by pin (YAML enforcement only landed in v0.14.0). Several repos never listed `- id: code-comments` in their managed block at all. The drift is invisible until someone runs a sweep by hand. ## Scope * Converge each repo's managed agentic-os `rev` toward the latest release. * Ensure the managed hook block lists the expected rule set, including `code-comments`. * Warn, do not fail, on version drift (repo pinned below latest). * Warn, do not fail, on a missing expected rule (rule absent from the managed block). * Both signals at warning level so the role reports the gap without blocking convergence runs. ## Note - trivially-tiny repos folded in here Eight repos carry only 2 hand-written `.coily/coily.yaml` comment lines each after the managed-marker false-positive is removed (tracked in the agentic-os issue): gauntlet, luca, atmosphere, factorio-mods, message-ops, scoop-bucket, sirens-discord-ops, coilysiren. They did not get their own content issue. When this role bumps their pin and `code-comments` starts enforcing YAML, the hook will surface those two lines on the next commit. Fix inline then. ## Done when * an ansible role converges managed aos revs and rule sets across the workspace * the role emits warning-level output on version drift and on missing expected rules
coilysiren added
P3
and removed
P2
labels 2026-06-17 08:39:39 +00:00
coilyco-ops added
P4
and removed
P3
labels 2026-07-10 09:00:16 +00:00
Sign in to join this conversation.
No description provided.