Add individually tracked P0-X subtask issues with milestone + board automation

[Copilot]

Issue #56 bundled P0-X1 through P0-X7 as an untracked checklist with no individual visibility, milestone assignment, or board presence. The non-functional project_board.json file added noise without doing anything.

Changes

create-p0x-subtasks.yml (new)

One-shot workflow_dispatch that creates P0-X1–P0-X7 as individual issues. Each issue carries focused exit-criteria, appropriate layer: labels, P0: critical, milestone lookup, and a Part of #56 parent reference. Idempotent — re-runs skip already-existing titles (PRs are excluded from the title-collision check). Summary comment on #56 only mentions the milestone when it was actually assigned. Supports dry_run input.

enforce-milestone.yml (new)

Fires on issues.opened / issues.labeled. Maps priority label → milestone and assigns it if the issue has none:

Label	Milestone
P0: critical	v0.1 — Minimal Viable
P1: high	v0.5 — Alpha
P2: medium / P3: low	v1.0 — Production

project-board-automation.yml (new)

Fires on issues.opened / pull_request.opened. Uses actions/add-to-project@v1 to auto-add items to the Projects v2 board. Gated by both vars.PROJECT_URL and secrets.PROJECT_TOKEN; fork PRs are excluded (no secrets available). No-op until the operator configures both.

project_board.json (deleted)

Static JSON that defined a board structure but had no execution path. Replaced by real automation.

close-legacy-issues.yml (deleted)

Removed from this branch — the file was deleted from main as an information hazard. This branch now matches main on that file and the PR merges cleanly.

Original prompt

Turn 'P0-X1 to P0-X7 subtasks listed in Issue #56 (#56) into individually tracked enforce linkage to GitHub board + milestones+ automation endpoints

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: Looking at the issues and my docs, I feel like I'm not leveraging GitHub properly.

The issues should form a tree or a bush. Instead we have things like Task 1 which encompasses Tasks 2..10 competing with Tasks 2..10 and causing merge conflicts.

I'm growing .md files faster than I'm developing code. I have a DESIGN.md a PLAN.md and a TODO.md and I feel like they're duplicating features that GitHub offers and doing a poor job of it and I'm losing accountability in the process.

What can be done? What GitHub features as I either not using, or not using properly, that would help me take the beast?

Assistant: It sounds like you've built an excellent foundation of organization using markdown files (DESIGN.md, PLAN.md, TODO.md), but you could possibly streamline your workflow by using GitHub's built-in features. Let’s explore some improvements based on your points:

---

1. Overlapping Issues and Merge Conflicts

Challenge:

• Issues like "Task 1" are overarching but lead to merge conflicts when parts of them (e.g., Tasks 2–10) are broken into sub-tasks.
• Sub-tasks are competing on the same level in your issue tracking system.

Solution: Organize Projects and Issues Effectively

• Use Issue Hierarchies: Convert overarching tasks like "Task 1" into an Epic Issue. Within it, detail the smaller actionable tasks (Tasks 2–10) as checklist items in the description. For long-term organization:

  • Use issue linking (mark smaller tasks as Linked Issues) to ensure you can track dependencies and progress.
  • Use Milestones to group issues based on phases or sprints.

• Breaking Branches Properly: Divide work into feature-specific branches (e.g., feature/task-2) rather than having overlapping branches. During Conflict Fixing, consider rebasing branches regularly to avoid growing divergence.

Relevant GitHub Features:

• Issue Checklists: Add tasks in markdown checkboxes in the issue description.
• GitHub Projects/Taskboards:
  • Set up a project board for your repository.
  • Use the Kanban layout to map lifecycle stages (To Do, Doing, Done).
• Draft Pull Requests: Open pull requests early for visibility during development.

---

2. Markdown Files vs GitHub Collaboration Tools

Challenge:

• Files like DESIGN.md, PLAN.md, and TODO.md duplicate project management features.
• .md files may fall out of sync or clutter the repo, making accountability difficult.

