v1.6.59

[roncodes]

Ready for immediate release: version bumped and RELEASE.md written, so merging tags v1.6.59 and publishes.

Both mail templates failed to compile, so every verification and credentials email threw instead of sending. Any flow that delivers a code returned a 400 carrying the Blade error — customer signup, SMS login with email fallback, password reset, account closure, driver login.

syntax error, unexpected token "else", expecting end of file
(View: .../core-api/views/mail/verification.blade.php)

Cause

The greeting read:

Good Morning@if($user->name), {{ delinkify($user->name) }}@endif!

Blade only treats @ as a directive when the preceding character is not a word character — the rule that keeps foo@bar.com from compiling. So Morning@if(...) stayed literal text while the @endif after the echo compiled normally, leaving an unmatched endif that broke the enclosing if/elseif/else. Confirmed by compiling the view and reading the output:

<?php if($currentHour < 12): ?>
    Good Morning@if($user->name), <?php echo e(...); ?><?php endif; ?>!
<?php elseif($currentHour < 18): ?>     ← now orphaned

Introduced in v1.6.56 by the fix for a null user name, and shipped again in v1.6.57 and v1.6.58. user-credentials.blade.php has the identical break.

Fix

The greeting is built in one expression, so no directive ever sits against a word. delinkify() returns '' for a null or empty name, which is what makes the no-name case fall through to the bare greeting.

Why nothing caught it

No test ever compiled a view — the templates were only exercised through mocked mailers, which never render them. This PR adds a test that compiles every Blade view in the package and runs php -l over the result. I verified it fails against the shipped template and passes against the fix, so it is a real guard.

Full suite green; coverage gate at 100%.

Impact on the contract runs

This is the cause of most of the current failures in both collections — Request Customer Creation Code, Request Customer Login SMS, Request Driver Login SMS, Forgot Customer Password, Authenticate a Customer via SMS, Start Account Closure, Setups a verification request. They should clear once this is in the published image.

Two failures are not explained by this and remain open: fleetops List Organizations (Invalid platform API token.) and storefront List Network Stores.

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (941b59e) to head (11f3849).

Additional details and impacted files

@@             Coverage Diff             @@
##                main      #242   +/-   ##
===========================================
  Coverage     100.00%   100.00%           
  Complexity      6730      6730           
===========================================
  Files            397       397           
  Lines          22448     22448           
===========================================
  Hits           22448     22448           

Flag	Coverage Δ
backend	100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.