hermes - 💡(How to fix) Fix Harden launcher behavior when invoked from outside the Hermes checkout

Summary

Audit Hermes launcher/startup behavior for assumptions about the current working directory.

Current state

A local scratch probe was used to check cwd-dependent behavior when Hermes is invoked from another local command-tower directory. The probe is not suitable for PR because it only contains machine-local paths, but the underlying concern is worth tracking generically.

Proposed direction

• Identify launcher/startup paths that assume the process cwd is the Hermes checkout.
• Prefer explicit repo/home path resolution where the runtime already knows the Hermes install location.
• Add a small regression test only if a concrete cwd-sensitive failure is reproduced.

Acceptance criteria

• Either document that current launcher behavior is cwd-safe, or patch the affected path.
• Do not encode user-specific absolute paths in tests or scripts.