Agent status: Claude may miss updates with a custom configuration folder #27660

What happens

When System default Claude uses a user-defined configuration folder, Orca may install its status scripts in the default folder instead. The launched agent then may not report whether it is working or finished.

Expected

Install status reporting in the configuration folder actually used for the launch, including Linux on Windows. Keep managed account folders and the user’s System default folder distinct.

Notes

An earlier attempt is in #6956, closed because it was too far behind main; its description has the diagnosis. On origin/main, src/main/claude-accounts/claude-profile-router.ts:133 honors the custom folder, but src/main/agent-hooks/managed-agent-hook-registry.ts:48 omits it and src/main/claude/hook-settings.ts:50 defaults to the home folder. A current reproduction with a custom System default folder is unverified; managed account setup passes its folder at src/main/claude-accounts/claude-profile-setup.ts:67.