Remove title slug check and test duplicate titles (#116)

## Summary
- Remove `docs-check-titles` pre-commit hook and mise task — wiki-links resolve by filename stem, not frontmatter title, so slug-format titles and uniqueness aren't needed
- Add two test cards (`title-test-alpha`, `title-test-beta`) with identical `title: Title Test Card` to verify duplicate titles don't break Quartz or obsidian.nvim
- Retitle `index.md` from `blumeops-documentation` to `BlumeOps`
- Add GitHub and Forgejo repo links to homepage intro

## Test plan
- [ ] Deploy to docs site and verify both test cards render and cross-link correctly
- [ ] Verify homepage title renders as "BlumeOps"
- [ ] Verify repo links on homepage work
- [ ] After confirming, remove test cards in a follow-up

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/116

docs/changelog.d/feature-docs-title-cleanup.doc.md

@@ -0,0 +1 @@
+Remove docs-check-titles pre-commit hook, add repo links to homepage, and test duplicate frontmatter titles.

docs/index.md

@@ -1,5 +1,5 @@
 ---
-title: blumeops-documentation
+title: BlumeOps
 aliases: []
 id: index
 tags: []
@@ -14,11 +14,11 @@ infrastructure.
 ## What is BlumeOps?
 
 BlumeOps is my personal homelab infrastructure managed entirely through code.
-Everything lives in a single git repository, from service configs to deployment
-automation. Even the [[forgejo]] instance that hosts this repo is defined
-within it, making BlumeOps fully self-hosting. It's a digital life raft I built
-for myself as I went, and you can see it all from within your editor of choice.
-(I recommend vim.)
+Everything lives in a [single git repository](https://github.com/eblume/blumeops), from service configs to
+deployment automation. Even the [[forgejo]] instance that [hosts this repo](https://forge.ops.eblu.me/eblume/blumeops)
+is defined within it, making BlumeOps fully self-hosting. It's a digital life
+raft I built for myself as I went, and you can see it all from within your
+editor of choice. (I recommend vim.)
 
 These services run on my home [[hosts|infrastructure]], primarily an m1 mac
 mini named [[indri]] and a Synology NAS called [[sifaka]]. The infrastructure

docs/reference/infrastructure/title-test-alpha.md

@@ -0,0 +1,13 @@
+---
+title: Title Test Card
+tags:
+  - infrastructure
+  - test
+---
+
+# Title Test Card (Alpha)
+
+This card tests that duplicate frontmatter titles don't break wiki-link resolution.
+This card and [[title-test-beta]] share the same `title:` frontmatter value.
+
+If you can read both cards and the links work, the test passes.

docs/reference/infrastructure/title-test-beta.md

@@ -0,0 +1,13 @@
+---
+title: Title Test Card
+tags:
+  - infrastructure
+  - test
+---
+
+# Title Test Card (Beta)
+
+This card tests that duplicate frontmatter titles don't break wiki-link resolution.
+This card and [[title-test-alpha]] share the same `title:` frontmatter value.
+
+If you can read both cards and the links work, the test passes.

docs/reference/reference.md

@@ -46,6 +46,7 @@ Host inventory and network configuration.
 - [[tailscale]] - ACLs, groups, tags
 - [[gandi]] - DNS hosting for `eblu.me`
 - [[routing|Routing]] - DNS domains, port mappings
+- [[title-test-alpha]] / [[title-test-beta]] - Duplicate title test (temporary)
 
 ## Kubernetes
 

docs/tutorials/ai-assistance-guide.md

@@ -96,7 +96,6 @@ BlumeOps operations are driven by mise tasks. Run `mise tasks` to list all avail
 | `tailnet-up` | Apply Tailscale ACL changes via Pulumi |
 | `docs-check-links` | Validate wiki-links in documentation (includes orphan detection) |
 | `docs-check-index` | Check every doc is referenced in its category index |
-| `docs-check-titles` | Check for duplicate doc titles |
 | `docs-check-filenames` | Check for duplicate doc filenames |
 | `docs-review-stale` | Report docs by last-modified date, highlight stale ones |
 | `docs-review-tags` | Print frontmatter tag inventory across all docs |