Inconsistent role terminology: "Manager" vs "Team Lead" vs "Team Leader"

[ChesterSchendel]

Problem

The same role (Clerk org:admin — the person who leads a client team) is referred to by three different terms across the UI. Flagged by Chester 2026-05-29. "Manager" is NOT a Clerk term (Clerk only uses org:admin / org:member) — it's our own copy; the code maps org:admin → a "manager" badge/ring.

Current usage map

"Team Lead" (the provisioning/customer-facing flow):

• src/app/admin/clients/new/page.tsx (form labels)
• src/app/admin/(tabbed)/clients/page.tsx:174 (table header)
• src/app/api/admin/clients/route.ts (validation messages)
• src/app/dashboard/page.tsx:113, src/app/api/dashboard/route.ts (comments)

"Team Leader" (banner + hq):

• src/components/TeamSetupBanner.tsx:15 ("Team leader" label)
• src/content/hq/_sections.ts:36

"Manager" (team dashboard + reviews — the inconsistent ones):

• src/app/dashboard/team/page.tsx:465 ("Manager" badge), :890 ("manager")
• src/app/dashboard/team/members/[userId]/page.tsx:264-266, :346 ("Manager access required", "team managers")
• src/app/dashboard/reviews/request/page.tsx:43,73,74,100,112 ("Your manager will see it", "Manager decides", etc.)

Marketing (separate decision — may be intentional buyer-persona language):

• src/app/products/page.tsx:83,85 ("design leads and managers", "Manager dashboard")
• src/app/pricing/page.tsx:400 ("manager dashboards")

DO NOT change

• src/app/dashboard/team/page.tsx:181,196 — "Drawbackwards account manager" means the Drawbackwards sales/relationship contact, a different concept. Leave it.

Proposed fix

1. Decide the canonical in-app term (recommend "Team Lead" — already the term in the flow customers go through). Resolve Lead-vs-Leader too. Needs Ward's nod.
2. Replace role-sense "Manager" → canonical term in team dashboard, member detail, reviews UI.
3. Decide marketing language separately with Ward (persona "manager" may be intentional).
4. Optionally rename internal code (isManager, the "manager" ring value) for maintainability — lower priority.
5. Record the canonical term in /hq/glossary (per the docs-lockstep rule) so it stops drifting.

[ChesterSchendel]

/hq terminology drift after #264 (post-merge verification, 2026-05-29)

#264 set "Team Lead" as canonical in glossary.mdx + journeys.mdx + the in-app code, but the decision didn't propagate to the rest of /hq. Remaining role-sense "Manager"/"Team Leader" to update to Team Lead:

• roles.mdx lines 17, 18, 35 (roles table + capability matrix header)
• features.mdx lines 37 ("Team Leaders"), 172 ("manager view"), 177 ("Manager-controlled seat invites")
• gtm.mdx line 126 ("Managers see designer trends")
• decisions.mdx line 163 ("manager workflow")
• _sections.ts line 36 (roles page intent description)

Do NOT change: team.mdx line 13 "Project manager" — that's Michael's job title, not the role. (Same exclusion as "account manager.")

Mechanical doc-only cleanup; bundle with the marketing-copy decision (the two "Manager dashboard" references on /products and /pricing that need Ward's call).