fix: Check YAML kind field before parsing agent configs

[Gops123]

Summary

Fixes #89

When loading agents from a directory, the daemon now checks the kind field before attempting to parse files as Agent configs. This prevents confusing errors when the directory contains non-Agent YAML files (Trigger, Fleet, Flow, etc.).

Problem

Previously, when the agents directory contained a Trigger file (or any non-Agent YAML), the daemon would try to parse it as an Agent and fail with:

Error: Failed to parse agent config: pr_review.yaml

  Field: spec
  Error: missing field `model`

This was confusing because:

1. The file is a valid Trigger, not an invalid Agent
2. The error message didn't clarify that the file should be in a different directory

Solution

Added a yaml_file_has_kind helper function that checks the kind field before attempting full deserialization:

fn yaml_file_has_kind(path: &Path, expected_kind: &str) -> bool {
    #[derive(Deserialize)]
    struct KindCheck {
        kind: Option<String>,
    }
    // ... parse and check kind
}

Changes

• crates/aof-core/src/registry.rs:

  • Added yaml_file_has_kind helper function
  • Updated AgentRegistry.load_directory to skip non-Agent files

• crates/aof-triggers/src/handler/mod.rs:

  • Added TriggerHandler::yaml_file_has_kind method
  • Updated load_agents_from_directory to check kind before parsing

Testing

# Create a directory with mixed YAML files
mkdir /tmp/mixed-agents
cp examples/agents/devops.yaml /tmp/mixed-agents/
cp examples/triggers/slack-starter.yaml /tmp/mixed-agents/pr_review.yaml

# Run daemon - now works without error
aofctl serve --agents-dir /tmp/mixed-agents
# Logs: "Skipping non-Agent file: /tmp/mixed-agents/pr_review.yaml"
# Logs: "Loaded agent 'devops' from /tmp/mixed-agents/devops.yaml"

Checklist

• Code follows project style
• Tests pass
• Documentation N/A (internal behavior change)

🤖 Generated with Claude Code

[Gops123]

/review