docs: add Wednesday Solutions section to README

[Ganeshship]

Summary

Adds a Built by Wednesday Solutions section to the README, positioned right after the badges row and before the "Not just another chat app" pitch. High-visibility placement that introduces the team behind Off Grid and routes interested readers to the AI-Native Mobile Squads hire page.

What's in the section

• BUILT BY caption + Wednesday logo (104px, clickable, links to mobile.wednesday.is)
• Single-paragraph pitch: "Off Grid is built by Wednesday Solutions. We run AI-Native Mobile Squads: pre-vetted iOS and Android engineers paired with AI tooling for code review, testing, screenshot regression, and release notes. Squads plug into your org in a week and ship to production from day one."
• Hero stats as SVG images: 4x faster to ship · 2x fewer crashes · 10x more output, same cost · 100% money-back if we miss the claims
• Closing question: "Want the same team that shipped offline AI to a phone working on your product?"
• Primary CTA: Hire an AI-Native Squad → linking to https://mobile.wednesday.is/hire-ai-native-mobile-squad

Optional commit (reviewer's call)

The last commit ce33bc7f is marked OPTIONAL in its commit message. It does two things on top of the rest of the PR:

1. Adds the 100% money-back guarantee as a 4th stat tile alongside 4x / 2x / 10x
2. Rewords 10x more work to 10x more output (outcome-focused vs activity-focused)

The PR is fully usable without this commit — the section already works with just the three core stats. If the reviewer prefers leaner / less marketing-flavored stats, this commit can be reverted independently:

git revert ce33bc7f
# or before merge: git rebase -i main and drop the commit

The first three commits (a441da45, aad0f4f5, 9a37fc42) are the core, non-optional change.

Why SVG for the hero stats

Markdown headings have unreliable margin behavior across renderers (h1 vs <sub> baseline drift, sanitizers stripping inline style attributes). Embedding the stats as SVG with text positioned at exact pixel coordinates gives pixel-perfect typography that looks identical in every markdown viewer.

Dark mode support

All five SVGs (Wednesday logo + 4 stat blocks) include a white background <rect> baked into the SVG itself. Without it, the dark text fills (#0d1117 for numbers, #0B0B0D for the wordmark) would render as near-invisible on GitHub's dark theme. The white bg appears as a "card" in dark mode and blends seamlessly with the page in light mode.

New assets in src/assets/

• wednesday-logo.svg (Wednesday brand wordmark, dark fill on white bg)
• stat-4x.svg, stat-2x.svg, stat-10x.svg (200×80 each, ~250 bytes)
• stat-100.svg (introduced in optional commit) — same dimensions, slightly smaller label font to fit longer caption

Brand voice compliance

Followed docs/brand_tone_voice.md:

• No em dashes (used hyphens, middle dots, arrows)
• No exclamation marks
• No forbidden words (no "leverage", "seamlessly", "showcase", "robust", "comprehensive", etc.)
• No "Not just X, but Y" patterns
• Proof-first throughout — every claim tied to a number

Commit history

1. a441da45 — Initial Wednesday Solutions section + 4 SVGs
2. aad0f4f5 — White background added to all SVGs for dark-mode compatibility
3. 9a37fc42 — Trim copy and route CTA to hire-ai-native-mobile-squad landing page
4. ce33bc7f — OPTIONAL — Add 100% money-back stat tile + reword 10x claim to "more output"

Test plan

• Verify README renders correctly on github.com (light mode)
• Verify README renders correctly on github.com (dark mode) — SVGs should appear as white cards with readable text
• Verify Wednesday logo and all 4 stat SVGs load
• Verify primary CTA links to https://mobile.wednesday.is/hire-ai-native-mobile-squad
• Verify body link "Wednesday Solutions" links to https://mobile.wednesday.is/
• Decide whether to keep or revert the optional commit ce33bc7f

[greptile-apps]

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

[gemini-code-assist]

Code Review

This pull request introduces a promotional section for Wednesday Solutions in the README, along with several new SVG assets for statistics and branding. The review feedback highlights important usability and accessibility improvements, specifically recommending larger tap targets for mobile users by removing _{tags from links and implementing dark mode support for the SVG assets to prevent visibility issues on dark backgrounds.}

[gemini-code-assist]

This link is wrapped in a <sub> tag, which significantly reduces the tap target size. According to the general rules, interactive elements should have a minimum tap target size (e.g., 36px) to improve usability on touch devices. Consider removing the <sub> tag to increase the clickable area.

Suggested change

	<a href="https://mobile.wednesday.is/"><sub><b>30+ ENTERPRISE CLIENTS &nbsp;·&nbsp; 4.8 / 5 ON CLUTCH</b></sub></a>
	<a href="https://mobile.wednesday.is/"><b>30+ ENTERPRISE CLIENTS &nbsp;·&nbsp; 4.8 / 5 ON CLUTCH</b></a>

References

1. Interactive elements like buttons should have a minimum tap target size (e.g., 36px) to improve usability on touch devices.

[gemini-code-assist]

The secondary CTA link is wrapped in a <sub> tag, making it a very small tap target on mobile devices. To adhere to the project's usability guidelines for minimum tap target size (36px), consider removing the <sub> tag.

Suggested change

	<p align="center"><sub>or <a href="https://mobile.wednesday.is/"><b>see how we work →</b></a></sub></p>
	<p align="center">or <a href="https://mobile.wednesday.is/"><b>see how we work →</b></a></p>

References

1. Interactive elements like buttons should have a minimum tap target size (e.g., 36px) to improve usability on touch devices.

[gemini-code-assist]

The fill color #0d1117 is identical to GitHub's dark mode background color, making the text invisible for users with that theme. To ensure visibility across all themes, you can use a CSS media query within the SVG to adjust the colors dynamically.

<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 200 80" width="200" height="80">
  <style>
    @media (prefers-color-scheme: dark) {
      .main { fill: #f0f6fc; }
      .sub { fill: #8b949e; }
    }
  </style>
  <text x="100" y="48" text-anchor="middle" font-family="system-ui, -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif" font-size="44" font-weight="800" fill="#0d1117" class="main">10x</text>
  <text x="100" y="72" text-anchor="middle" font-family="system-ui, -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif" font-size="13" font-weight="400" fill="#57606a" class="sub">more work, same cost</text>
</svg>

[gemini-code-assist]

The fill color #0d1117 is identical to GitHub's dark mode background color, making the text invisible for users with that theme. To ensure visibility across all themes, you can use a CSS media query within the SVG to adjust the colors dynamically.

<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 200 80" width="200" height="80">
  <style>
    @media (prefers-color-scheme: dark) {
      .main { fill: #f0f6fc; }
      .sub { fill: #8b949e; }
    }
  </style>
  <text x="100" y="48" text-anchor="middle" font-family="system-ui, -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif" font-size="44" font-weight="800" fill="#0d1117" class="main">2x</text>
  <text x="100" y="72" text-anchor="middle" font-family="system-ui, -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif" font-size="13" font-weight="400" fill="#57606a" class="sub">fewer crashes</text>
</svg>

[gemini-code-assist]

The fill color #0d1117 is identical to GitHub's dark mode background color, making the text invisible for users with that theme. To ensure visibility across all themes, you can use a CSS media query within the SVG to adjust the colors dynamically.

<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 200 80" width="200" height="80">
  <style>
    @media (prefers-color-scheme: dark) {
      .main { fill: #f0f6fc; }
      .sub { fill: #8b949e; }
    }
  </style>
  <text x="100" y="48" text-anchor="middle" font-family="system-ui, -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif" font-size="44" font-weight="800" fill="#0d1117" class="main">4x</text>
  <text x="100" y="72" text-anchor="middle" font-family="system-ui, -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif" font-size="13" font-weight="400" fill="#57606a" class="sub">faster to ship</text>
</svg>

[gemini-code-assist]

The logo uses a dark fill color (#0B0B0D) which will be invisible on GitHub's dark theme. Consider adding a media query to switch the fill to a lighter color (e.g., #FFFFFF) when the user's system is set to dark mode.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.31%. Comparing base (8a18763) to head (9a37fc4).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #335      +/-   ##
==========================================
- Coverage   82.32%   82.31%   -0.01%     
==========================================
  Files         231      231              
  Lines       11900    11900              
  Branches     3265     3265              
==========================================
- Hits         9797     9796       -1     
  Misses       1246     1246              
- Partials      857      858       +1     

see 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Ganeshship]

@alichherawalla can you please review this and merge.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud