Development record

The brief at .abcd/development/brief/05-internals/03-configuration.md:7 says: Beyond those eleven, the binary reads only keys a person opts into: the provider adapter's `oracle` keys and the interview's list style, the implement loop's `pace`, and the runner routes under `roles` and `runner`. The shipped surface differs: The binary also reads `reservation.github_username` from the machine layer (internal/core/claim/holder.go, holderKey, used by the reserve verb) and `consistency.max_request_bytes` (internal/core/intent/consistency_config.go) through the layered config reader; neither key appears anywhere in the chapter. (v0.14.2 release crosscheck, undocumented-surface, raised by opus in a34.)