New: Runtime Beta Mode

Introduces betamode – a runtime toggle to enable experimental beta rules.

When configuring rules (flowscanner.configRules):

• Users are now prompted: "Do you want to opt-in for beta rules?"
• Default: No (opt-out) – safe and stable rule set.
• Selecting Yes includes rules from core.getBetaRules() in the rule selection list.

betamode: true is written to .flow-scanner.yml only if opted in.
Fully backward compatible – existing configs without betamode default to false.
Beta rules are dynamically loaded and can be enabled/disabled per configuration session

Command Flow Makeover

• Removed deprecated environment configuration attributes.
• Added rimraf to simplify environment cleanup for developers.
• Improved flow selection logic and general configuration flow.
• Removed legacy expression settings no longer in use.
• Replaced YAML parsing dependency with cosmiconfig for more flexible configuration loading.
• Configuration UI now pre-selects all items when none are selected.
• Updated documentation with improved usage instructions.

Privacy & Open VSX Compliance

We’ve strengthened our security policy to fully align with the Eclipse Open VSX Publisher Agreement (v1.1 – September 2025).

Key Changes:

• Calc Coverage removed – The functionality that fetched Test Run data to estimate Flow coverage has been fully eliminated. This change ensures full compliance with our updated Security Policy and the Eclipse Open VSX Publisher Agreement (v1.1 – September 2025), while aligning with our client-side architecture goals.
• Introduces a new Security Policy officially noted in README.md: Zero persistent data – Metadata (e.g., timestamps, Flow state) is used in-memory only during active sessions and discarded immediately upon close. No data is ever stored, logged, or transmitted.
• Removes xml2js and vite dependencies

All analysis remains 100% client-side with no external network calls.

See full details in SECURITY.md

Expression Configuration Dialogue

• adds severity in the results view
• Bring back configure rules(with legacy support)
• Initiate a dialogue to define rule expressions if not found in local settings

The MissingFaultPath rule now correctly ignores "Wait for Amount of Time" and "Wait Until Date" nodes

Upgraded to lightning-flow-scanner-core v5.9.0. This release fixes the MissingFaultPath rule to correctly ignore "Wait for Amount of Time" and "Wait Until Date" nodes, checking fault paths only for relevant nodes like "Wait for Conditions". Resolves Issue #272 (contributed by @chazwatkins). See v5.9.0 release notes for full details.