docs: versioned publishing with mike + CLAIMED story rewrite

[romeokienzler]

Summary

Two related documentation improvements:

1. Versioned docs publishing (mike)

Replaces the single-copy mkdocs gh-deploy with mike, mkdocs-material's standard multi-version tool.

• Push to main → publishes the in-development docs as the dev version.
• Release tag vX.Y.Z → publishes that version (labelled X.Y.Z) and updates the latest alias; the site root redirects to latest.
• Adds the material version selector dropdown via extra.version: { provider: mike, default: latest } in mkdocs.yml.

The workflow's paths filter was removed because, on GitHub Actions, a paths filter under push also applies to tag pushes — a release tag that doesn't touch docs/** would otherwise be silently skipped and never publish.

2. "What is CLAIMED?" rewrite

Rewrites the docs home-page intro to tell the project's story: CLAIMED started as a reusable component library, became powerful through the C3 Component Compiler (now the centerpiece), and grew by integrating MLX for experiment/asset tracking and terratorch-iterate for HPO/NAS. The layer table is extended from three to four rows to match.

Files

• mkdocs.yml — add extra.version mike block.
• .github/workflows/docs.yml — mike-based deploy, tag trigger, bot git identity.
• docs/index.md — narrative rewrite + 4-row layer table.

Verification

• After merge, a push to main should publish dev; pushing a vX.Y.Z tag should publish X.Y.Z + latest. Confirm the version dropdown renders at https://claimed-framework.github.io/claimed/.
• Note: the first mike run reorganises the existing flat gh-pages into per-version subdirectories (expected).

🤖 Generated with Claude Code