Skip to content
Educational satire No money Priced in time Human review required
BarkBowlTime-commerce dogfooding

Operator smoke test

Deployment Parity

Compare the package the source expects with the plugin, theme, seeder, evidence, and cached HTML the live site actually serves.

Deployment Parity

Compare source, plugin, theme, seed, evidence, and cached HTML.

This report is for the recurring live-site drift problem: the source package moves forward while public HTML or REST still reports an older release.

Package
1.29.0
Seed
2026.06.11.031
Status
pass

Loaded plugin package version

Status: pass

Expected: 1.29.0

Actual: 1.29.0

Upload and activate the plugin ZIP for the target release, then clear caches.

Active theme version

Status: pass

Expected: 1.29.0

Actual: 1.29.0

Upload and activate the matching BarkBowl theme ZIP.

Seeder target constant

Status: pass

Expected: 2026.06.11.031

Actual: 2026.06.11.031

Confirm the v1.29.0 plugin is active; older plugin code reports older seed targets.

Last seeder run

Status: pass

Expected: 2026.06.11.031

Actual: 2026.06.11.031

Run BarkBowl → Seeder twice and verify idempotency.

Bundled evidence assets

Status: pass

Expected: >=270 source-controlled JSON evidence assets after v1.19 route-repair and copy-audit expansion

Actual: 423

If this is low, verify the plugin ZIP was fully replaced and no stale directory remained.

Cached page staleness check

Status: human-review

Expected: Homepage, Public Diagnostics, Runtime Verification, Deployment Parity, Evaluation Lab, Release Manifest, and Surface Agreement all show 1.29.0 / 2026.06.11.031

Actual: runtime-loaded package values pass; external cached HTML still requires human/browser confirmation

If any public HTML surface still shows an older package after REST reports the target version, clear CDN/page/object/browser caches and purge any static page cache.

Deployment Parity is a read-only smoke report. It does not approve release, certify safety, validate credentials, probe private networks, train models, or replace WordPress Admin/server-log verification.