The ios-app template says a top-level extra_prompt renders nothing; it renders #2708

emrg/server/ios_app_prompt.md §0.1 tells its reader that extra_prompt placed at a task record's top level "reads as absent", and that the section then renders "empty and silent — no error, no log line, nothing to notice". The code does not behave that way.

_template_task_context (emrg/server/scheduler.py) honours the top-level position, and logs a warning when a record carries the field in both places. Measured on this checkout through the real builder:

So a host who follows the ios-app template's instruction and writes the field at the top level would not lose it — but a template that says otherwise teaches every round to expect silence that no longer happens, and to report a blocked item about a section that rendered correctly.

The paragraph describes the state before the position was honoured in emrg/server/scheduler.py; the template that carries it was written after that change, so the sentence is stale rather than a live behaviour.

What finishing this needs:

• The paragraph states the mechanism the code implements: config: is canonical and wins when both are present, a top-level block renders when config: carries none, and the losing copy is named in a warning.
• It keeps telling the reader to place the field under config:, since that is the canonical home.
• A test pins the claim so the sentence and the mechanism cannot drift apart again — the two carriers that already disagree are in this repository, so this is a rule a guard can measure.