Purple Dragon PowerTools v2.5.2

Purple Dragon PowerTools v2.5.2 — Uninstall Website

• After a successful interactive Windows uninstall, opens https://www.purpledragonfoundationltd.xyz/ in the user's default browser.
• Silent uninstalls, upgrades, cancelled and failed removals do not open the website.
• Includes the v2.5.1 status refresh hotfix.

Applies to the Setup installer; Portable has no uninstaller. Existing installations need the v2.5.2 Setup package to receive the updated uninstaller. Native Windows browser-launch acceptance remains pending. Executables remain unsigned; release integrity uses checksums and signed metadata.

Purple Dragon PowerTools v2.5.1

Purple Dragon PowerTools v2.5.1 — Status Refresh Hotfix

• Stops telemetry and process status banners flashing Loading / Ready on every sample.
• Keeps the previous visible status during routine polling and refreshes unchanged timestamps at most every 30 seconds.
• Failures, changed status details, and recovery appear immediately. Live measurements keep their configured sampling frequency.

Validation: status regression tests, actual-page DOM fault-injection checks, syntax checks and release publisher policy tests. Native Windows visual acceptance remains unverified. Windows executables remain unsigned; release integrity uses SHA-256 and the signed release manifest.

Purple Dragon PowerTools v2.5.0

Purple Dragon PowerTools v2.5.0 — Clear Status & Notifications

Status: Unreleased. Native Windows acceptance and signed publication remain pending.

• Core center reads show Loading, Ready, Unavailable, Unsupported, Administrator required or Refresh failed, with checked and last-success times.
• Failed reads offer retries through existing refresh functions. Retrying does not approve UAC prompts, execute cleanup, publish releases or perform system changes.
• Failed process/app refreshes retain last successful data and label the snapshot as stale.
• Notifications now have a bounded session history, severity, unread count, dismissal and history clearing.
• Quiet Mode suppresses routine in-app/Windows popups while errors remain visible. A separate switch controls routine in-app popups. Automation notification suppression is recorded; desktop events reach the session center when the renderer is connected.

Notification history and read-status details remain in memory for this session and are not exported or saved. Only boolean preferences persist in pt.notifications.v1 and notification-preferences.json. Existing release notification preferences remain independent. No configuration migration is required.

Validation: syntax, status classification, failed-read preservation, overlapping-read ordering, read-only retry catalog, preference validation, navigation/workspace/dialog/updater/publisher regressions and actual-page DOM fault-injection checks. Native Windows toast behavior, UAC states, high-DPI visuals, installer/portable builds and upgrade acceptance still need verification before publication.

Purple Dragon PowerTools v2.2.0

Purple Dragon PowerTools v2.2.0 — Update & Release Center 2.0

Purple Dragon PowerTools v2.2.0 introduces a cryptographically verified update pipeline while keeping source code public and official releases tightly controlled.

Update & Release Center 2.0

• Added token-free checks against the official bubblegump30/PurpleDragonPowerTools GitHub Releases feed.
• Added Stable and Preview channels.
• Added Manual, Startup, 6-hour, 12-hour, Daily, and Weekly check policies.
• Added local update settings with atomic persistence.
• Added current/latest version comparison, release history, and packaged/source build-origin reporting.
• Added optional release notifications.

Download & Verification Engine

• Added manual Setup or Portable package staging.
• Added streaming downloads into protected Electron user-data staging.
• Added GitHub release-host allowlisting, size limits, and progress reporting.
• Added SHA-256 verification using GitHub asset digests, SHA256SUMS.txt, and release-manifest hashes.
• Published hashes must agree; disagreement fails closed.
• Added GitHub-Verified signed annotated release-tag validation.
• Added signed release-manifest.json validation.
• Added local OpenSSH SSHSIG verification for release-manifest.json.sig.
• The manifest signing key must match the same Ed25519 key embedded in the GitHub-Verified release-tag signature.
• The manifest commit must match the commit targeted by the signed release tag.

