Hi sine143,
Good questions, and thanks so much for your help, no fooling. Here's a link to a chart showing the results of the very first test run weeks ago:

On that chart is a description of the test gear and environment.
Here's a photograph of that highly sophisticated test environment

:
There's nothing in front of the cabinet for 10 meters or so, and at that point there are 2 trees (no leaves at this time of year) of 8 - 12" diameter, and 10 meters past those trees, a bunch of scrub bushes and so on. The hillside slopes down gently from where the cabinet is in the photo. We live in a semi-rural area so I can crank it for a while without anyone but my wife and daughter yelling at me. Our closest neighbor (whose property begins about 300 feet behind the cabinet) likes guns, so he has no grounds for complaint, since I'm all for people with guns having some idea of how to use them properly. You may fire when ready there bubba! Practice makes perfect and all that sort of thing, just point your weapon in a safe direction, and remember that them there bullets bounce eh.
The point of all the foregoing being that reflected sound has indeed some, but not in my opinion a whole lot, of influence on results obtained in this location. But I am certainly ready to receive instruction and correction!
The file generated by AudioTool is opened with UltraEdit and cleaned up (replacing spaces with tabs as column delimiters, multiple tabs with single tabs, and so on), then imported into Excel 2013, where the data are used to generate a scatter plot. Sometimes the frequency and SPL values are out of synch for a few rows, yuck. Indeed the necessity of file cleanup is one of the reasons for my lack of confidence in the toolset: why cannot AudioTool guarantee that it will keep its rows and columns straight for cryin' out loud? Android is not a realtime OS but that phone has a dual-core processor, surely we can find a way?
Oh just saw your edit, but will leave my blather here, by your leave

. Sometimes the phone was taped to a mic stand, sometimes it was held in my hand as I held it in front of the cabinet from the side. I did not observe any differences in results, so long as it was just my arm sticking into the sound field.
Also I am aware that many phones have a built-in high-pass filter in their audio circuitry to reduce wind noise and so on (one spec frequently cited is 24 dB/octave from 250 Hz on down). But the clincher for me is that the results match what I hear. The cabinet "turns on" somewhere around 45 Hz, but doesn't really get going until somewhere around 200 - 250 Hz. So without very substantial EQ like that shown in an earlier screenshot of the Behringer DSP UI, it produces what we used to call a "boxy" sound, heavy on the midrange and light on the low end. The published curve does show that sensitivity in the 20 Hz- 200 Hz range is lower than that for higher frequencies, but the cab I built displays a bigger difference than does the published curve. Removing the restrictor plate did make a significant improvement, but the cabinet did not seem to be tuned any lower with the plate in place.
Removing the plate made a big difference in the port noise, an important point at least to me. Now even when rendering a 30 Hz sine wave, port noise while still audible is reduced by perhaps 12 dB from its level with the plate in place.
Physics imposes hard limits on what can be done in a small space, given the many constraints on any portable speaker design intended for reproduction of full-range audio content. Maybe my expectations were unrealistic, or maybe I just hosed up the build. My hope now is that perhaps I can avoid hosage with Box 2 of 2, and better still find a way to beef up the bottom end reproduction on Box 1 of 2.
I'm learning as I go and am most grateful to you, sine143, and to everyone who shares their expertise in these forums.
Thanks and all the best
aeolos