#220 - Feature: Convention updates — cross-repo boards, architecture IDs, Capacitor stages - forgejo_admin/pal-e-platform

### 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 via MCP tools) ### User Story As Betty Sue I want existing convention and SOP notes updated with cross-repo board patterns, new architecture IDs, and expanded Capacitor lifecycle stages So that the conventions reflect proven patterns from the Capacitor pipeline dogfood ### Context The Capacitor pipeline session (2026-03-26) proved that cross-repo pipeline boards work with `consumer:X` labels, that Tailscale subnet routing is an architecture component worth tracking, and that the Capacitor mobile lifecycle needs iOS build pipeline and App Store submission stages. These updates formalize what was learned. ### File Targets pal-e-docs notes to update (via MCP tools, not file edits): 1. **`convention-kanban-over-plans`** — add "Cross-Repo Pipeline Boards" section documenting the pattern, document `consumer:X` label convention for cross-repo board items 2. **`convention-architecture-ids`** — add `arch:tailscale-subnet` component entry 3. **`sop-capacitor-mobile-lifecycle`** — add Stage 5 (iOS Build Pipeline) and Stage 6 (App Store Submission) with Gates 3-5 ### Acceptance Criteria - [ ] `convention-kanban-over-plans` contains a "Cross-Repo Pipeline Boards" section - [ ] `consumer:X` label pattern documented in the cross-repo boards section - [ ] `convention-architecture-ids` contains `arch:tailscale-subnet` entry - [ ] `sop-capacitor-mobile-lifecycle` contains Stage 5 (iOS Build Pipeline) with gate criteria - [ ] `sop-capacitor-mobile-lifecycle` contains Stage 6 (App Store Submission) with gate criteria ### Test Expectations - [ ] `convention-kanban-over-plans` has a heading matching "Cross-Repo Pipeline Boards" - [ ] `convention-kanban-over-plans` mentions `consumer:X` label pattern - [ ] `convention-architecture-ids` includes `arch:tailscale-subnet` - [ ] `sop-capacitor-mobile-lifecycle` includes Stage 5 and Stage 6 headings with Gates 3-5 ### Constraints - These are pal-e-docs note updates via MCP tools, not code changes - Additive changes only — don't restructure existing content - Must stay within the 3-target threshold for this sub-ticket - Follow existing section formatting in each note ### Checklist - [ ] `convention-kanban-over-plans` updated with cross-repo section - [ ] `convention-architecture-ids` updated with tailscale-subnet - [ ] `sop-capacitor-mobile-lifecycle` expanded with Stages 5-6 - [ ] Changes verified via `get_note` after update - [ ] No contradictions introduced with other convention notes ### Related - Parent: `forgejo_admin/pal-e-platform#183` - `project-capacitor-mobile` — dogfood source for these conventions - `feedback_pipeline_stages_not_phases.md` — behavioral memory confirming "stages" naming

forgejo_admin commented

2026-03-28 11:37:20 +00:00

Owner

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 via MCP tools)

User Story

As Betty Sue
I want existing convention and SOP notes updated with cross-repo board patterns, new architecture IDs, and expanded Capacitor lifecycle stages
So that the conventions reflect proven patterns from the Capacitor pipeline dogfood

Context

The Capacitor pipeline session (2026-03-26) proved that cross-repo pipeline boards work with consumer:X labels, that Tailscale subnet routing is an architecture component worth tracking, and that the Capacitor mobile lifecycle needs iOS build pipeline and App Store submission stages. These updates formalize what was learned.

File Targets

pal-e-docs notes to update (via MCP tools, not file edits):

convention-kanban-over-plans — add "Cross-Repo Pipeline Boards" section documenting the pattern, document consumer:X label convention for cross-repo board items
convention-architecture-ids — add arch:tailscale-subnet component entry
sop-capacitor-mobile-lifecycle — add Stage 5 (iOS Build Pipeline) and Stage 6 (App Store Submission) with Gates 3-5

Acceptance Criteria

convention-kanban-over-plans contains a "Cross-Repo Pipeline Boards" section
consumer:X label pattern documented in the cross-repo boards section
convention-architecture-ids contains arch:tailscale-subnet entry
sop-capacitor-mobile-lifecycle contains Stage 5 (iOS Build Pipeline) with gate criteria
sop-capacitor-mobile-lifecycle contains Stage 6 (App Store Submission) with gate criteria

Test Expectations

convention-kanban-over-plans has a heading matching "Cross-Repo Pipeline Boards"
convention-kanban-over-plans mentions consumer:X label pattern
convention-architecture-ids includes arch:tailscale-subnet
sop-capacitor-mobile-lifecycle includes Stage 5 and Stage 6 headings with Gates 3-5

Constraints

These are pal-e-docs note updates via MCP tools, not code changes
Additive changes only — don't restructure existing content
Must stay within the 3-target threshold for this sub-ticket
Follow existing section formatting in each note

Checklist

convention-kanban-over-plans updated with cross-repo section
convention-architecture-ids updated with tailscale-subnet
sop-capacitor-mobile-lifecycle expanded with Stages 5-6
Changes verified via get_note after update
No contradictions introduced with other convention notes

Parent: forgejo_admin/pal-e-platform#183
project-capacitor-mobile — dogfood source for these conventions
feedback_pipeline_stages_not_phases.md — behavioral memory confirming "stages" naming