NAME
dashboard - thin command switchboard for Developer Dashboard
SYNOPSIS
dashboard help
dashboard init
dashboard update
dashboard doctor [--fix]
dashboard ps1 [--jobs N] [--cwd PATH] [--mode compact|extended] [--color]
dashboard paths
dashboard path list
dashboard path resolve <name>
dashboard path add <name> <path>
dashboard path del <name>
dashboard path locate <term...>
dashboard path project-root
dashboard of [--print] [--line N] [--editor CMD] <file|scope> [pattern...]
dashboard open-file [--print] [--line N] [--editor CMD] <file|scope> [pattern...]
dashboard ticket [ticket-ref]
dashboard jq [path] [file]
dashboard yq [path] [file]
dashboard tomq [path] [file]
dashboard propq [path] [file]
dashboard iniq [path] [file]
dashboard csvq [path] [file]
dashboard xmlq [path] [file]
dashboard encode < input.txt
dashboard decode < token.txt
dashboard indicator set <name> <label> <icon> <status>
dashboard indicator list
dashboard indicator refresh-core [cwd]
dashboard collector write-result <name> <exit_code>
dashboard collector status <name>
dashboard collector list
dashboard collector job <name>
dashboard collector output <name>
dashboard collector inspect <name>
dashboard collector log
dashboard collector run <name>
dashboard collector start <name>
dashboard collector stop <name>
dashboard collector restart <name>
dashboard skills install <git-url>
dashboard skills uninstall <repo-name>
dashboard skills update <repo-name>
dashboard skills list
dashboard skill <repo-name> <command> [args...]
dashboard config init
dashboard config show
dashboard auth add-user <username> <password>
dashboard auth list-users
dashboard auth remove-user <username>
dashboard page new [id] [title]
dashboard page save <id>
dashboard page list
dashboard page show <id>
dashboard page encode [id]
dashboard page decode [token]
dashboard page urls <id>
dashboard page render [id|file]
dashboard page source <id|token>
dashboard action run <page_id> <action_id>
dashboard docker compose [--addon NAME] [--mode NAME] [--service NAME] [--project DIR] [--dry-run] <compose-args...>
dashboard serve [logs [-f] [-n N]|workers <N>] [--host HOST] [--port PORT] [--workers N] [--foreground]
dashboard stop
dashboard restart [--host HOST] [--port PORT] [--workers N]
dashboard shell [bash|zsh|sh|ps|powershell|pwsh]
dashboard version
dashboard <custom-subcommand> [args...]DESCRIPTION
The public dashboard entrypoint is intentionally kept thin.
It only:
bootstraps the repo lib path when running from a checkout
runs layered per-command hooks across
DD-OOP-LAYERSstages dashboard-managed built-in helpers under ~/.developer-dashboard/cli/dd/
resolves the effective command from the deepest child layer back to home
execs the resolved helper or custom command
The real built-in command implementations live outside this entrypoint, either in private staged helper scripts under share/private-cli/ or in reusable Perl modules loaded by those helpers.
PURPOSE
Public entrypoint script in the Developer Dashboard codebase. This file bootstraps the runtime, resolves DD-OOP-LAYERS hooks and command targets, stages private helpers, and hands execution off to the final command. Open this file when you need the implementation, regression coverage, or runtime entrypoint for that responsibility rather than guessing which part of the tree owns it.
WHY IT EXISTS
It exists as the one public executable users run. Its job is intentionally narrow: bootstrap the environment, evaluate layered hooks, resolve the final command, and hand off without owning the heavy implementation bodies itself.
WHEN TO USE
Use this file when you are changing top-level command bootstrap, layered hook execution, helper staging, or command handoff behaviour.
HOW TO USE
Run dashboard <command>. If you are changing this file, keep it focused on bootstrap, layered hook execution, helper staging, command resolution, and exec; move heavy behaviour into modules or staged helper scripts instead.
WHAT USES IT
It is used directly by end users, by tests that execute dashboard ..., by staged shell helpers that re-enter the public command, and by release/integration smoke flows.
EXAMPLES
dashboard paths
dashboard page listBoth commands go through this public switchboard, which then resolves hooks and hands off to the real helper implementation.