Remove issue templates from forgejo #1113

New issue

Closed

opened 2026-07-11 15:40:38 +00:00 by coilysiren · 2 comments

coilysiren commented

2026-07-11 15:40:38 +00:00

Owner

Which surface

Other / not sure

What happened

What you expected

Steps to reproduce

ward version

OS and install method

No response

Before filing

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

### Which surface Other / not sure ### What happened // ### What you expected // ### Steps to reproduce // ### ward version // ### OS and install method _No response_ ### 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 commented

2026-07-13 03:19:41 +00:00

Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-ward-1113 on host KAI-DESKTOP-TOWER.

Reserved by ward agent --harness codex (reserved 2026-07-13T03:19:38Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (3h TTL). --override-reservation 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#1113 · branch issue-1113 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-ward-1113 · ward v0.633.0 · dispatched 2026-07-13T03:19:38Z
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.633.0).

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-ward-1113` on host `KAI-DESKTOP-TOWER`. Reserved by `ward agent --harness codex` (reserved 2026-07-13T03:19:38Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (3h TTL). `--override-reservation` 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#1113` · branch `issue-1113` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-1113` · ward `v0.633.0` · dispatched `2026-07-13T03:19:38Z` - **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.633.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a commit

2026-07-13 03:31:34 +00:00

chore: remove issue templates

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

2026-07-13 03:31:41 +00:00

Remove issue templates from forgejo #1153

coilyco-ops commented

2026-07-13 03:33:57 +00:00

Member

WARD-OUTCOME: submitted

details

workflow: pull-request-and-merge; review summary: review gate intentionally skipped because the temporary ward default pending brokered QA felt: straightforward but noisier than expected because the repo-wide comment hook needed cleanup confidence: high surprises: the hook set flagged unrelated comment debt before it would accept this small deletion follow-ups: PR #1153 is open and checks are green; merge remains for the director loop

WARD-OUTCOME: submitted <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate intentionally skipped because the temporary ward default pending brokered QA felt: straightforward but noisier than expected because the repo-wide comment hook needed cleanup confidence: high surprises: the hook set flagged unrelated comment debt before it would accept this small deletion follow-ups: PR #1153 is open and checks are green; merge remains for the director loop </details>

coilysiren closed this issue

2026-07-13 07:39:00 +00:00

coilysiren referenced this issue from a commit

2026-07-13 07:39:00 +00:00

Merge ward PR #1153: Remove issue templates from forgejo