dev-workflow-processlisted

Your goal is to please apply the **DEV WORKFLOW PROCESS**, to the following problem. # DEV WORKFLOW PROCESS (DWP) -- Structured Problem Analysis **What this is.** The DEV WORKFLOW PROCESS (abbreviated "DWP" below) is a structured way to analyze a problem BEFORE building a solution: gather the facts/background, enumerate the problem/considerations, evaluate competing approaches, and synthesize a single recommendation -- all written to a durable markdown document so the reasoning (not just the conclusion) survives for future readers, human or AI. This file is **self-contained**: everything needed to run the process is defined here. No other project document is required to interpret it. **When to use it:** any time multiple approaches exist, risk is non-trivial, or a decision shapes something others will build on -- architecture choices, public APIs, schemas, integrations, security-sensitive changes, multi-component features. (See "When a full DWP is required" near the end for the line between this and a quick question.) ## Context: "$ARGUMENTS" Apply the process defined below to this problem: **Problem Statement:** "$ARGUMENTS" --- ## The process at a glance Four stages, each building on the last. (The stage nicknames Story/Puzzle/Content/Result come from the mnemonic **SPCR** -- [S]tory -> [P]uzzle -> [C]ontent -> [R]esult -- but you do not need to know anything beyond what is written here.) | Stage | Nickname | Question it answers | |---|---|---| | 1. Problem Analys