coilyco-flight-deck/agentic-os

Fork 0

Retire the issue-corpus renderer/docs now that forgejo-issues replaces it #343

New issue

Closed

opened 2026-07-08 21:48:30 +00:00 by coilyco-ops · 7 comments

coilyco-ops commented

2026-07-08 21:48:30 +00:00

Member

Context

Kai decided on 2026-07-08 that the old issue-corpus design should stop: the newer coilyco-bridge/deploy forgejo-issues service should be the shared issue mirror and agent lookup surface instead of rendering all Forgejo issues into coilysiren/inbox/corpus and mounting that into /substrate.

The repo still presents issue-corpus as an active feature:

docs/FEATURES.md has the Issue-corpus discovery index entry.
docs/issue-corpus.md documents the active design.
scripts/render-issue-corpus.py, scripts/issue-corpus-repos.txt, tests, and .forgejo/workflows/issue-corpus.yml carry the old implementation.
The related ward consumer (coilyco-flight-deck/ward#575) is now closed as superseded.
The replacement service work is coilyco-bridge/deploy#92.

Do

Retire or clearly mark the issue-corpus path as superseded so future agents do not revive it.

Remove the active docs/FEATURES.md entry, or replace it with a short superseded pointer to coilyco-bridge/deploy#92 if the historical breadcrumb is worth keeping.
Remove active docs/workflow/script surfaces that would keep the old renderer alive, unless a narrow historical note is needed.
Delete tests/config that only exist for the retired renderer.
Check for references to issue-corpus, coilysiren/inbox/corpus, and render-issue-corpus and update them to point at the forgejo-issues service where appropriate.
Keep unrelated session-log corpus exploration (agentic-os#298) out of scope unless a direct reference incorrectly depends on the retired issue-corpus path.

Acceptance

docs/FEATURES.md no longer advertises the git-rendered issue corpus as an active capability.
No scheduled workflow continues trying to render/push the old corpus.
Any remaining references are explicitly historical/superseded and point to coilyco-bridge/deploy#92 as the replacement direction.
ward exec test and pre-commit pass, or any pre-existing failures are identified.

Filed from the read-only director surface after Kai noticed the direct conflict between the inbox/substrate corpus spec and the newer self-hosted Forgejo issue service.

## Context Kai decided on 2026-07-08 that the old issue-corpus design should stop: the newer `coilyco-bridge/deploy` `forgejo-issues` service should be the shared issue mirror and agent lookup surface instead of rendering all Forgejo issues into `coilysiren/inbox/corpus` and mounting that into `/substrate`. The repo still presents issue-corpus as an active feature: - `docs/FEATURES.md` has the Issue-corpus discovery index entry. - `docs/issue-corpus.md` documents the active design. - `scripts/render-issue-corpus.py`, `scripts/issue-corpus-repos.txt`, tests, and `.forgejo/workflows/issue-corpus.yml` carry the old implementation. - The related ward consumer (`coilyco-flight-deck/ward#575`) is now closed as superseded. - The replacement service work is `coilyco-bridge/deploy#92`. ## Do Retire or clearly mark the issue-corpus path as superseded so future agents do not revive it. - Remove the active `docs/FEATURES.md` entry, or replace it with a short superseded pointer to `coilyco-bridge/deploy#92` if the historical breadcrumb is worth keeping. - Remove active docs/workflow/script surfaces that would keep the old renderer alive, unless a narrow historical note is needed. - Delete tests/config that only exist for the retired renderer. - Check for references to `issue-corpus`, `coilysiren/inbox/corpus`, and `render-issue-corpus` and update them to point at the `forgejo-issues` service where appropriate. - Keep unrelated session-log corpus exploration (`agentic-os#298`) out of scope unless a direct reference incorrectly depends on the retired issue-corpus path. ## Acceptance - `docs/FEATURES.md` no longer advertises the git-rendered issue corpus as an active capability. - No scheduled workflow continues trying to render/push the old corpus. - Any remaining references are explicitly historical/superseded and point to `coilyco-bridge/deploy#92` as the replacement direction. - `ward exec test` and pre-commit pass, or any pre-existing failures are identified. Filed from the read-only director surface after Kai noticed the direct conflict between the inbox/substrate corpus spec and the newer self-hosted Forgejo issue service.

coilyco-ops commented

2026-07-08 21:49:22 +00:00

Author

Member

🔒 Reserved by ward agent --harness codex — container engineer-codex-agentic-os-343 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-08T21:49:19Z). 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/agentic-os#343 · branch issue-343 · harness codex · workflow direct-main
Run: engineer-codex-agentic-os-343 · ward v0.466.0 · dispatched 2026-07-08T21:49:19Z
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.466.0).

