From 226a451fcd37ec37dd23d9d0ee3da691b3f45f60 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9s=20Pe=C3=B1a?= Date: Fri, 7 Aug 2026 19:07:47 -0600 Subject: [PATCH] fix(dojoos-api-consumer): repair the broken local OpenAPI spec paths (DOJ-6634) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Two absolute local paths still named `dojo-documentation`, which no longer exists on disk — the local checkout was renamed with the repo. Unlike the other two repos in this sweep, these are filesystem paths, and a filesystem has no rename redirect. They are broken now, not stale: /home/…/dojocoding/dojo-documentation/public/openapi.yaml BROKEN /home/…/dojocoding/dojocoding-docs/public/openapi.yaml EXISTS (64901 bytes) Nobody reported it because line 99 is guarded with "if the file exists" and the next step is a live WebFetch of docs.dojocoding.io. The agent degrades gracefully: step 1 silently never fires, step 2 succeeds, everything looks fine. A silent fallback that never fires is indistinguishable from one that works, which is exactly how this survived the rename. What was actually lost is the reason to fix it: every session pays a network round trip the local mirror existed to avoid, and the offline path is gone — if docs.dojocoding.io is unreachable the agent now falls through to `STATUS: ERROR — OpenAPI spec unreachable`, where the mirror would have carried it. Two lines. The six remaining `dojo-documentation` mentions in this repo are prose or repo-relative rather than absolute paths, including line 365's "the dojo-documentation platform", and are left for the separate cosmetic pass. Co-Authored-By: Claude Opus 5 (1M context) --- agents/dojoos-api-consumer.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/agents/dojoos-api-consumer.md b/agents/dojoos-api-consumer.md index b110d1b..8f6d5dd 100644 --- a/agents/dojoos-api-consumer.md +++ b/agents/dojoos-api-consumer.md @@ -96,7 +96,7 @@ SPEC_FETCHED_AT: On your first invocation in a session, resolve the spec in this order (stop at the first that works): -1. **Local fallback**: `Read` `/home/kvttvrsis/Documentos/GitHub/dojocoding/dojo-documentation/public/openapi.yaml` if the file exists. +1. **Local fallback**: `Read` `/home/kvttvrsis/Documentos/GitHub/dojocoding/dojocoding-docs/public/openapi.yaml` if the file exists. 2. **Live fetch**: `WebFetch` `https://docs.dojocoding.io/openapi.yaml` with the prompt `"Return the full raw YAML content verbatim, no summarization"`. 3. **Hard fail**: if both fail, return `STATUS: ERROR` with `ERROR_DETAIL: "OpenAPI spec unreachable — cannot operate"`. @@ -361,7 +361,7 @@ Expected trajectory: as @william + @garbanzo ship Launchpad endpoints, the `SPEC ## Reference — where the spec lives - **Canonical (live)**: `https://docs.dojocoding.io/openapi.yaml` -- **Local mirror (dev)**: `/home/kvttvrsis/Documentos/GitHub/dojocoding/dojo-documentation/public/openapi.yaml` +- **Local mirror (dev)**: `/home/kvttvrsis/Documentos/GitHub/dojocoding/dojocoding-docs/public/openapi.yaml` - **Stoplight Elements viewer**: served at `https://docs.dojocoding.io/` (the dojo-documentation platform) - **Shipped via**: DOJ-3170 (2026-04-14)