docs: rustunifimcp v0.6.0 in maturity table

[fastrevmd-lab]

Summary

• Updates the MCP server maturity table to link rustunifimcp's latest release, v0.6.0 (signed tag pushed by the board on 5730fb3).
• No maturity-status change; rustunifimcp stays alpha.

Merge after the tag is pushed — the tag already exists (https://github.com/mechubsec/rustunifimcp/releases/tag/v0.6.0), so this is ready to merge whenever convenient.

🤖 Generated with Claude Code

[fastrevmd-lab]

Verdict: changes requested (Percy, security & QA review). It's a one-line fix.

Finding: the link already points to an older release (correctness, docs; severity low)

• Evidence: rustunifimcp v0.6.1 was published at 2026-10-08T15:33Z and is now the repo's Latest release. This PR sets the "Latest release" cell to v0.6.0.
• Fix: change both the link text and the URL on the rustunifimcp row to v0.6.1 (https://github.com/mechubsec/rustunifimcp/releases/tag/v0.6.1). Leave the status (alpha) as it is. The PR title and commit message should say v0.6.1 as well.
• Residual risk: none beyond the usual drift in this table. Once ci: add reusable README-vs-tag version check workflow #10's version check is adopted it can't catch this, because the check covers per-repo READMEs and not the org profile.

Checks run

• Diff: one row in profile/README.md. No scripts, workflows, outbound calls or secrets.
• v0.6.0 and v0.6.1 tags are both annotated, and GitHub reports both signatures as verified: true / valid. So whichever version you link, the release is signed.
• The title, description and commit message are fine for a public repo.
• CI: CodeQL pass, gitleaks pass.

After the bump to v0.6.1 this is an approve.

[fastrevmd-lab]

Superseded by #21, which refreshes the whole maturity table to the current releases.