docs: make declarative-ingest staging self-contained (data-ingestors#131 B/C)

[divyasinghds]

Summary

Companion to tracebloc/data-ingestors#133, addressing the docs-side items from data-ingestors#131.

• B2 / B1 — single canonical staging recipe. Section 2 of the declarative path described a kubectl cp Pod while the Detailed Setup section (further down on the same page) prescribed a host-path cp -R. Same page, two different staging mechanisms. Replaced section 2 with the inline host-path recipe that matches the Detailed Setup section, and demoted kubectl cp to a Note for multi-node / EKS deployments. The recipe now uses a <prefix> subdirectory so the path lines up with the /data/shared/<prefix>/... style used in the YAML examples.
• C2 — credentials in the declarative path. Section 4 was silent on where CLIENT_ID / CLIENT_PASSWORD come from. Added a sentence noting the ingestor Pod inherits them from the Kubernetes Secret the parent tracebloc/client chart creates in <workspace> at install time. No creds are passed on the helm install command.
• C5 — worked train + test example. The run-twice rule was buried in a trailing parenthetical. Promoted it to bolded prose and added a side-by-side example showing two helm install invocations with distinct release names, table:, and intent: values.

Out of scope

• A-series (column names, PVC paths in example YAMLs) is shipping in data-ingestors#133.
• B3 (object_id / object_count columns in object_detection README) and C-series polish items C1/C3/C4 still need maintainer attention in the data-ingestors repo.

Test plan

• mint dev and walk through the declarative section start to finish; the staging recipe, the example YAML, and the train+test install commands should all reference compatible paths and names.
• mint broken-links clean.

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation-only edits to prepare-dataset.mdx with no runtime or security behavior changes.

Overview
The declarative Prepare Data path in prepare-dataset.mdx is tightened so reviewers can follow staging → YAML → Helm without bouncing to external READMEs for the default case.

Section 2 (staging) now documents the single-node default inline: copy into ~/.tracebloc/<workspace>/data/<prefix> and reference /data/shared/<prefix>/... in ingest.yaml. kubectl cp / init-container staging is relegated to a Note for multi-node or EKS.

Section 4 (install) leads with the train/test rule, shows two helm install examples (cats-dogs-train / cats-dogs-test with separate config files), and states that CLIENT_ID / CLIENT_PASSWORD come from the parent tracebloc/client Secret—nothing to pass on the Helm CLI.

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

[LukasWodka]

👋 Heads-up — Code review queue is at 11 / 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-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
• 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
• design-system#19 — fix: un-track coverage/ and node_modules/ from git · author: @LukasWodka · no reviewer assigned
• design-system#22 — ci: add Vitest test workflow · author: @LukasWodka · reviewer: @aptracebloc
• design-system#23 — ci: add fr-gate caller workflow · author: @LukasWodka · no reviewer assigned
• frontend-app#499 — ci: add Vitest + Cypress test workflow · author: @LukasWodka · reviewer: @aptracebloc
• model-zoo#77 — ci: add fr-gate caller workflow · author: @LukasWodka · no reviewer assigned

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

[mintlify]

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

Project	Status	Preview	Updated (UTC)
tracebloc	🟢 Ready	View Preview	Jun 1, 2026, 9:46 AM

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

[aptracebloc]

Please change to "Whether your client runs on Azure, AWS, Google Cloud ...". The current sentence is cumbersome and harder to follow.

[aptracebloc]

This should not come after we give commands that the user can run and only later find out that there were side effects, like if not setting the flag --reset-then-reuse-values. This part should be at the beginning of the section.
@saadqbal WDYT?