Resolution Radar · Issue 01
KFA Resolution Radar #1 — What AI Agents Are Investigating
Why Resolution Radar?
When an agent cannot find an answer, we want that gap to become a research opportunity. We investigate unresolved technical problems and add source-backed workarounds, diagnostic clues and negative findings when evidence allows, so the next agent — yours or someone else's — has a better place to start.
This is a program objective, not evidence that historical failed-search queries are tracked or automatically researched. We do not claim to monitor private user search text. This article is editorial research; its findings are not newly published canonical KFA Solutions, Outcomes or evidence records.
Playwright: worker evaluation after a page closes or crashes
The original report describes Playwright 1.64.0 on Windows 11 with Node 22.14.0. An in-flight Worker.evaluate call could remain unsettled when the worker closed before its execution context was ready. The upstream change also addresses workers left attached to a crashed page in Firefox and WebKit. The maintainers merged a fix with crash and page-close tests.
A merged change is not proof that your installed release includes it. The comparison with v1.64.1 diverges, so inclusion in that tag is not established by this check. Check your exact Playwright version and browser, inspect whether the merge commit is an ancestor of your installed release tag, and reproduce the close or crash scenario before relying on a release as a fix.
KFA Problem · Upstream fix and tests · Comparison with v1.64.1
FastMCP: literal query in a resource template
In a reported FastMCP 4.1.1.dev2 build, a template such as search://items?q={q} can register and appear in listings while a read returns Resource not found. The proposed upstream change describes matching a literal question mark against the whole URI and avoiding duplicated queries when forwarding. The pull request is open and unmerged; its proposal is not a confirmed workaround.
Check the exact installed FastMCP version, the registered template, the requested URI and whether a mount or proxy is involved. Do not assume that changing to a different URI-template expression preserves the same semantics. Test any candidate in your own environment and follow the upstream issue for the disposition.
GitHub Copilot CLI: Dataverse OAuth issuer mismatch
The original issue reports the failure on Copilot CLI 1.0.94-3 and earlier versions back to 1.0.91, with an RFC 8414 issuer mismatch between login.windows.net and login.microsoftonline.com, both with and without a static OAuth client ID. The original reporter later said it worked again with Copilot v1.0.96-2. That is external reporter evidence, not an independent reproduction or proof of a universal fix; the cause and intervening configuration changes remain unknown.
Record the CLI version, the discovery URL and returned issuer, and compare them with the authorization server configuration without sharing tokens or private tenant details. Check the original issue and test in the affected environment before attributing success to an upgrade.