#15370: Dev

<!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> This PR adds a Windows packaging/release workflow plus supporting PowerShell scripts and docs, and introduces a WhatsApp `minResponseConfidence` config intended to suppress low-confidence auto-replies. Key issues to resolve before merging: - `.env.example` now contains non-dotenv narrative text and no trailing newline, making it unusable as an env template. - The WhatsApp confidence threshold is only read from the channel-level config, ignores the new account-level setting, and defaults missing confidence to `1.0` (so suppression likely never triggers). - The Windows workflow has an inconsistent build-output verification (`dist/entry.js` vs expected `dist/index.js`), and the autogenerated release notes include hardcoded links to a different repository. <h3>Confidence Score: 2/5</h3> - This PR needs fixes before merge due to CI-breaking workflow checks and miswired configuration behavior. - Score reduced because the new Windows workflow likely fails (verifies the wrong dist entry file) and the new WhatsApp confidence gating does not behave as configured (account-level setting unused; missing confidence defaults to pass). These are functional issues that should be corrected prior to merging. - .github/workflows/windows-package.yml, src/web/auto-reply/monitor/process-message.ts, .env.example _{Last reviewed commit: d3f4fde} <!-- greptile_other_comments_section --> _{(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!} <!-- /greptile_comment -->