add some caveats

src/2024h2/0002-Async-Rust.md

@@ -2,10 +2,14 @@
 
 | Metadata | |
 | --- | --- |
-| Owner(s) | nikomatsakis, tmandry; compiler-errors |
+| Owner(s) | nikomatsakis, tmandry |
 | Teams | Lang |
 | Status | WIP |
 
+## WIP
+
+This is a very rough draft! It has not been reviewed by, well, anyone, and currently represents nikomatsakis's starting opinion. Expect it to change.
+
 ## Motivation
 
 This is an umbrella goal to advance Rust's Async I/O roadmap. The specific plans for 2024 are:
@@ -43,9 +47,10 @@ We have identified three "subgoals" for 2024:
 
 * Solve the "Send Bound" problem
 * Stabilize async closures
-* XXX Async drop -- what is petrochenkov doing?
 * Prototype possible designs for a Rust "async standard library"
 
+* XXX Async drop -- what is petrochenkov doing?
+
 ### Looking further out
 
 Our overall vision for async is that using async Rust should feel very similar to sync Rust, but with extra superpowers. The standard library should offer interop traits as well as traits for doing structured concurrency, similar to what is found in Kotlin. Standing up a simple service should use some executor to implement this functionality by default, but it should be easy to change, and most of the standard library support should work just as well in embedded environments as it does in multicore server setups.
@@ -63,7 +68,7 @@ This is an "umbrella goal" with a number of subparts.
 | What | Owners |
 | ---  | --- |
 | Overall effort | tmandry, nikomatsakis |
-| Stabilize async closures | compiler-errors |
+| Stabilize async closures | compiler-errors? |
 | Resolve send bounds | ? |
 | Prototype Rust async stdlib | ? |