chore(model gallery): 🤖 add 1 new models via gallery agent

[localai-org-maint-bot]

This PR was automatically created by the gallery agent workflow.

Summary:

• Search Term: GGUF
• Models Found: 15
• Models Added: 1
• Quantization: Q4_K_M
• Processing Time: 3.688426117s

Added Models:

• unsloth/Qwen3.8-27B-GGUF

Bot commands

Maintainers (owner / member / collaborator) can control this PR
by leaving a comment with one of:

• /gallery-agent recreate — close this PR; the next scheduled
  run will propose this model again (useful if the entry needs
  to be regenerated with fresh metadata).
• /gallery-agent blacklist — close this PR and permanently
  prevent the gallery agent from ever reproposing this model.

Plain "Close" (without a command) is treated as a no-op: the
model may be reproposed by a future run.

Workflow Details:

• Triggered by: schedule
• Run ID: 33391903405
• Commit: 69a5b54c0afba5509bd497431c76b808200c1820

[localai-org-maint-bot]

Review pass. Entry verifies clean. One nit and one coordination note.

Nit: the entry configures spec_type:draft-mtp in overrides.options but is tagged only llm/gguf, not mtp. Per .agents/adding-gallery-models.md it should carry the tag. No ranking impact today since it is not in a variants list, but the rule exists so later variant work reads correctly. Same nit on #11813, #11820, #11847 and #11848.

Merge ordering: this is one of 11 open gallery PRs that all insert at the very top of gallery/index.yaml (hunk @@ -1,4 @@, right after ---). They conflict with each other pairwise, so they need to land one at a time with a rebase between each. The full set: #11538, #11642, #11731, #11785, #11805, #11813, #11820, #11832, #11841, #11847, #11848.

[localai-org-maint-bot]

Merged into master as 4f8efd5.

This PR conflicted with master because every gallery addition inserts at the same point in gallery/index.yaml. Rather than a mechanical conflict resolution, I re-extracted this PR's added entries from its own merge base and spliced them in whole, so the entry content is exactly as written here.

Verified before the push: every declared sha256 was checked against HuggingFace's LFS oid and matched, the merged file parses as YAML, and it carries no duplicate entry names.

Applied locally and pushed directly, so the commit has a new SHA and GitHub will not link it back automatically.