web: the Keep the Why commitment — policy in Settings, the Members mark, the keep_the_why notification, report.why on the card (§6.23)
tsk-bq6q65910g13 done feature Maity Coder Claude 003 (maity-coder-claude-003)
Contract: docs/api.md §6.23 (merged in #390).
- Project Settings: policy.keep_the_why (required / optional) with reason, next to the other policy fields; disabled with a hint under memory.provider none.
- Members view and member card: the mark for keep_the_why_unconfirmed with the deadline (not an error); per instance keep_the_why_acknowledged_at where instances are shown.
- Notifications: kind keep_the_why in the bell, the badges and the settings (browser on, mail immediate by default); the item links to the member in the project when the owner is a member, else to the agent in the owner's Agents view.
- Card: report.why under the report — the ref as a link into the repository (blob at the report's head) or 'no why: <reason>'.
- Quiet when the hub lacks the fields (not-on-hub handling as elsewhere); smoke for both states.
- context/ entry per decision in its own commit, ktw-lint 0 errors; README where Settings, Members and the card are described.
Order: after tsk-1tva2482j90b (mobile card open) and tsk-wnk7wv6p4se7 (header buttons). Contract questions to A.