Implement CLI options

[v-Kaefer]

Add a temporary markdown file under .github that lists the current code changes for the commit, in a format you can paste into a commit message or use as a
checklist.

Key Changes

• Add .github/COMMIT_SUMMARY.md.
• Keep it human-readable and concise, with bullets for the actual changes made in this branch.
• Include the main areas changed:
  • local shell wizard flow
  • GitHub auth/PAT handling - docs updates for the new wizard flow - workflow wiring and CLI reuse where relevant
• Mark it clearly as temporary so it can be removed after the commit is made.

Test Plan

• Verify the file exists and is readable in .github.
• Verify the content reflects the current diff, not placeholder text.
• Verify it is markdown and easy to copy into a commit message or commit note.

Assumptions

• The file is a temporary helper, not a long-term repo artifact.
• Markdown is the preferred format because .github already uses markdown templates.
• The file should summarize the current branch changes, not generate an automated changelog. </proposed_plan>

Linked Issue

• Closes #

Milestone

• MS0

Summary

How to test

• Test type: automated | smoke | manual
• Steps: describe the commands, manual flow, or verification evidence

Evidence

• Screenshot/GIF attached (when applicable)
• Log/output attached (when applicable)
• Manual checklist executed (when applicable)

Known risks

DoD checklist

• Scope implemented as defined
• Tests executed and documented
• Evidence attached
• No known critical breakage introduced

[v-Kaefer]

@copilot All tests seem to be failling. Identify if they are fit for the actual codebase. And plan fixes/improvements for them.

[Copilot]

@copilot All tests seem to be failling. Identify if they are fit for the actual codebase. And plan fixes/improvements for them.

The pytest suite (9 tests) was actually passing — the red CI badges were from two unrelated gate checks, not from pytest. Root cause:

1. No pytest CI workflow existed — tests were never being run in CI at all.
2. Branch naming — copilot/clean-implementation-for-reuse didn't match the allowed prefix list.
3. PR metadata — Closes #<issue-number> was a placeholder, not a real issue reference.

Fixes in commit 0da66ad:

• Added .github/workflows/tests.yml to run pytest on every push and PR
• Fixed .github/workflows/branch-naming.yml to allow copilot/ prefix and replaced the now-removed phase prefix with milestone
• Added [dev] optional extras to pyproject.toml (pytest>=8) so the CI install is self-contained

Test improvements (9 → 16 tests):

• test_label_value_returns_none_when_no_match — surfaced that label_value returns None, not "", when there's no prefix match
• test_load_backlog_raises_when_milestones_key_missing
• test_load_labels_raises_when_color_missing
• test_load_milestones_raises_when_title_missing
• test_sync_labels_dry_run_prints_label_list
• test_sync_milestones_dry_run_prints_milestone_list
• test_issue_generation_dry_run_prints_stories_and_tasks

[v-Kaefer]

@copilot PR metadata validation, seems too strict. What can we about it.

[Copilot]

@copilot PR metadata validation, seems too strict. What can we about it.

Two changes in commit 739ff77:

1. Draft PRs skip validation — the job now runs only when github.event.pull_request.draft == false, so works-in-progress don't get blocked.

2. N/A accepted as a valid issue reference — when there genuinely isn't a linked issue, write Closes #N/A (or just #N/A) in the PR body. The template has been updated with a comment to show this option:

   - Closes #<issue-number>  <!-- use N/A if there is no linked issue: Closes #N/A -->
   

Real issue numbers (Closes #123, Fixes #42, Resolves #7) still work as before, and placeholders like Closes #<issue-number> still fail — which is intentional to prevent merged PRs with unfilled templates.