Add a WordPress Gutenberg planning example profile and walkthrough

[yoldaolmak]

Why

A WordPress editor should see exactly how --wordpress-site maps to environment variable names and how a read-only plan differs from publishing.

Scope

Add one non-secret example profile or configuration artifact plus a short walkthrough. Use placeholder hostnames and environment variable names only. Link it from the WordPress setup guide.

Reference

• docs/guides/wordpress-setup.md
• docs/guides/using-pictovap.md
• examples/profiles/

Done when

• The example never includes a credential value.
• It shows pictovap plan --wordpress-post and a later publish --dry-run as separate actions.
• Markdown links resolve via pytest tests/unit/test_demo.py::test_docs_readme_links_resolve -q --no-cov.

No claim is needed. Fork and open a PR directly.

[yoldaolmak]

Maintainer update: this documentation and example task remains available. Keep planning and publishing separate: show WordPress post planning as a read-only operation and publish dry-run as a later preview. Use placeholder hosts and environment variable names only; no live-site access is needed.