Here is a list of all topics with brief descriptions:

Kernel / native API	The backtest and forward-execution engine, and the API a host drives it with
Pine adapter (TradingView-parity policy layer)	The layer that turns a transpiled PineScript strategy into kernel commands and reproduces TradingView's own behaviour where it differs from a neutral engine — order priority within a bar, intraday caps, entry admission, rounding thresholds, the quirks a parity corpus measures
Types	POD types and enums passed across the C ABI
Strategy lifecycle	Create, run, and destroy a compiled strategy instance
Per-strategy configuration	Override `input`
Historical to realtime streaming	Warm on confirmed OHLCV and continue the same strategy instance on normalized ordered trades from any data source
Live-runtime surface (ABI v4)	Default-off flags and read-only accessors used by pineforge-live
Version query	Runtime version metadata
Generated Strategy Settings	Additive, opt-in validation and effective-settings receipts
Recorded outputs	What a module records besides trades, read after a run or between the inputs of a stream (docs/outputs.md)
Status codes	Every `int`-returning symbol here answers 0 or one of these
Translated enumerations	Every value below is the exact integer of the C++ alternative it names, pinned by static_asserts in src/native_c_host.cpp
Transport types
Entry points