Fixes #597 

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

On recent Node 22s, they fail with the following weird error:

```
 [BackendBuildError] Unable to deploy due to CDK Assembly Error
    ∟ Caused by: [_AssemblyError] Assembly builder failed
  Error: aused by: [Error] ENOENT: no such file or directory, open '/tmp/cdk-integ-0dbc757n71oo/node_modules/@aws-amplify/backend-output-storage/lib/index.js?tsx-namespace=1749655833950'
```

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

…n locate the source file (#592)

With this change

```
"fileUrlPath": "lib/payloads/hotswap.d.ts",
```

becomes

```
"fileUrlPath": "lib/payloads/hotswap.ts",
```

in `toolkit-lib.api.json`.

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

Co-authored-by: Ian Hou <45278651+iankhou@users.noreply.github.com>

Updates the engine contract `ICli` to support other engines. The main
change here is to make all methods async. For `watch` this required some
more changes and a switch to a callback based system instead of
returning and EventEmitter. Finally the PR changes the return type of
`list` to be an array of stack names instead of a newline separated
string.

Due to the "viral" nature of async/await, this touches a lot of code
paths.

Contains some related clean-up:

- simplified the mock engine `MockCdkMocks` to not depend on the anyway
unused `CdkCliWrapper` any more
- set `isolatedModules` in tsconfig instead of jest in `integ-runner`
- Remove duplicated command input types from `cdk-cli-wrapper` in favor
of the same types from `@aws-cdk/cloud-assembly-schema`

After this change is in, it will be possible to implement an engine
based on toolkit-lib.

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

…ailing due to an upstream error (#606)

Upstream problem:
aws-amplify/amplify-backend#2849

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

…tifact (#590)

This gives libraries the opportunity to report the feature flags they
support, and what values they saw during synthesis.

I purposely did not bump the schema version, since I want this feature
to be fully incremental without disturbing existing users: there is no
consumption of this new schema yet, that will come later, but we don't
want to force people to upgrade their CLI's unnecessarily. That's bad
DX.


---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

---------

Signed-off-by: github-actions <github-actions@github.com>
Co-authored-by: github-actions <github-actions@github.com>
Co-authored-by: Momo Kornher <kornherm@amazon.co.uk>

This PR updates the PR lint workflow and projenrc configuration to
dynamically generate the list of allowed scopes based on the monorepo
packages.

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

Small QoL improvement so that engineers always have an esbuild bundle
metafile available to [analyze](https://esbuild.github.io/analyze/).

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

Editorial changes to the CLI readme to ensure this will end-up in the
correct release notes.

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

#595)

Fixes [#30583](aws/aws-cdk#30583)

CLI’s context-passing mechanism relied on serialising every entry to a
"KEY=VALUE" string, leading CLI to only allows passing string context,
so even JSON booleans (true/false) and numbers became plain strings.
This resulted in losing the typed context, like boolean feature-flags
are always being passed as string "true"/"false". This incorrectly
passed feature flags caused certain integration tests snapshot in the
[aws-cdk](https://github.com/aws/aws-cdk/tree/main/packages/%40aws-cdk-testing/framework-integ)
library to be updated with incorrect values causing the integration
tests to fail.

This fix retains the type of context values when passed via CLI, by
correctly JSON parsing the context while building user configuration.
Values that aren’t valid JSON will fall back to plain strings, so
existing workflows should continue working as is. This will restore
correct typing for feature flags without disrupting existing tests.

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

---------

Co-authored-by: Momo Kornher <kornherm@amazon.co.uk>

We used to upload logs with the name of the suite we're running, but now
that we are running the same suite multiple times with different node
versions it's possible to get the following error:

```
Error: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
```

We need to make the logs entirely unique by including all matrix
parameters.


---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

In #613 we made the artifact ID unique for different Node versions, but
the characters in `lts/*` aren't all safe for inclusion in the artifact
ID.

Slugify the artifact ID first before using it.

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

Upgrades project dependencies. See details in [workflow run].

[Workflow Run]:
https://github.com/aws/aws-cdk-cli/actions/runs/15669014073

------

*Automatically created by projen via the "upgrade" workflow*

---------

Signed-off-by: github-actions <github-actions@github.com>
Co-authored-by: github-actions <github-actions@github.com>
Co-authored-by: Momo Kornher <kornherm@amazon.co.uk>

Any tests that synth an assembly require a little longer to run. Let's
just acknowledge that. Otherwise we keep running into test failures due
to timeouts locally.

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

The title says it all :)

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

---------

Signed-off-by: github-actions <github-actions@github.com>
Co-authored-by: github-actions <github-actions@github.com>

…of workflow (#608)

This makes it possible to change the package config on a branch, and
test it, without having to merge workflow changes to `main` to properly
pick up that new package.

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

Replaces the deprecated `ts-jest` config of the same name.

Also includes some small alignments of `tsconfig.dev.json` files with
their corresponding parent, where previously missed.
Also removes `dom` from `integ-runner` since this is not needed.

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

---------

Co-authored-by: Rico Hermans <rix0rrr@gmail.com>