Spike: Board items for non-code operations projects #56

New issue

Open

opened 2026-03-30 21:21:43 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

2026-03-30 21:21:43 +00:00

Contributor

Type

Spike

Lineage

Standalone — emerged from westside-accounting project setup (2026-03-30). Operations project has no natural code repo. Board item creation blocked by item type requirements.

Repo

forgejo_admin/pal-e-mcp (board item API) + ~/.claude/hooks/check-board-item.sh

Question

Should non-code operations projects use issue-only Forgejo repos for tracking, or should a new standalone task board item type be added that requires neither note_slug nor forgejo_issue_url?

What to Explore

Current item types: issue (needs forgejo_issue_url), todo/plan/phase/repo/project (need note_slug)
Hook check-board-item.sh enforces forgejo_issue_url for issue type
API enforces note_slug for todo type at validation layer
Workaround used: created forgejo_admin/westside-accounting issue-only repo (no code)
Alternative: add task item_type accepting title + description only
Trade-off: Forgejo issues give comments, history, labels. Standalone tasks are lighter but lose that.

Success Criteria

Decision: new item_type vs issue-only repos vs hook relaxation
Pattern documented for operations projects
Follow-up ticket if API change needed

Time-box

1 session (2 hours max)

project-westside-accounting — project that surfaced this gap
board-westside-accounting — created but empty
check-board-item.sh hook

### Type Spike ### Lineage Standalone — emerged from westside-accounting project setup (2026-03-30). Operations project has no natural code repo. Board item creation blocked by item type requirements. ### Repo `forgejo_admin/pal-e-mcp` (board item API) + `~/.claude/hooks/check-board-item.sh` ### Question Should non-code operations projects use issue-only Forgejo repos for tracking, or should a new standalone `task` board item type be added that requires neither `note_slug` nor `forgejo_issue_url`? ### What to Explore - Current item types: `issue` (needs forgejo_issue_url), `todo`/`plan`/`phase`/`repo`/`project` (need note_slug) - Hook `check-board-item.sh` enforces forgejo_issue_url for issue type - API enforces note_slug for todo type at validation layer - Workaround used: created `forgejo_admin/westside-accounting` issue-only repo (no code) - Alternative: add `task` item_type accepting title + description only - Trade-off: Forgejo issues give comments, history, labels. Standalone tasks are lighter but lose that. ### Success Criteria - [ ] Decision: new item_type vs issue-only repos vs hook relaxation - [ ] Pattern documented for operations projects - [ ] Follow-up ticket if API change needed ### Time-box 1 session (2 hours max) ### Related - `project-westside-accounting` — project that surfaced this gap - `board-westside-accounting` — created but empty - `check-board-item.sh` hook