Surveys implement a `coverage` rate, allowing eg. 10% of editors to be selected to see a survey and the other 90% never see it. I believe this is a sticky association which relies on a cookie set by `mw.experiments.getBucket`. This cookie seems to not be invalidated by a change to the coverage rate for a survey, which means that changing the rate partway through a campaign will have a surprising impact which is difficult to predict. For example, if the campaign has been running for many weeks and targets logged-in users, then the pool of users without a cookie will be small and changing coverage will have little effect. If the campaign targets anonymous users and was only running for a few days, then changing coverage will have a large and expected effect.
This task is complete once we've documented the behavior of changing `coverage` [[ https://www.mediawiki.org/wiki/Extension:QuickSurveys | in the manual ]].
Depending on what we find, follow-up work might include a behavior change such as invalidating "don't show" cookies when the coverage is changed (but leaving "have seen / dismissed / responded" cookies untouched).
More questions we want clarify on:
* Is bucket assignment reset for every new session, or sticky for logged-in users?
* Is there a maximum number of impressions per user, or will the survey show up on every page view until dismissed?
* How does the dismissal feature work? Is there always a button to dismiss, what does it look like? Is dismissal done via cookie (so would not have an effect for high-privacy browsing?)