wp-scaffoldlisted

# WP Scaffold Single skill, four sub-modes. Picks the right `scaffold_*` tool, scopes destination paths, refuses destructive overwrites, surfaces every file written so the user can review or roll back. ## Iron Rule <EXTREMELY-IMPORTANT> 1. NEVER scaffold without `allow_destructive: true` — the flag is mandatory because file_write is irreversible at REST scale; the explicit ask forces user awareness. 2. NEVER scaffold into an existing slug without first checking it does not exist (`file_read` the bootstrap path, expect 404) — a hidden overwrite into an active plugin breaks the live site. 3. ALWAYS surface every absolute path written + every backup file created — the only reliable rollback is to restore the `.wplab-bak-...` siblings or `rm -rf` the slug dir. </EXTREMELY-IMPORTANT> ## When to use - "Create a plugin called X with a REST endpoint." - "Scaffold a new Gutenberg block called testimonial-card." - "Build a starter block-theme called my-theme." - "Register a block pattern called hero-with-cta." Skip when: - User wants to EDIT an existing block/plugin/theme → `wp-content` (post editing), `wp-edit-design` (layout), or direct `file_write`. - User wants to install a plugin from wordpress.org → use core REST `wp/v2/plugins` POST (covered by `wp-content`). ## Boundary Owns: - `rolepod_wp_scaffold_block` — block.json + index.js + render.php (dynamic) OR save() (static) + style.css. - `rolepod_wp_scaffold_plugin` — plugin bootstrap PHP + admin page + REST stub + CLI com