— Codex, via ward agent

🔒 Reserved by `ward agent --harness codex` — container `engineer-codex-agentic-os-343` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-08T21:49:19Z). 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/agentic-os#343` · branch `issue-343` · harness `codex` · workflow `direct-main` - **Run:** `engineer-codex-agentic-os-343` · ward `v0.466.0` · dispatched `2026-07-08T21:49:19Z` - **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.466.0). </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-09 00:07:29 +00:00

Author

Member

🔒 Reserved by ward agent --harness codex — container engineer-codex-agentic-os-343 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-09T00:07:27Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL); --force overrides.

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

Resolved: coilyco-flight-deck/agentic-os#343 · branch issue-343 · harness codex · workflow pr
Run: engineer-codex-agentic-os-343 · ward v0.470.0 · dispatched 2026-07-09T00:07:27Z
Comment thread: 0 included in the pre-flight read, 1 stripped (ward's own automated comments).
- stripped: @coilyco-ops (2026-07-08T21:49:22Z)

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

— Codex, via ward agent

🔒 Reserved by `ward agent --harness codex` — container `engineer-codex-agentic-os-343` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-09T00:07:27Z). 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/agentic-os#343` · branch `issue-343` · harness `codex` · workflow `pr` - **Run:** `engineer-codex-agentic-os-343` · ward `v0.470.0` · dispatched `2026-07-09T00:07:27Z` - **Comment thread:** 0 included in the pre-flight read, 1 stripped (ward's own automated comments). - stripped: @coilyco-ops (2026-07-08T21:49:22Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.470.0). </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-09 00:13:04 +00:00

Author

Member

WARD-OUTCOME: blocked - review summary: blocked: codex: exit status 1

Review panel verdicts:

codex: ERROR: codex: exit status 1 (conf 0.00)
claude: ERROR: claude: exit status 1 (conf 0.00)
goose: ERROR: goose: exit status 1 (conf 0.00)

— Codex, via ward agent

WARD-OUTCOME: blocked - review summary: blocked: codex: exit status 1 Review panel verdicts: - codex: ERROR: codex: exit status 1 (conf 0.00) - claude: ERROR: claude: exit status 1 (conf 0.00) - goose: ERROR: goose: exit status 1 (conf 0.00)  — Codex, via `ward agent`

coilyco-ops commented

2026-07-09 00:13:42 +00:00

Author

Member

WARD-OUTCOME: blocked - ward review gate failed before a pass verdict
blocked: codex: exit status 1
The in-container review gate failed closed, so I stopped before opening a PR. The failure was in the reviewer harness, not in the diff itself, and the reviewed change remains on the issue branch.

WARD-OUTCOME: blocked - ward review gate failed before a pass verdict blocked: codex: exit status 1 The in-container review gate failed closed, so I stopped before opening a PR. The failure was in the reviewer harness, not in the diff itself, and the reviewed change remains on the issue branch.

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

2026-07-09 00:14:12 +00:00

ward salvage: ward-salvage/agentic-os-a019446c #347

coilyco-ops commented

2026-07-09 00:14:12 +00:00

Author

Member

⚠️ Reopened: this run's work did not land on `main`

