Which @angular/* package(s) are the source of the bug?

core

Is this a regression?

No

Description

When I run ng generate @angular/core:signal-input-migration on a brand new CLI-generated v19 project containing a decorator-syntax @input "foo", the migration analyzes tsconfig.app.json and tsconfig.spec.json and runs the migration for each of the tsconfigs. This results in template file having foo()() instead of foo(). If I delete tsconfig.spec.json, the migration only analyses tsconfig.app.json and runs once, resulting in foo() as expected.
This same behavior happens with the signal-query migration.

Please provide a link to a minimal reproduction of the bug

No response

Please provide the exception or error you saw

Please provide the environment you discovered this bug in (run ng version)

Angular CLI: 19.2.11
Node: 22.15.0
Package Manager: npm 10.9.2
OS: darwin arm64

Angular: 19.2.10
... common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1902.11
@angular-devkit/build-angular   19.2.11
@angular-devkit/core            19.2.11
@angular-devkit/schematics      19.2.11
@angular/cli                    19.2.11
@schematics/angular             19.2.11
rxjs                            7.8.2
typescript                      5.7.3
zone.js                         0.15.0

Anything else?

Have tried specifying analysis-dir option as well but get the same result.