Configure the Project #2 kanban board (views, WIP, automations)

[jorisjonkers-dev-agents]

Context. Project #2 lives at https://github.com/orgs/JorisJonkers-dev/projects/2. The fields and options are already set via API, but views, WIP limits, and built-in workflows are owner-UI-only — GitHub exposes no API/gh command for them, so this issue is a precise click-path rather than a script.

A · Board view (UI)

1. Open the project → ＋ New view → Board.
2. Group by → Status. Confirm the columns read: Backlog → Ready → In Progress → In Review → Blocked → Done (drag to reorder if needed).
3. Rename the view "Board" and save.

B · WIP limits (UI)

On the Board view, click each column header → Set limit:

• In Progress → 3
• In Review → 5

C · Built-in workflows (UI — Project → ⚙ → Workflows)

Enable:

• Item added to project → set Status: Backlog
• Pull request merged → set Status: Done
• Issue closed → set Status: Done
• Auto-archive items → when Status is Done for 2 weeks

D · Confirm auto-add (already wired)

New issues/PRs across the org auto-add via the add-to-project-caller.yml workflow — no action needed; just confirm a freshly opened issue appears in Backlog.

Why no script

The GitHub ProjectsV2 GraphQL API can set field values and add items (which the automation already does), but cannot create views, set WIP limits, or toggle built-in workflows — those are owner-only UI settings. So this one is hands-on.

Acceptance

• Board view with the 6 columns in order
• WIP limits on In Progress (3) and In Review (5)
• Closing an issue / merging a PR auto-moves it to Done; Done items auto-archive after 2 weeks

---

Where to run: gh commands run from anywhere (they name repos explicitly) and need gh auth status as an org-admin. Steps marked (in your .github clone) must run inside the cloned repo.

[ExtraToast]

Configured Project #2 via the owner UI (https://github.com/orgs/JorisJonkers-dev/projects/2). Summary of changes:

A · Board view

• The existing Status-grouped board view was renamed "Kanban" → "Board".
• Confirmed column order: Backlog → Ready → In Progress → In Review → Blocked → Done.

B · WIP limits

• In Progress → 3
• In Review → 5

C · Built-in workflows

Workflow	State	Action
Item added to project	On	Changed Set value Ready → Backlog (it had been set to Ready)
Pull request merged	On	Status: Done (already correct)
Item closed (= issue closed)	On	Status: Done (already correct)
Auto-archive items	Enabled	filter is:closed updated:<@today-2w

Note on auto-archive: the spec asked for "when Status is Done for 2 weeks", but GitHub's auto-archive filter only accepts issue/PR search qualifiers and rejects status:Done with "Unknown field name 'status'". Since closing an issue and merging a PR are exactly what set Status to Done, is:closed is the faithful equivalent — GitHub normalized it to is:issue,pr is:closed updated:<@today-2w, covering both closed issues and merged PRs. The 2-week window is preserved.

D · Auto-add

• The external add-to-project-caller.yml wiring is unchanged. With "Item added to project" now setting Backlog, newly opened issues/PRs will land in Backlog. (Final confirmation just needs the next freshly opened issue to be observed.)

All acceptance criteria are met. Closing.