Create draft plans for addressing each limitation

README.md

@@ -384,17 +384,22 @@ the full image, default `9.18`).
 
 ## Limitations
 
-This is a first version. Things that do not work (yet):
+This is a first version. Things that do not work (yet), each with a plan for
+addressing it in [`plans/`](plans/README.md):
 
-- `RETURN *`, `EXPLAIN` and `PROFILE`.
-- Write statistics: write queries report "(no changes, no records)" even when they
-  changed the graph.
-- Anything AGE does not support, for example multiple labels per node, pattern
-  comprehensions, temporal and spatial types, indexes and constraints through Cypher.
-- User and role management, `SHOW TRANSACTIONS`, `:sysinfo`.
-- TLS (`bolt+s://`, HTTPS).
-- Each query's full result is fetched from PostgreSQL before it is streamed to the
-  client, so very large results use memory in boltage.
+1. `RETURN *`, `EXPLAIN` and `PROFILE`
+   ([plan](plans/01-return-star-explain-profile.md)).
+2. Write statistics: write queries report "(no changes, no records)" even when they
+   changed the graph ([plan](plans/02-write-statistics.md)).
+3. Anything AGE does not support, for example multiple labels per node, pattern
+   comprehensions, temporal and spatial types, indexes and constraints through Cypher
+   ([plan](plans/03-age-unsupported-features.md)).
+4. User and role management, `SHOW TRANSACTIONS`, `:sysinfo`
+   ([plan](plans/04-users-transactions-sysinfo.md)).
+5. TLS (`bolt+s://`, HTTPS) ([plan](plans/05-tls.md)).
+6. Each query's full result is fetched from PostgreSQL before it is streamed to the
+   client, so very large results use memory in boltage
+   ([plan](plans/06-streaming-results.md)).
 
 ## Development