docs: expand alias guide and dotfiles-garden connection note

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: codekiln

pages/Logseq___Frontmatter___alias.md

@@ -1,8 +1,14 @@
-## `alias::` for more convenient or alternate names
+# `alias::` for more convenient or alternate names
 	- In Logseq, if page `[[Super Long Name]]` has frontmatter `alias:: [[Shortname]]`, then clicking on `[[Shortname]]` in the wiki will take you to page `[[Super Long Name]]`.
 	- It is appropriate and useful for making note of real alternate names, plural or contextual link surfaces, handles, acronyms, and other useful discovery forms.
-	- By default, this garden tries to use the singular form for the canonical page name, and may use alias for the plural form.
-	- Canonical page names should remain singular where the garden naming convention calls for singular names; plural or contextual references belong in aliases.
-	- Do not create an alias that only repeats parent namespace context already expressed by the page title.
-	- Aliases are human-curated, not agent-generated. Agents should suggest alias candidates in the chat response rather than writing them to the page without explicit instruction.
-	- When auditing or pruning aliases, verify each with `rg '[[Candidate Name]]' pages/ journals/` to check graph usage before keeping it. For a graph-wide audit, [[nbb-logseq]] is more appropriate than ad hoc text search.
+	- ## Aliases are human-curated, not agent-generated
+		- Agents should suggest alias candidates in the chat response rather than writing them to the page without explicit instruction.
+	- ## Do not proliferate many aliases, be judicious
+		- Every alias added to the graph slows down the auto-complete time and potentially confuses the human operator as to which is the "canonical" version.
+	- ## Use Aliases for Plural Forms
+		- By default, this garden tries to use the singular form for the canonical page name, and may use alias for the plural form.
+		- Canonical page names should remain singular where the garden naming convention calls for singular names; plural or contextual references belong in aliases.
+	- ## Do not be redundant with aliases
+		- Do not create an alias that only repeats parent namespace context already expressed by the page title.
+	- ## Searching for Aliases
+		- When auditing or pruning aliases, verify each with `rg '[[Candidate Name]]' pages/ journals/` to check graph usage before keeping it. For a graph-wide audit, [[nbb-logseq]] is more appropriate than ad hoc text search.

pages/My___Dotfiles___Connection to This Garden.md

@@ -1,2 +1,3 @@
 - My dotfiles are connected to this knowledge garden (logseq-encode-garden).
-- I want my dotfiles to be as self-explanatory as possible, but have the dependencies of my dotfiles documented in my garden. Therefore I have the technologies and dependencies declare their [[logseq-url]]
+- I want my dotfiles to be as self-explanatory as possible. That said, pretty much every technology I use is one I do not understand completely, and this knowledge garden is my system for learning things about technology.
+- Therefore I aspire to converge upon the invariant that the technologies and dependencies in my dotfiles should declare in code comments a [[logseq-url]] to the logseq-encode-garden page pointing to the [[Logseq/Entity]] page in this garden where I'm learning about and keeping track that software project or plugin or whatever.