NAME

paths - private runtime path helper for Developer Dashboard

SYNOPSIS

dashboard paths

DESCRIPTION

This private helper is staged under ~/.developer-dashboard/cli/dd/ so the main dashboard command can expose the active runtime path set without loading the full runtime first.

PURPOSE

This staged helper exposes dashboard paths, the command that prints the active runtime path set as JSON. It is the shell-visible entrypoint for the layered runtime roots, helper directories, config roots, and other path values that the dashboard discovers for the current working directory.

WHY IT EXISTS

It exists because path reporting is a built-in dashboard feature, but the public switchboard should only dispatch to a helper while the path runtime owns the layered discovery and serialization rules.

WHEN TO USE

Use this file when changing the dashboard paths CLI contract, the staged helper handoff, or the exact examples contributors use to inspect active runtime roots from the shell.

HOW TO USE

Users run dashboard paths. The staged helper forwards the request to the lightweight path runtime, which collects layered dashboard roots from ~/.developer-dashboard down to the current project, computes the effective paths for helpers, config, dashboards, and related runtime assets, and prints that payload as JSON for human inspection or shell consumption.

WHAT USES IT

It is used by shell bootstrap code, by users debugging layered runtime state, and by tests that verify the active runtime path payload and home-vs-project layer precedence.

EXAMPLES

Example 1:

dashboard paths

Run the public built-in command path that stages or re-enters this helper.

Example 2:

~/.developer-dashboard/cli/dd/paths --help

Inspect the staged helper directly after dashboard init or helper extraction has populated the home runtime.

Example 3:

prove -lv t/05-cli-smoke.t t/30-dashboard-loader.t

Rerun the focused staged-helper and thin-loader tests after changing helper dispatch behavior.

Example 4:

prove -lr t

Verify that the helper still behaves correctly inside the complete repository suite.