Applied all changes besides some I'm not sure about:

• Edit-mesh menus (see inline comments)
• Extra separators (see inline comment)
• Add quick effects (don't have a strong opinion but not sure about this)

While i agree that remove doubles is a general purpose tool, workflow wise seems logical to be grouped into the Clean up as often it is used in that context after an mesh edit. As it can address the lamina faces and overlapping edges it is useful in those modes too.
I'm okay with adding it back to the Specials menu (similar to Delete being accessible through the Vertex, Face and Edge menus).

Concerning the Fill menu that naming is disputable indeed. Maybe Calling it Fill/Tessellate since new faces are created ? Even though the initial data does exist, the Fill tool does already overlap with tessellation in some cases, as it can be used to change already existing face data - from an user POV (like reverting a Poke of a Cylinder cap or a ngon/quad split into triangles).

EDIT: concerning separators in the Object specials menu some of them can be removed. The reason why went with this way (at the bottom of the block) is - as the menu has a lot of switch statements which can cause a bit of confusion with duplicate separators.
In case of selecting a mesh object there was always a separator drawn on top of the last two entries (that visually clashed with the menu title line, in case of hemi also).

Concerning the VIEW3D_MT_object_specials menu seems that the check for the light strength is not robust enough. If the Emission node is deleted/ Renamed it will cause the menu to crash.

File "startup\bl_ui\space_view3d.py", line 1448, in draw
    value = lamp.node_tree.nodes["Emission"].inputs["Strength"].default_value
KeyError: 'bpy_prop_collection[key]: key "Emission" not found'

In D2876#67867, @Vuk Gardašević (lijenstina) wrote:

While i agree that remove doubles is a general purpose tool, workflow wise seems logical to be grouped into the Clean up as often it is used in that context after an mesh edit. As it can address the lamina faces and overlapping edges it is useful in those modes too.
I'm okay with adding it back to the Specials menu (similar to Delete being accessible through the Vertex, Face and Edge menus).

Don't mind having it in the Cleanup menu - am just against moving it there from the vertex / specials menu.

Concerning the Fill menu that naming is disputable indeed. Maybe Calling it Fill/Tessellate since new faces are created ? Even though the initial data does exist, the Fill tool does already overlap with tessellation in some cases, as it can be used to change already existing face data - from an user POV (like reverting a Poke of a Cylinder cap or a ngon/quad split into triangles).

Don't have real strong opinion but think these could be separate menus:

• Fill create -> new geometry to fill an area that did not have faces already.
• Tessellate -> add/adjust divisions to existing filled regions.

hi, in the latest revision all seems well.
I would question why the "Screen Areas" menu has been broken apart as I think most people would use hotkeys for this once they discover the menu. Possible a better name could be had for the menu such as "Toggle View"
It's understandable that the View > persp/ortho entries were exposed again as the don't exactly fit into the View > Directions menu.

Concerning the Fill menu that naming is disputable indeed. Maybe Calling it Fill/Tessellate since new faces are created ? Even though the initial data does exist, the Fill tool does already overlap with tessellation in some cases, as it can be used to change already existing face data - from an user POV (like reverting a Poke of a Cylinder cap or a ngon/quad split into triangles).

Don't have real strong opinion but think these could be separate menus:

Fill create -> new geometry to fill an area that did not have faces already.
Tessellate -> add/adjust divisions to existing filled regions.

how about a compromise here and call the menu Fill/Adjust ?

part of the design of this patch is to allow future menu additions by starting with a smaller solid base.
we can always approach this area again and make subtle changes if needed. (on a smaller more individual menu basis.)

thanks @Vuk Gardašević (lijenstina) @ideasman42 for help.
it would be great to see this resolved soon.
Brendon

What was the rationale to not merge the Area operators into a single dropdown? Just naming?

It would benefit other editors as well since most of them have Toggle Maximize Area, Toggle Fullscreen Area, and Duplicate Area into New Window in the View menu or similar (Python Console has it under 'console').

In the case of the 3D View it could include Toggle Quad View, like in this patch.