Add branding assets and PR lifecycle agent prompt

[cmeans]

Summary

• Add Dev role branding logos in three sizes (40px, 128px, 256px) under branding/
• Add prompts/pr-lifecycle-agent.md -- a dispatch template for managing the full PR lifecycle (CI polling, Codecov detail checks, label transitions, sequential queue rebasing)

Test plan

• Verify logo images render correctly on GitHub
• Review PR lifecycle agent template for accuracy

🤖 Generated with Claude Code

[cmeans]

QA Review — PR #2 (cmeans/claude-dev)

Informal review — this repo doesn't have the QA workflow, so no labels.

Branding (3 logos)

All three PNGs render correctly on GitHub. Code brackets on a shield, dark background with cyan accent. Clean design.

• 256px — crisp, all details sharp ✓
• 128px — clean at display size ✓
• 40px — legible, brackets still recognizable at favicon/badge size ✓

PR Lifecycle Agent Prompt

Well-structured 4-phase template. A few observations:

Strengths:

• Phase 1 CI polling correctly excludes QA Gate from the "pending" check — smart, since QA Gate stays pending until QA Approved
• "Do NOT use gh pr checks --watch" — good warning, that would block forever
• Phase 2 Codecov comment check (not just status) — catches the common trap of "codecov passed but patch coverage has gaps"
• Phase 4 rebase uses --force-with-lease — safe force push ✓
• "Important" rules are exactly right: never merge, never fix failures, never skip codecov detail, report-and-stop on unexpected

Observations (not blockers — this is a personal tools repo):

1. Phase 4 assumes a local clone exists. git checkout {{NEXT_BRANCH}} won't work if the agent was dispatched in a clean environment. Could add a git fetch origin {{NEXT_BRANCH}} before checkout, or note "assumes worktree context" in the docs.

2. {{#if NEXT_PR}} / {{/if}} Handlebars syntax won't be evaluated — the user manually pastes the template. Consider a note like "Remove Phase 4 if no NEXT_PR" or split into two templates (single PR vs queued).

3. notify-send + paplay are Linux-specific. Fine for your setup, but if you ever share this prompt, a note about platform would help.

4. Phase 1 step 2 edge case: If checks haven't started yet (e.g., GitHub is slow), the grep returns empty — same as "all passed." Could add a "checks found" guard: if gh pr checks returns no lines at all, wait before declaring success.

None of these are blockers — the template is practical and well-thought-out. It automates exactly the tedious parts of the PR lifecycle while keeping the human/QA in the loop for decisions.

Verdict

Looks good. Ship it.