Add Forgejo package cleanup coverage for dev-base draft tags #534

New issue

Open

opened 2026-07-14 15:50:45 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-07-14 15:50:45 +00:00

Member

promote.yml now publishes commit-scoped draft image tags before moving release. Forgejo package cleanup rules should prune versions matching draft tags after a short retention window. The current ward ops forgejo surface exposes repo package enablement but not package cleanup rule management, so follow up by either configuring the rule manually or adding a guarded ops verb.

coilyco-ops commented

2026-07-15 04:01:40 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

Holder: launch intent for container engineer-codex-agentic-os-534 on host kais-macbook-pro-2.local.

Accepted by ward agent --harness codex (reserved 2026-07-15T04:01:39Z). Concurrent ward agent runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (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/agentic-os#534 · branch issue-534 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-agentic-os-534 · ward v0.696.0 · dispatched 2026-07-15T04:01:30Z
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.696.0).

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-agentic-os-534` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T04:01:39Z). Concurrent `ward agent` runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (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/agentic-os#534` · branch `issue-534` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-agentic-os-534` · ward `v0.696.0` · dispatched `2026-07-15T04:01:30Z` - **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.696.0). </details> </details>  — Codex, via `ward agent`