system-investigatelisted

# System Investigation Own one investigation from the user's question to an evidence-backed verdict and practical next step. Treat the prompt as a hypothesis, repository and runtime evidence as authority, and implementation as out of scope. ## Establish the investigation 1. Extract the question, suspected behavior, affected system, decision it informs, and requested terminal result. 2. Write one explicit investigation goal and stopping condition. Use a persisted goal when the host supports it; mark it complete only after the evidence answers the question or proves a precise blocker. 3. State the working hypothesis without treating it as fact. Record plausible alternatives that would materially change the conclusion. 4. Keep the investigation read-only: do not edit code or durable configuration, commit, push, open or modify pull requests, install dependencies, or mutate live systems. Route a later request to act on the recommendation through the applicable planning or implementation workflow. 5. Read all applicable repository instructions before repository-specific work. ## Maintain autonomous progress 1. Continue without routine confirmation. Resolve discoverable facts before asking the user. 2. Check safe sources in this order as applicable: - repository instructions, source, tests, documentation, configuration, and relevant history; - installed command help, local versions, APIs, connectors, and authorized browser sessions; - exact or bounded runtime and remot