Explicit diagnostics

Request only useful sections/profile and explain the task/purpose. Diagnostics is a signed one-shot helper, separate from Daemon negotiated telemetry. Reading a stored report/inventory page does not authorize another collection.

Evidence and limitations

Retain original target/source/time, warning and unavailable/unsupported/partial coverage. Inventory/startup are explicit sections, with platform-specific results; Mac startup returns unsupported evidence, not measured duration. Empty or stale is not healthy zero. No guaranteed repair follows from a snapshot.

Use Mech's deferred diagnostic planner or your external assistant's discoverable CLI/API diagnostic capability. Review exact target and scope, then collect only with current access/local consent. Admission, explicit deadline/cancellation and uncertain execution stay separate: reconcile original operation, never blindly rerun a repair because acknowledgement was lost. Stored artifacts remain private.

Access, Mech, CLI and API describe authorized consumers. Monitoring setup follows its separate exact-review contract.

Startup evidence

A stored startup read begins no scan and never derives duration from uptime or monitoring. Explicit startup section collection is separate. Original period/source, comparison baseline and failure/unsupported coverage stay truthful; Mac duration is unsupported. A newer valid report may retain earlier measurements beside failure, while missing/transport failures need not replace canonical state.