# Refactor Queue Contract

`<분석 대상 저장소>/refactor-queue.yaml` is the ordering SSOT for bounded refactoring work.

## Responsibility split

- Queue: order, active item, summary state.
- `docs/<프로젝트>/refactor/<project>/<item>/work-item.json`: detailed problem, goal, type, scope, acceptance criteria, evidence references.

## Selection

1. Ignore items whose analysis snapshot is no longer `COMPLETE`, revision-current, and clean.
2. Among actionable `READY` items, lower priority number wins: `P0` → `P1` → `P2` → `P3`.
3. For equal priority, file order wins.
4. At most one WorkItem is active. Do not start another while the active item is baselining, changing source, verifying, or waiting for approval.
5. One scheduled execution works on at most one bounded item.

## Summary entry shape

```yaml
- project: backend-clean-architecture
  id: RF-001
  priority: P1
  status: READY
  detail: docs/<프로젝트>/refactor/backend-clean-architecture/RF-001/work-item.json
```

The queue does not duplicate detailed analysis or evidence. If queue summary and `work-item.json` disagree, stop and reconcile instead of guessing.