feat: add and update shared components (BackToTopButton, ScrollDownArrow, Logo, Typography, SocialShare, LoadingSpinner, ErrorBoundary, SkipLink, VisuallyHidden, Divider) and update changelog

Author: ashleyshaw

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

@@ -1,3 +1,21 @@
+# ⚠️ WARNING: Strict Mustache Placeholder Enforcement
+
+All contributors must use the correct mustache placeholders in all template files, folders, and code. Do not use generic placeholders (like `{{slug}}`) where a more specific one is required (e.g., `{{cpt1_slug}}`, `{{taxonomy1_slug}}`).
+
+**Never hard-code plugin-specific values** in the scaffold. All identifiers, class names, translation domains, and meta keys must use the appropriate placeholder as defined in `scripts/mustache-variables-registry.json`.
+
+The mustache registry is updated automatically by running:
+
+```sh
+node scripts/scan-mustache-variables.js --update-registry
+```
+
+If you add, rename, or remove placeholders, always update the registry and review the change report in `scripts/reports/`.
+
+See `docs/GENERATE_PLUGIN.md` for more details and the latest warning.
+
+**Failure to follow these rules will break plugin generation and may result in lost work.**
+
 ---
 name: Plugin Generator Instructions
 description: >-

.github/instructions/generate-plugin.instructions.md

@@ -58,3 +58,9 @@ Avoid embedding secrets or skipping tests in workflow steps.
 - Run `npm test` and `composer test` where applicable.
 - Run `npm run lint` and `composer lint` to ensure coding standards before release.
 - Dry-run release workflows locally or via workflow_dispatch in a staging branch before production tags.
+
+## Agent prompts & guardrails
+
+- The release-scaffold agent loads `.github/prompts/create-release-scaffold.prompt.md` when running in **full release** mode and `.github/prompts/pre-release-validation.prompt.md` when only validating. Keep both prompts aligned with the instructions so the wizard steps remain consistent.
+- All templated files that contain `{{mustache}}` placeholders must be handled through the dry-run scripts (`npm run lint:dry-run`, `npm run dry-run:all`, `npm run dry-run:release-scaffold`). No workflow updates should mutate the placeholders directly.
+- This instruction set is specific to the `lightspeedwp/block-theme-scaffold` release process — reuse the prompts and validation suite whenever you prepare a new tag for that repository.