fix(#386): strip surrounding quotes from the ingest path prompt + clarify dataset-name rules

[divyasinghds]

Fixes two independent UX papercuts in the interactive tracebloc data ingest flow (both localized to the guided-prompt code).

Part 1 — strip surrounding quotes from the "Where is your data?" prompt

The prompt is read literally, not shell-parsed. A pasted quoted path — common when dragging a folder into a terminal (auto-quoted) or quoting a path with spaces — had the quote chars become part of the path, so ingest failed with e.g. no such file or directory: "'/home/me/my data/train'".

• Added stripSurroundingQuotes (removes at most one matching pair of the same surrounding quote char '/"; inner and mismatched quotes untouched) and dequotePath (trim → strip → trim).
• Applied to the interactive answer before expandHome / statDatasetPath, and inside validateDatasetPath so the re-prompt guard is consistent (an answer of just an empty quote pair is now rejected at the prompt instead of dying later with a messy error).
• Applied only to the guided answer — never the flag/positional path (the shell already de-quotes those).

Acceptance: pasting '…' or "…" resolves identically to the bare path; an unquoted path with spaces still works; a name that really contains a quote loses only the single matched outer pair.

Part 2 — clarify the dataset-name rules

Names must match [A-Za-z_][A-Za-z0-9_]*, but the hint/error never said hyphens and spaces are rejected, so kebab-case (tsc-train) surprised users.

• Name-prompt hint now reads "no hyphens or spaces, use _".
• First line of the ValidateTableName error now leads with "no hyphens or spaces (use _)" before the MySQL/PVC rationale.

Wording only — nothing changes about what names are accepted or rejected.

Validation

• go build ./..., go test ./..., go vet, gofmt -s all pass.
• Regenerated zz-all-strings.golden for the hint change (only that line moved).
• Added table-driven tests for the quote helpers ('/a/b', "/a/b", bare, spaces, name-with-a-quote, mismatched, empty-quote pairs) plus a wording-pin test for the error.

Closes#386

🤖 Generated with Claude Code

---

Note

Low Risk
Localized CLI prompt/validation and copy changes with no change to accepted table names or non-interactive ingest paths.

Overview
Fixes two guided data ingest UX issues (#386).

Path prompt: The "Where is your data?" answer is read literally (not shell-parsed), so pasted '…' or "…" paths failed with no such file or directory. The flow now stores dequotePath (trim + stripSurroundingQuotes for one matching outer '/" pair) before expandHome / stat, and validateDatasetPath uses the same canonicalization so '' / "" are rejected at the prompt. This applies only to the interactive answer, not flag/positional paths.

Dataset name: Copy-only updates to the name-prompt hint and ValidateTableName error text to state that hyphens and spaces are not allowed and _ should be used; validation rules are unchanged.

Adds table-driven tests for the quote helpers and a wording pin for invalid kebab-case names; golden strings updated for the hint line.

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

[saadqbal]

Clean, well-scoped fix — the dequote path canonicalization is consistent between store and validate, and the mismatched/inner-quote edge cases are handled correctly. Tests pass locally. 👍