Implement resource-uploads (openspec change)

[rubenvdlinde]

Hydra pipeline tracking issue — auto-filed for openspec change resource-uploads on development.

Spec

openspec/changes/resource-uploads/

---

Gemigreerd van Codeberg — oorspronkelijk Conduction/launchpad#21, 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-21-* and logs/reviews/launchpad-21-*.jsonl to diagnose, then apply retry:queued or rebuild:queued to resume.

[rubenvdlinde]

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

[Hydra supervisor] Timeout on slot 5 (build) after 15969s. Container killed — no stage record was persisted to hydra.json for this run. Self-learning pattern: container-crashed-mid-stage.

[rubenvdlinde]

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

[Hydra Supervisor] security-review hit an Anthropic API overload and was re-queued.

The Claude CLI exhausted its internal retries. The reviewer formed no opinion, so the pipeline is treating this as transient infrastructure, not a review failure. The supervisor will keep re-dispatching on each tick until the API recovers or an operator applies needs-input manually.

Error sample:

API Error: 529 Overloaded. This is a server-side issue, usually temporary — try again in a moment. If it persists, check status.claude.com.

This comment is posted once per stall to avoid spam.

[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

[rubenvdlinde]

juan-claude op 2026-06-02 (van Codeberg):

[Hydra Supervisor] Orphaned security-review:running label detected (worker exited without emitting a verdict). Escalated to needs-input. Check logs/pipeline-21-* and logs/reviews/launchpad-21-*.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.

[rubenvdlinde]

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

Pipeline escalation: Applier dispatch skipped because openspec/changes/resource-uploads/hydra.json could not be read from the PR branch (feature/21/resource-uploads) or from the local spec path. An empty hydra.json would make the applier trivially pass on the "no unfixed CRITICAL" decision rule, so this is a hard block. Investigate the missing metadata and re-queue with retry:queued once restored.