Scripting diagnostics and boundaries
Reference: This page is a source-based technical synthesis of the LaTeX chapter cited below. For exact syntax, availability or ABI signatures, verify the versioned source, manifest and executable tests.
Scope and source boundary
Script diagnostics must identify the boundary between syntax, evaluation, host integration and execution state.
Runtime operation requires observable startup, diagnostics, health, resource ownership and orderly shutdown. The source treats instrumentation and lifecycle as first-class engineering work. A successful startup does not prove that all services, transports or external dependencies are healthy, and an internal feature is not automatically a published contract.
Engineering rules
- Record startup prerequisites, configuration and failure surfaces.
- Instrument errors, correlations and operational latency where source support exists.
- Scope and release long-lived services, sessions and external handles.
- Check tests and manifests before describing a feature as production-ready.
Chapter outline (original LaTeX headings)
- Diagnostics as Part of the Runtime Contract
- Logging Levels
- Correlation Identifiers
- Action Diagnostics
- Provider and Broker Diagnostics
- Interpreter Diagnostics
LaTeX provenance
Primary chapter: Runtime/logiCells Runtime Programming with RadStudio/logging-diagnostics-and-monitoring.tex.