docs: add use case pipeline reference page

[divyasinghds]

Summary

• Adds tools-help/pipeline-reference.mdx — a transparency page that documents what the tracebloc client does to your data and model in each of the nine supported use cases.
• Each accordion covers: input format, preprocessing (incl. split strategy), training/validation step, default loss/optimizer, cycle-level metrics with the underlying library calls (sklearn, torchmetrics, lifelines), and inference output.
• Closes with a 6-step "reproduce locally" checklist so an evaluating user can run the same pipeline on the same data and compare metrics number-for-number.
• Wired into the Tools & Help group in docs.json.

Test plan

• mint dev renders the page and the new nav entry appears under Tools & Help
• All nine accordions expand correctly
• mint broken-links passes
• Spot-check by an owner of core/metrics/ and core/domains/ in tracebloc-client that the per-use-case metric lists and loss formulas are accurate (notably segmentation boundary metrics and the Cox loss description)

🤖 Generated with Claude Code

---

Note

Low Risk
Low risk documentation-only change; primary risk is incorrect or outdated pipeline details potentially confusing users.

Overview
Adds a new tools-help/pipeline-reference.mdx transparency page that documents the tracebloc client’s end-to-end training/inference lifecycle and per-use-case preprocessing, loss/optimizer defaults, and cycle-level metrics across supported tasks.

Wires the page into the Tools & Help section of docs.json so it appears in the docs navigation, and includes a short checklist for reproducing runs locally and comparing metrics.

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

[mintlify]

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

Project	Status	Preview	Updated (UTC)
tracebloc	🟢 Ready	View Preview	May 7, 2026, 9:58 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[LukasWodka]

👋 Heads-up — Code review queue is at 12 / 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):

• client#108 — chore: sync main → develop after misrouted docs PRs · author: @saadqbal · no reviewer assigned
• docs#14 — docs: migrate join-use-case API examples to snake_case (0.7.0) · author: @divyasinghds · no reviewer assigned
• docs#4 — docs: switch install to extras syntax for tracebloc_package 0.6.33 · author: @LukasWodka · reviewer: @saadqbal
• documentation-lagecy-#7 — docs: migrate start-training and hyperparameters to snake_case API (0.7.0) · author: @aptracebloc · reviewer: @LukasWodka
• model-zoo#59 — fix: pin revision on every from_pretrained() call · author: @aptracebloc · no reviewer assigned
• start-training#10 — ci: add WIP-limit-check caller workflow · author: @LukasWodka · no reviewer assigned
• start-training#6 — chore: add PR template + customer bump + stale auto-close · author: @LukasWodka · no reviewer assigned
• start-training#9 — ci: add kanban closure-routing caller workflow · author: @LukasWodka · reviewer: @saadqbal
• tracebloc-py-package#117 — TEST: trigger WIP-limit-check (do not merge — will close shortly) · author: @saadqbal · no reviewer assigned
• tracebloc-py-package#123 — chore: tighten huggingface extra pins to compatible major-version ranges · author: @aptracebloc · no reviewer assigned

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

[divyasinghds]

Superseded by #26 — renamed to "How training works" and rebased onto develop.