Targeted Documentation Accuracy Audit

Reviewed PrintMaster source snapshot: 565f4c0 (565f4c0762e467f083f54a9e0e7f6bc23ada56c3), on 2026-10-02. This page summarizes the repository audit record.

This was a targeted, source-based operational accuracy pass, not an exhaustive documentation or security audit, nor a live deployment certification. A follow-up reviewed five server operations and validated their OpenAPI contract; other API operations remain outside scope. Imported source/sourceCommit metadata records provenance, not proof of accuracy. Runtime code at the reviewed snapshot took precedence over stale README, example, and template comments.

Reviewed Scope

The original pass corrected configuration, installation, features, Docker deployment, server overview, historical security architecture, and WebSocket proxy notes. Existing headings were retained for linked-anchor compatibility. The historical security design is explicitly legacy; its planned controls and examples must not be read as shipped behavior.

Verified Operational Findings

All source links below are pinned to the reviewed PrintMaster program commit, not the documentation repository.

• CLI: Removed unsupported -port, -data-dir, -log-level, and old overview -db examples; documented supported configuration, generation, service, output, health, and version flags. Evidence: agent flags, server flags.
• Server config and stores: TOML uses [server], not [web]; database settings use driver/dsn, not type/postgres_url. Implemented stores are SQLite and PostgreSQL. [logging].file is unsupported. Evidence: server config, common config, store.
• Server listeners/TLS: Standalone defaults to HTTPS 9443. HTTP 9090 requires BEHIND_PROXY=true, PROXY_USE_HTTPS=false; true selects HTTPS upstream. TLS modes are self-signed, letsencrypt, and custom, with minimum TLS 1.2. Evidence: listeners, TLS.
• Server image identity: Alpine 3.21 with shell/tooling and default PUID=0/PGID=0, ownership setup, and optional su-exec privilege drop; not a distroless UID-65532 image. Evidence: Dockerfile, entrypoint.
• Bootstrap user: Startup creates the configured username only if absent; it does not reset an existing user’s password or role. Evidence: bootstrap implementation.
• Agent local auth: Protected routes do not admit every remote client. Loopback bypass requires allow-local-admin; forwarding headers affect the current detector, so direct access and proxy headers must be controlled. Evidence: agent auth, agent config.
• Agent web listeners: Runtime unified/UI defaults are HTTP 8080 and HTTPS 8443. Legacy TOML enable_tls is not the runtime switch; unsupported certificate fields were removed from examples. Evidence: agent runtime, settings defaults, settings types.
• Alerts: Seeded toner warning is at or below 20%; critical is at or below 5%. Supply rules evaluate toner levels, not dedicated drum, fuser, waste-toner, or paper-out thresholds. Evidence: seeded rules, evaluator.
• Proxy transport: WebSocket dispatch invokes local handlers directly. Printer proxy supports HTTP/HTTPS and selected streaming paths; ordinary paths still buffer and use default timeouts. Evidence: server proxy, agent WS client, printer proxy.
• TLS trust: The HTTP client’s custom CA pool is not propagated to WSS. Printer HTTPS can skip certificate verification. WebSocket transport is encrypted only with WSS. Evidence: HTTP client, WSS client, printer transport.

Validation Boundaries

The original audit record reports 11 passing docs unit tests, a pinned Hugo 0.150.1 Docker build with --gc --minify --panicOnWarning, and a generated-site check of 52 HTML pages and 50 search entries with local links/assets/anchors passing. These are historical results for that pass, not current page counts or evidence of runtime correctness. No live printer, agent, or server deployment was exercised.

The original operational pass did not review API pages or contracts. The separately documented server API subset now covers five existing operations at the same snapshot; download its YAML. That limited reference does not make the remaining API surface audited or establish a broad stable API guarantee.

Remaining Work — Explicitly Nonexhaustive

• Audit API routes beyond the five-operation subset and retained feature-guide request examples.
• Review getting started, troubleshooting, updates, discovery, and other untouched guides.
• Correct known stale Unraid proxy/environment examples; review database upgrades and other deployment guidance.
• Check agent component roadmap claims, logger/module overviews, project security examples, and other roadmap/release/development designs.
• Perform a protocol-level review of historical proxy message examples and function inventories.
• Verify package URLs, published image architectures/tags, UI navigation labels, metric retention, schedules/groups, and performance figures; these were not exhaustively checked.
• Review migration records, imported source docs, templates, and package/release/installer configuration separately; none was certified by the operational pass.

Do not infer that untouched pages, or every paragraph of a corrected page, are accurate from this record. Recheck source behavior when upgrading beyond 565f4c0.