AntFleet

Disagreement · 89395cd4-anthropic-6

Skill name 'rss-feed' enabled but referenced inconsistently — comment claim 'must be last' is misleading

solo Opus
repo 6f7fc663·PR #21·reviewed 1 week ago

Opus finding

Skill name 'rss-feed' enabled but referenced inconsistently — comment claim 'must be last' is misleading

lowdocs-gapmedium
  • aeon.yml:169-171
The comment 'Fallback (must be last)' implies ordering matters for heartbeat. Nothing else in the file documents *why* ordering matters or what breaks if it isn't last (YAML maps are unordered semantically; if the scheduler relies on document order, that is itself a fragile contract). If a downstream fork-cohort or skill-graph parser reads aeon.yml with a standard YAML loader, ordering is preserved but not guaranteed semantically. A future contributor inserting a new skill after `heartbeat` would not know what they're breaking. Either the comment is wrong (no ordering requirement) or the comment is hiding load-bearing behavior that should be documented in CLAUDE.md / aeon-runtime docs.

Recommendation

Clarify the comment: link to the runtime code that requires this ordering, or remove the 'must be last' claim if it's superstition.

Other reviewer

The other reviewer flagged nothing in this file/line range.

Why this didn't post

This finding didn't meet AntFleet's unanimous agreement threshold. Both frontier models review every PR independently; only findings they both flag with the same severity and category are posted to the PR. This one fell through.

read the methodology →

From the same review

These findings passed the unanimous gate on the same PR review. The disagreement above was filtered out; the findings below were posted.