produced ocra binary misbehaves when running from same dir with another Gemfile

[repu1sion]

In my understanding produced binary should be an independent container which doesn't care what's going on on customer's pc or in his local dir. But when ocra produced executable is placed in same dir with Gemfile from some another project let say, it overrides internal Gemfile, parsed during build and replaces it with Gemfile from local dir. And it leads to internal errors like this:

c:\archive\develop\packed-mn-orig\build\iso>metanorma.exe -x xml "sources/amendment/rice-amd.np.adoc"
Traceback (most recent call last):
        1: from c:/archive/develop/packed-mn-orig/build/iso/ocr2F02.tmp/src/metanorma:136:in `<main>'
c:/archive/develop/packed-mn-orig/build/iso/ocr2F02.tmp/src/metanorma:136:in `require': cannot load such file -- metanorma-rsd (LoadError)

Internal Gemfile parsed during build contained metanorma-rsd, and binary was created successfully, but if we have in current dir with executable Gemfile from another project - in current case with some tests, which doesn't contain metanorma-rsd it leads to such a funny bug.

Any thoughts why its possible and should it be probably fixed?