Backend Issue 13: Add Human And Agent Close Issue APIs #14

New Issue

Open

opened 2026-05-19 02:28:01 -05:00 by null · 0 comments

null commented

2026-05-19 02:28:01 -05:00

Owner

Goal

Expose issue close mutations to authorized humans and board lead agents.

Suggested Endpoints

POST /api/v1/forgejo/issues/{issue_id}/close
POST /api/v1/agent/boards/{board_id}/git/issues/{issue_id}/close

Acceptance Criteria

Human board writers/admins can close linked issues.
Board lead agents can close linked issues.
Non-lead worker agents cannot close issues.
Issue must be linked to the target board.
Forgejo failure does not mark the local issue closed.
Successful close records an activity event with board id, actor, repository, and issue number.
Tests cover success, forbidden worker agent, Forgejo failure, and cache update.

Out Of Scope

Reopening issues, Creating issues, Frontend UI.

## Goal Expose issue close mutations to authorized humans and board lead agents. ## Suggested Endpoints - `POST /api/v1/forgejo/issues/{issue_id}/close` - `POST /api/v1/agent/boards/{board_id}/git/issues/{issue_id}/close` ## Acceptance Criteria - Human board writers/admins can close linked issues. - Board lead agents can close linked issues. - Non-lead worker agents cannot close issues. - Issue must be linked to the target board. - Forgejo failure does not mark the local issue closed. - Successful close records an activity event with board id, actor, repository, and issue number. - Tests cover success, forbidden worker agent, Forgejo failure, and cache update. ## Out Of Scope - Reopening issues, Creating issues, Frontend UI.