Skip to content

fix(dojoos-api-consumer): repair the broken local OpenAPI spec paths (DOJ-6634) #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lapc506 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(dojoos-api-consumer): repair the broken local OpenAPI spec paths (DOJ-6634) #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions agents/dojoos-api-consumer.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,7 +96,7 @@ SPEC_FETCHED_AT: <ISO timestamp when spec was cached this session>

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"`.

@dojo-code-reviewer dojo-code-reviewer Bot Aug 8, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 P3 (minor) — The absolute local fallback path is specific to a single developer's machine structure (/home/kvttvrsis/...). If other team members run or develop this plugin locally, the absolute path lookup will fail for them, meaning they won't benefit from local offline mirroring. This forces them to fall back to live network fetches each time, which is slower and won't work in offline scenarios. We could add a sibling relative path fallback check (e.g., ../dojocoding-docs/public/openapi.yaml or checks relative to ~) to make the setup portable across development environments.

[pass 1]

3. **Hard fail**: if both fail, return `STATUS: ERROR` with `ERROR_DETAIL: "OpenAPI spec unreachable — cannot operate"`.

Expand Down Expand Up @@ -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)

Expand Down