Collections, built by Reader Experience, already provides the list container. This epic adds the editing layer on top: status per page, a progress tracker, private goals, opt-in nudges, and an impact reflection. Before we commit to estimates, we need a clear picture of what each piece needs technically, where it hooks in, and what depends on other teams.

The question of where editing metadata lives relative to a Collection is covered in the companion task on the Collections branch. This task covers everything else.

Questions to answer

Status and progress (Stage 1)

• How do we detect that an editor published an edit to a page on their list, including across wikis, so status can update without a manual step?
• What's the cost of computing the progress rollup ("6 of 10 done") on read vs storing it?
• What happens to status when a page is renamed, deleted, or merged?

Entry points

• Save dialog (T439892): what extension point lets us add a row under "Watch this page" in both VisualEditor and the source editor, on desktop and mobile web? Who owns that dialog and needs to sign off?
• Leaving without saving (T439893): same question for that moment.
• How do we check whether a page is on an event worklist, so the Event Pathways dialog takes precedence and we never show both?
• How do we decide a page "still needs work" (maintenance templates, quality level)? What data source is reliable across wikis?

Goals and nudges (Stage 2)

• Where do private goals live, and what does the goal format decision (free text vs structured) change technically?
• Is a new Echo notification type feasible, and who on the Echo side needs to agree?
• What's needed for email nudges, and how do they respect existing email preferences?
• How do we enforce a shared notification frequency cap with Event Pathways?

Impact reflection

• Which pageview source do we use, what time windows are practical, and what are the rate or freshness limits?

Deliverables

• A short write-up answering the questions above, with a recommendation for each
• A list of dependencies on other teams (Reader Experience, Editing, Echo owners, Event Pathways, Test Kitchen) with what we need from each
• Rough size per piece of work (S / M / L) and the order they should be built in
• Risks and open questions that need a product or Legal decision
• Follow-up implementation tasks created as subtasks of T436377