tenant.openagents/omega

Give a custom data directory its own instance lock

Give a custom data directory its own instance lock The macOS single-instance lock keys its port on release channel and uid only. Two Omega processes pointed at different --user-data-dir roots share no state, yet the second was refused with 'omega is already running', and ZED_RELEASE_CHANNEL is debug_assertions-only so a release build had no way to move the port either. Every clean-profile proof therefore had to begin by quitting the owner's live session. That blocked the identity-first first-run and theme-and-agent-setup observations on three separate release candidates, and it is why omega#16's clean-user journey ran on a seeded profile instead of a pristine one. The offset is derived from the directory path, so the same profile keeps the same port across launches: a custom instance still refuses a second copy of itself, which is the property the lock exists for. Release Notes: - A second Omega with its own --user-data-dir now starts instead of being refused as a duplicate instance.