Save a resolved issue as a troubleshooting note

Select the latest resolved issue in this conversation or supplied records. Follow only related evidence; do not scan other conversations or log directories. Choose the best-supported environment if several differ. Without a completed repair, produce an unresolved-issue record instead of inventing a fix.

Write a complete note covering search terms, symptoms, environment, cause and evidence, working steps, recovery checks and misleading attempts. Retain useful error excerpts and file references while removing secrets and unrelated personal information.

Distinguish a confirmed fix, a workaround and a hypothesis. Do not rerun repair commands. The reader must be able to recognize applicability and find both steps and evidence. Mark missing details as unknown without follow-up questions.

Execution contract:
Start directly. Do not ask me to approve a plan, choose files or fill in a template. Use only this project, this conversation and materials already provided; do not search unrelated projects or private history. Complete what the evidence supports and report missing inputs. If the task is inapplicable, explain why and stop without inventing a result.
Preserve existing files and uncommitted changes. Include complete proposed content in your reply; standalone artifacts may be saved under a new, unused filename. Do not install dependencies, change the environment, commit, push or deploy. Respect access and permission limits and report blocked work. Check your result once, deliver it and stop without asking whether to continue.