[integrator] SCRUM board: how agents move cards #13

Closed
opened 2026-10-23 22:39:51 -05:00 by yuuhikaze · 1 comment
Owner

status: the SCRUM board (/k8s-services/rgxr/projects/1) is live. Forgejo has no projects API, so cards move through the web routes with a bot web login. All agents keep their cards current here.

Columns — Backlog, To Do, In Progress, Done (data-id 1–4 on the board page; read them from the HTML rather than hardcoding).

Credentials — OpenBao rgxr/forgejo-web, keys username, password (bot rgxr-agent, temporary). Never paste them into issues: this repo is public.

curl -sS -H "X-Vault-Token: $VAULT_TOKEN" "$VAULT_ADDR/v1/rgxr/data/forgejo-web" | jq -r .data.data.password

Log in — Forgejo 16 has no _csrf form field; it checks the Origin header. A 303 to / means success.

J=cookies.txt; B=https://git.yhkze.net
curl -sS -c $J -b $J -o /dev/null -w '%{http_code}\n' -H "Origin: $B" \
  --data-urlencode user_name=rgxr-agent --data-urlencode "password=$PASS" "$B/user/login"

Add an issue to the board — ID is the issue's internal .id from GET /api/v1/repos/k8s-services/rgxr/issues/<number>, not the #number.

curl -sS -b $J -H "Origin: $B" --data "issue_ids=$ID&id=1" "$B/k8s-services/rgxr/issues/projects"

Move a card — returns {"ok":true}.

curl -sS -b $J -H "Origin: $B" -H 'Content-Type: application/json' \
  -d "{\"issues\":[{\"issueID\":$ID,\"sorting\":0}]}" "$B/k8s-services/rgxr/projects/1/$COLUMN_ID/move"

These are internal web routes and can break on a Forgejo upgrade. A failed card move never blocks real work: log it and continue.

Current placement: #12 (core), #2, #5, #6 → In Progress; #4 → To Do. Close/move your own cards as PRs merge.

status: the SCRUM board (`/k8s-services/rgxr/projects/1`) is live. Forgejo has no projects API, so cards move through the web routes with a bot web login. All agents keep their cards current here. **Columns** — Backlog, To Do, In Progress, Done (`data-id` 1–4 on the board page; read them from the HTML rather than hardcoding). **Credentials** — OpenBao `rgxr/forgejo-web`, keys `username`, `password` (bot `rgxr-agent`, temporary). Never paste them into issues: this repo is public. ```bash curl -sS -H "X-Vault-Token: $VAULT_TOKEN" "$VAULT_ADDR/v1/rgxr/data/forgejo-web" | jq -r .data.data.password ``` **Log in** — Forgejo 16 has no `_csrf` form field; it checks the `Origin` header. A 303 to `/` means success. ```bash J=cookies.txt; B=https://git.yhkze.net curl -sS -c $J -b $J -o /dev/null -w '%{http_code}\n' -H "Origin: $B" \ --data-urlencode user_name=rgxr-agent --data-urlencode "password=$PASS" "$B/user/login" ``` **Add an issue to the board** — `ID` is the issue's internal `.id` from `GET /api/v1/repos/k8s-services/rgxr/issues/<number>`, not the `#number`. ```bash curl -sS -b $J -H "Origin: $B" --data "issue_ids=$ID&id=1" "$B/k8s-services/rgxr/issues/projects" ``` **Move a card** — returns `{"ok":true}`. ```bash curl -sS -b $J -H "Origin: $B" -H 'Content-Type: application/json' \ -d "{\"issues\":[{\"issueID\":$ID,\"sorting\":0}]}" "$B/k8s-services/rgxr/projects/1/$COLUMN_ID/move" ``` These are internal web routes and can break on a Forgejo upgrade. A failed card move never blocks real work: log it and continue. Current placement: #12 (core), #2, #5, #6 → In Progress; #4 → To Do. Close/move your own cards as PRs merge.
Owner

Cleanup note: with the board work finished (cards #70–#73 in Done, description fixed), the temporary access was retired: rgxr/forgejo-web and rgxr/forgejo-token were deleted from OpenBao, and the rgxr-agent account is being retired via the admin UI (this Forgejo build 405s on user deletion via API). The web-route recipe above (login → issues/projects → projects/1/{column}/move) remains accurate if fresh credentials are ever provisioned.

**Cleanup note:** with the board work finished (cards #70–#73 in Done, description fixed), the temporary access was retired: `rgxr/forgejo-web` and `rgxr/forgejo-token` were deleted from OpenBao, and the `rgxr-agent` account is being retired via the admin UI (this Forgejo build 405s on user deletion via API). The web-route recipe above (login → `issues/projects` → `projects/1/{column}/move`) remains accurate if fresh credentials are ever provisioned.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
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
k8s-services/rgxr#13
No description provided.