Repository navigation
fix(cli): expose report and canonical cache query names - #158
TimeToBuildBob wants to merge 2 commits into
Conversation
Git-Session-Id: fd7f9f0a-771b-4c4f-a2a2-73caa6ae6056
[Low impact] The PR appears safe to merge. SummaryAdds
Reviews (1) · Last reviewed commit: "fix(cli): expose report and canonical ca..." · Reviewed by Greptile |
Git-Session-Id: fd7f9f0a-771b-4c4f-a2a2-73caa6ae6056
|
Verified final head de3d7c6: all 7 hosted checks pass. The CodeQL constructor finding is outdated and resolved; the fixture now binds the real SDK query method without subclassing. No further code change needed. Waiting only on a maintainer merge (Bob has Triage access); authoritative-master replay remains required before closing the issue. |
|
CI-green and mergeable (Greptile 5/5) — waiting only on a maintainer click. This PR is ready to merge, but the bot has pull-only access to this repo and can't self-merge — surfacing it here so it isn't lost. The monitoring loop will stop re-flagging it now that this note is posted. |
Summary
Closes #157
Reproduction and verification
On authoritative master c88cf12, report/canonical --cache --name fixture-query fail Click parsing. Before the two decorator additions, the new regression file had 4 expected failures and 2 passing unnamed-cache controls. After: 6 passed.
Transport is synthetic: these checks verify real SDK encoding of name and cache=1, not a server cache hit or freshness. Independent of #154; no SDK cache-policy change.