Repository: angular
Issue: Untracked() should break cycle in computations
Labels: area: core,needs: clarification,core: reactivity

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

core

### Is this a regression?

No

### Description

I just updated to the **19.1.2** version and suddenly I get an error at compiling time: `Error: Detected cycle in computations.`

It made me discover that I have a `rxResource` whose request calls a `linkedSignal` that depends on the resource's value itself.

Here's part of my code: 
- I want `loadedRanges` to update with the new range, but only after the resource has finished loading.
- On the other hand, the resource needs access to the `loadedRanges` to know if the range has already been loaded or not

But if I use `untracked` in the resource's request, shouldn't it break the cycle? Especially if it depends on a `linkedSignal` which should always have a value.

```
  from = signal(new Date());
  to = signal(new Date());

  loadedRanges = linkedSignal<any, any[]>({
    source: () => ({
      value: this.resource.value()
    }),
    computation: (source, previous) => {
      const previousRanges = previous?.value || [];
      if (source.value) {
        const newRange = {
          from: untracked(() => this.from()),
          to: untracked(() => this.to()),
        };
        return this.mergeRanges([...previousRanges, newRange]);
      } else {
        return previousRanges;
      }
    },
  });

  resource = rxResource<any[], any>({
    request: () => {
      const requiredRange = {
        from: this.from(),
        to: this.to(),
      };
      const ranges = untracked(() => this.loadedRanges()); // <-- here I use the untracked
      const isLoaded = this.isRangeFullyCovered(requiredRange, ranges);
      return isLoaded ? undefined : true;
    },
    loader: () => {
      // call to the API
      return of([]);
    }
  });
```

My code was working without problems before updating (with the v19.0.1).
Am I wrong stating that untracked should break the cycle, and the error shouldn't be triggered?

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-8jm3wgx2?file=src%2Fmain.ts

### Please provide the exception or error you saw

```true
Error: Detected cycle in computations.
```

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

```true
Angular CLI: 19.1.3
Node: 18.19.1
Package Manager: npm 10.2.4
OS: darwin x64

Angular: 19.1.2
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
... service-worker

Package                              Version
--------------------------------------------------------------
@angular-devkit/architect            0.1901.3
@angular-devkit/build-angular        19.1.3
@angular-devkit/core                 19.1.3 (cli-only)
@angular-devkit/schematics           19.1.3
@angular/cdk                         19.1.0
@angular/cli                         19.1.3
@angular/fire                        19.0.0
@angular/material                    19.1.0
@angular/material-date-fns-adapter   19.1.0
@schematics/angular                  19.1.3
ng-packagr                           19.0.0
rxjs                                 7.8.1
typescript                           5.6.3
zone.js                              0.15.0
```

### Anything else?

_No response_