handledProperties wiring-evidence matrix

For every SDK provider class declaring handledProperties, checks that each declared property is actually CONSUMED — a read off the template property bag (properties['X'] / properties.X / a destructure), tracked per class through this.helper(properties) delegation. A declaration with no such evidence is either a wiring gap or a mis-declared property (the #1392 ECRProvider class), and gen-property-coverage.ts cannot see it: that pre-flight passes on the strength of the declaration alone.

A computed read properties[k] also counts when k iterates a literal name table (table-loop), but only when the loop body DELIVERS one of those reads. A body that merely compares them — an immutability guard or a change-detection scan — earns nothing, since crediting it would let one syntactic site vouch for every name in the table on the strength of a diff. The table itself is resolved LEXICALLY from the loop outward, so a table declared inside another class's method cannot vouch for this one. Reads off previousProperties are never evidence.

Summary

• Provider classes classified: 84
• Declared properties: 1138 (1136 with read evidence)
• Fully wired classes: 82
• Allow-listed classes (visible, non-blocking): 2
• Classes with a whole-bag blind spot (recorded, never an excuse): 22
• Wiring gaps (blocks CI): 0

Wiring gaps

None. Every declared handledProperties entry has read evidence or a rationale'd allow-list entry.

Allow-listed declarations — VISIBLE, non-blocking

Declared handled with no read evidence, deliberately not failing CI. A KNOWN GAP rationale is a real un-wired property awaiting a fix (removing the entry is what makes this critic verify that fix); a NOT-A-BUG rationale is a declaration that is correct without a read.

Whole-bag blind spots — visibility only, NOT an excuse

Sites where a whole property bag left the evidence walk (a spread, an unresolvable computed key, a call this script cannot resolve). Every class below still had to earn read evidence for each declared property; the list exists so a reviewer can see where the analysis is blind. Two fully-understood non-deliveries are deliberately NOT listed: a call whose result only feeds a comparison or a .length measurement (JSON.stringify(properties) === ...), and a comparison-only table loop. Nothing is hidden from the walk in either case — the site simply does not deliver.

Full classification