Enhance GitHub Project Plan with new labels, board columns, and maint…

docs/GITHUB_PROJECT_PLAN.md

@@ -1,10 +1,23 @@
 # GitHub Project Organization Plan
 
 ## Labels
+
+### Core Classification
 - `type:bug`, `type:feature`, `type:task`, `type:docs`, `type:security`
 - `priority:P0`, `priority:P1`, `priority:P2`
 - `difficulty:beginner`, `difficulty:intermediate`, `difficulty:advanced`
+- `size:S`, `size:M`, `size:L`, `size:XL`
+
+### Status & Workflow
 - `status:blocked`, `status:needs-design`, `status:ready`
+- `status:in-review`, `status:done`
+
+### Wave 5 Specifics
+- `wave:5`
+- `phase:1` through `phase:7`
+- `track:FE`, `track:BE`, `track:SC`, `track:SDK`, `track:DEVOPS`, `track:QA`, `track:SECURITY`, `track:DX`, `track:DOCS`, `track:AI/AUTOMATION`
+
+### Areas (Legacy/Legacy Mapping)
 - `area:frontend`, `area:backend`, `area:onchain`, `area:devex`, `area:docs`
 - `stellar:migration`, `drips:wave`
 
@@ -14,12 +27,47 @@
 3. `M3 - Stellar Wallet Integration`
 4. `M4 - Drips/Wave Contributor Expansion`
 
-## Board Columns
-- Backlog
-- Ready
-- In Progress
-- In Review
-- Done
+## Board Columns & Lane Definitions
+
+| Column | Purpose | Entry Criteria | Exit Criteria |
+| :--- | :--- | :--- | :--- |
+| **Inbox (Triage)** | New incoming issues. | Issue created; missing core labels. | Labeled with `track`, `difficulty`, `size`, `phase`, `priority`. |
+| **Backlog** | Validated and scoped tasks. | Core labels present; `status:ready` or `status:blocked`. | Moved to **Ready** when prioritized for active Milestone. |
+| **Ready** | Available for contributors. | `status:ready`; part of active Milestone. | Contributor assigned. |
+| **In Progress** | Active development. | Assigned to contributor. | PR submitted and linked to issue. |
+| **In Review** | Peer review and CI validation. | PR submitted; CI passing. | PR approved and merged. |
+| **Done** | Completed work. | PR merged; issue closed. | N/A |
+
+## Track-Based Routing Rules
+
+Issues are categorized by **Track** to balance reviewer load and contributor specialty.
+
+| Track | Primary Labels | Board Routing / Focus |
+| :--- | :--- | :--- |
+| **Core Migration** | `track:SC`, `track:BE` | High-priority; gated by migration milestones. |
+| **Integration** | `track:SDK`, `track:FE` | Focused on ergonomics and wallet-contract interfaces. |
+| **Stability/Ops** | `track:QA`, `track:DEVOPS` | Continuous support; unblocks other tracks. |
+| **DevEx/Docs** | `track:DX`, `track:DOCS` | High-velocity "Easy Wins" for new contributors. |
+| **Automation** | `track:AI/AUTOMATION` | Workflow and triage optimization. |
+
+### Routing by Difficulty & Size
+- **Beginner (S/M)**: Routed to **Ready** queue immediately for new contributors.
+- **Intermediate (M/L)**: Standard track for experienced contributors.
+- **Advanced (L/XL)**: Requires maintainer synchronization before assignment.
+
+## Maintainer Triage Routine
+
+To reduce triage latency and ensure consistent issue quality, maintainers follow this routine 2x per week:
+
+1. **Scan Inbox**: Review all issues in the **Inbox (Triage)** column.
+2. **Assign Track**: Apply the most relevant `track:*` label.
+3. **Assess Difficulty/Size**: Estimate impact and complexity based on [WAVE5_ISSUE_TRACKS.md](./wave/WAVE5_ISSUE_TRACKS.md).
+4. **Map to Phase**: Assign the issue to the current or future `phase:*` Milestone.
+5. **Set Status**: 
+   - Apply `status:ready` if the objective, scope, and acceptance criteria are clear.
+   - Apply `status:blocked` if external dependencies or design decisions are pending.
+6. **Promote**: Move to **Backlog** or **Ready** (if prioritized).
+7. **Clean Up**: Ensure every issue has a clear "Acceptance Criteria" checklist before it reaches the **Ready** column.
 
 ## Prioritization Rules
 - P0: security, broken builds, data integrity

docs/wave/REVIEWER_PLAYBOOK.md

@@ -128,5 +128,6 @@ Run this at each 2×/week triage session:
 ## Related Docs
 - [Wave 5 Issue Tracks](./WAVE5_ISSUE_TRACKS.md)
 - [Wave 5 Execution Plan](./WAVE5_EXECUTION_PLAN.md)
+- [GitHub Project Board Plan](../GITHUB_PROJECT_PLAN.md)
 - [GitHub Strategy](../SOROBAN_GITHUB_STRATEGY.md)
 - [PR Review Template](./../.github/PULL_REQUEST_TEMPLATE.md) *(if present)*

docs/wave/WAVE5_EXECUTION_PLAN.md

@@ -44,8 +44,9 @@ This document orchestrates contributor operations and governance while delegatin
 - Operational docs aligned with current branch and milestone state.
 
 ## Maintainer Workflow Expectations
-- Triage issues at least 2x/week.
-- Validate scope and dependencies before labeling `wave:ready`.
+- Triage issues at least 2x/week following the [Maintainer Triage Routine](../GITHUB_PROJECT_PLAN.md#maintainer-triage-routine).
+- Validate scope and dependencies before labeling `wave:ready` and moving to the **Ready** lane.
+- Enforce track-based routing as defined in the [Project Board Plan](../GITHUB_PROJECT_PLAN.md#track-based-routing-rules).
 - Enforce single-track PR scope unless explicitly marked cross-track.
 - Keep milestone burndown visible and updated weekly.
 - Publish weekly Wave status note: completed, blocked, reprioritized.

docs/wave/WAVE5_ISSUE_TRACKS.md

@@ -89,3 +89,4 @@ Reviewers must validate:
 ## Operational Mapping
 - Phase mapping: see [WAVE5_PHASES](./WAVE5_PHASES.md)
 - Execution governance: see [WAVE5_EXECUTION_PLAN](./WAVE5_EXECUTION_PLAN.md)
+- Triage and Board Lanes: see [GITHUB_PROJECT_PLAN](../GITHUB_PROJECT_PLAN.md)