chore: daily flake.lock update

[caffeine-ci-generic-rw]

Automated changes by the update-flake-lock GitHub Action.
as defined in .github/workflows/update-flake-lock.yml
and run in: https://github.com/caffeinelabs/motoko/actions/runs/26547852585/attempts/1:

Flake lock file updates:

• Updated input 'candid-src':
    'github:dfinity/candid/dd3d5ab' (2026-05-20)
  → 'github:dfinity/candid/f97db28' (2026-05-27)

[github-actions]

Cursor AI review

👍 APPROVE — looks safe to merge

Category	Assessment	Details
Summary	✅	Automated daily flake.lock bump: only candid-src moves from dd3d5ab (2026-05-20) to f97db28 (2026-05-27); no compiler, RTS, or workflow source changes.
Code Quality	✅	Mechanical lock update from the existing update-flake-lock workflow; no new code.
Consistency	✅	Matches the repo’s established flake-input pinning pattern (rev, narHash, lastModified).
Correctness	✅	Lock entry is internally consistent; candid-src is flake: false and used as a Nix source for didc/deser test fixtures (nix/tests.nix, nix/shell.nix), not as the Motoko compiler build.
Tests	✅	No .mo/.ok or compiler test edits; CI on this PR is the right gate for upstream candid test-suite drift.
Changelog	✅	Build-input pin only; no user-visible language, prelude, or CLI behavior change.

Verdict

Decision: APPROVE
Risk: Very Low
Reason: Single-input flake.lock automation with no Motoko compiler, codegen, RTS, or typechecker changes. Residual risk is confined to Nix candid integration tests if upstream fixtures changed; that is appropriate for CI on merge.

---

Generated for commit eaa87a8

[github-actions]

Comparing from ea3801a to eaa87a8:
The produced WebAssembly code seems to be completely unchanged.
In terms of gas, no changes are observed in 5 tests.
In terms of size, no changes are observed in 5 tests.