Feature: New conventions — pipeline-stages, blocker-labels, and label table updates #221

Open
opened 2026-03-28 11:37:35 +00:00 by forgejo_admin · 0 comments

Type

Feature

Lineage

Child of forgejo_admin/pal-e-platform#183 (Convention updates — kanban alignment from Capacitor dogfood)

Repo

forgejo_admin/pal-e-platform (tracked here; changes are pal-e-docs note edits and new note creation via MCP tools)

User Story

As Betty Sue
I want new convention notes for pipeline stages and blocker labels, plus updated label tables in the ticket template
So that the full vocabulary from the Capacitor pipeline dogfood is documented and discoverable

Context

The Capacitor pipeline session (2026-03-26) established two new patterns that need their own convention notes: the 4-stage pipeline model (Playground, Svelte Sandbox, App, App Store) and the blocker label taxonomy (blocker:external, blocker:internal). Additionally, the template-ticket Label Conventions table needs consumer:X and blocker:X rows added.

File Targets

pal-e-docs changes (via MCP tools, not file edits):

  1. NEW: convention-pipeline-stages — create new convention note documenting:
    • The 4 pipeline stages: Playground, Svelte Sandbox, App, App Store
    • Naming convention: {project}-playground, {project}-svelte-playground, {project}-app, {project}-api
    • Use "stages" not "phases" (per feedback_pipeline_stages_not_phases.md)
  2. NEW: convention-blocker-labels — create new convention note documenting:
    • blocker:external — blocked by external dependency (vendor, upstream, third-party)
    • blocker:internal — blocked by internal dependency (another ticket, deploy order, review)
  3. template-ticket — add consumer:X and blocker:X rows to the Label Conventions table

Acceptance Criteria

  • convention-pipeline-stages note exists with all 4 stage names
  • convention-pipeline-stages documents the {project}-* naming convention
  • convention-pipeline-stages uses "stages" terminology, not "phases"
  • convention-blocker-labels note exists with blocker:external and blocker:internal definitions
  • template-ticket Label Conventions table includes a row for consumer:X
  • template-ticket Label Conventions table includes a row for blocker:X

Test Expectations

  • convention-pipeline-stages note retrievable via get_note(slug="convention-pipeline-stages")
  • convention-pipeline-stages contains all 4 stage names: Playground, Svelte Sandbox, App, App Store
  • convention-blocker-labels note retrievable via get_note(slug="convention-blocker-labels")
  • convention-blocker-labels defines both blocker:external and blocker:internal
  • template-ticket Label Conventions table has consumer:X and blocker:X rows

Constraints

  • These are pal-e-docs note updates and creations via MCP tools, not code changes
  • New notes should follow existing convention note structure (check convention-kanban-over-plans for format reference)
  • Must stay within the 2-new-notes + 1-table-update threshold for this sub-ticket
  • Tag new notes with convention tag for discoverability

Checklist

  • convention-pipeline-stages note created with proper structure
  • convention-blocker-labels note created with proper structure
  • template-ticket Label Conventions table updated with new rows
  • All new notes tagged with convention
  • Changes verified via get_note after creation/update
  • No contradictions introduced with other convention notes
  • Parent: forgejo_admin/pal-e-platform#183
  • feedback_pipeline_stages_not_phases.md — behavioral memory confirming "stages" naming
  • project_pipeline_naming_convention.md — behavioral memory confirming {project}-* naming
  • convention-kanban-over-plans — sibling convention (updated in sub-ticket 2)
### Type Feature ### Lineage Child of `forgejo_admin/pal-e-platform#183` (Convention updates — kanban alignment from Capacitor dogfood) ### Repo `forgejo_admin/pal-e-platform` (tracked here; changes are pal-e-docs note edits and new note creation via MCP tools) ### User Story As Betty Sue I want new convention notes for pipeline stages and blocker labels, plus updated label tables in the ticket template So that the full vocabulary from the Capacitor pipeline dogfood is documented and discoverable ### Context The Capacitor pipeline session (2026-03-26) established two new patterns that need their own convention notes: the 4-stage pipeline model (Playground, Svelte Sandbox, App, App Store) and the blocker label taxonomy (blocker:external, blocker:internal). Additionally, the `template-ticket` Label Conventions table needs `consumer:X` and `blocker:X` rows added. ### File Targets pal-e-docs changes (via MCP tools, not file edits): 1. **NEW: `convention-pipeline-stages`** — create new convention note documenting: - The 4 pipeline stages: Playground, Svelte Sandbox, App, App Store - Naming convention: `{project}-playground`, `{project}-svelte-playground`, `{project}-app`, `{project}-api` - Use "stages" not "phases" (per `feedback_pipeline_stages_not_phases.md`) 2. **NEW: `convention-blocker-labels`** — create new convention note documenting: - `blocker:external` — blocked by external dependency (vendor, upstream, third-party) - `blocker:internal` — blocked by internal dependency (another ticket, deploy order, review) 3. **`template-ticket`** — add `consumer:X` and `blocker:X` rows to the Label Conventions table ### Acceptance Criteria - [ ] `convention-pipeline-stages` note exists with all 4 stage names - [ ] `convention-pipeline-stages` documents the `{project}-*` naming convention - [ ] `convention-pipeline-stages` uses "stages" terminology, not "phases" - [ ] `convention-blocker-labels` note exists with `blocker:external` and `blocker:internal` definitions - [ ] `template-ticket` Label Conventions table includes a row for `consumer:X` - [ ] `template-ticket` Label Conventions table includes a row for `blocker:X` ### Test Expectations - [ ] `convention-pipeline-stages` note retrievable via `get_note(slug="convention-pipeline-stages")` - [ ] `convention-pipeline-stages` contains all 4 stage names: Playground, Svelte Sandbox, App, App Store - [ ] `convention-blocker-labels` note retrievable via `get_note(slug="convention-blocker-labels")` - [ ] `convention-blocker-labels` defines both `blocker:external` and `blocker:internal` - [ ] `template-ticket` Label Conventions table has `consumer:X` and `blocker:X` rows ### Constraints - These are pal-e-docs note updates and creations via MCP tools, not code changes - New notes should follow existing convention note structure (check `convention-kanban-over-plans` for format reference) - Must stay within the 2-new-notes + 1-table-update threshold for this sub-ticket - Tag new notes with `convention` tag for discoverability ### Checklist - [ ] `convention-pipeline-stages` note created with proper structure - [ ] `convention-blocker-labels` note created with proper structure - [ ] `template-ticket` Label Conventions table updated with new rows - [ ] All new notes tagged with `convention` - [ ] Changes verified via `get_note` after creation/update - [ ] No contradictions introduced with other convention notes ### Related - Parent: `forgejo_admin/pal-e-platform#183` - `feedback_pipeline_stages_not_phases.md` — behavioral memory confirming "stages" naming - `project_pipeline_naming_convention.md` — behavioral memory confirming `{project}-*` naming - `convention-kanban-over-plans` — sibling convention (updated in sub-ticket 2)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo_admin/pal-e-platform#221
No description provided.