ctf-tui: Add version 0.1.2

[gandli]

Adds manifest (v0.1.2).\n\n- URL: https://github.com/gandli/ctf-tui-launcher/releases/download/v0.1.2/ctf-tui-windows-x86_64.zip\n- SHA256: 02ca639a6f6067b07f44aae47144ae78664c7516579d037dc02faa4d9b194f5b\n- Dependency: docker

[github-actions]

Your changes did not pass all checks.

Please address the issues in the manifest and comment starting with /verify to rerun the checks.

ctf-tui

• Lint
• Description
• License
• Hashes
• Checkver
• Autoupdate

Check the full log for details.

[gandli]

Thanks for reviewing!\n\nFor this manifest:\n- Binary: \n- Depends on Docker for challenge lifecycle commands.\n- Release source/checksum: https://github.com/gandli/ctf-tui-launcher/releases/tag/v0.1.2\n\nI can update fields quickly if maintainers prefer a different dependency declaration style.

[gandli]

Thanks for reviewing!

For this manifest:

• Binary: ctf-tui.exe
• Depends on Docker for challenge lifecycle commands.
• Release source/checksum: https://github.com/gandli/ctf-tui-launcher/releases/tag/v0.1.2

I can update fields quickly if maintainers prefer a different dependency declaration style.

[z-Fng]

To add a new package to this bucket, please follow the standard way to create a package request issue first and link it to your PR.

When creating a package request, you can check the criteria for a package to be accepted in this bucket, which can help you determine whether your PR is likely to be approved. The information provided in the issue can also help maintainers quickly get the necessary details.

For a package to be acceptable in this bucket, it should be:

1. Non-GUI tool *
2. Reasonably well-known and widely used (if it's a GitHub project, it should have at least 500 stars and/or 150 forks) *
3. English interface (or at least English documentation) *
4. Latest stable version *
5. Full version (i.e. not a trial version) *
6. Fairly standard install (e.g. uses a version-specific download URL, no elaborate pre/post install scripts) *

[z-Fng]

Thanks for your contribution! However, it appears that your package request doesn't fully meet the essential criteria.

Please feel free to reopen this PR once it fully meets the criteria, or consider creating your own bucket instead.