docs: add v0.6 launch post

[aram-devdocs]

Closes #64.

Summary

• add a new mdBook launch post at docs/src/blog/launch-v0.6.md
• link the post from docs/src/SUMMARY.md
• keep the post plain Markdown with no remote embeds and no docs stack changes

Repo settings already completed outside this PR

• GitHub Discussions enabled on aram-devdocs/plumb
• starter discussion categories are present
• roadmap issue #56 is pinned

Notes

• no book.toml or CNAME change in this PR
• plumb.dev currently resolves but returns HTTP 403, so the post keeps the current public docs URL at https://plumb.aramhammoudeh.com/

Verification

• rg -n -i "\b(delve|tapestry|landscape|leverage|robust|seamless|comprehensive|vibrant|streamline|streamlined|unleash|unlock|journey|elevate|in today's fast-paced|in the world of|dive in|dive into|in conclusion|it's important to note)\b" docs/src/blog/launch-v0.6.md docs/src/SUMMARY.md -> no matches
• rg -n "<(img|script|iframe|video)|!\[[^\]]*\]\(https?://|<https?://[^>]+\.(png|jpg|jpeg|gif|svg|webm|mp4)" docs/src/blog/launch-v0.6.md -> no matches
• git diff --check -> pass
• git diff --cached --check -> pass
• git status --short -> clean after commit

Environment blockers

• just is not installed in this environment, so just validate could not be run here
• mdbook is not installed in this environment, so a full mdBook build could not be run here

[github-actions]

I have everything needed for the review. All checks are complete.

---

PR #182 — docs: add v0.6 launch post

Files changed: docs/src/SUMMARY.md (+4), docs/src/blog/launch-v0.6.md (+82)
Buckets: docs
Rust code changes: none

---

1. Determinism invariants

N/A — no Rust code touched.

2. Workspace layering

N/A — no Rust code touched.

3. Error handling

N/A — no Rust code touched.

4. Test coverage

N/A — no new public APIs.

5. Documentation

Humanizer pass: regex scan for all prohibited vocabulary (delve, leverage, seamless, comprehensive, unleash, journey, elevate, in the world of, dive in, in conclusion, …) — no matches. Structural AI-pattern scan (rule-of-three, negative parallelism, stilted openers) — no matches. Prose reads clean: short declarative sentences, no hedging, no flourishes.

---

Punch list

docs/src/SUMMARY.md:5–8 — minor warning (not blocking)
"Blog" is inserted before "Getting started". A first-time visitor on the docs site sees the blog post before the install guide. Conventional docs UX puts task-oriented navigation (install, quickstart) ahead of news/announcements. Consider moving the Blog section after the Contributing section at the bottom, or at minimum after "Getting started".

docs/src/blog/launch-v0.6.md:25–34 — minor warning (not blocking)
The "Install status" section names four channels (install script, cargo install, Homebrew, build from source) in a bullet list, then notes only the fourth works today. The list-first structure implies parity at a glance before the disclaimer. A single sentence up front ("The only supported path today is building from source") and then the list as "planned channels" would be less likely to send readers on a dead-end install attempt.

docs/src/blog/launch-v0.6.md:64–82 — nit
"Join the discussion" and "Contact" both list Discussions and Issues. The duplication is two bullets; low cost if left as-is, but the Contact section adds nothing that the preceding paragraph didn't already say.

---

No blockers. No Rust invariants at risk. Humanizer passes. The two warnings are content UX calls, not correctness issues.

Verdict: APPROVE