Fix folder interactions and integrity diagnostics

[alexphillips-dev]

What changed

• route Docker and VM folder icon, name, and expand controls through a shared lifecycle-safe delegated action controller
• remove obsolete installed runtime scripts during upgrades
• exempt the exact generated icon asset-pack activation record from runtime-integrity false positives
• package dev version 2026.07.28.06 with curated release notes, updated SBOM/CSP inventory, checksum, and regression coverage

Why

The attached sanitized support bundle showed healthy Docker/VM configuration and storage paths, but all rendered Docker folders remained collapsed. The affected controls still depended on the declarative compatibility bridge introduced during the security migration. The same bundle's Storage and paths finding came only from two retired installed scripts and the generated icon-asset-pack.json record.

Impact

Folder icon/context, folder name/edit, and expand/collapse controls use one idempotent delegated handler on Docker and VM pages. Upgrade cleanup removes the retired scripts, while runtime integrity continues to flag every unrecognized executable/config runtime file except the exact installer-managed icon activation record.

Validation

• bash scripts/run_ci_suite.sh --lane lint --lane tests — passed (904 passed, 1 intentional skip; run with Windows native tar first in PATH)
• bash scripts/run_ci_suite.sh --lane fixture-browser — passed (30/30; runtime performance budgets passed)
• bash scripts/run_ci_suite.sh --lane guards --lane docs-guards — passed
• bash scripts/release_guard.sh — passed
• bash scripts/release_notes_consistency_guard.sh — passed
• bash scripts/install_smoke.sh — passed
• deterministic package build — passed; SHA-256 e78b2e2f7d662058c6b3f603f7ab79783a3b0691f7a624be65180a37e389d3e2