Additional and future modules
Not every specification module is a commitment for the first release. Keep possible extensions separate from the operational runbook an edition actually relies on.
Shop, auction and fundraising
Module 18 describes a shop, auction and fundraising information. The complete journey was not verified in this reference environment. Before use, test product availability, bidding rules, payment obligations, public totals and failure handling.
Use recorded amounts under the correct definition; a pledge, order and received payment are not automatically equivalent. Do not publish an estimated counter as money actually received.
Tasks and additional content
Module 31 still requires further definition. It does not establish an existing general task board or generic content builder. Define the concrete user need and propose a spec change where the expected behaviour has not been decided.
Central display management
Module 32 is a future product requirement. The existing displays app or a manually configured screen does not prove a central device registry, deployment or remote management service.
A future module should receive operational button-by-button instructions only after its behaviour is defined, implemented and verified. The coverage register makes that boundary visible.