Reviewing Llama Stack Code

Code review in llama-stack focuses on implementation logic, not auto-generated recordings. Ensure CI checks pass, verify backward compatibility of APIs, assess distributed-system resiliency patterns, and confirm proper error propagation and logging before approving changes.

Backward compatibility review ensures existing APIs remain stable across versions. Examine breaking changes for clear migration guidance, validate that existing client code continues to function, and document any necessary deprecation paths.

Distributed-systems review assesses failure modes, synchronization patterns, telemetry propagation, and resiliency. Check that error handling works across service boundaries, logging captures distributed traces, and components fail gracefully under network partitions.

Recordings folders contain auto-generated CI test outputs. Ignore their contents during manual code review and focus on the implementation logic; the CI pipeline validates recordings separately.

llama-stack contributions require appropriate test coverage and clear documentation. Verify that changes include integration tests, that new APIs are documented, and that distributed-system implications are explained for operators.