sloppy doctor

Inspect Sloppy artifacts and Plan-visible metadata.

sloppy doctor [artifacts-dir|plan.json|--plan <path>|--artifacts <dir>] [--format text|json] [--dispatch] [--report]

sloppy doctor reports Plan-visible configuration, capabilities, auth, providers, routes, runtime features, dependency metadata, and related artifact state. It is not a full system-install diagnosis command today.

What it checks

• native Plan parsing;
• route, provider, and capability metadata, including Program Plans with no route metadata by design and web Plans with partial/dynamic route metadata;
• route rate-limit metadata, partial rate-limit extraction, and public login routes with no rate-limit metadata;
• route dispatch metadata when --dispatch is passed;
• Plan-visible legacy health route metadata;
• dependency graph metadata and compatibility findings;
• native FFI metadata, dynamic library load checks, and symbol resolution;
• SQLite metadata and the fact that SQLite needs no external DB driver;
• PostgreSQL provider metadata with optional client-library guidance when the app uses PostgreSQL;
• SQL Server provider metadata with optional Microsoft ODBC Driver 17/18 guidance when the app uses SQL Server.

When invoked without an artifact path or Plan path, doctor reports the current CLI/package bootstrap state it can see from the installed files. That output is basic availability evidence, not a complete operating-system or package-manager health check.

Text output

Current text output uses status-prefixed lines. The following example is from a contributor source build without the V8 bridge enabled, so it shows the engine.v8 and Plan-extraction warnings you'd see during early bring-up. A supported npm platform package includes the runtime that executes handlers, so on those installs engine.v8 is not warned about and app.plan.* rows reflect the artifact you point at:

Sloppy Doctor

[ok] bootstrap.assets: bootstrap runtime asset found
[warn] engine.v8: V8 bridge disabled in this build; V8 runtime tests not run
[warn] providers.live: live provider checks are not configured by default and no live DB was contacted
[warn] package.runtime: package release status requires package smoke
[ok] app.plan.parse: app plan parsed by native Plan v1 parser
[warn] app.plan.routes: no route metadata present
[warn] app.plan.providers: provider metadata not present
[warn] app.plan.capabilities: capability metadata not present
[ok] dependency.graph: dependency graph available: 1 package(s), 4 module(s), 1 Node binding(s)
[ok] ffi.native: native FFI metadata available: 1 library, 4 function(s)
[ok] sqlite.provider: SQLite is embedded; SQLite providers do not require PostgreSQL, SQL Server, libpq, or ODBC
[warn] postgres.provider: PostgreSQL is optional; apps that use it need a connection string and libpq from a bundled provider package when available or from the system
[warn] sqlserver.provider: SQL Server is optional; apps that use it need Microsoft ODBC Driver 17 or 18 visible to the driver manager

The exact rows depend on the current platform, build, package, and provider environment.

With --dispatch, doctor also reports the Plan route dispatch mode, artifact status/hash, classic fallback availability, segment-trie metadata, native no-JS endpoint count, and native URL writer count. In this alpha, native-compiled means Plan-backed native dispatch with routes.slrt integrity validation: the compiler emitted routes.slrt, the Plan recorded its hash, and the runtime validated it before building the native dispatch table from app.plan.json.

Doctor also reports route JSON readiness when dispatch metadata is available:

• schema-backed native request route counts
• native JSON response route counts
• aggregate JSON fallback counts
• per-route body JSON bindings without schema metadata
• per-route request and response fallback reasons, including route identity

These warnings keep generic paths visible instead of silent.

The richer app.health() and app.management() bootstrap app-host APIs expose their live state through the endpoints they register. App-host tests can inspect the same state through app.__getPlanContributions().ops.

With --report, doctor writes .sloppy/reports/doctor-report.json and breadcrumb JSONL. The report is local evidence for the command invocation and is not uploaded.

Full system/package doctor checks are planned separately. Today, doctor is focused on Sloppy artifacts, package bootstrap files, and Plan-visible metadata.

Exit codes

Code	Meaning
0	No errors
1	One or more checks reported error

Warnings are informational unless the checked Plan requires the unavailable feature. Missing PostgreSQL or SQL Server support is reported as an optional provider dependency, not as a broken Sloppy install for SQLite-only apps.