Task: Board hygiene — label unlabeled items + add missing story: labels #170

New issue

Open

opened 2026-03-26 17:25:25 +00:00 by forgejo_admin · 1 comment

forgejo_admin commented

2026-03-26 17:25:25 +00:00

Contributor

Type

Feature

Lineage

standalone — discovered during board audit 2026-03-26.
NOTE: This is actually a Task (non-code work). Filed as Feature to pass hook validation until claude-custom#167 ships Task type routing.

Repo

forgejo_admin/claude-custom (tracking repo — actual work is pal-e-docs board operations)

User Story

As Betty Sue (PM),
I want all board items to have complete traceability labels,
So that every piece of work on the board is provably connected to a user story and architecture component.

Context

Board audit of board-pal-e-agency found 4 items with zero labels (pre-hook era) and 6 items missing story: labels. Once Ticket A (claude-custom#167) ships story: as a hard block, these items would fail if recreated. Clean them up proactively.

File Targets

No code files. All work is pal-e-docs update_board_item calls:

4 items with NO labels (backlog):

#65 (linkedin-scheduler CI) — needs type:, arch:, story:
#63 (gcal-mcp CI) — needs type:, arch:, story:
#164 (Phase 15: Capacitor Audit Agent) — evaluate: label or remove
#167 (Phase 17: Pipeline Enforcement Gates) — evaluate: label or remove

6 items missing story: (todo/backlog):

#377, #360, #363, #342, #365, #347 — each needs story: from project-pal-e-agency User Stories

Acceptance Criteria

All 10 items have type:, arch:, and story: labels
Phase items evaluated and either labeled or removed with justification
Labels use valid keys from project-pal-e-agency user stories table
No items in todo column missing story: label

Test Expectations

list_board_items(board_slug="board-pal-e-agency") shows all items labeled
Verify story: keys match project-pal-e-agency User Stories table

Constraints

Look up each Forgejo issue to understand the work before assigning story: label
Use project-pal-e-agency user story keys: superuser-manage, superuser-onboard, pm-scope, dev-execute, qa-review, dottie-docs

Checklist

All items updated
No unrelated changes

project-pal-e-agency — project
story:pm-scope — user story
arch:kanban — architecture component

### Type Feature ### Lineage standalone — discovered during board audit 2026-03-26. NOTE: This is actually a Task (non-code work). Filed as Feature to pass hook validation until claude-custom#167 ships Task type routing. ### Repo `forgejo_admin/claude-custom` (tracking repo — actual work is pal-e-docs board operations) ### User Story As Betty Sue (PM), I want all board items to have complete traceability labels, So that every piece of work on the board is provably connected to a user story and architecture component. ### Context Board audit of board-pal-e-agency found 4 items with zero labels (pre-hook era) and 6 items missing story: labels. Once Ticket A (claude-custom#167) ships story: as a hard block, these items would fail if recreated. Clean them up proactively. ### File Targets No code files. All work is pal-e-docs `update_board_item` calls: **4 items with NO labels (backlog):** - #65 (linkedin-scheduler CI) — needs type:, arch:, story: - #63 (gcal-mcp CI) — needs type:, arch:, story: - #164 (Phase 15: Capacitor Audit Agent) — evaluate: label or remove - #167 (Phase 17: Pipeline Enforcement Gates) — evaluate: label or remove **6 items missing story: (todo/backlog):** - #377, #360, #363, #342, #365, #347 — each needs story: from project-pal-e-agency User Stories ### Acceptance Criteria - [ ] All 10 items have type:, arch:, and story: labels - [ ] Phase items evaluated and either labeled or removed with justification - [ ] Labels use valid keys from project-pal-e-agency user stories table - [ ] No items in todo column missing story: label ### Test Expectations - `list_board_items(board_slug="board-pal-e-agency")` shows all items labeled - Verify story: keys match project-pal-e-agency User Stories table ### Constraints - Look up each Forgejo issue to understand the work before assigning story: label - Use project-pal-e-agency user story keys: superuser-manage, superuser-onboard, pm-scope, dev-execute, qa-review, dottie-docs ### Checklist - [ ] All items updated - [ ] No unrelated changes ### Related - `project-pal-e-agency` — project - `story:pm-scope` — user story - `arch:kanban` — architecture component

forgejo_admin commented

2026-03-26 17:29:19 +00:00

Author

Contributor

Scope Review: READY

Review note: review-398-2026-03-26
All 10 board items verified against live board data. Template 11/11 sections complete. No blocking dependencies. Acceptance criteria all verifiable via list_board_items.

Observations (non-blocking):

Other boards (westside-basketball, pal-e-platform, pal-e-docs) likely need the same hygiene pass — separate tickets recommended.
Board item #364 uses story:scope-review which is not in the User Stories table — outside this ticket's scope but worth noting.
Phase items #164 and #167 will likely be removed per kanban-over-plans feedback.

## Scope Review: READY Review note: `review-398-2026-03-26` All 10 board items verified against live board data. Template 11/11 sections complete. No blocking dependencies. Acceptance criteria all verifiable via `list_board_items`. **Observations (non-blocking):** - Other boards (westside-basketball, pal-e-platform, pal-e-docs) likely need the same hygiene pass — separate tickets recommended. - Board item #364 uses `story:scope-review` which is not in the User Stories table — outside this ticket's scope but worth noting. - Phase items #164 and #167 will likely be removed per kanban-over-plans feedback.