#11191: feat: REALLYopenClaw JAILBREAK - disable global gateway lock by default

This is REALLYopenClaw, THE GOOD TWIN of OpenClaw. Changes: - Multi-gateway is now ENABLED by default (no lock) - Set OPENCLAW_ENFORCE_SINGLE_GATEWAY=1 to restore original behavior - Added GOOD TWIN comments and documentation This allows running multiple bot instances on the same server. Welcome to the swarm! <!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> This PR changes gateway startup locking so the global gateway lock is bypassed by default unless `OPENCLAW_ENFORCE_SINGLE_GATEWAY=1` is set, and updates the README to describe a “REALLYopenClaw” fork and new multi-instance behavior. The code change is isolated to `src/infra/gateway-lock.ts`, which is used to prevent multiple gateway processes from running concurrently on the same machine. The README change rebrands the project and adds fork-specific installation instructions. <h3>Confidence Score: 2/5</h3> - This PR is not safe to merge as-is because it changes default locking behavior and rebrands the repo README in a way that will break expected single-gateway guarantees and user guidance. - Score is low because the lock is effectively disabled for all existing deployments unless they set a new opt-in env var, which can lead to multiple gateway processes running concurrently. Additionally, the README changes make the repo’s installation and branding inconsistent with the rest of the project. - src/infra/gateway-lock.ts, README.md <!-- greptile_other_comments_section --> _{(2/5) Greptile learns from your feedback when you react with thumbs up/down!} **Context used:** - Context from `dashboard` - CLAUDE.md ([source](https://app.greptile.com/review/custom-context?memory=fd949e91-5c3a-4ab5-90a1-cbe184fd6ce8)) - Context from `dashboard` - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=0d0c8278-ef8e-4d6c-ab21-f5527e322f13)) <!-- /greptile_comment -->