Expand description
HTTP handlers for TechnicalSpec (Story 3.8 — FR33).
Routes:
POST /technical-specs— create a Draft spec (syndic/superadmin)POST /technical-specs/{id}/bump— create a new version (syndic/superadmin)POST /technical-specs/{id}/submit— Draft -> PendingSignatures (syndic/superadmin)POST /technical-specs/{id}/signatures— record a signature (signatory)GET /technical-specs/{id}— spec detailsGET /technical-specs?acp_id={uuid}— list specs for an ACP
All routes are JWT-protected. The two GET routes above took
AuthenticatedUser without using it (_user) — the Phase B scope
tightening promised in the Story 3.8 acceptance notes — and are now
cloisonnées like sign_technical_spec (#882).