feat: add harbor

[gabrielcosi]

Overview

Adding Harbor (goharbor/harbor-helm) as an OCI mirror.

Additional information

Upstream's release workflow pushes to oci://ghcr.io/${{ github.actor }}, so charts land in whichever maintainer pushed the tag — ghcr.io/goharbor/harbor holds only a test tag. The Docker Hub push 401s. goharbor/harbor-helm#2294 fixes both but has sat unreviewed since January.

Upstream tracking issue: goharbor/harbor-helm#2265

Requirements

• I have read and agree with the contributing guidelines
• AI usage disclosure: YES — used Claude Code to prepare the metadata file and PR.

[greptile-apps]

Greptile Summary

Adds Harbor Helm chart mirroring metadata.

• Configures harbor from https://helm.goharbor.io.
• Pins the upstream chart version to 1.19.1.

Confidence Score: 5/5

The change appears safe to merge with no actionable defects identified.

The metadata follows the repository schema and points the existing Helm fetch workflow to an available Harbor chart and version.

T-Rex Logs

What T-Rex did

• The upstream index request returned HTTP 200 with exactly one matching chart entry.
• The index resolution produced the Harbor chart URL https://helm.goharbor.io/harbor-1.19.1.tgz.
• The archive download returned HTTP 200, and the SHA-256 digest matched the index digest.
• The embedded harbor/Chart.yaml declares name=harbor and version=1.19.1, and the validation exited with code 0.
• No tracked files were altered and only the requested proof artifacts were created.

_{Ran code and verified through T-Rex}

Important Files Changed

Filename	Overview
apps/harbor/metadata.yaml	Adds schema-conformant Harbor chart metadata whose registry, chart name, and pinned version match the repository’s mirroring workflow.

_{Reviews (1): Last reviewed commit: "feat: add harbor" | Re-trigger Greptile}