[BUG] .roomodes doesn't align with published JSON schema

[algorhythm85]

Problem (one or two sentences)

When I add # yaml-language-server: $schema=https://www.schemastore.org/roomodes.json to the top of a .roomodes file, the documented structure does not validate against it. If I modify the file to conform to the schema, Roo no longer seems to understand it.

Context (who is affected and when)

Developers who want to declare a schema with which to validate their configuration.

Reproduction steps

1. Export a built-in Roo mode (e.g. architect-export.yaml)

2. In VSCode, add the following at the top of the file:

   # yaml-language-server: $schema=https://www.schemastore.org/roomodes.json
   ---

3. Observe validation errors

   # yaml-language-server: $schema=https://www.schemastore.org/roomodes.json
   ---
   customModes:
     - slug: architect
       name: 🏗️ Architect
       # ...
       # Property description is not allowed. 
       description: Plan and design before implementation
       # ...
       groups:
         - read
         # Incorrect type. Expected "string | Edit Permission with Path Restrictions".
         # Value is not accepted. Valid values: "read", "edit", "browser", "command", "mcp".
         - - edit
           - fileRegex: \.md$
             description: Markdown files only
         - mcp
       # Property source is not allowed.
       source: project

According to the schema, a valid groups: configuration should look something like:

    groups:
      - read
      - type: edit
        allowedPaths: [\.md$]
      - mcp

Expected result

The configuration structure validates against the JSON schema without errors.

Actual result

There are multiple validation errors.

Variations tried (optional)

No response

App Version

v3.50.4

API Provider (optional)

None

Model Used (optional)

No response

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

<details>
<summary>VSCode Problems Export</summary>


[{
	"resource": "<project path>/architect-export.yaml",
	"owner": "_generated_diagnostic_collection_name_#0",
	"code": "513",
	"severity": 8,
	"message": "Property description is not allowed.",
	"source": "yaml-schema: Custom Mode",
	"startLineNumber": 15,
	"startColumn": 5,
	"endLineNumber": 15,
	"endColumn": 16,
	"modelVersionId": 3,
	"origin": "extHost2"
},{
	"resource": "<project path>/architect-export.yaml",
	"owner": "_generated_diagnostic_collection_name_#0",
	"severity": 8,
	"message": "Incorrect type. Expected \"string | Edit Permission with Path Restrictions\".",
	"source": "yaml-schema: Simple Permission | Edit Permission with Path Restrictions",
	"startLineNumber": 74,
	"startColumn": 9,
	"endLineNumber": 77,
	"endColumn": 1,
	"modelVersionId": 3,
	"origin": "extHost2"
},{
	"resource": "<project path>/architect-export.yaml",
	"owner": "_generated_diagnostic_collection_name_#0",
	"code": "1",
	"severity": 8,
	"message": "Value is not accepted. Valid values: \"read\", \"edit\", \"browser\", \"command\", \"mcp\".",
	"source": "yaml-schema: Simple Permission",
	"startLineNumber": 74,
	"startColumn": 9,
	"endLineNumber": 77,
	"endColumn": 1,
	"modelVersionId": 3,
	"origin": "extHost2"
},{
	"resource": "<project path>/architect-export.yaml",
	"owner": "_generated_diagnostic_collection_name_#0",
	"code": "513",
	"severity": 8,
	"message": "Property source is not allowed.",
	"source": "yaml-schema: Custom Mode",
	"startLineNumber": 78,
	"startColumn": 5,
	"endLineNumber": 78,
	"endColumn": 11,
	"modelVersionId": 3,
	"origin": "extHost2"
}]


</details>

[roomote-v0]

I've analyzed this issue and here's my proposed implementation plan:

Problem Summary

The SchemaStore JSON schema at https://www.schemastore.org/roomodes.json does not match the actual .roomodes configuration format that Roo Code uses internally. There are three key discrepancies:

1. Missing properties on customMode: The schema lacks description and source (both optional in the actual type).
2. Wrong groups format: The schema defines edit permissions as { type: "edit", allowedPaths: [...] }, but Roo Code actually uses a tuple format: ["edit", { fileRegex: "\\\.md$", description: "Markdown files only" }].
3. Property naming mismatch: The schema uses allowedPaths/disallowedPaths arrays, while the actual code uses a single fileRegex string pattern plus an optional description.

Proposed Fix

Add a correct JSON schema file to this repository that accurately reflects the actual .roomodes format as defined in packages/types/src/mode.ts:

1. Create schemas/roomodes.json -- a JSON Schema (draft-07) that matches the real internal types:

   • customMode object with all properties: slug, name, roleDefinition, whenToUse?, description?, customInstructions?, groups, source?
   • groups items as oneOf: a simple string enum ("read", "edit", "command", "mcp") OR a tuple [groupName, { fileRegex?, description? }]
   • The tuple format correctly represents how file-restricted edit permissions actually work

2. Add tests to verify the schema validates correctly against the built-in mode definitions (e.g., the architect mode with its tuple-style edit group).

This gives users a correct schema they can reference. A separate PR to SchemaStore to update their copy would be a follow-up.

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[algorhythm85]

@roomote I approve this plan

[roomote-v0]

Thanks for the approval! I've seen your comment and will proceed with the implementation now. I'll open a draft PR to share progress shortly.

[roomote-v0]

Opened a draft PR with my attempt at addressing this: #11791

The PR adds a correct schemas/roomodes.json (JSON Schema draft-07) that matches the actual .roomodes format, including tuple-style group entries, all optional properties (description, source, etc.), and all five tool groups. Also includes 18 tests validating the schema. Feedback welcome!

[algorhythm85]

@mrubens @cte @jr @hannesrudolph @daniel-lxs Any thoughts on this? Concerns?