fix honey compiler blockers

README.md

@@ -48,9 +48,10 @@ Instead of passing these on the command line, a project can describe its build
 in Brolang itself. `brolang new <project>` creates a project with local `std`
 and `ffi` copies; `brolang init` does the same for the current directory without
 overwriting existing files. `brolang build [root]` reads a `config` constant
-from `root/build.bro` and compiles the program package it names. Without
-`root`, it searches the current directory and parents for the nearest
-`build.bro`. Build outputs are written to `root/build/<name>`.
+from exactly one of `root/build.bro` or `root/build.hon` and compiles the
+program package it names. Without `root`, it searches the current directory
+and parents for the nearest build file. Build outputs are written to
+`root/build/<name>`.
 
 ```bro
 b :: import "@std/build"
@@ -67,15 +68,16 @@ config :: b.BuildConfig{
 ```
 
 `name` is a plain executable name, and `source` is the program package relative
-to `build.bro`. The list fields map to the matching C options (`libraries` →
+to the build file. The list fields map to the matching C options (`libraries` →
 `-l`, `lib_paths` → `-L`, `includes` → `-I`, `defines` → C defines, `links` →
 linker inputs) and, like those flags, their paths are relative to the invocation
 directory. Lists take the address of an array literal; empty lists are written
 `&[]`. See `examples/build/` for runnable projects.
 
 Projects can declare tests directly and run them with `brolang test [root]`.
-The command reads the same `build.bro`, writes `build/<name>-test`, and reuses
-its C link inputs, libraries, include paths, and defines.
+The command reads the same build file—exactly one of `build.bro` or
+`build.hon`—writes `build/<name>-test`, and reuses its C link inputs,
+libraries, include paths, and defines.
 
 ```bro
 math :: import "../math"