pal-e-docs

Phase 7f-3: Template Drift Fix (Issue Migration)

phase-postgres-7f-3-template-drift Phase

Project
Goal: Fix three templates that still reference pal-e-docs issue notes after the 2026-03-02 migration to Forgejo issues-as-specs.
Owner: Betty Sue (doc work, no code)
Discovered during: Phase 8a template audit

Templates to Fix

Template Problem Fix
<code>template-pr-body</code> Related Notes section references pal-e-docs issue slugs. Changelog says issues tracked in pal-e-docs (wrong since 2026-03-02). Add Forgejo issue reference (<code>Closes org/repo #N</code>). Keep plan slug reference. Fix changelog.
<code>template-project-page</code> Issues section says "Links to issue notes" with pal-e-docs slugs. Split into Forgejo Issues (features) and Bugs (pal-e-docs notes). Update section description.
<code>template-bug</code> No mention of Forgejo issues. Ambiguous whether bugs should migrate. Add clarification: bugs stay as pal-e-docs notes. Add "When to file a Forgejo issue instead" guidance.

Design Decision

Bugs stay in pal-e-docs. They're lightweight discovery items found mid-session, not full agent-executable specs. The tag lifecycle (bug,open → bug,resolved) works. Feature/enhancement issues go to Forgejo.
  • template-issue — the 2026-03-02 migration that caused this drift
  • phase-postgres-7f-doc-cleanup-sop — parent phase