fix: prevent Pinterest Save overlays on community invitation

[roboclaw-bot]

MUST: Keep Allow edits from maintainers enabled for this PR so maintainers can help update the branch when needed.

What Problem This Solves

Fixes: Pinterest Save and hover controls can cover the community invitation artwork when Pinterest processes docs page images.

User Impact

User impact: the invitation stays visible and usable while its decorative artwork opts out of Pinterest Save controls. This uses the Pinterest image-local contract; arbitrary extensions may ignore it, and no live Pinterest-extension test is claimed.

Why This Change Was Made

Apply nopin="nopin" and data-pin-nopin="true" only to both theme variants in the shared invitation renderer. This covers every locale without changing copy, layout, styles, links, dismissal behavior, article images, or page-wide saving policy.

Pinterest documents single-image opt-out and Save/hover-button exclusion.

Evidence

• Focused rendered-HTML regression demonstrated red before / green after; covers all 21 locale homes plus an article, both artwork themes, preserved invitation content/controls, and image-local scope.
• 33 focused tests passed (community invitation, home content/layout, and preview builder), in 4.29 seconds.
• Bounded preview built 30 pages. Matching homepage/article HTML was byte-identical to baseline after removing only the two opt-out additions; generated CSS and JavaScript hashes matched.
• DOM-only Chromium verification passed all 8 home/article × light/dark × desktop/mobile combinations: visibility, loaded artwork, unchanged content/link geometry, and persistent dismissal. No invitation screenshots or videos were captured.
• Independent AutoReview covered the complete three-file candidate through P0–P3; scoped-clean with no findings. Syntax and whitespace checks passed.
• Full publishing build/smoke suite was not run locally; this is a bounded renderer change without routing, index, or artifact-policy changes. CI results are reported separately.

Worked on by

• @vincentkoc — requested the fix and directed the scope; RoboClaw implemented and verified it.

Work sessions

• Original discussion with @vincentkoc
• Implementation and verification

---

View the OpenClaw team session