Transactional Setup installation

Installation remains manual-only. Automatic download and automatic install are disabled.

A Setup package can become install-ready only when:

• PowerTools is running as an installed packaged Windows build;
• the verified package is newer than the current version;
• SHA-256 verification passed;
• the release tag is GitHub-Verified;
• a signed release manifest is present and valid;
• the manifest signature verifies locally with the same release key.

Immediately before installation, the staged installer is hashed again.

Rollback and post-update health

• Creates a rollback snapshot of the current installed application before running Setup.
• Verifies the backed-up application executable and resources/app.asar.
• Uses an external PowerShell helper so the transaction survives the PowerTools shutdown.
• Re-checks the transaction record and installer package after PowerTools exits.
• Launches the target version after installation and waits for a delayed health marker.
• Health requires the expected version, writable user data, intact runtime, a live renderer, zero renderer crashes, and no renderer error.
• Automatically restores the previous application files if the new build does not pass health checks.
• Verifies restored executable and app.asar hashes before relaunching the previous build.
• User data is preserved throughout rollback.

Rollback restores application files, not arbitrary Windows registry state. Apps & Features metadata can require later reconciliation after a failed installation followed by file rollback.

Official release trust

Official v2.2.0 releases publish:

• Purple-Dragon-PowerTools-Setup-2.2.0-x64.exe
• Purple-Dragon-PowerTools-Portable-2.2.0-x64.exe
• SHA256SUMS.txt
• release-manifest.json
• release-manifest.json.sig

The annotated Git tag and detached release-manifest signature use the same dedicated Ed25519 release-signing key.

Windows Authenticode remains a separate trust layer and is not claimed for these binaries until a Windows code-signing certificate is available.

Purple Dragon PowerTools v2.1.0

Purple Dragon PowerTools v2.1.0 — Stable Release

Channel: Stable
Platform: Windows x64
Publisher: Purple Dragon Foundation Ltd
License: MIT

Purple Dragon PowerTools v2.1.0 is the first Stable public release. It promotes the v2.1.0 release-candidate line after public-release hardening, reproducible Windows packaging, privacy/security review, startup-performance improvements, and owner acceptance testing.

Highlights

• Stable Windows Setup and Portable builds
• Reproducible dependency locks and clean CI builds
• SHA-256 checksums for published executables
• Hardened Electron renderer boundaries
• Renderer-created windows and unexpected navigation blocked
• Sanitized diagnostics and support-report exports
• Credential storage requires Electron safeStorage
• Loopback-only custom local AI endpoints
• Cloud System-Aware context remains separately opt-in
• Improved startup responsiveness through staggered telemetry providers
• Hidden Performance/Network charts no longer redraw unnecessarily
• Multi-drive HDD / SSD / NVMe / USB storage support
• NordVPN and ExpressVPN Center
• AI Command Center with Direct Model, Dragon Router, and Dragon Council
• Automation Engine, Change Journal + Undo, Feature Lab, Security Center, Privacy & App Trust Intelligence, and GitHub Release Center

Release integrity

The Stable release workflow is required to create a cryptographically signed annotated Git tag named v2.1.0.

After pushing the tag, the workflow asks GitHub for the tag object's verification status. If GitHub does not report the signature as verified, the workflow deletes the remote tag and stops before creating the release.

Published binaries are accompanied by SHA256SUMS.txt.

Windows code-signing status

The Git tag signature and Windows executable signature are separate trust mechanisms.

The Stable Git tag is required to be GitHub-Verified. The Windows executables may still be unsigned until a Windows Authenticode code-signing certificate is available. Windows Defender SmartScreen can therefore display an Unknown Publisher/reputation warning.

Do not disable Windows security features to install Purple Dragon PowerTools.

Compatibility

v2.1.0 has completed the project's release-candidate acceptance cycle. Broader compatibility testing across additional motherboard, VPN, storage, network, and Windows environments remains an ongoing post-release validation track.

