docs: typed-wasm is a meeting point for two unrelated languages (#73)

## Summary

Adds a top-of-file [NOTE] admonition to README.adoc making it
unambiguous that **AffineScript** and **Ephapax** — both of which target
typed-wasm and both of which interface with
\`crates/typed-wasm-verify/\` — are two SEPARATE, UNRELATED languages.

The shared \`affine\` syllable in both names is substructural-logic
family terminology, not a project relationship. Ephapax is internally
dyadic and contains an \`ephapax-affine\` sublanguage — that sublanguage
is *not* AffineScript.

## Why

AI agents have repeatedly conflated AffineScript with Ephapax (or with
Ephapax's internal \`ephapax-affine\` sublanguage). The two repos share
zero AST / typing / borrow-checker / codegen — they meet only here, at
typed-wasm. Workers on \`crates/typed-wasm-verify/\` in particular need
to know that the agreement theorems against each consumer are
independent.

## Companion PRs

- hyperpolymath/ephapax#152 — adds README admonition + CLAUDE.md
disambiguation + a2ml [disambiguation] block.
- hyperpolymath/affinescript#393 — symmetric hooks in affinescript.
- Canonical disambiguation doc at
[nextgen-languages/docs/disambiguation/ephapax-vs-affinescript.md](https://github.com/hyperpolymath/nextgen-languages/blob/main/docs/disambiguation/ephapax-vs-affinescript.md)
(commit 2fcb55a).

## Test plan

- [ ] AsciiDoc renders cleanly on GitHub.
- [ ] Admonition appears before the existing \"Progressive type safety\"
tagline.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

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

Author: hyperpolymath

README.adoc

@@ -11,6 +11,31 @@ image:https://img.shields.io/badge/OpenSSF-Best_Practices-green?logo=opensources
 image:https://img.shields.io/badge/believe__me-0-brightgreen[believe_me: 0]
 image:https://img.shields.io/badge/Levels-L1--10_checked_core_(L11--12_draft)-blue[Levels: checked core]
 
+[NOTE]
+.typed-wasm is a meeting point for two unrelated languages
+====
+Two distinct languages target this format and interface with the
+`crates/typed-wasm-verify/` crate inside this repo:
+
+- **AffineScript** at https://github.com/hyperpolymath/affinescript[`hyperpolymath/affinescript`]
+  — a successor to JS / TypeScript / ReScript (application language, OCaml compiler).
+- **Ephapax** at https://github.com/hyperpolymath/ephapax[`hyperpolymath/ephapax`]
+  — a research language for WebAssembly memory safety (Rust + Coq + Idris2).
+
+The two **share nothing else**: separate ASTs, separate type checkers,
+separate compilers, separate proof stories. The word `affine` overlapping
+in both names is substructural-logic-family terminology, not a project
+relationship. Specifically: Ephapax is internally dyadic and contains an
+`ephapax-affine` *sublanguage* — that sublanguage is *not* AffineScript.
+
+When working on `crates/typed-wasm-verify/`, the agreement theorems against
+each consumer are independent — a fix that aligns the verifier with one
+language's invariants says nothing about the other.
+
+Canonical disambiguation:
+link:https://github.com/hyperpolymath/nextgen-languages/blob/main/docs/disambiguation/ephapax-vs-affinescript.md[nextgen-languages/docs/disambiguation/ephapax-vs-affinescript.md].
+====
+
 **Progressive type safety for WebAssembly linear memory — checked L1-L10 core, 0 believe_me in the checked proof package.**
 
 == Two Roles (ADR-004)