[AI Assistance] Refactor origin lock checks This change refactors origin gating to a single fail-closed boolean predicate isOriginAllowedByLock(establishedOrigin, targetOrigin) in Tool.ts: - Eliminates validateOriginLock and removes redundant gate in AiAgent2, the check already existed in AiAgent and when V2 is shipped fully we can squash AiAgent2 and AiAgent into one class to avoid this future confusion. - GetSourceContentTool filters candidate files against the origin lock upfront, preventing cross-origin existence probing. - ListSourcesTool evaluates the established origin once outside its filter loop. - Adds dedicated unit tests for isOriginAllowedByLock and canonicalizes test assertions across tool test suites. Bug: 559104374 Change-Id: Idd0205fb121f4990fbe853f42935125a9824e1d1 TAG=agy CONV=401d6ddf-8863-46c0-b0da-516acd8cbdda Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/8378426 Auto-Submit: Jack Franklin <jacktfranklin@chromium.org> Commit-Queue: Jack Franklin <jacktfranklin@chromium.org> Reviewed-by: Simon Zünd <szuend@chromium.org>
The client-side of the Chrome DevTools, including all TypeScript & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com. Check out the Chromium DevTools documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.
DevTools frontend repository is mirrored on GitHub.
DevTools frontend is also available on NPM as the chrome-devtools-frontend package. It's not currently available via CJS or ES modules, so consuming this package in other tools may require some effort.
The version number of the npm package (e.g. 1.0.373466) refers to the Chromium commit position of latest frontend git commit. It's incremented with every Chromium commit, however the package is updated roughly daily.
There are a few options to keep an eye on the latest and greatest of DevTools development:
Follow What's new in DevTools.
Follow Umar's Dev Tips.
Follow these individual Twitter accounts: @umaar, @malyw, @kdzwinel, @addyosmani, @paul_irish, @samccone, @mathias, @mattzeunert, @PrashantPalikhe, @ziyunfei, and @bmeurer.
Follow to g/devtools-reviews@chromium.org mailing list for all reviews of pending code, and view the log, or follow @DevToolsCommits on Twitter.
Checkout all open DevTools tickets on crbug.com
Use Chrome Canary and poke around the experiments.