Manage a design system in Paper

1. Read paper-ds.json and references/versioning.md. Check the target Paper file with paper-ds-canvas. If there is no manifest, use paper-ds-setup; do not restart setup for an existing system.
2. Identify the subject and the decision. Read its source, actual content and states, existing Paper nodes, Foundations guidance, and revision record. Prefer the user's named nodes over a generic component lookup.
3. Route the request using the table below. Continue through the requested work, not every stage of the lifecycle.
4. Before changing artwork, read it back. The user may have edited it since the last round. Checkpoint those edits and preserve them as the starting point.
5. At the end, report what changed, its revision, verification evidence, and what remains unapproved or unimplemented. Keep critique in chat, not on the sheet.