S1 closes with two named residues, and S2 opens on 0020's keys

The stop condition asked for a component this project did not author,
calling and being called, with every WIT type a shipped release can
express. The types hold in both directions and the un-authored zoo.wit is
called through reflection alone. What did not close is recorded in the
roadmap rather than rounded up: the calling side is exercised only by
repo-authored guests (a real third-party component would take a Rust
toolchain the flake deliberately does not carry), and a resource nested
in a container in an import's signature stays a named refusal.

The README's five minutes now ends where a user's second question starts:
generate a namespace, and unwrap is the result sugar.

Claude-Session: https://claude.ai/code/session_01XF5Hfq4Ca2N2XYEzWQQuHt

Author: chaploud

README.md

@@ -66,10 +66,21 @@ resolution order).
 
 WIT values arrive as the Clojure data you would guess: `record` → map,
 `variant` → `[:tag payload]`, `enum` → keyword, `flags` → set, `option` →
-value-or-nil, `result` → `[:ok v]`/`[:err e]`, resources → `AutoCloseable`
-handles. The full mapping — and why it is not negotiable — is
+value-or-nil, `result` → `[:ok v]`/`[:err e]` (with `host/unwrap` as the
+opt-in throw-on-err sugar), resources → `AutoCloseable` handles. The full
+mapping — and why it is not negotiable — is
 [`doc/design/0012`](doc/design/0012-wit-clojure-type-mapping.md).
 
+Prefer names an editor can complete and clj-kondo can arity-check? Generate
+an ordinary namespace and check it in
+([`doc/design/0020`](doc/design/0020-generated-namespaces.md)):
+
+```clojure
+(require '[cljwit.host.gen :as gen])
+(gen/write-ns! "component.wasm" {:ns 'acme.component})
+;; => "src/acme/component.clj" — then: (acme.component/greet i "world")
+```
+
 ## Why now
 
 Three things landed that were not true a year ago:

doc/roadmap.md

@@ -83,11 +83,21 @@ gate red outside `nix develop`. When it is built it should be a generated
 exports are ordinary functions — is what S1 delivers instead (`0014`).
 
 **Stop condition.** A component this project did not author, calling and being
-called, with every WIT type a shipped release can express. Two of the three
-hold: `dev/resources/zoo.wit` is the un-authored component, and `0012`'s rows
-are marshalled in both directions except `map`, `list<T,N>`, `stream`/`future`
-and `error-context`, none of which are in a shipped release. Host imports are
-the third (`0017`).
+called, with every WIT type a shipped release can express.
+
+**Closed 2026-07-30, with two named residues.** Every `0012` row a shipped
+release can express marshals in both directions (`0016`–`0018`), the
+un-authored `zoo.wit` is called through reflection alone, and host imports,
+WASI and resources work in both ownerships. What did not close, recorded
+rather than rounded up:
+
+- **The calling side is exercised only by guests this repo wrote.** A real
+  third-party component that calls its host would take a Rust toolchain this
+  flake deliberately does not carry. The first such component to misbehave
+  against `cljwit.host` reopens this.
+- **A resource nested in a container in an import's signature** is refused at
+  instantiate (`:nested-resource`) rather than marshalled. The first real
+  component that needs the shape reopens it.
 
 ### S2 — Developer experience skeleton (weeks)
 

doc/status.md

@@ -3,31 +3,29 @@
 _Short by design, and printed at every session start — so findings live in
 `doc/design/`, plans in `doc/roadmap.md`, and only the present tense here._
 
-**Updated:** 2026-07-30 · **Phase:** S1 delivered, closing (pre-alpha, no compiler)
+**Updated:** 2026-07-30 · **Phase:** S1 closed, entering S2 (pre-alpha, no compiler)
 
 ## Next
 
-1. **Close S1 against its stop condition.** What remains of "a component this
-   project did not author, calling and being called, with every WIT type a
-   shipped release can express": the un-authored component (`zoo.wit`) is
-   *called*; the *calling* side is exercised only by guests this repo wrote.
-   One named capability gap: **a resource nested in a container in an
-   import's signature is refused at instantiate** (`:nested-resource`) rather
-   than marshalled — `import-stub` routes only whole parameters/results
-   through the rep table. Accepted until a real component needs the shape;
-   the first one that does reopens it.
-2. **The ergonomics layer (`0015` revisited).** Its blockers are gone —
-   marshalling and host imports both exist — so the generated-`.clj` shape
-   ("not a macro, and the instance not ambient") is buildable now. Decide
-   whether S1 ships with it or it opens S2.
-3. **S2 — developer experience skeleton** (`doc/roadmap.md`): `cljwit.edn`,
-   an nREPL entry point, the shadow-cljs shape.
+1. **S1 is closed with two named residues** (`doc/roadmap.md` records them):
+   the calling side is exercised only by repo-authored guests — a real
+   third-party component reopens it — and a resource nested in a container
+   in an import's signature is refused at instantiate (`:nested-resource`)
+   rather than marshalled.
+2. **S2 — developer experience skeleton** (`doc/roadmap.md`): `cljwit.edn`,
+   an nREPL entry point, the shadow-cljs shape. `0020` opened it: the
+   generator's option keys (`:ns`, `:interface`, `:rename`, `:dir`) are
+   `cljwit.edn`'s keys, and the regenerate-and-diff drift check the
+   generated files cannot do for themselves belongs there.
 
 Done since the last update: `0016` `own<T>` handles, `0017` host imports
 (A–F), `0018` host-defined resources, `0012`'s `ex-data` contract shrunk to
-what reflection can supply, `0019` libwasmtime resolution for library users.
-What is left of `0012` is `map`, `list<T,N>`, `stream`/`future` and
-`error-context`, none of which a shipped release can express.
+what reflection can supply, `0019` libwasmtime resolution for library users,
+`0020` generated namespaces (`cljwit.host.gen` — one tagged var per export,
+instance first, `host/unwrap` as the opt-in result sugar), `host/describe`,
+and the reflection delete contracts the headers require. What is left of
+`0012` is `map`, `list<T,N>`, `stream`/`future` and `error-context`, none of
+which a shipped release can express.
 
 ## Where we are