Updates the requirements on [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/parser) to permit the latest version.
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/parser/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.69.0/packages/parser)

---
updated-dependencies:
- dependency-name: "@typescript-eslint/parser"
  dependency-version: 8.69.0
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>

Updates the requirements on [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin) to permit the latest version.
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.69.0/packages/eslint-plugin)

---
updated-dependencies:
- dependency-name: "@typescript-eslint/eslint-plugin"
  dependency-version: 8.69.0
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: cce <51567+cce@users.noreply.github.com>

verify_deployment.py:276 printed a U+2194 inside the DRIFT branch. On a
cp1252 console that raises UnicodeEncodeError *after* the comparison has
run and correctly found the mismatch, so the process dies inside its own
failure report and exits 2 ("could not complete the check") instead of 1
("DRIFT").

The exit codes are a contract, stated in that file's own docstring: 0
match, 1 drift, 2 could not check. A reviewer who sees 2 concludes the
tooling failed, not that the deployment diverged. So this downgraded a
real finding to an inconclusive one -- silently, and only on the platform
the maintainer actually works on.

It survived this long because the line only executes when something is
wrong. No green run could ever reach it. That is exactly the shape of
defect this repo keeps finding: a path that is never exercised until it
matters.

Adds sdk/tests/test_reports_print_on_a_windows_console.py, which scans the
scripts a reviewer is told to run for characters cp1252 cannot encode on
print lines. Em dash and ellipsis are deliberately allowed -- they ARE in
cp1252 and are used throughout these reports; flagging them would make the
guard unusable and it would be deleted.

The guard was mutation-tested rather than trusted: reintroducing the U+2194
makes it fail, and it does not fire on plain ASCII or on em dash/ellipsis.
A scan that cannot fail would have been worth nothing here.

Suite: 145 passed, 5 skipped. verify_deployment.py still prints MATCH.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Close the TestNet contract drift: deploy app 770964251 from the committed artifact

See https://github.com/algorandfoundation/algokit-utils-ts/pull/612

README tells reviewers to run the hermetic verification, and running it
unpacks the pinned Falcon tarball to falcon-src/ and builds in place,
leaving codec.lib and libfalcondet1024.pdb behind. .gitignore covered
build/ but not these, so following the documented path left three
untracked files and a dirty `git status`.

Found by actually running the advertised command rather than assuming it
was clean. Full run: 4 axes PASS, exit 0 -- including Axis C re-signing
the committed goldens byte-identically from a ziglang build, which is a
different compiler from the MinGW gcc used elsewhere in this session.
Cross-compiler byte-identity is what FALCON_FPEMU=1 exists to guarantee,
now demonstrated rather than asserted.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>