MCP Apt problems and fixes

Search and show read cached package information, and search matches a package-name substring, not a description. An empty cache, an unavailable source or an architecture restriction can all remove candidates. Ask the environment owner to review how fresh the package information is and whether a source failed, and check the errors of any update even when it reports success.

Read the package record and check the utility or library you needed. A half-configured record means setup did not complete, and an install or upgrade can list packages as done even when a setup script failed. The verify tool only checks that a record exists, not the files. Report the result to the environment owner before retrying.

A policy to keep configuration files cannot bring back custom content that was overwritten during an install. Stop dependent changes and use the environment's own backup or recovery process, and give the person responsible for recovery the affected file paths and the operation result.

A removal script can fail while the response still says the removal succeeded, and earlier packages in a multi-package request may already have changed. Read the status of each affected package. Do not assume another purge is harmless; escalate the discrepancy.

A few tools are not available yet. Repeating them does not add the missing behaviour, so use the supported operation for the task or ask the environment owner for another route.

A timeout is not an undo, and other clients can share the same environment. Coordinate with the environment owner to find out whether work is still active before retrying. Do not delete lock files as a routine response, and do not run a native package manager against the same environment.

Look for a downloaded-only status, an extraction error and fetch warnings in the result. The files may be present while the tree is incomplete, so do not build from an unconfirmed partial tree.