[josha-ms]

Discovery Toolbox v1.11.8

Promote the reviewed, merged Toolbox source to the customer distribution, replacing v1.10.76.

Customer-facing changes

• More reliable cross-region manifests and saved-script round trips, including preservation of per-agent questions and verifiers.
• Default grounded validation plans enforce their declared numeric canary instead of reporting success for a no-dataset answer. Existing custom plans without a verifier retain their behavior.
• Honest diagnostic failures: required Kubernetes reads remain incomplete when later shell commands succeed; unread indexing data stays unknown rather than becoming zero.
• Scope-correct cleanup guidance and Dsv3/v4 quota coverage.
• Accurate teardown completion, measured progress counters, retained error/retry details and fresh confirmation/force-delete consent for new operations.
• Region Readiness and parent navigation groups show chat-started running activity.

Artifact and provenance

• Source commit: fefa8c843bd9032d9ff378ff9102fb3f5ec04744
• Built: 2026-10-26T21:34:27.312Z
• Customer VSIX: utilities/discovery-toolbox/vsix/DiscoveryToolbox-v1.11.8.vsix
• Size: 1,539,843 bytes
• SHA-256: 67bc11ee5b9d9bd39bffec02fb77dd017b907c62ef148ccba77323c8380fa3c4

The anonymous download from this exact PR head matches the audited local artifact and update manifest. The customer build uses public repository links and safe public defaults; its dev scripts are removed. All ten configured customer defaults, matching bundled/landing documentation and the 25-file archive were verified. No internal repository URLs, internal source or diagnostic exports were found in the inspected package. Production-dependency audit reports zero findings in 30 declared dependencies; that is not a claim about all development dependencies.

Validation

• Merged source passed its contract/type/build gates, 14 teardown executor/runner/store cases, generated-shell fault-injection checks, six focused Chromium regressions and 20 isolated extension-host checks.
• Installed 1.11.8 read-only smoke verified Azure previews/quota reads and actual native running-blue/idle transitions. The operator webview round trip was not run because its panel was closed; rendered UI coverage came from Chromium.
• Earlier live validation informed these fixes, but was not six clean end-to-end runs of this exact customer package. Four attempts passed their configured gates, one exposed the corrected grounding false positive, and one failed during Azure RP provisioning.
• No new Azure deployments, cleanup mutations or role grants were performed for this publication.

Changes are confined to the release folder: README/privacy version provenance, replacement VSIX and update manifest. After merge, the extension's normal update check will discover v1.11.8. Until then, the main-branch customer feed remains on the previous release.

[josha-ms]

ryansok — v1.11.8 is ready for the required review and merge. All ten reported checks are green. The five-file release diff is scoped correctly, and the anonymous download from head 5863d1c9f2ae96e7a6f081b8cad31b8466364c0b matches the audited customer VSIX and manifest:

67bc11ee5b9d9bd39bffec02fb77dd017b907c62ef148ccba77323c8380fa3c4

I attempted normal squash auto-merge, but GitHub returned: User is not authorized for this protected branch (enablePullRequestAutoMerge). Auto-merge is not enabled; no admin bypass or protection change was attempted. Please complete the normal maintainer approval/merge when ready.

[ryansok]

Approve

[ryansok]

Approve