Map workflow semantics for WHAT/WHEN/WHERE catalogs

[github-actions]

Scope: Translate existing workflow concepts (triggers, schedules, safe-outputs) into the shared catalog, aligned with current trigger/frontmatter vocabulary and safe-outputs concepts already used by the compiler.

Acceptance criteria:

• Catalog covers initial supported scenarios (scheduled/triggered flows, safe-output routing inferable from earlier answers).
• Each option maps clearly to prompt-generation intent and doesn't contradict existing terminology.

Notes: Prefer a small, high-confidence initial catalog over exhaustive coverage.

Context: Parent #53498 · Phase 1 — Shared model and prompt contract · Size: M · Depends on: #aw_t1 · Owner: Fenster

Created from /squad plan accept on #53498.
Related to #53498

Generated by 🤖 Squad for #53498 · auto · 65 AIC · ⌖ 3.95 AIC · ⊞ 35.6K · ◷
_{Comment /squad to run again}

_{Add this agentic workflow to your repo}

To install this agentic workflow, run

gh aw add bradygaster/squad/workflows/squad.md@dev

[github-actions]

✅ Checked the repository — this is already implemented, no PR needed.

Evidence: Issue #53514 asks for a WHAT/WHEN/WHERE catalog translating workflow concepts (triggers, schedules, safe-outputs) into a shared data model. That catalog already exists in full:

• docs/public/schemas/wizard-data-model.schema.json — normative JSON Schema defining goalCategories (WHAT), triggerOptions (WHEN), destinationOptions (WHERE), and promptTemplate.
• docs/public/schemas/wizard-data-model.example.json — conforming example with 3 goal categories (issue automation, scheduled report, PR review assistant), 7 trigger options, and 4 destination options.
• docs/src/content/docs/specs/wizard-data-model-specification.md — the formal spec (v1.0.0) describing conditional progression (WHAT → WHEN → WHERE) and future CLI reuse.

Acceptance criteria verification:

1. "Catalog covers initial supported scenarios (scheduled/triggered flows, safe-output routing inferable from earlier answers)" — ✅ Covered: schedule-daily/schedule-weekly/manual-dispatch (scheduled), on-issue-opened/on-issue-comment/on-pull-request/slash-command (triggered), and each destinationOption carries inferFromTriggerTypes so WHERE can be inferred from the selected trigger's type.
2. "Each option maps clearly to prompt-generation intent and doesn't contradict existing terminology" — ✅ Verified against pkg/parser/schemas/main_workflow_schema.json: triggerOption.type enum values (schedule, issues, pull_request, issue_comment, workflow_dispatch, slash_command, discussion, push, other) match the compiler's trigger vocabulary exactly, and destinationOption.safeOutputType values (add-comment, add-labels, create-pull-request, create-discussion) match real safe-outputs handler keys in the compiler schema.

No dependency issue was resolvable (Depends on: #aw_t1 is an unresolved placeholder, not a real issue reference), and no other open blockers were found. Since the deliverable already satisfies both acceptance criteria, I'm not opening an empty/no-op pull request.

Generated by Squad Implement Worker · auto · 75 AIC · ⌖ 2.37 AIC · ⊞ 11K · ◷

_{Add this agentic workflow to your repo}

To install this agentic workflow, run

gh aw add bradygaster/squad/workflows/squad-implement-worker.md@a70c752010f8adfb33f06c7aafb32db09aab1060