# aaronrene — component dev work queue

## Purpose

Master tracker for tickets handed off to **aaronrene** (component dev,
`write` collaborator on `gabriel/musehub`). Every ticket assigned to him
should be linked here as a child, in the order he's expected to pick them
up. This issue doesn't contain implementation detail itself — each child
issue is fully specced on its own; this is just the queue + a single place
to see his overall assignment load and sequencing.

## Why a queue instead of assigning everything at once

Most of the backlog below is already thoroughly specced (phases, ASCII
mockups, acceptance criteria) and safe to hand off outright — aaronrene has
already shown he can pick up a fully-specced ticket and deliver
(musehub#84's two-column scroll fix, reviewed and shipped this cycle,
plus the proposal-permissions bug he surfaced organically). The queue exists
so we hand off one (or a small batch) at a time instead of dumping the
entire backlog on him — easier to review, easier to reprioritize if
something more urgent lands.

## Active

- [ ] #129 — Rich social preview cards for repo links (no dynamic OG image
      today). Assigned. See that issue for full phase breakdown
      (design → implement `/opengraph-image` endpoint → wire into repo
      pages + verify on a real platform debugger).

## Candidate follow-ups (not yet assigned)

Not committed yet — listed here so the next hand-off doesn't require
re-triaging the backlog from scratch. All are GUI-heavy, already have
detailed specs (several with ASCII layout mockups), and don't require deep
familiarity with Muse's core VCS internals:

- #24 — Symbol Detail Page — God-Tier Redesign
- #25 — Symbols Page v2 — Symbol-First Intelligence Browser
- #32 — Releases List: Version History Mission Control
- #33 — Release Page: Semantic Version Observatory
- #34 — Issues List: Codebase Intelligence Mission Control

## Handoff convention

- One child ticket assigned at a time (or a tightly related small batch),
  not the whole candidate list.
- Each child ticket must already have: background/root-cause, explicit
  goal, phase breakdown, and acceptance criteria before being assigned —
  if a candidate isn't at that bar yet, spec it further here first.
- When a child ticket ships, check it off here and note the shipping
  commit/proposal.