leopardwm: Add version 0.2.2

[jcardama]

Adds LeopardWM — a scroll-first tiling window manager for Windows 10/11, written in Rust (GPL-3.0).

Re-submission of #17777, updated to the current release (0.2.2). A user has since requested Scoop availability (jcardama/LeopardWM#42).

• Shims the CLI binaries (lwm, leopardwm-cli); the daemon (leopardwm.exe) and watchdog ship in the same directory and are launched by the CLI.
• checkver: github + autoupdate pull the hash from each release's checksums.txt, so future versions bump automatically.
• The manifest hash matches the published checksums.txt for v0.2.2 and the release zip URL resolves.

Happy to adjust per review.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new Scoop package manifest file bucket/leopardwm.json is added for LeopardWM, a scroll-first tiling window manager for Windows 10/11. The manifest defines version 0.2.2, homepage, license, and a 64-bit architecture section with a GitHub release download URL, SHA-256 hash, and extracted directory name. Two executables are declared (lwm.exe and leopardwm-cli.exe). An autoupdate block configures automatic version tracking via GitHub, using $version templating for the download URL and extracted directory, and a regex pattern against checksums.txt for hash retrieval.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

package-request-needed

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description provides context about LeopardWM, mentions it's a resubmission, and explains the manifest configuration. However, it does not follow the required template format with the conventional PR title checkbox and issue linkage.	Add the required checklist items from the template, including the conventional PR title confirmation and link to a related issue (Closes/Relates to #XXXX).

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'leopardwm: Add version 0.2.2' directly corresponds to the main change—adding a new package manifest for LeopardWM at version 0.2.2.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

bucket/leopardwm.json (1)

1-30: Run the local manifest validation/install checks before merge.

Please run:

• scoop config debug true
• scoop config gh_token <your-github-token>
• .\bin\checkver.ps1 -App leopardwm -f
• .\bin\formatjson.ps1 -App leopardwm
• scoop install bucket/leopardwm.json -a 64bit

Contribution refs: https://github.com/ScoopInstaller/.github/blob/main/.github/CONTRIBUTING.md and https://github.com/ScoopInstaller/Scoop/wiki/App-Manifests.
As per coding guidelines: new/updated manifests should be locally validated with checkver, formatted, and installation-tested per architecture.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@bucket/leopardwm.json` around lines 1 - 30, The leopardwm.json manifest file
requires local validation and testing before merging. Run the following checks
in order: first configure Scoop by enabling debug mode and setting your GitHub
token, then validate the manifest using checkver.ps1 with the force flag to
verify version detection and hash accuracy, next format the manifest using
formatjson.ps1 to ensure proper JSON formatting, and finally test the actual
installation with scoop install using the manifest path and 64bit architecture
flag to confirm the application installs correctly. Do not merge until all these
validation steps complete successfully.

Source: Coding guidelines

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@bucket/leopardwm.json`:
- Around line 1-30: The leopardwm.json manifest file requires local validation
and testing before merging. Run the following checks in order: first configure
Scoop by enabling debug mode and setting your GitHub token, then validate the
manifest using checkver.ps1 with the force flag to verify version detection and
hash accuracy, next format the manifest using formatjson.ps1 to ensure proper
JSON formatting, and finally test the actual installation with scoop install
using the manifest path and 64bit architecture flag to confirm the application
installs correctly. Do not merge until all these validation steps complete
successfully.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: be18a513-0aab-4134-ab6a-e3251e48b61f

📥 Commits

Reviewing files that changed from the base of the PR and between 245d4ef and a5279d1.

📒 Files selected for processing (1)

• bucket/leopardwm.json

[aliesbelik]

Same as #17777 (comment).