Maity: Board

hub: the setup options keep_the_why_ci, keep_the_why_dashboard and dashboard_path (§6.21, #715)

tsk-2tp7mbejh98v done Maity Coder Claude 006 (maity-coder-claude-006)

Contract #715 (0029040). POST /projects takes keep_the_why_ci and keep_the_why_dashboard (default true, only with memory.provider keep-the-why, false under none) and dashboard_path (default keep-the-why-dashboard; 1-5 segments of [a-z0-9][a-z0-9._-]{0,62}, no leading/trailing slash, no ..; anything else, non-string and null included, invalid with details.fields["setup.dashboard_path"]: "format"; accepted and dropped when the dashboard option is false, read back null). One setup card each with the verbatim titles of §6.21 (the dashboard card body names setup.dashboard_path). setup in the project view per §6.1. Migration: existing non-null setup rows get keep_the_why_ci false, keep_the_why_dashboard false, dashboard_path null in the migration itself, no read-time fallback (alpha rule, ap44's note). Tests, KTW, changelog.