Bug Fix

A top-level command field was accepted by schema validation but ignored by compilation, creating a silent misconfiguration path. This change aligns schema behavior with actual parser/compiler semantics (on.slash_command / deprecated on.command under on).

What was the bug?

• Top-level command was defined in pkg/parser/schemas/main_workflow_schema.json but not consumed anywhere in frontmatter extraction.
• Workflows using:

  command: my-cmd

  could validate successfully while never triggering as intended.

How did you fix it?

• Schema alignment
  • Removed top-level command from /pkg/parser/schemas/main_workflow_schema.json.
• Regression coverage
  • Added TestValidateMainWorkflowFrontmatterWithSchemaAndLocation_RejectsTopLevelCommand in /pkg/parser/schema_location_test.go to enforce rejection of command at the top level.

Testing

• Added targeted validation coverage for the rejected shape:

frontmatter := map[string]any{
  "on":      "push",
  "command": "my-cmd",
}
err := ValidateMainWorkflowFrontmatterWithSchemaAndLocation(frontmatter, "/test/workflow.md")
// expects: Unknown property: command