Thanks for the testing notes Elena!

(1) The fields correctly intercept invalid value such as 0.002 - the warning appears. But the suggested values (from the value selector at the end of the field) include negative values.

This is because we currently do not have no support for rules that are stricter than a datatype. In other words, we can specify the form should accept an integer, but we cannot specify that we're interested in an integer from a specific range. As a result, negative integers are suggested (as they are integers as well). T358659 will likely change that (note the task's scope is wider than its name).

(2) Do we need apostrophes around Mentorship?

Probably not. There is a different bug in that line as well (one which cannot be seen now, but will be visible with T360473), which I filled as T361933: Community configuration: Special:CommunityConfiguration/PROVIDER should display the provider name in the header instead of provider ID last Friday. I added a note to remove the apostrophes as part of that task as well.

(3) x (in the above screenshot) I didn't find the presence of this control in figma design

Filled as T362044: Community configuration: Decision about how to display the boolean controls in Special:CommunityConfiguration/Mentorship. Thanks for the reminder!

Going through the rest of the testing notes.

(4) Mentorship section in Special:EditGrowthConfig has information that is not present on Special:CommunityConfiguration/Mentorship
What Special:EditGrowthConfig has:

• short explanation of Mentors roles, a suggestion, and a link to more information

This is yet to be implemented as part of T358335: Allow to display informational sections in the editor.

• "Are mentorship features enabled?" is the first question

Indeed. This is to be decided on in T362044: Community configuration: Decision about how to display the boolean controls in Special:CommunityConfiguration/Mentorship (and implemented in an engineering follow-up task, once a decision's been made).

Also, should we have "Send us your feedback" on Special:CommunityConfiguration/Mentorship?

Maybe? @JFernandez-WMF, I don't see the feedback link in the Figma designs. Is that intentional? Do we want to have it somewhere? There's also a help link included – I'm not filling a task yet, as I don't think we have anything useful to link (T350629), but noting just in case.

(5) The fields occupy the whole page width (Special:EditGrowthConfig limits the fields length).

@JFernandez-WMF Do you have any thoughts on what is the intended behaviour here, plese?

(6) @Tacsipacsi comment https://phabricator.wikimedia.org/T354463#9674654

IMO, issues highlighted there should be resolved. Since the T354463 task is now in Design Review, I'll leave it up to @JFernandez-WMF and/or @KStoller-WMF to either move it back to Doing (if we should make changes as part of this task), or to fill a new task for follow-up improvements.

I don't see the feedback link in the Figma designs. Is that intentional? Do we want to have it somewhere? There's also a help link included – I'm not filling a task yet, as I don't think we have anything useful to link (T350629), but noting just in case.

I added T362203: Community Configuration: Edit History & Help Links.

Since the T354463 task is now in Design Review, I'll leave it up to @JFernandez-WMF and/or @KStoller-WMF to either move it back to Doing (if we should make changes as part of this task), or to fill a new task for follow-up improvements.

I added T362285: Community Configuration: Add Character count to Edit Summary

(5) The fields occupy the whole page width (Special:EditGrowthConfig limits the fields length).

@JFernandez-WMF thoughts on this?
The very wide fields don't look great in my perspective, but curious if there is any official design guidance on this.