pal-e-docs

Phase 2: Milestone Note Type + Convention

phase-2026-03-16-2-milestone-note-type Phase

phase
Project

Phase 2: Milestone Note Type + Convention

Goal: Make milestone a first-class note_type with lifecycle statuses, create the template, and establish the "one milestone per project, one plan per milestone" convention.
Owner: Dev agent (schema change) + Betty Sue/Dottie (convention/template docs)
Repo: forgejo_admin/pal-e-docs, forgejo_admin/pal-e-docs-sdk, forgejo_admin/pal-e-docs-mcp
Depends on: None

Scope

Backend (pal-e-docs)

  • Add "milestone" to NoteType literal in routes/notes.py
  • Add VALID_STATUSES entry: "milestone": ["not-started", "active", "completed"]

SDK + MCP

  • Update SDK note_type docstrings to include "milestone"
  • Update MCP tool descriptions to include "milestone"

Conventions (pal-e-agency docs)

  • Create template-milestone note
  • Update template-plan — add guidance that plans should have a milestone parent
  • Update template-project-page — milestones as primary organizer
  • Create or update convention: "One active milestone per project, one plan per milestone"

Deliverables

  • Backend: PR #187 merged — added "milestone" to NoteType + VALID_STATUSES (schemas.py, routes/notes.py). 577 tests pass.
  • Convention: template-milestone created in pal-e-agency.
  • Remaining: SDK + MCP docstring updates, template-plan and template-project-page convention updates still pending.
  • plan-2026-03-16-knowledge-architecture — parent plan
  • milestone-2026-03-16-knowledge-architecture — this milestone is the first dogfood (created as doc type, will be upgraded to milestone type)
  • template-plan — will be updated
  • template-project-page — will be updated