Tighten the design-partner intake loop for early evaluators

[hudsonaikins]

Problem

The repo now has public install and packaging surfaces, but we still need a tighter design-partner loop so early users can evaluate ProfitCtl, share results, and give structured feedback.

Scope

• turn the current design-partner guidance into a simpler public intake checklist
• define what feedback we need from the first 5 evaluations
• align the docs with a benchmark -> install -> compare -> calibrate -> feedback workflow

Acceptance Criteria

• the design-partner docs are short enough to use in real outreach
• maintainers know what signals to capture from early evaluators
• the public docs point to one clear next step after evaluation

[hudsonaikins]

Addressed by PR #32 and merged into main. See #32 for the implementation details.