[BUG] .roomodes schema $id points to GitHub blob HTML instead of the schema document

[shaun0927]

Problem (one or two sentences)

The generated .roomodes schema advertises a $id that points to the GitHub blob HTML page instead of the JSON schema document itself.

Context (who is affected and when)

This affects tooling or schema consumers that dereference $id (or use it as the canonical schema document identity) when working with Roo custom modes.

Reproduction steps

Tested locally on current main at cb83656718.

1. Generate the schema object locally:

import { generateRoomodesJsonSchema } from './packages/types/src/roomodes-schema'

const schema = generateRoomodesJsonSchema()
console.log(schema['$id'])

2. Observe that the generated $id is:

https://github.com/RooCodeInc/Roo-Code/blob/main/schemas/roomodes.json

3. Fetch that URL's headers:

curl -I -L https://github.com/RooCodeInc/Roo-Code/blob/main/schemas/roomodes.json

4. Observe that GitHub serves:

content-type: text/html; charset=utf-8
x-raw-download: https://raw.githubusercontent.com/RooCodeInc/Roo-Code/main/schemas/roomodes.json

Expected result

The generated $id should point to the actual JSON schema document (or another stable JSON-serving canonical URL), not the blob HTML page.

Actual result

The schema $id points to a GitHub HTML page, so dereferencing it returns HTML instead of the schema document.

Variations tried (optional)

Existing schema tests still pass locally, so this appears to be a narrow canonical-URL bug rather than a broader schema-generation problem.

Related prior work:

• #11790 fixed schema/content mismatch problems
• #11791 added the generated schema file

I could not find an existing issue specifically for the $id URL itself.

App Version

main (cb83656718)

API Provider (optional)

No response

Model Used (optional)

No response

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

This seems like a low-severity tooling follow-up, but it is still a real correctness problem for schema consumers.

[shaun0927]

Claiming. I have a small follow-up fix prepared that only updates the schema $id to a JSON-serving canonical URL, regenerates the checked-in schema, and adds a regression assertion for the metadata value.

[roomote-v0]

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

1. Update the $id URL in packages/types/src/roomodes-schema.ts (line 53) from the GitHub blob URL (https://github.com/RooCodeInc/Roo-Code/blob/main/schemas/roomodes.json) to the raw content URL (https://raw.githubusercontent.com/RooCodeInc/Roo-Code/main/schemas/roomodes.json) so that dereferencing it returns actual JSON instead of HTML.

2. Regenerate the checked-in schema by running pnpm --filter @roo-code/types generate:schema to update schemas/roomodes.json with the corrected $id.

3. Add a regression test in packages/types/src/__tests__/roomodes-schema-sync.spec.ts (or a new test) that asserts the $id value starts with https://raw.githubusercontent.com/ to prevent this from regressing.

This is a minimal, targeted fix. The existing drift-detection test already ensures the checked-in schema stays in sync with the generator, so step 2 keeps that passing.

(Note: I see @shaun0927 has claimed this issue -- happy to defer if they already have a PR in progress.)

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

[shaun0927]

Follow-up PR opened: #12130