Dependency management and package installation stability. Goldie's declared dependency on `@swmansion/argent@^0.22.0` is unresolvable because that version range does not exist on the public npm registry.

## Bug

`npm i -g goldie` fails with:

```
npm error code ETARGET
npm error notarget No matching version found for @swmansion/argent@^0.22.0.
npm error notarget In most cases you or one of your dependencies are requesting
npm error notarget a package version that doesn't exist.
```

## Cause

Every published `goldie` version (checked 0.2.0 and 0.2.1) declares:

```json
"@swmansion/argent": "^0.22.0"
```

but the latest version of `@swmansion/argent` actually published to npm is `0.13.0` (both the `latest` and `next` dist-tags point to it). There is no published version in the `^0.22.0` range, so the install can never resolve for anyone.

```
$ npm view @swmansion/argent dist-tags --json
{
"latest": "0.13.0",
"next": "0.13.0"
}
```

## Repro

```
npm i -g goldie
```

## Expected

Either `goldie`'s dependency range is relaxed to match a published `argent` version, or a compatible `@swmansion/argent@0.22.0+` is published to npm.

## Environment

- npm registry (public)
- Node v25.1.0
- macOS