Build Log

Leashline UX + Architecture

June 18, 2026

Full route UX overhaul. Sally's five edge cases handled. First deploy to leashline.forgekits.build. Rail + Rounds engines named. Armory splits into two catalogs.

LeashlineArchitecture

UX improvements

Named engines

Rounds configs sketched

Reusable patterns

Live deploy

Timeline

Start

Route UX: 'On my way' → 'Start visit'

Tappable phone, address, access notes

Finish panel + Issue workflow built

Editable SMS draft, 7 issue chips, log or text owner

Running late + injury chip + badges

Unpaid + Watch reliability, pre-written lateness text

Leashline brand applied

Nunito Sans, full token set, real SVG logo, favicon, OG, PWA

GitHub + Vercel deploy

leashline.forgekits.build live, Jungebez/leashline repo created

End

Rail + Rounds named, Armory split documented

PROJECT_INDEX + forge-platform + armory.md all updated

What shipped

Route UX — renamed 'On my way' to 'Start visit' / 'In progress' badge

Tappable phone (tel:) and address (Google Maps) on visit cards and clients page

Access notes tap-to-copy with clipboard confirmation

Finish visit inline panel — editable SMS draft, optional soft note toggle, skip text option

Issue workflow — 7 quick chips, free-text note, log + text owner or log only

Running late button — pre-written lateness text, logs to change_log

Injury chip surfaces vet note + emergency contact inline

Unpaid + Watch reliability badges on individual visit cards

Leashline brand — Nunito Sans, full brand token set, real SVG logo in sidebar/mobile header

Favicon, apple-touch-icon, OG image, PWA theme-color wired into layout.tsx

GitHub repo created (Jungebez/leashline), connected to Vercel, deployed to leashline.forgekits.build

PROJECT_INDEX, docs/forge-platform.md, docs/armory.md — all updated with Rail+Rounds framing

“Name the engine. Then every new vertical is just a config.”
— Architecture insight — June 18