Unsupported or inaccessible telemetry should report Unavailable or Unsupported rather than fabricated values.

Privacy

• Credentials are not intentionally exported in diagnostics.
• Support exports redact local identifying data and common credential formats.
• Detailed per-process names, installed-application names, activity details, and user-folder analysis are omitted from public support reports.
• Users should still inspect diagnostics before posting them publicly.

Verification

After downloading the release:

Get-FileHash -Algorithm SHA256 .\Purple-Dragon-PowerTools-Setup-2.1.0-x64.exe
Get-FileHash -Algorithm SHA256 .\Purple-Dragon-PowerTools-Portable-2.1.0-x64.exe

Compare both results with SHA256SUMS.txt.

Security reports

See SECURITY.md. Do not publish passwords, API keys, tokens, signing keys, private paths, or unsanitized diagnostic information in a public issue.

License

Purple Dragon PowerTools v2.1.0 is released under the MIT License.

Purple Dragon PowerTools v2.1.0-rc.1

Purple Dragon PowerTools v2.1.0-rc.1 — Release Candidate Notes

Channel: Prerelease / Release Candidate
Platform: Windows x64
Publisher: Purple Dragon Foundation Ltd
Stable release: Not yet approved

v2.1.0-rc.1 is the first public-release-readiness build of Purple Dragon PowerTools. It combines the existing v2.1.0 feature set with security, privacy, packaging, diagnostics, and repository hardening intended for outside testing.

Highlights

• Public-release readiness checklist and security-reporting policy
• Hardened Electron renderer navigation and window creation
• Existing renderer isolation retained: context isolation on, Node integration off, sandbox on
• Sanitized diagnostic logging and support-report exports
• Windows CI packaging for NSIS installer and portable executable
• SHA-256 checksum generation for release artifacts
• Git-history credential-pattern scan
• GitHub bug-report / feature-request templates
• Release Candidate labeling throughout the application
• Existing NordVPN + ExpressVPN Center retained
• Existing AI Command Center, Storage & Data Hub, Privacy & App Trust, Automation, Change Journal, Feature Lab, Security Center, and Reliability features retained

Privacy changes

Support-report exports now redact or omit host/user identifiers, IP/MAC addresses, file paths, credentials, serial identifiers, detailed process/application names, activity details, and user-folder analysis.

Diagnostic logs redact common credential formats and local identifiers before they are written.

Users should still review any diagnostic file before sharing it publicly.

Windows packages

The Release Readiness workflow is configured to produce:

• NSIS installer
• Portable Windows executable
• SHA256SUMS.txt

Treat CI artifacts as test builds until this release candidate passes the Windows smoke-test matrix.

Verify a downloaded build

Compare the artifact against SHA256SUMS.txt. For example:

(Get-FileHash .\Purple-Dragon-PowerTools-2.1.0-x64.exe -Algorithm SHA256).Hash

The returned hash must match the corresponding line in SHA256SUMS.txt.

Code-signing status

This release candidate may be unsigned. Windows Defender SmartScreen can therefore show an unknown-publisher/reputation warning even when the checksum is correct.

Do not disable Windows security features to install PowerTools. See CODE_SIGNING.md.

Known release gates

The following must be resolved or explicitly documented before v2.1.0 is promoted to Stable:

• CI build must pass
• root and runtime dependency lockfiles must be reviewed and committed
• final software license selected: MIT
• Windows standard-user and administrator smoke tests must pass
• installer/uninstaller and portable-build tests must pass
• VPN-present and VPN-absent tests must pass
• single-drive, multi-drive, and USB-storage tests must pass
• offline startup must be tested
• real support-report exports must be inspected for privacy
• final code-signing status must be documented

License

Purple Dragon PowerTools v2.1.0-rc.1 is released under the MIT License. See LICENSE in the repository.

Reporting problems

Use the repository bug-report template for reproducible issues. Remove credentials, private paths, usernames, IP addresses, and other sensitive information before posting logs or screenshots.