docs(llm-commits): describe the Codex model the command actually pins

[worktrunk-bot]

The Codex setup section in the LLM-commits docs describes the pinned model as "the fast mini model", but the command it sits under pins gpt-5.6-luna — which is not a -mini model. The prose was written in #837 when the pin was a mini variant and was left behind when #3430 bumped gpt-5.4-mini → gpt-5.6-luna. This rewords the sentence to describe what the command actually pins, following #3430's own framing of gpt-5.6-luna as "the fast/low-cost variant of the current recommended (5.6) family".

docs/src/content/docs/llm-commits.md is the primary (non-command doc, per the sync taxonomy in docs/CLAUDE.md); the two mirrors under skills/ and plugins/ were regenerated by cargo test --test integration test_docs_are_in_sync, which now passes. The branch was rebased onto main after #3866 relocated the docs tree, so the edit lands at the post-#3866 path rather than the old docs/content/ one.

No regression test: the change is a single prose sentence with no behavior behind it. The sync test already pins the mirrors to the primary, which is the only mechanical invariant here.

Nightly sweep context

Found during the rolling survey (bucket 23/28), reviewing skills/worktrunk/reference/llm-commits.md.

Provenance:

$ git log --oneline -1 -S 'Uses the fast mini model' -- docs/content/llm-commits.md
cbe65a65e docs: add Codex config and optimize Claude Code for LLM commits (#837)
$ git log --oneline -1 -S 'gpt-5.6-luna' -- docs/content/llm-commits.md
c532d2dab docs(llm-commits): bump Codex commit-generation model to gpt-5.6-luna (#3430)

A repo-wide grep -i mini turned up no other stale reference to the old pin — the model string itself is consistent across src/cli/mod.rs, dev/config.example.toml, Taskfile.yaml, and src/output/commit_generation.rs; only this one sentence describes it.

[worktrunk-bot]

Reviewed the prose change — it matches #3430's own framing of gpt-5.6-luna, the primary/mirror split is right (llm-commits is a non-command doc, so docs/content/llm-commits.md is PRIMARY per the sync taxonomy in docs/CLAUDE.md), and a repo-wide grep confirms no other prose describes the pin. Not approving only because this is a self-authored PR.

One cross-PR note: #3866 relocates this same file (docs/content/llm-commits.md → docs/src/content/docs/llm-commits.md, plus a new docs/public/ copy) without touching this sentence, so whichever lands second needs a rebase — and if #3866 goes first, this edit has to be reapplied at the new primary path rather than replayed as-is.

[worktrunk-bot]

The cross-PR note in my review landed: #3866 merged at 07:01Z, ~8 minutes after that review, so this branch was editing a path that no longer exists. Rebased onto main and reapplied at the new primary — docs/src/content/docs/llm-commits.md — plus the two skill mirrors. cargo test --test integration test_docs_are_in_sync passes and regenerates nothing, so the mirrors are consistent with the new primary.

Rebase details

Old head 2694224 → new head 45536ce. Rename detection followed the file cleanly, so the diff is the same one-sentence change in three files:

• docs/src/content/docs/llm-commits.md — primary (non-command page, per the sync taxonomy in docs/CLAUDE.md as rewritten by docs: rebuild the site with Astro and Starlight #3866)
• skills/worktrunk/reference/llm-commits.md — derived skill copy
• plugins/worktrunk/skills/worktrunk/reference/llm-commits.md — generated plugin mirror

docs/public/llm-commits.md, which #3866 added, is a symlink to ../../skills/worktrunk/reference/llm-commits.md, so it picks the change up with no separate edit.

CI on 45536ce is still queued — after ~19 minutes of polling, only gate and the pre-commit.ci / dependabot checks are terminal; fast-checks, test (linux|macos|windows), code-coverage, and the advisory affected tests jobs had not started. The runner queue is backed up (this session itself started ~41 minutes after its trigger event), so those are unverified rather than failing.