Thanks for the explanation.
I'll review, check in with @nettrom_WMF, and update the Keep column by the end of the week.

If creating a new data provider is the "cleaner" technical solution, I think that's OK from the end-user perspective.

Agreed, Special:NewcomerTasksInfo is where we want that to link.

In T367493#9891832, @Urbanecm_WMF wrote:

Claiming to implement option 1.

@KStoller-WMF, heads-up about this task – curious to hear whether you have any preference for the long-term solution here.

As of now we are a go on a Monday (Jun 17, 2024) release to pilot wikis.
QA has given us the OK, and no blocking issues remain.

I've discussed this question with Growth Product Ambassadors and Growth's Movement Communications Specialist. After discussion, my recommendation is to move forward with option two:

Nice, this works just as I expected! (I did a quick test on eswiki beta).

Potential blurb:
The new CommunityConfiguration extension is available on Test Wikipedia. This extension allows communities to customize specific features to meet their local needs. Currently only Growth features are configurable, but the extension will support other Community Configuration use cases in the future.

I moved this to blocked to communicate that we should wait until the OOUI change was merged before testing.

This covers it as far as I know. For clarity I broke up "Add an image" into the two, as they have separate configuration settings:

@JFernandez-WMF, due to the way we are generating the form, I believe in the short-term adding an icon to the form will be challenging. (Please correct me @Sgs if I'm mistaken).

(11) there are two fields added to the end of Special:CommunityConfiguration/GrowthSuggestedEdits page - Weight of underlinked articles and Minimum required link score. Those fields are not present on Special:EditGrowthConfig or in the figma design. Such fields might require some technical knowledge and an additional understanding of a suggested link algorithm - is it expected from admin users?

Can we exclude the visual character count from the scope of this task?

That sounds like a good compromise for now, and hopefully covers most community use cases. I've adjusted the task description.