1 # hu13 build plan (hub)2 3 Source: DRAFT.md (root). This page is the swarm execution order.4 Each row maps to a f0rge issue with its own Success rubric.5 Process per item: research -> plan -> implement -> test -> iterate till verified.6 7 ## Research findings (locked)8 9 - Markdown: `pulldown-cmark = "0.13.4"` pinned. Frontmatter: tiny `---` split10   + `serde_yaml` pinned for f0rge YAML (spike R1 must confirm on real fixtures).11 - Real `.forge/` layout is dir-per-entity: `issues/<uuid>/issue.md`12   (+`comments/<uuid>.md`), `prs/<uuid>/pr.md` (+`patch.diff`, `comments/`,13   `reviews/`). Renderer MUST read this shape, not flat files.14 - Deps budget: pulldown-cmark + serde + serde_json + serde_yaml (+ chrono?15   prefer `time`/hand-rolled RFC3339). No tokio/hyper: std `TcpListener`,16   thread-per-conn or single-queue, only 2 POST routes.17 - `git bundle` available (git 2.55.0). Clone chain:18   `--clone-url` flag > `git remote get-url origin` > bundle/tarball always.19 - Rust 1.98.0, cargo + docker available. Single binary, one crate to start.20 21 ## Sequence22 23 - m1-code-tab: R1 spike, scaffold+CI+style, git reader, code tab.24 - m2-commits-wiki-feed: commit diffs, wiki, feed.atom (50).25 - m3-forge-api: f0rge readers, releases+artifacts (no cap), api JSON, agents page.26 - m4-mailbox: inbox forms+POSTs+storage+ack+license, then hardening.27 - m5-docker-v1: Dockerfile build-on-start, dogfood, polish, license re-read, v1 gate.28 29 ## Swarm dispatch notes30 31 - One issue = one branch = one PR. Issues are ordered; prefix number is order.32 - Subagents: Owl/Owlette for well-specified render issues, Platinum for33   inbox daemon + hardening. Supervisor reviews every PR, CI must pass.34 - Never touch `.forge/` entity files by hand except via `f0rge` CLI.35 - Dogfood continuously: `hu13 build` this repo from m1 on.