Solution: Replace Markdown Files with Centralized Features

• Replace PLAN.md and TODO.md with GitHub Projects:
  • Convert to-do items into tasks (issues). Move prioritization to GitHub Projects.
  • Track them in an interactive board where you can reorder/assign easily.
• Keep DESIGN.md as Proper Documentation:
  • Keep this file updated for your source-of-truth architecture, but consider moving more dynamic or front-end-facing details to a README.md or GitHub Wiki.

Relevant GitHub Features:

• GitHub Issues as Tasks: Replace ad-hoc .md files with GitHub Issues for collaborative and accountable task-tracking.
• Task Assignments and Labels: Use assignees for accountability and labels to classify (e.g., bug, enhancement, priority: high).

---

3. Scalability and Feature Overlap

Challenge:

• Growing complexity is making it hard to manage overlapping tasks, dependencies, and progress while ensuring team coordination.

Solution: Adopt GitHub Automation Where Possible

• Automate with GitHub Actions: Set up workflows to automate repetitive tasks (e.g., auto-labeling, CI/CD pipelines, etc.).
• Leverage Branch Protection Rules: Use branch protection to enforce proper reviews and avoid improperly merged code.
• External Tools: Use tools like ZenHub or Codetree to add additional layers of organization and dependencies, but only once you’ve hit GitHub's limits.

Relevant GitHub Features:

• Code Review Process/Protection: Standardize code reviews and require status checks prior to merging.
• Dependabot: Use to automate dependency updates.

---

Summary of Suggestions

High-Level Focus Areas:

1. Replace .md files for project management (e.g., PLAN.md, TODO.md) with GitHub Issues and Projects.
2. Organize and link issues hierarchically to eliminate conflict between overarching and dependent tasks.
3. Automate workflows and enforce process consistency with GitHub Actions and branch protection.

Would you like additional details or help setting up any specific parts (e.g., projects, workflows, or automations)?

User: ...

This pull request was created from Copilot chat.

---

📱 Kick off Copilot coding agent tasks wherever you are with GitHub Mobile, available on iOS and Android.

[Copilot]

Pull request overview

This PR replaces a non-functional project_board.json board definition with GitHub-native automation to (1) create individually tracked P0‑X subtask issues for #56, (2) auto-assign milestones based on priority labels, and (3) auto-add new issues/PRs to a Projects v2 board when configured.

Changes:

• Added a manual workflow to create P0‑X1…P0‑X7 as individual issues linked to parent #56 (with optional dry_run).
• Added an issue workflow to assign milestones based on P0–P3 priority labels when an issue has no milestone.
• Added a workflow to auto-add newly opened issues/PRs to a Projects v2 board (gated by repo variable), and removed the unused project_board.json.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
.github/workflows/create-p0x-subtasks.yml	One-shot issue factory for P0‑X1…P0‑X7 linked to #56, with label + milestone lookup logic.
.github/workflows/enforce-milestone.yml	Assigns milestones on issue open/label based on priority label mapping.
.github/workflows/project-board-automation.yml	Adds newly opened issues/PRs to a Projects v2 board when configured via repo var/secret.
.github/workflows/close-legacy-issues.yml	Removes #56 from the “legacy issues” close list (keeps it as live parent tracker).
project_board.json	Deleted unused static board definition file.

[devlux76]

@copilot I removed close-legacy-issues.yml from main, it's an information hazard. Now this PR won't merge, please rebase from head main and leave close-legacy-issues.yml out of the merge,

[Copilot]

@copilot I removed close-legacy-issues.yml from main, it's an information hazard. Now this PR won't merge, please rebase from head main and leave close-legacy-issues.yml out of the merge,

Done. close-legacy-issues.yml is deleted from the branch in commit 9ef492c. The PR now only contains the three new automation workflows (create-p0x-subtasks.yml, enforce-milestone.yml, project-board-automation.yml) and the removal of project_board.json — no conflict with main.