Discloud CLI and dashboard remote build error path mapping to local repository

Goal: determine whether failed Discloud deployments expose remote build errors with file paths and line numbers that correspond to files in the local repository, so debugging can start from the developer workstation.

Uncertainty: current Discloud CLI command names, dashboard navigation, and log retention after a failure are unverified. It is also unclear whether the CLI and dashboard show identical build output for the same failed deployment, or whether Discloud automatically remaps remote Node.js or Python stack traces to local source lines. Behavior may differ between CLI and dashboard versions.

Specific questions:

• Do Discloud remote build failure logs include repository-relative file paths and line numbers?
• Is the error output consistent between the Discloud CLI and web dashboard for the same failed deployment?
• Does Discloud remap Node.js or Python stack traces to local source files without manual configuration?