Guarded Change Workflow

Apply these rules as task-level constraints. Preserve stricter system, developer, and user instructions.

Authorization And Ambiguity

Treat analysis, inspection, review, explanation, research, and proposals as read-only unless the user explicitly requests a change.
Treat read-only as no changes to tracked files, project configuration, build outputs, or external state. Permit only disposable local diagnostic caches; do not trigger downloads.
Before any other side-effecting command during a read-only task, state the exact command, purpose, scope, and side effect, then obtain explicit user confirmation.
Require explicit user confirmation before continuing whenever information is insufficient or the request has multiple reasonable interpretations. State each interpretation and its impact; do not make an assumption.
Before changing filters, query conditions, or other scope-sensitive logic, confirm the exact expected condition.

When the user names a file, line, or commit, inspect it and its direct call chain first. Broaden the search only when that evidence is insufficient.
Prefer correctness and modification-scope safety over speed. Do not add process for a simple task.
Preserve unrelated working-tree changes. Report unrelated dead code without removing it.

Make only the smallest change directly required by the request. Follow existing local style.
Do not add unrequested features, configurability, speculative error handling, abstractions for single use, dependencies, public APIs, refactors, comment rewrites, or formatting changes.
When a simpler solution exists, explain it first. For a small defect, prefer the minimal patch.
Before adding an abstraction, dependency, public API, or touching an unmentioned module, explain why it is required, its impact scope, and the simpler alternative; wait for confirmation.
Remove only imports, variables, or functions made unused by the current change.
Ensure every changed line is directly traceable to the request. Eliminate unrelated diff before finishing.

Do not create or modify tests unless the user explicitly requests it. You may recommend tests.
For a change, run the narrowest existing checks that demonstrate correctness: targeted static analysis, lint, related tests, a debug/target build, and git diff --check as applicable.
Do not run full test suites, full analysis, or full builds unless necessary or explicitly requested.
Do not run release/profile builds, packaging, signing, installation, or device commands unless the task explicitly concerns them.