* fix: read developer override settings from user settings only (#230)
* fix(amazonq): read developer override settings from user settings only
* fix(amazonq): scope packaged developer settings
* fix(amazonq): use extension mode for dev overrides
* fix(amazonq): defer developer settings until activation
* fix(amazonq): own developer settings lifecycle
* fix(amazonq): scope developer settings in manifest
* fix: show code issue text as plain text in hovers and tooltips (#231)
* fix(amazonq): show code issue text as plain text in hovers and tooltips
* fix(amazonq): keep code issue text wrapping between words in hovers and tooltips
MarkdownString.appendText turns every space into , so long finding text
could only wrap mid-word. Escape the text with a helper that keeps spaces.
* fix: keep MCP server setting values out of the Amazon Q log (#240)
The chat webview message log keeps MCP settings messages with the values
of the name, transport, scope, timeout and command fields and tool
permission choices. The URL keeps only its origin, arguments keep only
flag names, env variables and headers keep only their names, and other
field values are hidden. Other messages are logged as before.
* fix: open only http and https links from chat (#232)
* fix(amazonq): open only http and https links from chat
* fix: validate external language server links
* fix: preserve validated external link queries
* test: stub external link confirmation directly
* test: inject external link opener
* fix(amazonq): open validated language-server web links without an extra prompt
Summary
window/showDocumentrequests from the language server. Other schemes are rejected with an error and are not opened.Server-side companion: Amazon-Q-Developer/language-servers#3061 applies the same web-URL requirement to the MCP OAuth authorization endpoint.
Verification
npm run testCompile -w packages/amazonqnpm run compileOnly -w packages/amazonqgit diff --check