docs: stage NanoClaw v2.0.54 Mintlify portal

[glifocat]

Summary

• Adds the staged Mintlify documentation portal under docs-site/ for the NanoClaw v2 MVP docs refresh.
• Pins source-truth callouts and version references to NanoClaw v2.0.54 / commit a33b1ae / package 2.0.54.
• Includes the MVP pages reviewed for v2 architecture, quickstart, migration, database/session model, and changelog coverage.

Validation

• mint validate — passed from docs-site/
• mint broken-links — passed from docs-site/

Source tag / commit

• Upstream source repo: qwibitai/nanoclaw
• Tag checked: v2.0.54
• Commit checked: a33b1ae
• Package version checked: 2.0.54
• Verification date: 2026-05-10

Reviewer notes

• Reviewer parent task t_452b8606 recommended GO for a draft PR.
• Scope is limited to docs-site/ changes only.
• The pre-existing .gitignore change adding .superpowers/ was intentionally left unstaged and is not included.
• Reviewer found no stale v2.0.28, e0e4f01, or data/ipc claims in the staged MDX pages.
• This is scoped as an MVP/staged docs portal; detailed channel/provider guides remain deferred.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
nanoclaw-docs	🟢 Ready	View Preview	May 10, 2026, 10:09 PM

[glifocat]

Captured follow-up docs vision from the team for this draft portal:

• Less verbose, more user-focused v2 docs.
• Tiered paths for different audiences:
  1. Non-technical users: basic setup and concepts.
  2. Technical users: advanced configuration.
  3. Business/enterprise: deployment and infrastructure.
• Stronger focus on the isolation model and the distinction between messaging groups vs agent groups.
• CLI help commands should integrate with docs to avoid duplicating generated command reference text.

I queued a follow-up Kanban task graph on nanoclaw-docs-portal to incorporate this before making the PR ready:

• t_1b5e2dff — Audience-tier IA update for NanoClaw docs portal
• t_d296c021 — Source-verify isolation model and group concepts for audience docs
• t_faf47e00 — Revise draft docs portal for audience-tiered v2 experience
• t_1c919ddb — Review audience-tier docs portal update before PR readiness

PR #293 should remain draft until that review gives a GO.

[glifocat]

Refinement from maintainer: use four audience paths, with concise labels and NanoClaw brand tone:

1. Get it running — users who just want the shortest path to a working install.
2. Tinker/customize — users who want to change behavior, add channels/providers, and adapt their fork.
3. Contribute — developers who want to understand the codebase, skills, architecture, and contribution flow.
4. Business/enterprise — evaluators/operators focused on deployment, infrastructure, security, isolation, and governance.

Tone/brand direction: match NanoClaw's official site voice: direct, practical, compact, opinionated, user-focused. Emphasize "AI team", "small enough to understand", "secure by isolation", "bespoke not bloatware", and "skills over features". Avoid generic enterprise SaaS tone and avoid over-explaining command reference material that should live in CLI help.