Decide classification of nested-binder-lambda after client probe #1046
Description
Decision needed
Decide whether nested-binder-lambda should remain a static-indicator or be promoted based on the client evidence from wrightkit/workshop-rs#521.
On client 2.25.0.1 - 154504.1 (zh-CN), the lambda probe appeared in the editor but produced 错误：此脚本中某些值无法叠加至多于1层。. The source-position control appeared without an observed error. The probes tested one particular pair of shapes; they do not establish the behavior of every binder combination. The client test did not measure runtime behavior.
Scope
Review the client evidence, the lint's current detection coverage, and its user-facing classification. Decide whether promotion is justified, and define any required changes or further probes. Do not assume the result applies to all five binder values without evidence.
Acceptance criteria
- The owner records a decision and its evidence, including the scope and remaining uncertainty.
- Any implementation or additional client probes required by the decision are tracked separately.
Activity
docs: record nested binder client probe (#597)
e54-bot commentedon Nov 3, 2026
Owner decision (2026-11-04): keep
nested-binder-lambdaas astatic-indicatorwarning. No promotion.Evidence: wrightkit/workshop-rs#521 (recorded in
docs/import-limits.mdby wrightkit/workshop-rs#597). On client2.25.0.1 - 154504.1(zh-CN), the lambda probe produced the nesting error and the source-position control did not. That is one accept/reject pair for one shape.Remaining uncertainty: the client behavior of the other binder combinations (the five binder values in each position) is not measured, so a promotion could report shapes the client accepts. Revisit only when probes for more combinations exist. No implementation or further probe is required by this decision, so nothing is tracked separately.