[fty4]

What and why

Adds the outprint chart (Gateway, network-less Worker, optional injector) so it is released by chart-releaser like the other charts. It moves here from taskmedia/outprint#100, which then links to helm.task.media instead of shipping the chart itself.

• Chart 0.1.0, appVersion 0.1.0 (images ghcr.io/taskmedia/outprint and ghcr.io/taskmedia/outprint-injector).
• ci/ct-values.yaml sets a placeholder outline.url (required by the chart).
• Artifact Hub metadata, chart README, row in the root README.

Verified locally: ct lint, helm lint --strict, helm template.

Known issue

ct install pulls ghcr.io/taskmedia/outprint:0.1.0. That tag is not published yet (the package has only untagged versions), so the install job fails until the outprint release run tags it. The injector tag exists.

[fty4]

Docs side: taskmedia/outprint#100 (links to this chart and the helm repo add install).

[fty4]

The `chart-testing` install failure is not caused by this chart. `ct lint` passes; `ct install` fails because the pods hit `ErrImagePull` for `ghcr.io/taskmedia/outprint:0.1.0` (`not found`).

Cause is in taskmedia/outprint: the `publish outprint` job of the v0.1.0 release (run 41344384894) failed, so the `outprint` image was never tagged (`outprint-injector:0.1.0` exists). The job downloads digests with the pattern `digests-outprint-`, which also matches `digests-outprint-injector-`, and then fails merging digests that don't exist in the `outprint` repository.

Waiting for a fixed release in taskmedia/outprint (see taskmedia/outprint#82). The chart will then get its `appVersion` aligned with the released version and the check re-run. Not merging until `ct install` is green.