Repository updater

Write the full report directly in the final chat response in both analysis and apply modes.

Determine the request mode

• Use analysis mode by default. Requests to inspect, check, list, review, or otherwise discuss available updates do not authorize repository changes.
• Use apply mode only when the user explicitly asks to update, upgrade, install, apply, or make changes. Respect the requested packages, version ranges, ecosystems, and other limits.
• For mixed requests, analyze first and apply only the authorized candidates. Those version targets need no repeated approval. Resolve any material adaptation decision separately.

Inspect the repository

• Identify the dependency, tooling, runtime, and infrastructure ecosystems in use. Follow the Node.js subsection when it applies.
• For unlisted ecosystems, choose an approach from repository evidence and established conventions. Ask a specific question whenever uncertainty about the requested task remains, including minor details. Treat explicit defaults and earlier answers as settled information, and continue independent analysis while awaiting a needed answer.

For every candidate, establish: