Skip to content

feat: open an undocumented runtime route from its finding - #190

Merged
bluejeans117 merged 4 commits into
mainfrom
feat/open-undocumented-runtime-route
Sep 22, 2026
Merged

bluejeans117 merged 4 commits into
mainfrom
feat/open-undocumented-runtime-route

Conversation

@bluejeans117

Copy link
Copy Markdown
Collaborator

Summary

  • LOOP-02: an implemented-but-undocumented finding opens the registered route instead of staying inert.
  • The page states that the running service registers the operation and OpenAPI does not document it. It is not treated as a spec operation.
  • Sending that request from the API Client is the next step.

Test plan

  • Runtime panel opens POST /internal/reindex as a runtime route and still opens documented findings as spec operations
  • Endpoint detail renders the registered route and still says operation not found for an unknown path
  • Client typecheck passes and adapter renderer assets match the standalone build
  • CI on this pull request

The disagreement check could name a route the service registered and
OpenAPI omitted, then leave that finding inert. Opening it now selects
the registered route and shows that the service implements it while the
contract does not. Sending the request is the next step.

Signed-off-by: Vishnu R <vishnurajesh45@gmail.com>
Opening an undocumented route left the operation view stuck, because the
request built for that route was stored once and then treated as proof
the next operation did not exist. The view now follows the selected
method and path. The runtime-route label is a message, and Tab in the
runtime dialog moves to that route and wraps back to close.

An undocumented route is an error only when discovery is complete.
Partial discovery keeps it a warning. Operators can name intentionally
undocumented operations so they are omitted from the finding.

Signed-off-by: Vishnu R <vishnurajesh45@gmail.com>
Acknowledged undocumented routes stay in the full route list and drop
out of the drift buckets. summary.runtime now counts matched plus
runtime-only routes, so those two numbers add up to the runtime total.

The Express, Fastify, and Hono examples acknowledge GET /internal/health,
so a complete discovery pass stays green while the route remains visible.

Signed-off-by: Vishnu R <vishnurajesh45@gmail.com>
The Runtime panel renders findings, not the routes array. Acknowledging
GET /internal/health removes its finding, so the route is absent from
the panel even though snapshot.routes still contains it.

Signed-off-by: Vishnu R <vishnurajesh45@gmail.com>
@bluejeans117
bluejeans117 merged commit 196245c into main Sep 22, 2026
@bluejeans117
bluejeans117 deleted the feat/open-undocumented-runtime-route branch September 22, 2026 13:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant