The public create/update contract for a project.
One class for both verbs, the way P13 shares a mutation request: the field
list is identical and only the REQUIRED set differs, so splitting it would
mean maintaining the same twenty rules twice.
PUT is the documented sparse update (§4.5): every rule is sometimes, so a
field the client did not send is not touched — never reset to a default.
A create-only field is rejected with missing, never prohibited:
Laravel's prohibited rule is the negation of required, so it PASSES for
an explicit null, "" or []. {"customer_id": null} therefore reached
patchAttributes() and unlinked the project's customer — leaving that
customer's portal user in the central chat room with no reconciliation to
evict them, the exact damage create-only exists to prevent — and "" hit
the foreign key as a 500. Create-only means ABSENT, which is what missing
actually tests.
Server-owned state is not accepted from a client on either verb:
author_id (the creator, and a budget-alert recipient), task_id_prefix
after creation (it is stamped into every task's human id),
budget_thresholds_notified (alert bookkeeping, re-armed by the server when
the threshold list changes) and the logo upload, which needs a signed upload
session the public contract does not expose yet.