NAME

collector - private built-in command wrapper for Developer Dashboard

SYNOPSIS

dashboard collector ...

DESCRIPTION

This private helper is staged under ~/.developer-dashboard/cli/dd/ so the public dashboard entrypoint can stay a thin switchboard.

PURPOSE

This staged helper exposes the collector lifecycle command family: run, start, stop, restart, status, output, inspect, list, and job/result maintenance. It is the CLI surface for the collector store and runner modules.

WHY IT EXISTS

It exists because collector process management is built-in dashboard behavior, but the command wrapper should stay staged and thin while the collector modules own execution and persistence rules.

WHEN TO USE

Use this file when changing collector CLI verbs, argument parsing, or how collector commands are handed off into the runtime manager and collector subsystems.

HOW TO USE

Users run dashboard collector <verb> .... The staged helper passes the request into the private runtime, which loads the collector store and runner and prints the resulting state or output.

WHAT USES IT

It is used by developers inspecting collector health, by restart/stop flows that coordinate collectors with the web process, and by collector lifecycle tests.

EXAMPLES

Example 1:

dashboard collector run sample-collector

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

Example 2:

~/.developer-dashboard/cli/dd/collector --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.