RHDH plugin → overlays → catalog propagate

Three-step chain after a fix or feature in redhat-developer/rhdh-plugins:

1. Update rhdh-plugins with the change, including a changeset; wait until merged and new package(s) are published to npmjs.com (e.g. @red-hat-developer-hub/backstage-plugin-app-defaults 0.0.3 and other packages published at the same time).
2. Update the overlays repo (rhdh-plugin-export-overlays) to fetch the commit SHA for the Version Packages PR related to the above change.
3. Grab the specific changes from that SHA and push them into rhdh-plugin-catalog, updating overlay-repo/, workspaces/, and other paths that sync-midstream.sh would touch for a full clone of just that workspace; open an MR that applies the updated files and bumps associated PLR(s) in .tekton/ to the appropriate tags (e.g. 2.0.0--0.0.3).

Prefer a surgical catalog MR over build/ci/sync-midstream.sh --force-clone <workspace> (minutes vs a long full re-clone/export). Fall back to scoped --force-clone only when export / plugin_builds annotations / workspace transform must be regenerated.

Repos and config

Resolve checkouts by invoking /rhdh-context by name and reading the paths it reports. To run its CLI directly instead, set RHDH to that skill's scripts/rhdh wrapper and use dot-notation keys: "$RHDH" --json config get repos.<key> | jq -r '.data.value' (see references/catalog-surgical-update.md). Use glab against gitlab.cee.redhat.com for catalog MRs (not gitlab.com).