feat(api-playground): Deploy saves the loaded document into the specs folder (PUT /api/specs/{filename}, confirm before overwrite); the folder's demo.yaml replaces the example; labels Specs, MiniGraph, Browse; api.playground.specs

[acn-ericlaw]

What

• PUT /api/specs/{filename} (DeploySwaggerFile): writes the text body into the specs folder, 409 for an existing name unless ?overwrite=true, 400 for a bad name or empty body. SpecFiles reads the folder before the bundled example; the property is renamed api.playground.specs.
• The page: Specs, MiniGraph and Browse labels; a Deploy button with a suggested name, a prompt and a confirm on 409; the Specs list refreshes after a deploy.
• The example document documents the PUT operation; README, the graph contract guide and CHANGELOG items 3 and 4 updated.

Why

Eric’s review of the MiniGraph integration: the loaded document should be one click from being served by the playground itself, under names and labels that say what they are, and a same-named file must never be replaced without asking.

🤖 Generated with Claude Code