[deep-report] Remove unused top-level `command` schema field (silent acceptance bug)

[github-actions]

Context

Identified by DeepReport intelligence briefing 2026-05-12 (Schema Consistency Check #31645).

pkg/parser/schemas/main_workflow_schema.json declares a top-level command field:

"command": { "type": "string", "description": "Command name for the workflow" }

But no parser or compiler code reads frontmatter["command"] as a top-level key (verified via grep across pkg/workflow/ and pkg/parser/). The actual command-trigger config is read from on.slash_command (preferred) or deprecated on.command in pkg/workflow/frontmatter_extraction_yaml.go.

Impact: A user could write command: my-cmd at the top level, schema validation accepts it, and the value is silently ignored at compile time — producing a workflow that does nothing they expect.

Expected Impact

• Eliminates a class of silent misconfiguration bugs
• Brings schema into honest alignment with parser behavior
• Quick cleanup, very low risk

Suggested Approach

• Remove the top-level command property from pkg/parser/schemas/main_workflow_schema.json
• Verify no workflow under .github/workflows/ uses a top-level command: key (already confirmed by report)
• Run make agent-finish to validate

Suggested Agent

Any coding agent.

Estimated Effort

30 minutes of agent time.

---

Source: DeepReport 2026-05-12 #aw_dr4

Generated by DeepReport - Intelligence Gathering Agent · ● 9.5M · ◷

• expires on May 14, 2026, 3:42 PM UTC