# `instar worktree create` works again on real agent homes

Agents are supposed to create build folders ("worktrees") with the `instar worktree create` command, which safely checks that the folder comes from a trusted copy of the project and then wires up the commit-time safety checks inside it. A previous fix (#777) was meant to let the command trust an agent's own home folder — agents fetch from a personal fork but push to the canonical project, so the check needed to look at ALL of a checkout's configured remotes, not just the first one.

That fix never actually worked on the machines it was built for. The reason is subtle: every git command in this code runs through a safety executor that, when pointed at the agent's own project folder, only permits a short list of read-only git operations. The command the #777 fix used to list remotes (`git remote -v`) is not on that list — so on a real agent home the listing silently failed, the trust check found nothing, and the command refused the folder anyway. Agents then fell back to creating worktrees with raw git, which skips the part that wires up the commit-time safety checks — so commits in those folders ran with no local checks at all, silently.

The fix swaps the remote-listing to a different git command (`git config --get-regexp`) that reads the exact same information and IS on the safety executor's permitted list. It also now explicitly reads "push" addresses, which is precisely how agent homes are configured (fetch from the fork, push to the canonical repo). Verified live against a real agent home: the command now resolves it correctly. Tests pin the exact failing shape — a project-folder lookalike with a fork origin — for both the second-remote and push-address cases, plus the rejection case when nothing is trusted.
