Skip to content

Add VIP policy preview and remediate plugin standards findings - #137

Merged
cport1 merged 2 commits into
mainfrom
feat/wordpress-vip-readiness
Nov 16, 2026
Merged

cport1 merged 2 commits into
mainfrom
feat/wordpress-vip-readiness

Conversation

@cport1

@cport1 cport1 commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

WebDecoy needs a reviewable VIP integration prototype and runtime remediation before pursuing production VIP support. This adds an offline edge-policy planner, fixes actionable plugin findings, and records the intentional operations that require scoped standards exceptions. It does not claim VIP certification or complete edge-traffic coverage.

Runtime changes:

  • Use VIP's GET circuit breaker and bounded VIP HTTP waits while preserving WordPress error/auth/response behavior and ordinary WordPress timeout budgets. Never replay or cache one-time POST exchanges.
  • Cache presentation aggregates for 60 seconds, separately from live protection and checkout velocity; explain the display refresh delay.
  • Validate direct-peer/display IPs and use the trusted-proxy-aware visitor address on the block page. Explicitly prevent caching of block and successful-clearance responses; add SameSite=Lax to the HttpOnly clearance cookie.
  • Replace raw exception logs with opt-in fixed event codes, use WordPress encoding/URL helpers in adapters, remove admin global-name collisions, constrain uninstall transient matching, and use soft lifecycle rewrite flushes.
  • Queue a targeted VIP robots.txt purge when selected categories change, with modern/legacy API guards.

The original VIPCS3.1.0 baseline is preserved: 45 errors / 191 warnings. The final source and WordPress.org package scans report 0 errors / 0 warnings with reviewed line-specific exceptions. This is not 236 bugs fixed: most original findings concern intentional custom-table operations or PHP request signals. remediation.md and reviewed-exceptions.json distinguish fixes from exceptions and record the remaining real VIP cache/proxy/load/API pilot requirements. No new file-wide suppression or excluded runtime directory was added. The new VIP CI job fails on findings.

The offline planner preserves unrelated UA restriction groups and validates group ownership, environment IDs, snapshot freshness, protected UA examples, and the combined rule limit. It emits proposed and rollback request bodies without credentials, network access, or an apply command. Declared UA matching is not verified bot identity. Full-list concurrency and rollback limits are documented.

Validation:

  • 269 PHP tests passed, including isolated VIP/non-VIP transport, error/auth preservation, site-scoped analytics cache expiry, diagnostics, malformed proxy input, and modern/legacy robots purge regressions.
  • 28 offline planner tests and 14 WordPress hook-order cases passed.
  • PHP 7.4 compatibility scan passed; syntax checks passed for 119 source/test PHP files.
  • WordPress.org test ZIP builds and passes the same VIP scan; updater, clearance client, docs, tests, and workflows remain excluded as appropriate.

No production deployment, published release, authenticated VIP API call, or VIP load test was performed.

@cport1 cport1 changed the title Add WordPress VIP policy preview and readiness assessment Add VIP policy preview and remediate plugin standards findings Nov 16, 2026
@cport1
cport1 merged commit 077417c into main Nov 16, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant