Under the hood
An internal rule-target schema pipeline gained one extra wrapping layer
What
An internal code path involving a ruleTargetInput schema now passes through one additional wrapping function call, going from three nested calls to four.
Why
The finding doesn't indicate what this extra layer does, so no practical effect on Claude Code's behavior can be stated.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What the added wrapping function does and whether it changes any observable behavior around `ruleTargetInput` is not established.