docs(glossary): split Aliases into Tool Aliases and Shell Aliases

[thernstig]

The single "Aliases" entry conflated two distinct concepts. Split into "Tool Aliases" (backend/version aliases via [tool_alias] / mise tool-alias) and "Shell Aliases" (directory-scoped shell command aliases via [shell_alias] / mise shell-alias), reflecting the current CLI and config structure.

[greptile-apps]

Greptile Summary

This PR improves the glossary by splitting the formerly unified "Aliases" entry into two distinct concepts that were being conflated.

• Tool Aliases entry now accurately describes both backend aliasing and version aliasing via [tool_alias] / mise tool-alias, matching the content in docs/dev-tools/aliases.md.
• Shell Aliases entry now covers directory-scoped shell command aliases via [shell_alias] / mise shell-alias, consistent with docs/shell-aliases.md.

Confidence Score: 5/5

Documentation-only change with no code impact; safe to merge.

The change is limited to the glossary and accurately reflects the CLI commands (mise tool-alias, mise shell-alias) and config sections ([tool_alias], [shell_alias]) that exist in the codebase. The descriptions align with the canonical docs they link to.

No files require special attention.

Important Files Changed

Filename	Overview
docs/glossary.md	Splits the single "Aliases" glossary entry into "Tool Aliases" and "Shell Aliases" with accurate descriptions referencing the correct CLI commands and config sections.

_{Reviews (5): Last reviewed commit: "Merge branch 'main' into main" | Re-trigger Greptile}

[gemini-code-assist]

Code Review

This pull request updates the glossary in docs/glossary.md by expanding the definition of 'Tool Aliases' to include backend and version aliases, and adding a new entry for 'Shell Aliases'. The reviewer suggested several improvements for consistency with other glossary entries, including formatting examples with backticks and standardizing the phrasing for how aliases are managed.

[github-actions]

This PR has had failing checks for more than 7 days. Feel free to reopen or create a new PR if you'd like to continue working on this.

[thernstig]

@risu729 I believe this fix was ok?

[risu729]

@thernstig yea I think so

[thernstig]

@risu729 open it again and merge then? 😆

[risu729]

@thernstig I can't. Idk if jdx can, as I don't understand how the PR reopen permissions work. I think it's easier to just recreate another PR.

[thernstig]

@risu729 open 🤖

[thernstig]

@risu729 ready to merge 😃

[risu729]

I can't. I don't have any permissions for this repo.

[thernstig]

Sorry, did not know.