The plan for the last two ports, and the one question nobody is awake to answer

HANDOFF-raylib-ports.md

@@ -0,0 +1,39 @@
+# Handoff — the last two raylib ports
+
+Two examples, `text_codepoints_loading` and `textures_image_processing`, ported into
+`examples/`. This file is the running record: what is done, what was decided without
+being able to ask, and what is still open. `PORTING.md` gets the findings that outlive
+the port; this file gets the state of the work.
+
+## Status
+
+- [ ] `examples/text-codepoints-loading.flan`
+- [ ] `examples/textures-image-processing.flan`
+- [ ] Headless acceptance cases for the halves that are arithmetic
+- [ ] `PORTING.md` section for this round
+
+## The plan, and why it is this one
+
+Both examples in the upstream tree load a file out of `resources/`, and neither file is
+in this repo. That is the first decision and it is made the same way the three textures
+examples already here made it: **nothing is vendored, the pixels are generated.**
+`parrots.png` is `❔` in raylib's own `examples/textures/resources/LICENSE.md` — no
+author, no licence — so it is not a file to copy into somebody else's repository on a
+sleeping author's behalf. The image-processing example builds its source image out of
+`gen-image-*` calls instead.
+
+The font is the harder half and is the one open question below.
+
+## Open questions for the author
+
+1. **Vendor `DotGothic16-Regular.ttf`?** `text_codepoints_loading` draws Japanese, and
+   there is no CJK font in this tree. The font is SIL OFL 1.1 and therefore
+   redistributable, but it is 2 MB of binary in a repository that has one 1 KB PNG in
+   it, and that is a call about the repository rather than about the port. The example
+   is written to work either way: it looks for the file, and if the font did not load it
+   says so on screen and falls back to the default font. Drop the TTF in and the glyphs
+   appear.
+
+## Log
+
+- Started from `957ba07` on `dev-loop`.