Registry-facing daily workflow for Cartograph widgets and blueprints. Use search before writing reusable logic, inspect before installing or editing, install to add a widget to the current project, and rate to leave registry feedback. When installing or inspecting, use the exact value from the 'id' field returned by search.

Mutate widgets already installed in the current project. Use this for installed copies only; use cg_registry install for adding a new widget. Actions: upgrade requires widget_dir and optionally version; uninstall requires widget_dir. Pass the widget directory path (e.g. cg/backend-retry-python).

Check health/status for installed widgets in the current project. Use this to see if widgets are out of sync with the library, have local modifications, or have updates available. Omit widget_dir to scan all installed widgets; provide a specific directory (e.g. cg/backend-retry-python) to inspect one.

Scaffold a new Cartograph widget or blueprint. Use name for the slug only, not the full widget_id; Cartograph combines domain + name + language for widgets. For blueprints, just use the name.

Run the full preflight / smoke pipeline without checking the module into the library. Use this as the dry run for checkin before recording reusable changes.

Run the full validation / smoke pipeline and then check the module into the library. Use this only for changes that should become reusable logic. Requires reason. Supports either path or widget_dir for compatibility.

Blueprint-specific composition management. Blueprints are higher-order widgets that compose other widgets as dependencies. Use this to add or remove dependencies.

Read or update Cartograph workflow defaults. Provide key to read the current value; provide both key and value to update it.

List or manage custom validation rules that run during Cartograph validate and checkin.

Recovery guidance for common Cartograph trouble states (e.g. local out of sync with cloud, checkin blocked, validation contamination, publish rejected). Use action=list to browse topics with one-line summaries, then action=get with a topic to read the full resolution. Reach for this before guessing when an agent is stuck on a Cartograph error state.