Use case or problem
My vault structures tasks hierarchically: a parent task (e.g. representing a project) with indented sub-tasks nested beneath it in the markdown. I’m building external tooling on top of the CLI that needs to reconstruct this parent/child structure (to group and diff tasks by their project), but the tasks command (in text, verbose, and format=json) returns status, text, file, and line number for each task, never its indentation level. Without that, there’s no way to tell which tasks are nested under which parent.
Proposed solution
Add an indentation/nesting field to tasks output, at least in format=json – either indent (raw leading-whitespace count) or a simpler depth (nesting level, 0 for top-level). Optionally, a parentLine field pointing at the nearest shallower task would remove the need for callers to reconstruct the ancestor stack themselves.
Current workaround (optional)
Since tasks already returns a line number, and obsidian read returns the raw file with indentation intact and matching line numbers, the hierarchy can be reconstructed by cross-referencing the two calls. But that requires a second full file read per note just to recover information the tasks command already passed over internally while building its output.