docs(affinescript-deno-test): record two codegen bugs discovered in pilot

Writing the first AffineScript-native test suite for double-track-browser
(commit b1f3b80) surfaced two AffineScript codegen bugs worth pinning in
the README so future contributors to the harness don't re-discover them
cold:

  1. Match-on-enum with distinct zero-arity constructors per arm emits
     invalid WASM (stack imbalance, rejected by WebAssembly.compile).
  2. Reading a non-first struct field from a function parameter returns
     0 regardless of the actual value. First-field reads work fine.

Both are OCaml codegen issues upstream in lib/codegen.ml; estate-wide
tracking lives in ~/Desktop/AI-WORK-todo.md §11.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: hyperpolymath

affinescript-ecosystem/affinescript-deno-test/README.adoc

@@ -157,6 +157,27 @@ return is unmarshalled by hand (AffineScript compiles `Bool` → i32, 0/1).
 Record<string, Record<string, ImportValue>>` option, then unify both paths
 behind `AffineModule`.
 
+=== Known AffineScript codegen bugs blocking richer test idioms
+
+Discovered 2026-04-19 while writing the double-track-browser lifecycle
+test pilot. Both are compiler bugs, not harness bugs — fixing them is
+upstream OCaml work on `developer-ecosystem/nextgen-languages/affinescript/
+lib/codegen.ml`.
+
+* **Enum-in-match codegen**: a `match` on an enum that returns distinct
+  zero-arity constructors across arms produces invalid WASM (stack
+  imbalance). The ideal form `match s { Uninitialised => Initialised(),
+  ... }` must currently be downgraded to a tagged struct.
+* **Parameter struct-field reads**: `s.field_1_or_later` where `s` is a
+  function parameter of struct type returns 0 regardless of the actual
+  value. First-field reads (`s.tag`) work. Workaround: pass scalars
+  instead of structs when possible, or read fields from let-bound locals
+  before calling into helpers.
+
+Scaling the harness to richer application-state test suites is gated
+on both. Estate-wide tracking in
+`~/Desktop/AI-WORK-todo.md` §11.
+
 == Why AffineScript rather than ReScript?
 
 ReScript is the estate's default TypeScript replacement and has a mature