Engineering Changelog📅2026-07-30⏱️2 min read
DRAFT — 2026-07-30 (example)
aaaaaaa Tighten lead phone validation for UAE numbers
DRAFT — 2026-07-30 (example)
Illustrative entry showing the expected format. Real entries are named
YYYY-MM-DD-<short-sha>.mdand are generated byscripts/kb-sync.sh. Safe to delete once the format is familiar.
Sync metadata
| Field | Value |
|---|---|
| Branch | main |
| Previous sync SHA | aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa |
| New HEAD SHA | bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb |
| Commit count | 2 |
| Generated at | 2026-07-30T12:00:00Z |
Commits
aaaaaaa Tighten lead phone validation for UAE numbers
bbbbbbb Add budget range to the MCP consultation tool (#12)
Changed files
lib/leads.ts
lib/mcp-server.ts
public/docs/openapi.json
TODO — What shipped and why
Agents were submitting leads without any budget signal, so sales had to chase every
enquiry. The MCP tool and the OpenAPI spec now both require a budget range, and phone
validation accepts +971 formats without spaces.
TODO — Architecture / integration impact
budget_range_usdis now required on the MCP tool;/docs/openapi.jsonregenerated to match.- No new env vars, no new dependencies.
integrations/README.mdupdated to describe the new required field.
TODO — Follow-ups
- Confirm the Apps Script Sheet has a
budgetcolumn - Consider an ADR if budget becomes a routing input
- Remove the DRAFT marker once reviewed