Remove sprint note type from platform #193

New issue

Closed

opened 2026-03-23 14:15:40 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

2026-03-23 14:15:40 +00:00

Owner

Type

Feature

Lineage

Standalone — board-pal-e-docs kanban MVP

Repo

forgejo_admin/pal-e-docs (primary), forgejo_admin/pal-e-app, forgejo_admin/pal-e-docs-sdk, forgejo_admin/pal-e-docs-mcp

User Story

As the superuser
I want the dead "sprint" concept removed from the platform
So that the codebase reflects continuous kanban and doesn't confuse agents or future contributors

Context

We use continuous kanban, not sprints. The sprint DB tables were replaced by boards in migration n4i5j6k7l8m9. But "sprint" still exists as a valid NoteType in the API schema, meaning notes of type "sprint" can still be created. Stale references exist across 4 repos.

File Targets

Files to modify:

pal-e-docs/src/pal_e_docs/schemas.py:19 — remove "sprint" from NoteType literal
pal-e-docs/src/pal_e_docs/routes/notes.py:58 — remove sprint status validation
pal-e-app/src/lib/colors.ts:24 — remove sprint color
pal-e-app/src/routes/notes/[slug]/edit/+page.svelte:21 — remove from dropdown
pal-e-docs-sdk/src/pal_e_docs_sdk/boards.py:14 — update docstring
pal-e-docs-mcp/src/pal_e_docs_mcp/tools/boards.py:3,32 — update docstrings/examples
pal-e-docs-mcp/tests/test_param_alignment.py:393-396 — fix test example

Files NOT to touch:

alembic/versions/*sprint* — historical migrations stay

Acceptance Criteria

No "sprint" in NoteType literal
Creating a note with type "sprint" returns 422
No sprint references in frontend dropdowns or color maps
Existing notes with type "sprint" (if any) migrated or handled

Test Expectations

Unit test: POST /notes with type "sprint" returns validation error
Run: pytest tests/test_note_type_enum.py

Constraints

One PR per repo (4 PRs total)
Check if any notes in the DB currently have type "sprint" before removing

Checklist

PR opened
Tests pass
No unrelated changes

project-pal-e-docs — all repos in this project

### Type Feature ### Lineage Standalone — board-pal-e-docs kanban MVP ### Repo `forgejo_admin/pal-e-docs` (primary), `forgejo_admin/pal-e-app`, `forgejo_admin/pal-e-docs-sdk`, `forgejo_admin/pal-e-docs-mcp` ### User Story As the superuser I want the dead "sprint" concept removed from the platform So that the codebase reflects continuous kanban and doesn't confuse agents or future contributors ### Context We use continuous kanban, not sprints. The sprint DB tables were replaced by boards in migration `n4i5j6k7l8m9`. But `"sprint"` still exists as a valid NoteType in the API schema, meaning notes of type "sprint" can still be created. Stale references exist across 4 repos. ### File Targets Files to modify: - `pal-e-docs/src/pal_e_docs/schemas.py:19` — remove "sprint" from NoteType literal - `pal-e-docs/src/pal_e_docs/routes/notes.py:58` — remove sprint status validation - `pal-e-app/src/lib/colors.ts:24` — remove sprint color - `pal-e-app/src/routes/notes/[slug]/edit/+page.svelte:21` — remove from dropdown - `pal-e-docs-sdk/src/pal_e_docs_sdk/boards.py:14` — update docstring - `pal-e-docs-mcp/src/pal_e_docs_mcp/tools/boards.py:3,32` — update docstrings/examples - `pal-e-docs-mcp/tests/test_param_alignment.py:393-396` — fix test example Files NOT to touch: - `alembic/versions/*sprint*` — historical migrations stay ### Acceptance Criteria - [ ] No "sprint" in NoteType literal - [ ] Creating a note with type "sprint" returns 422 - [ ] No sprint references in frontend dropdowns or color maps - [ ] Existing notes with type "sprint" (if any) migrated or handled ### Test Expectations - [ ] Unit test: POST /notes with type "sprint" returns validation error - Run: `pytest tests/test_note_type_enum.py` ### Constraints - One PR per repo (4 PRs total) - Check if any notes in the DB currently have type "sprint" before removing ### Checklist - [ ] PR opened - [ ] Tests pass - [ ] No unrelated changes ### Related - `project-pal-e-docs` — all repos in this project