kg-registry-product-url-update

Updating a stale product URL requires editing the KG-Registry resource file in a local repository clone to point the product to the correct current landing or download endpoint while preserving the product's identity and avoiding incorrect substitutions.

Identity-aware URL replacement selects a replacement endpoint based on product concept and metadata like id, name, description, format, and version, rather than relying on string similarity or HTTP status alone.

Yes, you must run the update from a local repository clone so the workflow can edit the correct resource file directly and validate the result locally before submission.

When repairing a product URL, you should optionally update nearby version-related fields and the parent resource last_modified_date to maintain metadata consistency across the KG-Registry entry.

You validate the edited KG-Registry resource file using the kg-registry-validation skill, which checks the updated product URL and metadata for compliance post-edit.

Your product URL redirects incorrectly because the product_url entry is stale or misdirecting, requiring an identity-aware URL replacement from authoritative sources to fix the dead link.