Point agent task lists at Gitea issue numbers #1714

Closed
opened 2026-10-29 12:24:30 +00:00 by sam · 1 comment
Owner

Work items are still handed to agents as GitHub numbers (Archie next 50 work items.md cites #1896, which is Gitea #497). GitHub is the mirror, so its numbers are
the ones that will stop being maintained.

Regenerate the list from the tracker instead, for example

tea issues list -r sam/archie --state open --labels priority::critical --output json

Every migrated issue keeps its old GitHub number in the body footer, so an old
reference still resolves.

Work items are still handed to agents as GitHub numbers (`Archie next 50 work items.md` cites #1896, which is Gitea #497). GitHub is the mirror, so its numbers are the ones that will stop being maintained. Regenerate the list from the tracker instead, for example tea issues list -r sam/archie --state open --labels priority::critical --output json Every migrated issue keeps its old GitHub number in the body footer, so an old reference still resolves.
sam added the mediumtask labels 2026-10-29 12:24:30 +00:00
sam self-assigned this 2026-10-29 12:24:30 +00:00
Author
Owner

Triaged: no code change is needed for this. No code change is needed in this repository; the request is operator content work, and the repo-side rule it asks for is already in the tree.

What the issue asks: the Markdown file Archie next 50 work items.md still cites GitHub numbers (#1896 rather than Gitea #497), and it wants the list regenerated from the tracker with tea issues list -r sam/archie --state open --labels priority::critical --output json.

What I checked:

  • That file is not in this repository. find for *work items* and for Archie* across /data/worktree returns no matches, and grep for next 50|next50|50 work finds nothing. No Go code, Taskfile target or tool reads or writes a work-item list; the only "task list" hits in the tree are the dashboard's task list (internal/webui/tasks_handlers.go, ui/src/tasks/*). So nothing here can be "pointed at Gitea numbers" — the list is an operator-held document, and regenerating it is content work, not a change to archie-core.
  • The instruction the issue wants already exists twice: AGENTS.md and CLAUDE.md carry an identical "## Issues (Gitea)" section — "Work is tracked as issues on the primary remote, never in Markdown TODO files. GitHub is a read-only mirror; do not open, close or comment there" — followed by the same command the issue proposes (CLAUDE.md:186: tea issues list -r sam/archie --state open --labels priority::critical). ui/AGENTS.md:135-136 repeats it for dashboard work.
  • A tracker-sourced listing exists in code as well: the issue_list tool (internal/gateway/issue_tools.go) returns number/title/labels from whichever forge connection is configured, via the daemon's OpenIssues (internal/infrastructure/issuerpc/issuerpc.go:102). Nothing in that path hardcodes GitHub.

So this is administrative: regenerate the external Markdown list from the tracker (and, if a copy of it is configured as agent context, point that config at tracker output instead). Doing that needs no commit.

Remaining, outside this tree: the actual regeneration of Archie next 50 work items.md with Gitea numbers, which I could not verify because the file is not in the repository.

If the operator instead wants the product to emit such a list (a generator or a new command), that is new mechanism and runs against AGENTS.md's "no compensating tools" and "never Markdown TODO files" rules — it would need a design decision first (feasibility workflow) rather than an implementation. That is not what the issue asks for, so I have not routed it there.

Triaged: no code change is needed for this. No code change is needed in this repository; the request is operator content work, and the repo-side rule it asks for is already in the tree. What the issue asks: the Markdown file `Archie next 50 work items.md` still cites GitHub numbers (#1896 rather than Gitea #497), and it wants the list regenerated from the tracker with `tea issues list -r sam/archie --state open --labels priority::critical --output json`. What I checked: - That file is not in this repository. `find` for `*work items*` and for `Archie*` across /data/worktree returns no matches, and grep for `next 50|next50|50 work` finds nothing. No Go code, Taskfile target or tool reads or writes a work-item list; the only "task list" hits in the tree are the dashboard's task list (internal/webui/tasks_handlers.go, ui/src/tasks/*). So nothing here can be "pointed at Gitea numbers" — the list is an operator-held document, and regenerating it is content work, not a change to archie-core. - The instruction the issue wants already exists twice: AGENTS.md and CLAUDE.md carry an identical "## Issues (Gitea)" section — "Work is tracked as issues on the primary remote, never in Markdown TODO files. GitHub is a read-only mirror; do not open, close or comment there" — followed by the same command the issue proposes (`CLAUDE.md:186`: `tea issues list -r sam/archie --state open --labels priority::critical`). ui/AGENTS.md:135-136 repeats it for dashboard work. - A tracker-sourced listing exists in code as well: the `issue_list` tool (internal/gateway/issue_tools.go) returns number/title/labels from whichever forge connection is configured, via the daemon's `OpenIssues` (internal/infrastructure/issuerpc/issuerpc.go:102). Nothing in that path hardcodes GitHub. So this is administrative: regenerate the external Markdown list from the tracker (and, if a copy of it is configured as agent context, point that config at tracker output instead). Doing that needs no commit. Remaining, outside this tree: the actual regeneration of `Archie next 50 work items.md` with Gitea numbers, which I could not verify because the file is not in the repository. If the operator instead wants the product to emit such a list (a generator or a new command), that is new mechanism and runs against AGENTS.md's "no compensating tools" and "never Markdown TODO files" rules — it would need a design decision first (feasibility workflow) rather than an implementation. That is not what the issue asks for, so I have not routed it there.
sam closed this issue 2026-11-06 22:19:49 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1714