# [accounts-keystore-extension@1.0.0-canary.8](https://github.com/algorandfoundation/wallet-provider-extensions/compare/accounts-keystore-extension@1.0.0-canary.7...accounts-keystore-extension@1.0.0-canary.8) (2026-08-13)

### Bug Fixes

* **keystore-core:** backwards compatibility for deprecated hd-seed ([9559130](https://github.com/algorandfoundation/wallet-provider-extensions/commit/9559130bf9d0bab1ad2c7fe13e9ae636be61931c))

### Features

* **keystore-core:** native PBKDF2 for deterministic-P256 ([c92e5da](https://github.com/algorandfoundation/wallet-provider-extensions/commit/c92e5da9f3c6925745012dd488ef16360bd5d719))

# [keystore@1.0.0-canary.21](https://github.com/algorandfoundation/wallet-provider-extensions/compare/keystore@1.0.0-canary.20...keystore@1.0.0-canary.21) (2026-08-13)

### Bug Fixes

* **keystore-core:** backwards compatibility for deprecated hd-seed ([9559130](https://github.com/algorandfoundation/wallet-provider-extensions/commit/9559130bf9d0bab1ad2c7fe13e9ae636be61931c))

### Features

* **keystore-core:** native PBKDF2 for deterministic-P256 ([c92e5da](https://github.com/algorandfoundation/wallet-provider-extensions/commit/c92e5da9f3c6925745012dd488ef16360bd5d719))

# [keystore-web@1.0.0-canary.2](https://github.com/algorandfoundation/wallet-provider-extensions/compare/keystore-web@1.0.0-canary.1...keystore-web@1.0.0-canary.2) (2026-08-13)

### Bug Fixes

* **keystore-core:** backwards compatibility for deprecated hd-seed ([9559130](https://github.com/algorandfoundation/wallet-provider-extensions/commit/9559130bf9d0bab1ad2c7fe13e9ae636be61931c))

### Features

* **keystore-core:** native PBKDF2 for deterministic-P256 ([c92e5da](https://github.com/algorandfoundation/wallet-provider-extensions/commit/c92e5da9f3c6925745012dd488ef16360bd5d719))

# [react-native-keystore@1.0.0-canary.17](https://github.com/algorandfoundation/wallet-provider-extensions/compare/react-native-keystore@1.0.0-canary.16...react-native-keystore@1.0.0-canary.17) (2026-08-13)

### Bug Fixes

* **keystore-core:** backwards compatibility for deprecated hd-seed ([9559130](https://github.com/algorandfoundation/wallet-provider-extensions/commit/9559130bf9d0bab1ad2c7fe13e9ae636be61931c))

### Features

* **keystore-core:** native PBKDF2 for deterministic-P256 ([c92e5da](https://github.com/algorandfoundation/wallet-provider-extensions/commit/c92e5da9f3c6925745012dd488ef16360bd5d719))

# [keystore-node@1.0.0-canary.2](https://github.com/algorandfoundation/wallet-provider-extensions/compare/keystore-node@1.0.0-canary.1...keystore-node@1.0.0-canary.2) (2026-08-13)

### Bug Fixes

* **keystore-core:** backwards compatibility for deprecated hd-seed ([9559130](https://github.com/algorandfoundation/wallet-provider-extensions/commit/9559130bf9d0bab1ad2c7fe13e9ae636be61931c))

### Features

* **keystore-core:** native PBKDF2 for deterministic-P256 ([c92e5da](https://github.com/algorandfoundation/wallet-provider-extensions/commit/c92e5da9f3c6925745012dd488ef16360bd5d719))

# [keystore-core@1.0.0-canary.2](https://github.com/algorandfoundation/wallet-provider-extensions/compare/keystore-core@1.0.0-canary.1...keystore-core@1.0.0-canary.2) (2026-08-13)

### Bug Fixes

* **keystore-core:** backwards compatibility for deprecated hd-seed ([9559130](https://github.com/algorandfoundation/wallet-provider-extensions/commit/9559130bf9d0bab1ad2c7fe13e9ae636be61931c))

### Features

* **keystore-core:** native PBKDF2 for deterministic-P256 ([c92e5da](https://github.com/algorandfoundation/wallet-provider-extensions/commit/c92e5da9f3c6925745012dd488ef16360bd5d719))

The module docstring reads as evidence: "ANY divergence in the Gaussian
sampler, rounding, or compressed encoding surfaces here as a byte mismatch.
That divergence-detection is the entire point of this KAT." Nothing in it has
ever run.

Two independent reasons, and the second is the one that gets missed:

  1. Nothing installs algo-pqc-kit. pyproject declares only `algorand` and
     `dev`; both CI test jobs run pip install -e ".[dev]". All three
     differential tests carry @requires_apk and skip on every run.
  2. Installing the package would not be enough. _ApkAdapter is wired to a
     GUESSED upstream API shape and degrades to NotImplementedError -> skip if
     that guess is wrong. The upstream API still has to be confirmed.

The fixture IS populated, so this is a working test wired to a dependency no
environment provides - which is why it reads green.

Adds TRELYAN_REQUIRE_INTEROP=1, mirroring TRELYAN_REQUIRE_KAT in
test_signature_kat.py, where a skip fails the job. CI does NOT set it, because
the dependency genuinely is not available. It exists so the inertness is
testable on demand rather than taken on trust, and so that pinning upstream
later is one environment variable away from being enforced.

No behaviour change: unset, the new test skips like the other three.

interop_algo_pqc_kit.py called

    c.inscribe(cell, artifact_hash, sig, b"ipfs://demo")

but inscribe()'s third positional parameter is a PRIVATE KEY: the client
re-derives M and signs internally (inscription.py:135-136). The signature
reached falcon.py:192 and raised "privkey must be 2305 bytes, got ...".

This happened in BOTH branches, so the flagship's documented interop example
had never run as shipped. Nothing caught it because no test in this repo
touches examples/ at all -- and the file's own "NOT yet executed end-to-end"
disclaimer was doing the job a test should have been doing.

The INTEROP_RECONCILED=True branch cannot be written against today's SDK
regardless of how the encoding question lands: submitting an externally
produced signature needs an inscribe_presigned() entry point, and none
exists. That branch now stops with an explicit error naming the missing API
instead of shipping code that cannot run.

Adds tests/test_examples_call_sites.py, which binds every example's SDK call
sites to the real inspect.signature and checks provenance: a value produced
by .sign() must never land in a `privkey` parameter. Arity alone cannot see
this -- a signature and a private key are both bytes and both fit the slot.

Security impact: none at runtime. Fail-closed, no key disclosure, nothing
deployed. The defect is that an audit-bound repo shipped an examples/ file
that could not execute, and had no mechanism that would ever say so.

register_cell asserts three things about a Cell ASA:

  :205  clawback == zero_address
  :206  freeze   == zero_address
  :207  manager  == zero_address

Only :205 had a test. test_register_rejects_clawback_cell's docstring claims
to cover "clawback (or freeze/manager)" but its fixture sets only `clawback`,
and the asserts are sequential, so it trips :205 and the other two are never
evaluated. The words freeze and manager appear in this file only in prose.
Deleting :206 and :207 turns nothing red.

Not cosmetic. A live freeze address can freeze the holder AFTER registration,
and a live manager can RE-ADD clawback and freeze afterwards - which restores
both AssetHoldingGet timing vectors the hardening closed at the source. The
manager guard is the load-bearing one: it is what makes the cell's config
immutable rather than merely clean at registration time.

Adds one fixture per guard and asserts WHICH guard fired, so a future
reordering of the three asserts cannot silently leave one uncovered again.

VERIFICATION IS INCOMPLETE, and deliberately not overstated: unlike the other
contract test added in this series, these two are NOT mutation-proved. Docker
Desktop on this machine wedged part-way through (orphaned runtime sockets that
cannot be deleted without a reboot - my own hard-kill of the process is the
likely cause), so LocalNet is unavailable and the suite cannot run here.

What HAS been checked:
  - both tests collect (24 collected, up from 22)
  - the asserted strings match the contract's messages exactly, one occurrence
    each in inscription.py and in the test
  - the fixtures mirror test_register_rejects_clawback_cell, which passes

What has NOT been checked: that they fail when :206/:207 are deleted. The CI
job in the contract-suite PR runs LocalNet successfully on a GitHub runner, so
that is where this should be confirmed.

Found by an adversarial claim-vs-enforcement sweep (TCE-19).

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

# [keystore@1.0.0-canary.20](https://github.com/algorandfoundation/wallet-provider-extensions/compare/keystore@1.0.0-canary.19...keystore@1.0.0-canary.20) (2026-08-13)

### Features

* keystore migrations ([a7ed907](https://github.com/algorandfoundation/wallet-provider-extensions/commit/a7ed90757812833b0712b85438651d008a1e49dc))

# [react-native-keystore@1.0.0-canary.16](https://github.com/algorandfoundation/wallet-provider-extensions/compare/react-native-keystore@1.0.0-canary.15...react-native-keystore@1.0.0-canary.16) (2026-08-13)

### Features

* keystore migrations ([a7ed907](https://github.com/algorandfoundation/wallet-provider-extensions/commit/a7ed90757812833b0712b85438651d008a1e49dc))