404 when reading PRs #875

New issue

Closed

opened 2026-07-09 22:41:34 +00:00 by coilysiren · 2 comments

coilysiren commented

2026-07-09 22:41:34 +00:00

Owner

Which surface

The operator surface (ward ops ...)

What happened

ward agent director --harness codex: not merging coilyco-bridge/agentic-os-kai#728 - could not read PR mergeability: forgejo pull request GET returned 404 Not Found after 106 byte(s): "{"message":"The target couldn't be found.","url":"https://forgejo.coilysiren.me/api/swagger","errors":[]}"

What you expected

Steps to reproduce

warded director --driver codex --repo coilyco-bridge/agentic-os-kai

ward version

0.540.0

OS and install method

mac

Before filing

I searched existing issues and this is not a duplicate.
This is not a security vulnerability (those follow SECURITY.md).

### Which surface The operator surface (ward ops ...) ### What happened ward agent director --harness codex: not merging coilyco-bridge/agentic-os-kai#728 - could not read PR mergeability: forgejo pull request GET returned 404 Not Found after 106 byte(s): "{\"message\":\"The target couldn't be found.\",\"url\":\"https://forgejo.coilysiren.me/api/swagger\",\"errors\":[]}" ### What you expected // ### Steps to reproduce warded director --driver codex --repo coilyco-bridge/agentic-os-kai ### ward version 0.540.0 ### OS and install method mac ### Before filing - [x] I searched existing issues and this is not a duplicate. - [x] This is not a security vulnerability (those follow SECURITY.md).

coilyco-ops added the

headless

labels

2026-07-10 00:41:50 +00:00

coilyco-ops commented

2026-07-10 00:44:46 +00:00

Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-ward-875 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-10T00:44:43Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL). --force overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/ward#875 · branch issue-875 · harness codex · workflow pull-requests-and-merge
Run: engineer-codex-ward-875 · ward v0.543.0 · dispatched 2026-07-10T00:44:43Z
Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.543.0).

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-ward-875` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-10T00:44:43Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL). `--force` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh**. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/ward#875` · branch `issue-875` · harness `codex` · workflow `pull-requests-and-merge` - **Run:** `engineer-codex-ward-875` · ward `v0.543.0` · dispatched `2026-07-10T00:44:43Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.543.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-10 00:52:40 +00:00

fix: soften Forgejo PR 404s #908

coilyco-ops commented

2026-07-10 00:57:07 +00:00

Member

WARD-OUTCOME: merge-ready

details

workflow: pull-requests-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default

felt: straightforward after the PR-read error path was normalized and the existing lint waiver was surfaced

confidence: high

surprises: Forgejo PR detail 404s now read as not found, and golangci-lint needed the existing launch-container waiver

follow-ups: director can merge PR #908 when policy allows

WARD-OUTCOME: merge-ready <details><summary>details</summary> workflow: pull-requests-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default felt: straightforward after the PR-read error path was normalized and the existing lint waiver was surfaced confidence: high surprises: Forgejo PR detail 404s now read as not found, and golangci-lint needed the existing launch-container waiver follow-ups: director can merge PR #908 when policy allows </details>

coilysiren closed this issue

2026-07-10 01:06:46 +00:00