[divakantpandey]

Fixes #2723.

Retrofit's @GET/@POST/... match the bare-verb branch of annotation_route_method that exists for JAX-RS, so each interface method became a Route with a HANDLES edge in the client project. Non-@Path paths must start with /, so Retrofit's relative v1/orders fell back to /.

JAX-RS verbs are marker annotations (the path is a sibling @Path), so a verb annotation with an argument is a Retrofit request. Such methods now store client_route_path instead of route_path, and cbm_pipeline_emit_def_route emits HTTP_CALLS with the same url_path/method properties as call-site service edges, so cross-repo matching treats them like any other outbound call. A separate field keeps every route_path consumer (prefix bridge, decorator backstop, UI) meaning "served endpoint" unchanged. The incremental routes re-extract an edited file and go through the same emit, so ensure_decorator_routes needs no change; the incremental test covers both routes.

Path handling: a leading / is kept, a relative path is rooted (Retrofit resolves it against the base URL), and a full URL is kept as written. A const val, a string template or a concatenation has no static value: no edge, rather than a / Route. Resolving same-file constants would cover the remaining two cases in the issue; I left it out to keep this change to the direction fix.

On the issue's fixture: client HANDLES 4 -> 0, HTTP_CALLS 0 -> 2; client -> server cross_http_calls 0 -> 2; billing caller 2 -> 1 (no longer lands on the client). JAX-RS server routes unchanged.

Checklist

• Every commit is signed off
• Tests pass locally: scripts/test.sh --suites pipeline_semantic_manifest_repro,pipeline,extraction,edge_types_probe,cross_repo,incremental (1360 passed, ASan/UBSan, macOS arm64)
• Lint: clang-format 20 clean on changed sources; cppcheck/clang-tidy not run locally
• New behavior is covered by a test: Kotlin and Java Retrofit (sequential + parallel), a JAX-RS interface control, and an incremental re-index; the three Retrofit tests fail without the fix

[github-actions]

Thanks for opening this — it has been seen, and it is queued.

This note is automated, but it is not a brush-off: it exists so you know where your PR stands instead of having to guess from silence.

Current review status: working through a backlog. 0.9.1-rc.1 is out, so the release freeze that held reviews is over — but it left a large queue of open pull requests behind it, and we are reading through them oldest-first. The background is in discussion #1144.

What that means for this PR, concretely:

• It will not be closed for inactivity. No stale bot touches pull requests here.
• It may still sit a while before a human reads it. That is on us, not on you.
• Older PRs are read first, so a recent one is not being skipped — it is behind a queue.

Things that will genuinely speed it up whenever review does happen:

• Keep it rebased on main — the tree is moving quickly right now, and a conflicting branch cannot be reviewed as the diff you intended.
• Get CI green, or say which failures you believe are pre-existing.
• Keep the change to one claim. Bundled features and refactors get split before they get merged, which costs you a round trip.
• Every commit needs a sign-off (git commit -s) — CI enforces DCO.

If this fixes a bug, a reproduction we can run is worth more than a description of the symptom.

Thanks for contributing, and sorry in advance for the wait.