badness: Add version 0.16.0

[jolars]

This PR adds Badness: a formatter, linter, and language server for LaTeX. The documentation is at https://badness.dev and the repo is at https://github.com/jolars/badness.

• Use conventional PR title: <manifest-name[@version]|chore>: <general summary of the pull request>
• I have read the Contributing Guide

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 47f5383e-73a9-485b-a3ec-4fe61bcd2f1f

📥 Commits

Reviewing files that changed from the base of the PR and between 52d5491 and c920be9.

📒 Files selected for processing (1)

• bucket/badness.json

Included review availability: Your plan includes up to 4 reviews per rolling hour; 0 remain after this review.

---

Summary by CodeRabbit

• New Features
  • Added Scoop installation support for badness version 0.16.0.
  • Added downloads for 64-bit and ARM64 systems.
  • Included automatic version checking and architecture-aware updates.
  • Added optional Visual C++ runtime support.

Walkthrough

Changes

Badness package manifest

Layer / File(s)	Summary
Add badness manifest bucket/badness.json	Adds badness version 0.16.0 metadata, the optional Visual C++ runtime dependency, 64-bit and ARM64 downloads with hashes, executable settings, GitHub version checking, and architecture-aware autoupdate rules.

Possibly related PRs

• ScoopInstaller/Main#8391: Adds a similarly structured GitHub-hosted Windows application manifest.
• ScoopInstaller/Main#8401: Adds a manifest with architecture-specific downloads, a VC++ runtime dependency, version checks, and autoupdate rules.

Merge Risk: ⚪ Minimal · up to c920b

This PR adds the Badness package manifest without any identified merge-blocking correctness, security, runtime, deployment, or availability risk; it is merge-ready after normal checks and review.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description summarizes the manifest addition, identifies Badness, provides project links, and confirms both required checklist items.
Title check	✅ Passed	The title clearly identifies the Badness manifest and the added version, and it follows the repository's conventional title format.
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.

---

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.}

[z-Fng]

• I have read the Contributing Guide

If you want to work on something that there is no GitHub issue for, including for submitting a new package, follow these steps:

1. Create a new GitHub issue associated with the relevant repository and propose your change there.

[z-Fng]

https://github.com/ScoopInstaller/Scoop/wiki/Criteria-for-including-apps-in-the-main-bucket

[jolars]

That was sloppy, sorry!