NAME
Developer::Dashboard::Doctor - runtime permission doctor for Developer Dashboard
SYNOPSIS
my $doctor = Developer::Dashboard::Doctor->new(paths => $paths);
my $report = $doctor->run(fix => 1);DESCRIPTION
This module audits the current home runtime and any older dashboard roots that still exist in the user's home directory, checking that directories are owner-only and that files are readable only by the owner unless they are meant to stay owner-executable.
METHODS
new, run
Construct the doctor service and audit the known dashboard roots.
PURPOSE
Perl module in the Developer Dashboard codebase. This file audits and repairs dashboard runtime permissions and health checks. 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 to keep this responsibility in reusable Perl code instead of hiding it in the thin dashboard switchboard, bookmark text, or duplicated helper scripts. That separation makes the runtime easier to test, safer to change, and easier for contributors to navigate.
WHEN TO USE
Use this file when you are changing the underlying runtime behaviour it owns, when you need to call its routines from another part of the project, or when a failing test points at this module as the real owner of the bug.
HOW TO USE
Load Developer::Dashboard::Doctor from Perl code under lib/ or from a focused test, then use the public routines documented in the inline function comments and existing SYNOPSIS/METHODS sections. This file is not a standalone executable.
WHAT USES IT
This file is used by whichever runtime path owns this responsibility: the public dashboard entrypoint, staged private helper scripts under share/private-cli/, the web runtime, update flows, and the focused regression tests under t/.
EXAMPLES
perl -Ilib -MDeveloper::Dashboard::Doctor -e 'print qq{loaded\n}'That example is only a quick load check. For real usage, follow the public routines already described in the inline code comments and any existing SYNOPSIS section.