Support registry-backed hyard clone handles

[zack-nova]

Summary

• Add registry-backed hyard clone <handle> support for Harness Package handles
• Update registry resolver support for the current catalog index schema
• Switch public quickstart/release/demo docs to handle-first clone/install examples

Linked Issue

Closes #152

Dev Brief Mapping

• Acceptance criterion 1: hyard clone product-lab-style handles resolve through the registry and create a runtime.
• Acceptance criterion 2: docs and demos teach package handles first while retaining explicit Git locators as advanced escape hatches.

What Changed

• hyard clone accepts curated and namespaced package handles, records registry provenance, and rejects Orbit Package handles with an install-oriented message.
• Registry resolution now consumes package-level identity plus version-level locator metadata.
• Release-surface checks cover the public clone handle path.

Validation

• Command: mise run fix
• Result: passed
• Command: mise run ci
• Result: passed
• Command: sh ./scripts/test_release_surface_hyard.sh
• Result: passed
• Manual verification: hyard clone product-lab --json against the official registry passed during local smoke testing.

Risk

Low to medium. hyard clone <bare-name> now treats handle-shaped bare names as registry handles; local relative paths should be passed as ./name or ../name.

Out of Scope

• Chinese documentation translations
• Removing explicit Git locator support
• Registry curation policy changes

Reviewer Notes

Chinese .zh.md draft docs were stashed and are not part of this PR.