decisionlisted

Record an architecture decision as an ADR. The user will describe the decision as: $ARGUMENTS ## Steps 1. **Read the ADR index**: Read `docs/architecture/decisions/README.md` to find the next available number (look at the last row in the Index table, increment by 1). 2. **Read the template**: Read the [ADR template](adr-template.md) for the output structure. 3. **Generate the slug**: Convert the title argument to a slug (e.g., "Temporal over Celery" → "temporal-over-celery"). Lowercase, hyphens, no special characters. 4. **Gather context**: Based on the decision topic, explore the codebase to understand: - What exists today (current state) - What alternatives were considered or could be considered - What the trade-offs are 5. **Write the ADR**: Create `docs/architecture/decisions/NNNN-{slug}.md` following the template. Fill in: - **Status**: `Proposed` for new decisions (the team must accept it) - **Date**: today's date - **Context**: the problem or force that motivates the decision - **Decision**: what is being decided - **Alternatives Considered**: at least 2 alternatives with pros/cons - **Consequences**: at least 1 positive, 1 negative, and optionally neutral 6. **Update the index**: Add a new row to the Index table in `docs/architecture/decisions/README.md`. 7. **Commit**: Stage both files and commit with message: `adr: add NNNN — {Title}` 8. **Summarize**: Tell the user: - The ADR number and file path - A brief summary of what w