I was able to edit the discovered 32/64-bit resources just fine although had an issue with package creation for the 64-bit one. Starting with the 32-bit resource, I added the package to my library after which I actually saw the files in the share. However, when I did the same for the 64-bit resource, the hashed folder was there but it was empty!
Then I proceeded to delete the 64-bit package and try again where the files showed up after a couple attempts. Don't know why this occurred but went ahead and created a managed s/w delivery policy from this s/w resource. Now an unusually small percentage of the 32-bit targets appear to be installing the app just fine although 64-bit ones are universally throwing "The system cannot find the file specified. (-2147024894)" error 1 in the client's alog.
I'm thinking of disabling/deleting the policies and going the right-click "Import Software" route instead of modifying the discovered resources as I did. Actually, in all of the Software Management Solution demos/videos that I've watched, don't think I've ever seen anyone modify discovered resources and turn them into deliverables so perhaps I should start at Import Software the next time around and make it a policy to "Never" update an existing resource (i.e. always create a new one)? Curious if anyone else has seen this odd behavior before?