Lay Pure out as a core with the parts selected around it

The app model, the tree store and the HTTP host lived in
prototypes/connections among the earlier document runtime, the store was
known only by its format's name, and Vega compiled six Pure sources by path.
Now, as the README's principle has it:

  core/   runtime, flow and the app model (module*.c), with what the core
          asks of storage (state.h, store.h)
  store/  the tree store (PURETRE3, PUREREC1)
  serve/  pure-serve: HTTP host, outbound delivery, JSON in place
  cli/    pure-run, pure-edit-module

A top-level make builds libpure.a (app model and store, for hosts to link)
and the hosts; make check runs the store's and the app model's tests. The
earlier runtime still builds from prototypes/connections against core/ and
store/ (check, check-tree and check-core pass). Design 009 records the rule:
parts by role behind libraries; git repositories split by coupling, so the
store stays here while its contract moves with the core, and Vega stays apart.

1 files changed, 1 insertions, 1 deletions

diff --git a/benchmarks/http/README.md b/benchmarks/http/README.md
index af9f62d..22fc6d3 100644
--- a/benchmarks/http/README.md
+++ b/benchmarks/http/README.md
@@ -7,7 +7,7 @@ Pure의 문서 서버들과 같은 계약의 axum(Rust)·drogon(C++) 서비스�
 cc -O2 -std=c17 -o load load.c
 (cd axum-baseline && cargo build --release)
 drogon-baseline/build.sh   # Debian의 drogon 패키지를 설치하지 않고 .deps에 풀어 빌드한다
-make -C ../../prototypes/connections build/pure-serve
+make -C ../.. build/pure-serve
 make -C ../../prototypes/connections BUILD=build/tree STORE=store-tree.c build/tree/pure-connections
 aup build ../../../aup/examples/editor.aup -o editor.pmod
 python3 run.py --module editor.pmod --directory /var/tmp   # 저장소를 둘 장치에서