wayfinder/research: unclear who runs git for research agents, and no review gate before closing AFK tickets

Hit while running `/wayfinder` on a map, working a `research` ticket. Three gaps between the skills, none of which are bugs in isolation. **1. `research` doesn't say who does git work for a background agent, and the branch isn't in its text.** `wayfinder` says research findings go "on a throwaway `research/ ` branch with a context pointer from the ticket", but the `research` skill only says "write the findings to a single Markdown file". An orchestrator has to improvise the branch/commit/push step. I delegated it to a worktree-isolated agent. Its shell had `cd`'d elsewhere (it cloned the provider source into `/tmp`), and git was refused until it ran from its own worktree. It then reported success on the file but not the branch. Suggest stating that the agent only writes the file, and the orchestrator does the branch/commit/push. **2. "Work through the map" step 4 has no review gate for AFK tickets.** "Post the answer, close the issue, append to the map" reads as one mechanical pass. For a research ticket the "answer" is an unreviewed subagent's recommendation, and the skill doesn't say whether the ticket closes on that or on a human decision. In my case the findings were posted as a resolution, the ticket closed and the map edited before the human had seen them. A line like "show a research result to the human before resolving" would prevent that. **3. Branch capture is described only in the charting flow.** The `research/ ` branch instruction is in "Chart the map" step 5. "Work through the map" has no equivalent, so a research ticket picked up later has no stated procedure for where findings go.