A consent prompt always goes into the stored page, so one stored copy cannot serve readers with and without it #1279

The problem

The InMobi, Didomi and Sourcepoint consent prompt modules run in the fetch phase alone, and an entry of the serve phase naming one is refused when the settings load. What a prompt writes is the same for every reader, so the fetch phase stores it in the page every reader is served from, and that is the right default. A publisher who wants the stored page without it, so that one stored copy can serve readers with and without the prompt, has no way to say so. The modules make the choice for the publisher.

The change

Each of the three modules declares both phases, so cmp.inmobi, cmp.didomi and cmp.sourcepoint may be named in a [[fetch]] or a [[serve]] entry. In the serve phase the prompt is written on each reader's copy. ts audit generate and the stock list keep each prompt in the fetch phase. A prompt selected with no entry of either phase naming it is refused as before, and the stock list's test allows a middleware that runs in several phases to be listed in one of them, checking that what is listed for a phase is registered for it and that everything registered is listed somewhere. Seven files, 102 lines added and 32 removed.

Where it is

Draft on the fork, jwrosewell#16, on top of the sellers module (fork pull request 15).