From 5f8f304076458f70b052670e0cbbd80e8676b2b5 Mon Sep 17 00:00:00 2001 From: Lucas van Staden Date: Wed, 7 Oct 2026 06:08:33 +0800 Subject: [PATCH 1/2] Shorten context7.json description to fit the 200-char schema limit The description added in #104 was 361 characters. Context7's schema (https://context7.com/schema/context7.json) caps it at 200, and the file failed validation. Context7 has since re-parsed the repo (2026-10-05) but its stored settings for /mage-os/devdocs are still the defaults: the generated description, default excludeFiles, and no rules. So none of the config from #104 took effect, and the 13 unlinked duplicate pages are still indexed in place of the published *_xml pages. This is the only schema error in the file; it now validates cleanly. Co-Authored-By: Claude Opus 5.5 --- context7.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/context7.json b/context7.json index cf92558..ad018be 100644 --- a/context7.json +++ b/context7.json @@ -3,7 +3,7 @@ "url": "https://context7.com/mage-os/devdocs", "public_key": "pk_HsBSv7f4tLBOYsckJH4BP", "projectTitle": "Mage-OS", - "description": "Developer documentation for Mage-OS, a community-governed independent distribution of Magento Open Source, compatible with Magento 2 extensions and themes. Covers installation, module development, theming, APIs, testing, and XML configuration file references. Mage-OS 3.x also ships features Magento Open Source lacks, such as built-in Returns Management (RMA).", + "description": "Developer docs for Mage-OS, a community-driven distribution of Magento Open Source compatible with Magento 2 extensions: install, modules, themes, APIs, XML config and built-in RMA.", "excludeFiles": [ "README.md", "CODEOWNERS", From 9e889f4d69f5551521ae2fafa432d5e32fd61681 Mon Sep 17 00:00:00 2001 From: Lucas van Staden Date: Wed, 7 Oct 2026 06:16:03 +0800 Subject: [PATCH 2/2] Validate context7.json against the Context7 schema in CI Context7 gives no error when context7.json is invalid. The description added in #104 exceeded the schema's 200-character limit and the library kept its default settings. This workflow runs check-jsonschema against https://context7.com/schema/context7.json whenever the file changes, so a schema error fails the PR instead of going unnoticed. Co-Authored-By: Claude Opus 5.5 --- .github/workflows/context7-validate.yml | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 .github/workflows/context7-validate.yml diff --git a/.github/workflows/context7-validate.yml b/.github/workflows/context7-validate.yml new file mode 100644 index 0000000..d18a86e --- /dev/null +++ b/.github/workflows/context7-validate.yml @@ -0,0 +1,25 @@ +name: "✅ - Validate context7.json" + +on: + push: + paths: + - context7.json + - .github/workflows/context7-validate.yml + pull_request: + paths: + - context7.json + - .github/workflows/context7-validate.yml + +jobs: + validate: + name: "✅ - Check context7.json against the Context7 schema" + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v4 + + # Context7 gives no feedback on an invalid file. After #104 shipped a + # description over the 200-character limit, the library kept its + # default settings, so catch schema errors here instead. + - name: "✅ - Validate" + run: pipx run check-jsonschema==0.38.2 --schemafile https://context7.com/schema/context7.json context7.json