Adds a second dApp transport next to WalletConnect, following the Algorand
Foundation's Liquid Auth protocol: the wallet registers/uses a passkey at a
Liquid Auth service with the "liquid" extension (service challenge signed by
the account key, linked to the dApp's requestId), then negotiates a direct
WebRTC data channel (public Google STUN) and answers ARC-0027 messages:
arc0027:sign_transactions (ARC-0001) and the arc0060:sign_data extension.

- src/scripts/liquid/protocol.ts: ARC-0027 CBOR+base64url envelope, deep links
  (mirror of the codec in biatec-wallet-use-wallet-client)
- src/scripts/liquid/webauthn.ts: attestation/assertion ceremonies
- src/shared/liquid.ts: signaling socket + RTCPeerConnection per pairing,
  presence-driven renegotiation
- src/store/liquid.ts: sessions, requests, responses, ARC-60 domain checks
- src/shared/decodeSignRequests.ts: request decoders extracted from wc.ts and
  shared by both transports (accept base64 and base64url)
- signer/signLiquidChallenge (sk + HD accounts), liquid/reset on logout
- Connect page: "Liquid Auth" tab; request tables take a `namespace` prop
- docs/LIQUID_AUTH.md: protocol summary, trust model, service deployment
  (RP ID must be the wallet's domain, CORS with credentials)
- locales: connect.liquid.* in all languages (English text for now)
- playwright/unit/liquidProtocol.spec.ts

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [org.jetbrains.kotlin.jvm](https://github.com/JetBrains/kotlin) from 2.4.10 to 2.4.20.
- [Release notes](https://github.com/JetBrains/kotlin/releases)
- [Changelog](https://github.com/JetBrains/kotlin/blob/master/ChangeLog.md)
- [Commits](https://github.com/JetBrains/kotlin/compare/v2.4.10...v2.4.20)

---
updated-dependencies:
- dependency-name: org.jetbrains.kotlin.jvm
  dependency-version: 2.4.20
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

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

Every other registered top-level command has one, and the README's
command list is where the published docs link from. Generated with
cobra/doc and put through the same banner substitution the existing
pages carry, checked by regenerating nodekit_restart.md and diffing it
against the committed copy.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NMKTAqwAPrGqB8hvgmBWu5

The decision record still listed stopping the backward walk early on
--since as deliberately deferred, on the grounds that it would change
what the flag means for entries Keep never drops on time. Three
optimizations went in since and do exactly that: the walk stops once a
chunk's oldest line is older than the bound, a forward stream bisects to
the first entry at or after it, and an archive written entirely before
it is not opened at all, which is the only way to skip a compressed one.
Reviewers of #193 read the record against the code and found the
contradiction three times over, once per site.

The record was the stale half. --since bounds the region of the history
that is read, and an entry whose timestamp cannot be read is shown when
it falls in that region: a panic dump belongs to the moment the lines
around it were written, and one from two hours ago is not part of the
last fifteen minutes. Written down as a decision, with the reasoning
alongside the cost the three optimizations avoid, and cross-referenced
from each of them and from Filter.Keep. The sentence in sinceOffset
calling its answer "never a filter" was the specific claim that had
stopped being true.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NMKTAqwAPrGqB8hvgmBWu5

The prescreen searches the undecoded line for the filter text verbatim,
which is only sound for bytes JSON never rewrites. Quotes, backslashes
and non-ASCII were excluded on that basis; `<`, `>` and `&` were not,
and they should have been. logrus writes its JSON through Go's encoder
with HTML escaping left on, so where the decoded message holds one of
those characters the line holds \u003c, \u003e or \u0026. `nodekit logs
--filter '<nil>'` therefore found nothing, however many entries said
<nil>.

Those three bytes now fall through to the full parse, along with the
rest of the text the raw search cannot be trusted on.

The corpus line and the two filters added to the one-sided prescreen
test fail without the fix.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NMKTAqwAPrGqB8hvgmBWu5

Two problems in reader.go, both raised in review of #193.

The backward walk sized the file, then read chunks of it with ReadAt and
ignored the count returned. A file truncated in place or replaced by a
shorter one after that stat hands back a short read with io.EOF, leaving
the tail of the buffer zeroed; those NUL bytes were then split into
lines, parsed as entries and charged against the scan budget. The walk
now takes only the bytes actually read, and drops the carry from the
chunk above with them, since the two halves no longer abut and splicing
them would invent a line neither file contains.

Follow read its lines with ReadBytes, which accumulates until it finds
the delimiter. The cap below it only ever saw a line that had already
been buffered whole, so a runaway line was bounded by the writer rather
than by us. It now reads the way forEachLine does, keeping at most
maxLineBytes across ErrBufferFull and discarding the rest, which is
where ParseLine would have sent it anyway.

The stale-size test fails without the first fix, emitting a 384-byte
entry of NULs. The follow test does not discriminate on output, since
the old path arrived at the same truncation by a more expensive route;
it guards the part of the rewrite that could go wrong, that the
discarded remainder does not disturb the line after it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NMKTAqwAPrGqB8hvgmBWu5

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps `kotlin` from 2.4.10 to 2.4.20.

Updates `org.jetbrains.kotlin:kotlin-gradle-plugin` from 2.4.10 to 2.4.20
- [Release notes](https://github.com/JetBrains/kotlin/releases)
- [Changelog](https://github.com/JetBrains/kotlin/blob/master/ChangeLog.md)
- [Commits](https://github.com/JetBrains/kotlin/compare/v2.4.10...v2.4.20)

Updates `org.jetbrains.kotlin.plugin.compose` from 2.4.10 to 2.4.20
- [Release notes](https://github.com/JetBrains/kotlin/releases)
- [Changelog](https://github.com/JetBrains/kotlin/blob/master/ChangeLog.md)
- [Commits](https://github.com/JetBrains/kotlin/compare/v2.4.10...v2.4.20)

---
updated-dependencies:
- dependency-name: org.jetbrains.kotlin:kotlin-gradle-plugin
  dependency-version: 2.4.20
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: org.jetbrains.kotlin.plugin.compose
  dependency-version: 2.4.20
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

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

This commit syncs the stable release version back to main branch
to ensure the next beta cycle starts from the correct version base.

Release: 2.4.1
Tag: v2.4.1

## [2.4.1](https://github.com/algorandfoundation/algokit-lora/compare/v2.4.0...v2.4.1) (2026-09-10)

### 🐛 Bug Fixes

* use utils 9.2.2 to work with Pera's PQ fee changes ([#609](https://github.com/algorandfoundation/algokit-lora/issues/609)) ([7461262](https://github.com/algorandfoundation/algokit-lora/commit/746126278c85c16b1da5c8570e0e156aafb24de4))