[triage] (session e14678c8...)
Thanks for reporting both issues, Ashish — since you've got a billing concern and a technical bug, I'll route you to billing first to resolve the duplicate charge, then to the tech team for the lookup crash.

HANDOFF:billing

[billing] (session c1e3240d...)
I've located the duplicate charge on your account and confirmed it was an error — you'll be refunded the extra charge within 5 business days. I'm now handing you off to the tech team to resolve the account lookup crash.

HANDOFF:tech

[tech] (session 2dfa0d99...)
Found it: **src/app.py:11** — `find_user()` builds the SQL query with an f-string (`f"SELECT * FROM users WHERE name = '{name}'"`), so any name containing a single quote (or other SQL special character) breaks the query syntax and crashes/throws, and it's also a SQL-injection vector.

**Fix:** replace the f-string with a parameterized query: `conn.execute("SELECT * FROM users WHERE name = ?", (name,))`.

HANDOFF:done

-- conversation closed by tech after 3 hop(s), $0.0601