docs: refresh README + stale --help strings for shipped v0.1

[aptracebloc]

Summary

Docs were stale from the Phase-0 era. Now that v0.1 is feature-complete on develop (all phases #148–#153 merged; dataset push covers 9 of 10 modalities), this refreshes the README and the three user-facing --help/output strings that still referenced unshipped phases. Docs/strings only — no behavior change.

README

• Status: Phase-0 blurb → "v0.1 feature-complete on develop; first release pending"; lists the 9 supported categories and the 2 not-yet (semantic_segmentation blocked on data-ingestors#136, instance_segmentation).
• Customer experience: dropped "once Phase 5 ships"; install commands flagged as post-tag (build-from-source until v0.1.0).
• Building from source: Go 1.22 → 1.26 (matches go.mod).
• Roadmap: all phases ✅; added the modality-widening + test-harness note and a v0.2 "next" list.

--help / output strings (were contradicting the shipped binary)

• cluster info no longer prints "Ready for tracebloc dataset push (coming in Phase 3)."
• dataset --help: dropped "submission … lands in Phase 4 / picked up by the helm flow" → describes the shipped stage + submit + watch flow.
• dataset push --help: "image_classification dataset … (in PR-b)" → category-agnostic, notes the 9 categories + --category.

Verification

go build, go vet ./..., go test ./..., and gofmt -s all clean.

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation and user-facing strings only; no functional or security-sensitive code paths changed.

Overview
Updates documentation and user-facing copy so they match v0.1 feature-complete on develop—no runtime behavior changes.

The README now describes shipped status instead of pre-alpha Phase 0: full dataset push (stage → submit → watch), 9 of 10 task categories with explicit gaps for semantic_segmentation / instance_segmentation, install commands noted as post-v0.1.0 tag (build from source until then), Go 1.26 in build instructions, and a roadmap table with all phases ✅ plus a short v0.2 “next” section.

CLI help and output are aligned with the binary: cluster info drops “coming in Phase 3”; dataset and dataset push long help describe the end-to-end jobs-manager flow and multi-category --category support instead of image-only / future-phase wording.

^{Reviewed by Cursor Bugbot for commit fd7844a. Bugbot is set up for automated code reviews on this repo. Configure here.}

[LukasWodka]

👋 Heads-up — Code review queue is at 23 / 8

Above the WIP limit. The team convention is to review existing PRs before opening new work.

Open PRs currently in Code review (oldest first):

• averaging-service#98 — ci: add fr-gate caller workflow · author: @LukasWodka · no reviewer assigned
• client#180 — fix(resource-monitor): always grant read-only ClusterRole (decouple from clusterScope) · author: @shujaatTracebloc · reviewer: @saadqbal
• client-runtime#45 — Staging: Enhance jobs-manager with HTTP proxy, ingestion endpoint, and fixes · author: @saadqbal · no reviewer assigned
• client-runtime#61 — docs: record MySQL credential threat-model decision · author: @saadqbal · no reviewer assigned
• client-runtime#67 — ci: publish jobs-manager images on merge (closes the deploy-delivery gap) · author: @LukasWodka · no reviewer assigned
• client-runtime#68 — fix(pods-monitor): watch the release namespace, not hardcoded "default" · author: @shujaatTracebloc · reviewer: @saadqbal
• client-runtime#70 — fix(#69): don't evict SB sender on payload serialize fail; drop redundant COPY · author: @saadqbal · no reviewer assigned
• data-ingestors#132 — ci: add fr-gate caller workflow · author: @LukasWodka · no reviewer assigned
• data-ingestors#133 — docs: fix declarative-ingest path/column drift (issue #131 A-series) · author: @divyasinghds · no reviewer assigned
• data-ingestors#138 — test(e2e): end-to-end ingestion equivalence suite (all modalities, real MySQL) · author: @LukasWodka · no reviewer assigned

Pull from review before opening new work. (This is a nudge from the kanban WIP check, not a block.)