DEFAULT_WALK_LIMIT

The number of component instances walk will produce before giving up.

This count is not a property of the authored UI. A ChildList.Template instantiates its subtree once per item of an array the agent sends, so a surface of a dozen components expands to whatever the data model happens to say: a table of 900 rows over 13 components is already 11,701 instances. So the number is set well above what a bound on hand-authored component count would justify, because that reasoning does not apply to the half of the expansion that data drives.

It remains a bound, and walk still raises rather than truncating. A renderer that must show lists longer than this wants virtualization rather than a larger number here.

What it counts is every reference followed, not every component found. A reference naming a component that never arrived, one the cycle guard turns back, and one DEFAULT_MAX_DEPTH stops are each charged, though none of them is emitted. Counting only what resolved would leave the cheapest payload of all unbounded: a ChildList of a hundred thousand ids the agent never defined costs nothing to look up and one placeholder each to draw. So walk raises on surfaces it once returned a short list for, and the number below bounds the work, which is what the bound was ever for.