An ephemeral ward container (codex mode) dispatched for this issue finished but its work was not merged to main, so the reaper preserved it on a branch before teardown and reopened the issue (a closing reference for #343 never reached main). Recover from the salvage branch below.

Repo: coilyco-flight-deck/agentic-os
Salvage branch: ward-salvage/agentic-os-a019446c
Pull request: not opened - PR creation failed: forgejo: parse created pull request: unexpected end of JSON input
Reason: run workflow does not land on main (--workflow pr/patch-only)
Container uptime at reap: 6m (age of the baked Forgejo PAT snapshot; a long-lived container is likelier to carry a rotated token)

Reap diagnostics

--- reap diagnostics ---
ward version:      v0.470.0
version source:    pinned via WARD_VERSION/--ward-version (v0.470.0)
HEAD:              e5116498ca31
origin/main:       ae3677c83d75
ancestry:          HEAD is NOT yet on origin/main - residual work remains to land
decision gate:     workflow does not land on main (--workflow pr/patch-only)
reason:            run workflow does not land on main (--workflow pr/patch-only)
provenance:        not read (workflow hold)
run-owned landed:  no
working tree:      clean
container uptime:  6m (baked Forgejo PAT age proxy)
--- end reap diagnostics ---

Recover

git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os.git ward-salvage/agentic-os-a019446c
git checkout -b ward-salvage/agentic-os-a019446c FETCH_HEAD

— Codex, via ward agent

## ⚠️ Reopened: this run's work did not land on `main` An ephemeral `ward container` (codex mode) dispatched for this issue finished but its work was **not merged to `main`**, so the reaper preserved it on a branch before teardown and reopened the issue (a closing reference for #343 never reached `main`). Recover from the salvage branch below. - **Repo:** `coilyco-flight-deck/agentic-os` - **Salvage branch:** `ward-salvage/agentic-os-a019446c` - **Pull request:** not opened - PR creation failed: forgejo: parse created pull request: unexpected end of JSON input - **Reason:** run workflow does not land on main (--workflow pr/patch-only) - **Container uptime at reap:** 6m (age of the baked Forgejo PAT snapshot; a long-lived container is likelier to carry a rotated token) ## Reap diagnostics ``` --- reap diagnostics --- ward version: v0.470.0 version source: pinned via WARD_VERSION/--ward-version (v0.470.0) HEAD: e5116498ca31 origin/main: ae3677c83d75 ancestry: HEAD is NOT yet on origin/main - residual work remains to land decision gate: workflow does not land on main (--workflow pr/patch-only) reason: run workflow does not land on main (--workflow pr/patch-only) provenance: not read (workflow hold) run-owned landed: no working tree: clean container uptime: 6m (baked Forgejo PAT age proxy) --- end reap diagnostics --- ``` ## Recover ```bash git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os.git ward-salvage/agentic-os-a019446c git checkout -b ward-salvage/agentic-os-a019446c FETCH_HEAD ```  — Codex, via `ward agent`

coilyco-ops commented

2026-07-09 21:33:43 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-agentic-os-343 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-09T21:33:41Z). 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/agentic-os#343 · branch issue-343 · harness codex · workflow direct-to-main
Run: engineer-codex-agentic-os-343 · ward v0.493.0 · dispatched 2026-07-09T21:33:41Z
Comment thread: 3 included in the pre-flight read, 2 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-09T00:13:04Z), @coilyco-ops (2026-07-09T00:13:42Z), @coilyco-ops (2026-07-09T00:14:12Z)
- stripped: @coilyco-ops (2026-07-08T21:49:22Z), @coilyco-ops (2026-07-09T00:07:29Z)

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

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-agentic-os-343` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-09T21:33:41Z). 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/agentic-os#343` · branch `issue-343` · harness `codex` · workflow `direct-to-main` - **Run:** `engineer-codex-agentic-os-343` · ward `v0.493.0` · dispatched `2026-07-09T21:33:41Z` - **Comment thread:** 3 included in the pre-flight read, 2 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-09T00:13:04Z), @coilyco-ops (2026-07-09T00:13:42Z), @coilyco-ops (2026-07-09T00:14:12Z) - stripped: @coilyco-ops (2026-07-08T21:49:22Z), @coilyco-ops (2026-07-09T00:07:29Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.493.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a commit

2026-07-09 21:41:25 +00:00

docs: retire issue-corpus renderer

coilyco-ops closed this issue

2026-07-09 21:41:25 +00:00

coilyco-ops commented

2026-07-09 21:41:55 +00:00

Author

Member

WARD-OUTCOME: done ✅

details

review summary: skipped by ~/.ward/config.yaml default
workflow: direct-to-main; review summary: skipped by ~/.ward/config.yaml default
felt: straightforward surgery. The main snag was container disk pressure around pre-commit and git hooks.
confidence: high
surprises: pre-commit hook caches and Go build temp space were too tight for the full suite in this container.
follow-ups: none.

WARD-OUTCOME: done ✅ <details><summary>details</summary> review summary: skipped by ~/.ward/config.yaml default workflow: direct-to-main; review summary: skipped by ~/.ward/config.yaml default felt: straightforward surgery. The main snag was container disk pressure around pre-commit and git hooks. confidence: high surprises: pre-commit hook caches and Go build temp space were too tight for the full suite in this container. follow-ups: none. </details>

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

coilyco-flight-deck/agentic-os#343

No description provided.

Rows
Columns

Retire the issue-corpus renderer/docs now that forgejo-issues replaces it #343

Context

Do

Acceptance

⚠️ Reopened: this run's work did not land on main

Reap diagnostics

Recover

⚠️ Reopened: this run's work did not land on `main`