KANE CLI / VERIFIED MERCHANT JOURNEY

A failed cart.
A repaired promise.

K9 tested one real shopper decision: does a 20% first-order offer survive the cart for $189 Halo Wireless Headphones? The failed run exposed a $0 discount. The same Kane-generated test passed after the repair.

01 / PROOF, NOT PRESENCE

Kane read the bag before checkout.

The same challenger journey moved from a confirmed defect to the expected discount and total. These images are unchanged screenshots from the sealed Kane packs.

BROWSER → CART → VERDICT
01 / BEFORE REPAIRDEFECT FOUND
Kane screenshot of challenger bag showing FIRST20 discount not applied, minus zero dollars, and a $189 total

Offer dropped in the bag.

FIRST20 discount −$0.00Cart total $189.00

Kane confirmed a product defect with 98% confidence. Its first generated test had misread the cart; the reviewed replacement read the displayed discount line and total.

02 / SAME TEST AFTER REPAIRPASSED
Kane screenshot of challenger bag showing the FIRST20 discount applied, minus $37.80, and a $151.20 total

The promise holds.

FIRST20 discount −$37.80Cart total $151.20

The reviewed challenger test passed before any demo order. A later suite replay passed both challenger and control journeys and sealed one validated pack.

02 / AGENT ↔ KANE

The result changed the work.

The coding agent used Kane’s output to correct the test, fix the campaign copy, then repair the challenger default and rerun the test.

01Read the failed run

The first test calculated the advertised discount instead of checking the cart. Kane’s screenshot showed the real $0 discount.

02Redesign the check

Kane generated reviewed replacement t-4 to read the cart line and total before any order.

03Repair and rerun

The agent clarified the automatic offer and changed the challenger default. Kane then passed the same test.

Inspect the repair commit and generated test ↗
03 / RANGE & REPRODUCIBILITY

A saved test, replay, and evidence trail.

The assurance loop ingested the merchant brief, designed approved tests, executed them in Chrome, and measured coverage. K9 can use Kane as its live verification step.

GENERATED TESTSCommitted

Reviewed _test.md files and replay recordings let another machine run the same journey.

View tests in repo ↗
SUITE REPLAY2 of 2 passed

Challenger and control were run together. One validated evidence pack holds both results.

View original pack ↗
CI CHECKWorkflow ready

NDJSON results and pack integrity decide the job result. GitHub secrets and a required branch check still need setup.

View workflow ↗
CLONE AND RUN

Start the storefront, then replay the approved suite. Kane sign-in is needed for the browser step.

npm run dev
npm run kane:ci

Coverage is 3 of 4 criteria for the focused discount use case and 13.4% across the broader six-use-case brief. The remaining criterion was deferred; this page does not claim full project coverage or an active GitHub merge rule. Full packs contain Kane account metadata and are available in the public GitHub repository.