[WIP] Add deprecated: true flag to rate-limit and inline-sub-agents - #34776

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

---

This section details on the original issue you should resolve

<issue_title>[deep-report] [quick-win] Add deprecated: true flag to rate-limit and inline-sub-agents in main_workflow_schema.json</issue_title>
<issue_description>### Problem

Per the Schema Consistency audit (discussion github/gh-aw#34599), the deprecation-warning infrastructure in pkg/workflow/compiler_orchestrator_tools.go:436-460 walks the schema and emits user-visible warnings for every field tagged deprecated: true. Two top-level fields with deprecation language in their description are missing the flag:

• rate-limit — description says "Legacy alias for 'user-rate-limit'. Prefer 'user-rate-limit' with 'max-runs-per-window'." — no deprecated: true
• inline-sub-agents — description says "Deprecated switch for inline sub-agent support..." — no deprecated: true

Result: users using these get silent acceptance / a debug-only log instead of a console warning + IDE strikethrough.

Suggested Fix

In the schema JSON, add "deprecated": true to both field definitions. 14 nested fields in the same schema already follow this convention.

Impact

Low-risk one-line additions × 2. Restores the deprecation warning path the team already invested in building.

Effort

~15 min — locate fields in pkg/workflow/main_workflow_schema.json, add deprecated: true, run schema/compiler tests.

Suggested Agent

Any coding agent. Pure config edit.

---

Source: DeepReport Intelligence Briefing 2026-05-25

Generated by 🔬 DeepReport - Intelligence Gathering Agent · opus47 7.7M · ◷

• expires on May 27, 2026, 3:47 PM UTC

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