fix(setup): stop the drafted profile from being unsavable

[ralyodio]

What was wrong

/setup read the site, drafted a profile, and then refused to save it: "that profile is incomplete".

Every list in workspaceProfileSchema capped an entry at 120 characters. That is the right length for a job title and the wrong length for a value proposition — the model writes those as sentences. Reproduced on production against profullstack.com, whose draft came back with one 132-character value proposition:

PUT /api/v1/onboarding/profile
400 {"error":{"code":"bad_request","message":"that profile is incomplete",
     "details":{"offering":["String must contain at most 120 character(s)"]}}}

It was a dead end, not an inconvenience: valuePropositions had no input on the form, so the offending line could not be shortened, and the error named offering — not which of its six fields, or which line of it.

What changed

• The contract distinguishes terms from sentences. ICP facets and competitors stay at 120; value propositions, likely pains and exclusions get 300. Limits are exported as profileLimits so the drafter and the schema cannot drift.
• The drafter clamps to those limits, cutting on a word boundary and marking the cut with …. A chatty model now yields a shorter draft rather than an unsavable one — a draft the contract refuses must not be reachable.
• The rejection is actionable. Keyed by full path (offering.valuePropositions.3), shown next to the save button instead of off-screen by the URL box, and value propositions are editable like everything else that gets saved.

Verification

• The exact production payload that returned 400 now validates against the schema.
• New round-trip test: whatever POST returns must be acceptable to PUT untouched.
• bun run check green — format, typecheck, 550 tests; apps/web typechecks clean.

🤖 Generated with Claude Code