kitaru-guided-tourlisted

# Kitaru guided tour Deliver an AHA before teaching the complete method. Use the public Kitaru returns-agent template to move from recorded traces, through a short prepared frontend review and reusable evaluator, to one bounded experiment result. ## Experience contract - Assume the user has not read the template agent and does not yet know how Kitaru works. Explain each example from the evidence visible in the review, translate internal names into plain language, and never require missing code or product context to understand a question. - Act as a friendly guide, not an invisible automation runner. At each meaningful transition, explain what the tour is doing, why that step matters, what Kitaru concept it demonstrates, and what the user will be able to see or do next. Keep routine commands in the background. - If standing user instructions strongly prefer terse or explanation-free responses, surface the tension before beginning the tour. Ask once: “This guided tour works best if I briefly explain each new concept and why each step matters. May I use a little more explanation than usual during the tour, while keeping routine commands and status updates compact?” If the user agrees, treat that answer as a tour-scoped clarification of their preferred style, not permission to ignore unrelated or higher-priority instructions. If they decline, remain concise but still explain the minimum needed to understand each checkpoint. - Use names that already