Mark rate-limit as experimental

[Copilot]

The rate-limit feature now emits an experimental warning during workflow compilation.

Changes

• Compiler warning emission: Added experimental warning in pkg/workflow/compiler.go when workflowData.RateLimit is configured, following the same pattern as sandbox-runtime, safe-inputs, and plugins features
• Integration test: Created rate_limit_experimental_warning_test.go to verify warning behavior across different rate-limit configurations

Implementation

// Emit experimental warning for rate-limit feature
if workflowData.RateLimit != nil {
    fmt.Fprintln(os.Stderr, console.FormatWarningMessage("Using experimental feature: rate-limit"))
    c.IncrementWarningCount()
}

Output Example

$ gh aw compile workflow-with-rate-limit.md
⚠ Using experimental feature: rate-limit
✓ workflow-with-rate-limit.md (25.3 KB)

Workflows without rate-limit configuration show no warning.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Pull request overview

Adds an “experimental feature” warning for workflows that configure rate-limit, aligning rate-limit with other experimental frontmatter features during compilation.

Changes:

• Emit a formatted warning to stderr (and increment compiler warning count) when workflowData.RateLimit is set.
• Add an integration test covering warning emission across multiple rate-limit configurations and the absence of warnings when rate-limit is not configured.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
pkg/workflow/compiler.go	Emits an experimental warning during validation when rate-limit frontmatter is present.
pkg/workflow/rate_limit_experimental_warning_test.go	Integration test verifying the warning appears only when rate-limit is configured.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.