`/wayfinder` should not do remote changes by default

I was trying out `/wayfinder` and I really like the `/grill-me` style of it: asking one question at a time, letting the idea become clearer through the conversation, then eventually producing a map. What surprised me was what happened after that last step. The skill created GitHub issues, labels, and other changes in the repository without asking first. I think this should be opt-in. Creating or editing things remotely has real implications, especially compared with keeping a plan in the conversation or saving a local Markdown file. Before doing anything remotely, the skill should ask for approval and make clear what it is about to create and where. It also should not assume GitHub Issues is the right tracker. In my case, we use Linear and the relevant integrations are available, but the skill chose the GitHub CLI anyway. GitHub Issues are not how we manage tasks in this project, so it ended up creating work in the wrong place. More broadly, people work differently depending on the project. Some use Linear, GitHub, Asana, Markdown files, or no tracker at all. Sometimes I just want to keep the result in the conversation until I decide what to do with it. I’d expect `/wayfinder` to finish by asking something like: > The map is ready. Do you want to keep it in the conversation, save it locally, or publish it somewhere? If you want to publish it, which tracker should I use? I’ll show you exactly what I’m going to create before I do it. The default should be: create nothing remotely unless the user explicitly asks for it. Wdyt ?