Implement custom-icon-upload-pattern (openspec change)

[rubenvdlinde]

Hydra pipeline tracking issue — auto-filed for openspec change custom-icon-upload-pattern on development.

Spec

openspec/changes/custom-icon-upload-pattern/

---

Gemigreerd van Codeberg — oorspronkelijk Conduction/launchpad#9, geopend door rubenvdlinde op 2026-06-01.

[rubenvdlinde]

rubenvdlinde op 2026-06-01 (van Codeberg):

[Hydra Supervisor] Orphaned build:running label detected (worker exited without emitting a verdict). Escalated to needs-input. Check logs/pipeline-9-* and logs/reviews/launchpad-9-*.jsonl to diagnose, then apply retry:queued or rebuild:queued to resume.

[rubenvdlinde]

al-gorithm-con op 2026-06-02 (van Codeberg):

Pipeline escalation: at least one reviewer returned a fail verdict. Per the no-applier-override-on-review-fail rule, the applier is skipped and the issue escalates to needs-input. Apply retry:queued after addressing reviewer findings, or rebuild:queued if the build output was fundamentally wrong. See hydra.json.cycles[-1].stages[] for specifics.

[github-actions]

Thank you for opening this issue! It has been assigned to @rubenvdlinde for review.

What happens next:

1. A maintainer will review this issue and determine the appropriate action
2. If accepted, it may be converted into an OpenSpec change for structured development
3. You will be notified of any status changes

Triage labels:

• triage:accept-feature — accepted as a new feature
• triage:accept-bugfix — accepted as a bug fix
• triage:needs-info — more information needed
• triage:wontfix — will not be addressed
• triage:duplicate — duplicate of another issue