The docmentation is not wrong, its written based on broadcom dynamics because thats where all 3rd party firmware such as dd-wrt began, also notice at the very beginning of it says (optional) meaning its not required. The assign WAN port to switch doesn't work and is not going to work currently using dd-wrt, so you can either A) unlock the thought out of your head, and move on with life or B) buy a broadcom based supported dd-wrt router and then the option to assign WAN to the rest of the switches would work . I believe YOU are wrong and not me or the documentation, you started out this whole topic thinking you would need VLANs to create a simple WAP, which you do not, also you are saying things like:
"Assigning eth1 to bridge must be done before WAN is set to disable because eth1 is not listed in the drop box for assignment to bridge when it's disabled" <-- that is never a part of the guide i linked, you simply set WAN to disabled, not assign eth1 to anything, so as i said, neither me nor the documentation is wrong, YOU are.
Also considering that the dd-wrt builds, be it buffalo or dd-wrt community, are in a perpetual state of beta, so i do not think you reporting this as a 'bug' will fix the problem, a non needed feature not working isn't really considered bug, its considered a feature that doesn't work, 'features' are all considered optional and not required for working operations. At best, they would simply remove the tick box within the webgui and you would still be left with a WAN port that you could not map to the rest of the LAN. And no, i wouldn't consider a public forum a place to report bugs, most developers RARELY read into public forums, coders/mods/webadmins maybe, but not the main programming devs, most public forums i know of are just that, public forums where you report a problem, and non company tech support gather to try to solve the problem. You could try reporting the problem directly to the dd-wrt trac, but i seriously doubt you'll have any luck.
http://svn.dd-wrt.com:8000