Initial public release

Aere Network public source. Everything here can be checked against the live
chain (chain id 2800, https://rpc.aere.network).

Scope note, stated up front rather than buried: consensus on chain 2800 is
classical secp256k1 ECDSA QBFT. The post-quantum work in this repository is at
the signature, precompile, account and transport layers. Nothing here makes the
consensus post-quantum, and no document in it should be read as claiming so.

REPRODUCE.md

@@ -108,9 +108,37 @@ Foundry. It lives at `aerenew/contracts/test/*.test.js`.
 ```bash
 cd aerenew/contracts
 npm ci                     # installs the pinned toolchain (hardhat, OZ 4.9.x)
-npx hardhat test           # runs the full suite
+npx hardhat test           # SEE THE WARNING BELOW: this currently crashes partway
 ```
 
+> **KNOWN DEFECT, measured 2026-07-20, published here rather than left for you to discover.**
+>
+> `npx hardhat test` does **not** currently run to completion on this repository. It exits with a
+> segmentation fault partway through, and it does so non-deterministically: two runs on the same
+> machine on the same day died at different points, one after about 49 minutes having reported 1,447
+> passing across 128 suites, the other after about 5 minutes at 846 passing across 44 suites. Because
+> the crash point moves, neither partial count is a valid test result and we do not quote either as
+> one.
+>
+> A crash whose location moves under identical input points at resource exhaustion rather than a
+> failing test. We have not yet isolated it, and we are not going to claim we have.
+>
+> **What works today:** running suites individually, which is how every per-file command elsewhere in
+> this document is written. Those commands are real and they pass. For example:
+>
+> ```bash
+> npx hardhat test test/AereFalcon512Verifier.test.js
+> ```
+>
+> **What this means for the coverage figure below:** it is a genuine lower bound, not a target we are
+> hedging. Fourteen test files cannot be instrumented at all on a 16 GB machine, and they are
+> disproportionately the post-quantum verifier suites, whose contracts therefore read as 0 percent
+> covered even though their tests pass when run outside the coverage harness.
+>
+> We would rather you learn this from us, in the file that invites you to check us, than from a
+> terminal.
+
+
 - Test file count: **137** files matching `test/*.test.js` [FRESH]
   (`find test -name '*.test.js' | wc -l` = 137).
 - Of those, **22** are invariant-property fuzz suites over burn, economics, and custody contracts