Agents - Source Excerpt 02 - Verification And Packaging

Back to Agents

Summary

This source excerpt begins near Verification And Packaging and preserves the surrounding evidence from Spiralist/AGENTS.md.

**Source path:** Spiralist/AGENTS.md

- Treat `wp-content/plugins/ns12-manuscript/exports/static-book/**` and `--zip/**` as generated/export copies.
- Do not edit WordPress core/vendor Markdown such as bundled theme font licenses or `wp-includes/sodium_compat/**`.
- Keep package-level READMEs short and point durable context back to `.uai/` and Wiki.FFTAC.org.

## Verification And Packaging

- Docs-only changes do not require deployment ZIP rebuilds.
- Theme or plugin package changes require the relevant version header to be bumped before packaging.
- Packaging-only deploy fixes also require a version bump for the affected package if a new ZIP will be uploaded to WordPress.
- Never leave WordPress showing the same `Current` and `Uploaded` version for a normal deploy; cancel, bump, rebuild, and upload the new versioned ZIP.
- Spiralist build output belongs in `WP-FFTAC/Spiralist-Publish` and only in that publish root.
- Production upload ZIPs must be built with the WP-FFTAC production script and the Spiralist manifest; do not use ad-hoc ZIP tools.
- Last official built package evidence used `powershell -NoProfile -ExecutionPolicy Bypass -File WP-FFTAC/scripts\build-workspace-production-zips.ps1 -DeploymentVersion 3.24.0`.
- Do not claim live deployment from the v3.24.0 ZIPs until the files have been uploaded/copied to production and post-upload route/discovery verification has passed.
- Upload deploy ZIPs only from `WP-FFTAC/Spiralist-Publish\UPLOAD-THEME` and `WP-FFTAC/Spiralist-Publish\UPLOAD-PLUGIN`, not from the repo root, Downloads, `D:\`, or temporary folders.
- Use `.uai/test-plan.uai` for test and lint commands.