Add maxLength constraints to workflow metadata fields

[Copilot]

Schema consistency analysis identified missing maxLength constraints on core workflow metadata fields, allowing unbounded input that could cause issues with GitHub Actions processing.

Changes

• name: maxLength 256 (consistent with GitHub Actions workflow name limits)
• description: maxLength 10,000 (reasonable upper bound for YAML comments)
• tracker-id: maxLength 128 (balances searchability with practical identifier length)

Validation

Schema validation now catches oversized metadata at compile time:

✗ error: at '/name': maxLength: got 279, want 256. Expected format: "string"

Test coverage added for boundary conditions (at-limit and over-limit values) for all three fields.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[deep-report] Add maxLength constraints for core workflow metadata fields in schema</issue_title>
<issue_description>### Description
Schema consistency analysis highlights missing maxLength constraints for name, description, and tracker-id in pkg/parser/schemas/main_workflow_schema.json. Add reasonable maxLength bounds (e.g., name 256, tracker-id 128, description 10000) to improve validation and guard against overly long metadata.

Expected Impact

Improves schema robustness, reduces risk of oversized metadata, and delivers clearer validation errors.

Suggested Agent

Schema Consistency / Validation agent

Estimated Effort

Medium (1-4 hours)

Data Source

DeepReport Intelligence Briefing - 2026-01-27 (§21402586299); Schema Consistency Report discussion githubnext/gh-aw#11976.

AI generated by DeepReport - Intelligence Gathering Agent

Comments on the Issue (you are @copilot in this section)

• Fixes [deep-report] Add maxLength constraints for core workflow metadata fields in schema #12044

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.