Publish LogBasset through Scoop

## Outcome

Publish LogBasset as a portable x64 application in the centralized Scoop Extras bucket. Use Scoop's `checkver` and `autoupdate` support for later stable versions without a LogBasset-owned publishing secret.

The accepted identifier, proposed as `logbasset`, remains subject to upstream acceptance.

## Scope

Add the accepted manifest under `ScoopInstaller/Extras/bucket/` with:

- Stable version and Apache-2.0 metadata.
- `architecture.64bit.url` pointing to the version-specific Windows ZIP.
- Matching SHA256.
- `bin: "logbasset.exe"`.
- GitHub-release `checkver`.
- `autoupdate` URL and checksum extraction.

No LogBasset repository file should change in this child.

Target Extras rather than Main: Scoop Main's current example threshold is at least 500 stars and 150 forks, which LogBasset does not currently meet. Do not create a project-owned bucket unless Extras rejects the package for a documented policy reason and a separate fallback is approved.

## Acceptance criteria

AC1. The accepted Extras manifest targets x64, identifies Apache-2.0, downloads the version-specific `logbasset_Windows_x86_64.zip`, verifies SHA256, and exposes `logbasset.exe` through `bin` without custom installer or uninstaller scripts.

AC2. The manifest hash matches both `Get-FileHash -Algorithm SHA256` and the asset's `checksums.txt` entry.

AC3. `checkver: "github"` and `autoupdate` regenerate the URL and checksum correctly using two already-published stable releases or a forced regeneration of the current stable release; the official `checkver.ps1 logbasset -u -f` flow succeeds.

AC4. From a test bucket or fork, `scoop install /logbasset`, `logbasset --version`, and `logbasset --help` succeed with the manifest version.

AC5. Updating between two published stable manifests via `scoop update logbasset` changes `logbasset --version`; `scoop uninstall logbasset` removes the shim.

AC6. The upstream contribution follows current proposal and PR rules, receives `/verify` when required, passes bucket checks, is merged into Extras, and the public package and PR URLs are recorded.

AC7. No project-owned bucket, repository secret, LogBasset release workflow, or custom installation script is added.

## Verification

On Windows in the Extras fork or test bucket:

1. Run the official manifest and forced-autoupdate checks.
2. Install from the test bucket.
3. Verify `--version` and `--help`.
4. Advance the manifest between two published versions and update.
5. Uninstall and confirm `Get-Command logbasset -ErrorAction SilentlyContinue` no longer resolves the command.

## Exclusions

Shared documentation, common Windows smoke, a project-owned bucket without an approved fallback, WinGet, Chocolatey, Microsoft Store, Windows ARM64, signing, and claims that Scoop guarantees SmartScreen or Mark-of-the-Web suppression.

## Credentials

A GitHub account and fork are sufficient. No Scoop API key or LogBasset repository secret is required.

## Sources

- https://github.com/ScoopInstaller/Scoop/wiki/App-Manifests
- https://github.com/ScoopInstaller/Scoop/wiki/App-Manifest-Autoupdate
- https://github.com/ScoopInstaller/Scoop/wiki/Criteria-for-including-apps-in-the-main-bucket
- https://github.com/ScoopInstaller/Extras
- https://github.com/ScoopInstaller/.github/blob/main/.github/CONTRIBUTING.md

Parent: #57
Blocked by: #58

Start with the Scoop manifest rules and the files under ScoopInstaller/Extras/bucket/, then inspect the LogBasset GitHub releases, ZIP asset, and checksums.txt. Run the official checkver.ps1 logbasset -u -f flow in a fork or test bucket, followed by install, version, help, update, and uninstall checks. Done means the accepted Extras PR passes bucket verification and the public package and PR URLs are recorded.

Escrito por el modelo de indexación a partir del texto del issue.