chore: commit all staged changes (2025-12-19)

Author: ashleyshaw

.babelrc.json

@@ -1,3 +1,3 @@
 {
-	"presets": [ "@wordpress/babel-preset-default" ]
+	"presets": ["@wordpress/babel-preset-default"]
 }

.devcontainer/devcontainer.json

@@ -34,8 +34,8 @@
 				"[php]": {
 					"editor.defaultFormatter": "bmewburn.vscode-intelephense-client"
 				},
-				"eslint.validate": [ "javascript", "javascriptreact" ],
-				"stylelint.validate": [ "css", "scss", "postcss" ],
+				"eslint.validate": ["javascript", "javascriptreact"],
+				"stylelint.validate": ["css", "scss", "postcss"],
 				"files.associations": {
 					"*.php": "php",
 					"*.html": "html"
@@ -49,7 +49,7 @@
 		}
 	},
 
-	"forwardPorts": [ 8080, 8443, 3306 ],
+	"forwardPorts": [8080, 8443, 3306],
 
 	"postCreateCommand": "npm ci && composer install",
 

.eslintrc.js

@@ -12,10 +12,10 @@ module.exports = {
 		'eslint:recommended',
 		'prettier',
 	],
-	plugins: [ 'jest' ],
+	plugins: ['jest'],
 	overrides: [
 		{
-			files: [ 'tests/**/*.js' ],
+			files: ['tests/**/*.js'],
 			env: {
 				jest: true,
 			},

.github/agents/release-scaffold.agent.md

@@ -24,9 +24,12 @@ metadata:
 
 ## Wizard Integration & Advanced Features
 
-This agent is tightly integrated with the **Release Scaffold Wizard** defined in `.github/prompts/create-release-scaffold.prompt.md` and implemented via `scripts/lib/wizard.js`.
+This agent is tightly integrated with the **Release Scaffold Wizard** defined in `.github/prompts/release-scaffold.prompt.md` and implemented via `scripts/lib/wizard.js`.
 
-- **Wizard Prompt:** All release-scaffold processes must use the wizard steps and config schema defined in `.github/prompts/create-release-scaffold.prompt.md`.
+- **Wizard Prompts:** All release-scaffold processes must use the canonical prompts:
+  - `.github/prompts/release-scaffold.prompt.md` (main release wizard)
+  - `.github/prompts/pre-release-scaffold-validation.prompt.md` (pre-release validation)
+- **Wizard Steps:** All wizard steps and config schema are now defined in `release-scaffold.prompt.md`. Do not reference or use `create-release-scaffold.prompt.md`—it has been merged.
 - **Wizard Interface:** Supports CLI, JSON, ENV, mock, and other interfaces as defined in `scripts/lib/wizard.js`.
 - **Mustache Placeholder Protection:** Never strip or replace `{{mustache}}` placeholders in the scaffold repository. Placeholders are only replaced during theme generation, not in the scaffold itself. Validate placeholder presence before every release.
 - **Conditional Logic:** Prompts for advanced checks (e.g., smoke test, schema validation) only if enabled in config or by user input.
@@ -35,7 +38,7 @@ This agent is tightly integrated with the **Release Scaffold Wizard** defined in
 - **Validation & Error Recovery:** Each step validates its outcome (e.g., placeholder integrity, version alignment). If a check fails, the wizard reports the error, suggests fixes, and can re-run after correction.
 - **Explicit Mapping:** Each wizard step maps to a config schema field and release check (see wizard prompt).
 
-See `.github/prompts/create-release-scaffold.prompt.md` for the canonical wizard steps and config schema.
+See `.github/prompts/release-scaffold.prompt.md` and `.github/prompts/pre-release-scaffold-validation.prompt.md` for the canonical prompts and wizard steps.
 
 ### Example: Using a Config File
 
@@ -82,6 +85,33 @@ This agent covers scaffold **pre-release preparation**:
 5. Optional generation smoke test to confirm placeholders replace correctly
 6. Release readiness reporting (no git pushes, tags, or merges)
 
+## Modes: Pre-Release Validation vs. Full Release
+
+The release-scaffold agent supports two primary modes, each with its own prompt and workflow:
+
+### 1. Pre-Release Validation Mode
+
+- **Prompt:** `.github/prompts/pre-release-scaffold-validation.prompt.md`
+- **How to select:** Use the wizard mode selector, or pass `--validation`/`--validate` on the CLI.
+- **What it does:**
+  - Runs all validation steps: placeholder checks, version alignment, schema validation, dry-run lint/format/test, documentation checks, generation smoke test, and security audit.
+  - **Does not** update the changelog, stage/commit changes, or perform any release actions.
+  - Produces a readiness report only. No files are modified.
+
+### 2. Full Release Mode
+
+- **Prompt:** `.github/prompts/release-scaffold.prompt.md`
+- **How to select:** Use the wizard mode selector, or run without validation flags (default).
+- **What it does:**
+  - Runs all validation steps as above.
+  - Updates the `CHANGELOG.md` with a new release entry if needed.
+  - Stages all changes, runs husky pre-commit hooks, and commits changes to git.
+  - Produces a readiness report and prepares the repository for release.
+
+The agent uses `scripts/utils/mode-detector.js` to determine the mode and `scripts/utils/logger.js` for structured logging.
+
+---
+
 ## Workflow
 
 1. **Confirm target version** from `VERSION`.

.github/instructions/block-json.schema.json

@@ -1,7 +1,7 @@
 {
 	"title": "WordPress block.json Schema",
 	"type": "object",
-	"required": [ "name" ],
+	"required": ["name"],
 	"properties": {
 		"$schema": {
 			"type": "string"

.github/instructions/release-scaffold.instructions.md

@@ -8,28 +8,34 @@ lastUpdated: "2025-12-12"
 
 # Release Scaffold Instructions
 
-You are a scaffold release assistant. Follow our block-theme scaffold frameworks to maintain the release prompts, docs, and automation that ship with the scaffold. Avoid applying generated-theme release steps here or stripping required mustache placeholders used in downstream theme generation.
+You are a scaffold release assistant. Maintain only the canonical scaffold release prompts and automation:
+
+- `.github/prompts/release-scaffold.prompt.md` (main release wizard prompt)
+- `.github/prompts/pre-release-scaffold-validation.prompt.md` (pre-release validation prompt)
+
+All previous or alternate prompts (such as `create-release-scaffold.prompt.md`) have been merged into the above files. Do not reference or use `create-release-scaffold.prompt.md`—all wizard steps and release workflow logic now reside in `release-scaffold.prompt.md`.
 
 ## Overview
 
-Use these instructions when updating the scaffold release prompt or related guidance in this repository. The goal is to keep the scaffold's release assets current without impacting the release process that runs in generated themes.
+Use these instructions when updating the scaffold release prompts or related guidance. The goal is to keep the scaffold's release assets current and avoid duplication or confusion with deprecated prompt files.
 
 ## General Rules
 
 - Keep scaffold files templated: retain mustache variables needed by generated themes.
 - Scope changes to scaffold assets only; defer generated-theme steps to `release.instructions.md`.
 - Reference organisation coding, linting, and testing standards instead of redefining them.
 - Document any automation changes in the changelog and agent notes.
+- Use only `.github/prompts/release-scaffold.prompt.md` and `.github/prompts/pre-release-scaffold-validation.prompt.md` for all scaffold release and validation workflows.
 
 ## Scaffold vs Generated Themes
 
-- **Scaffold artifacts**: `.github/prompts/release-scaffold.prompt.md`, `.github/agents/release-scaffold.agent.md`, and docs/RELEASE_PROCESS_SCAFFOLD.md.
+- **Scaffold artifacts**: `.github/prompts/release-scaffold.prompt.md`, `.github/prompts/pre-release-scaffold-validation.prompt.md`, `.github/agents/release-scaffold.agent.md`, and `docs/RELEASE_PROCESS_SCAFFOLD.md`.
 - **Generated theme artifacts**: use `.github/prompts/release.prompt.md` and `release.instructions.md` after placeholders are replaced.
 - Never copy scaffold-only files into generated theme releases; remind agents to remove them during generation.
 
 ## Detailed Guidance
 
-- **Templates & Prompts**: Ensure prompts describe placeholder cleanup, version alignment, and dependency checks without hard-coding theme names.
+- **Templates & Prompts**: Ensure prompts describe placeholder cleanup, version alignment, and dependency checks without hard-coding theme names. All wizard steps for release are now in `release-scaffold.prompt.md`.
 - **Automation Hooks**: Align with `.github/workflows/block-theme-build-and-e2e.yml` for validation steps and keep command examples current.
 - **Changelog Notes**: When scaffold release behaviour changes, add concise entries to `CHANGELOG.md` under the scaffold section.