Public repair packet samples
See what a Hermes repair packet looks like before approval
One sample below is backed by a real captured pipeline run with before/after screenshots. The others show the packet structure a customer reviews before Hermes changes a live WordPress site; their screenshot proof is pending a real run.
Every sample includes
Packet metadata and backup state
Redacted evidence from synthetic or test-store reproductions
File-level code change summary
Risk rationale and approval gate
Public examples are synthetic or test-store based. They avoid customer names, secrets, and production data.
Real pipeline evidence · seeded local workspace
Low risk
HRP-CAT-3097
Product prices unexpectedly show as $0.00
Hermes ran the price-zero scenario through the local WooCommerce repair pipeline, captured real before/after screenshots, traced the issue to a malicious mu-plugin, and produced a review packet that keeps the fix behind approval because the evidence is from a seeded local repair workspace.
Status: Real local pipeline packet captured
Environment: Seeded local WooCommerce repair workspace, not a customer production site
Code: wp-content/mu-plugins/price-display-engine.php
Risk rationale
Low because the packet deletes one malicious mu-plugin and does not touch theme files, database prices, checkout, payment, or order-state behavior.
Evidence preview
local-price-zero-1780388865254 completed on 2026-06-02 in the seeded local WooCommerce repair workspace.
Before capture needed
Real pipeline run must capture the checkout failure before this sample publishes a screenshot.
Trace evidence
Session-clearing hook fires before payment callback completion.
Proof pending · packet structure example
Medium risk
HRP-CHK-1042
WooCommerce checkout reloads with “session expired”
Hermes reproduces the checkout failure in a repair workspace, ties it to a specific checkout-session hook, and records the real-pipeline screenshot capture task needed before this public sample publishes visual proof.
Status: Provisional sample, pipeline proof pending
Environment: Isolated repair workspace with Stripe test mode
Code: wp-content/themes/storefront-child/functions.php
Risk rationale
Medium because the patch touches checkout-session behavior. Hermes constrains it to the payment callback path and keeps cart/catalog behavior outside scope.
Evidence preview
Real pipeline run must capture the checkout failure before this sample publishes a screenshot.
Webhook log
Stripe success event received with valid payment intent.
Order audit
Order remains pending after the webhook handler returns.
Proof pending · packet structure example
Medium risk
HRP-PAY-2118
Stripe payment succeeds but WooCommerce order stays pending
Hermes follows the paid Stripe webhook through the WooCommerce order-state logic, shows the stuck pending order evidence, and prepares a constrained diff plus replay checks before production apply.
Status: Provisional sample, pipeline proof pending
Environment: Isolated repair workspace with Stripe test-mode replay
Code: wp-content/plugins/store-customizations/order-status.php
Risk rationale
Medium because the fix changes order-state transitions. Hermes verifies paid and unpaid webhook paths before apply.
Evidence preview
Stripe success event received with valid payment intent.