feat(consume): one call over a folder asks every bundle under it

`okf consume <folder>` is the server's `okf_ask` with no bundle named,
byte for byte: no ranking of its own, every excerpt carrying its bundle
id. `--bundle-id` asks one bundle under the folder. A flag that acts on
one bundle's cut is refused by name over a folder rather than dropped,
because the server takes none of them. A bundle path reads as before.

v1.1 order F, part F2.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

README.md

@@ -1412,6 +1412,22 @@ nothing regenerated. Pointed at one bundle, it prints that bundle's card as
 before; the command decides which it was given by the same rule discovery uses
 (a directory carrying an `index.md` is a bundle).
 
+**And one question -- or several sub-questions -- asks every bundle under the
+folder in one call:**
+
+```sh
+okf consume ~/okf --question "first sub-question" --question "second sub-question"
+okf consume ~/okf --question "..." --bundle-id my-bundle   # just one of them
+```
+
+The reply is the server's `okf_ask` with no bundle named, byte for byte: the
+budget split between the bundles, one payload per bundle, and every excerpt
+carrying the id of the bundle it came from. There is no ranking of its own.
+The flags that change how ONE bundle is cut (`--ref`, `--ranking`,
+`--no-source-quota` and the rest) are refused over a folder, by name, rather
+than dropped, because the server takes none of them; point at one bundle to use
+them.
+
 `okf skill <bundle> --for-bundle` still writes the per-bundle form, with the
 identity and the numbers measured into the text — which is exactly what makes
 that file stale the moment the bundle is rebuilt. It refuses out loud when it