Fix ambiguous GraphQL variable placeholder in mutation template

[Copilot]

The mutation template in enum-02-editable-chip.md used ${enumFieldName} for GraphQL variable references, which is visually ambiguous — it reads like a JS template literal where the entire ${enumFieldName} token gets replaced by status, dropping the $ prefix and producing invalid GraphQL.

Change

• enum-02-editable-chip.md: Changed ${enumFieldName} → {$enumFieldName} in both the variable declaration and input reference of the mutation template

The {$enumFieldName} placeholder follows the file's existing {placeholder} convention with $ embedded, making it unambiguous that the expansion includes the GraphQL variable prefix:

# Before (ambiguous — ${...} looks like a single replaceable token)
mutation Update{EntityName}{EnumName}($id: ID!, ${enumFieldName}: {EnumName}!) {
    {updateMutation}(id: $id, input: { {enumFieldName}: ${enumFieldName} }) {

# After (clear — {$enumFieldName} expands to $status, {enumFieldName} expands to status)
mutation Update{EntityName}{EnumName}($id: ID!, {$enumFieldName}: {EnumName}!) {
    {updateMutation}(id: $id, input: { {enumFieldName}: {$enumFieldName} }) {

This matches the concrete example already present in the file ($status: LocationStatus! / input: { status: $status }).

---

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.