EvidenceKind

Type Alias: EvidenceKind

EvidenceKind = "image" | "document"

Defined in: report-support/evidence.dto.ts:24

SPEC-API-AUXILIARY-001 documents evidence purely by reference (CreateReportRequest. evidenceAssetIds: string[], see the spec's own report example) and assumes a presigned upload flow ("Uploads usam fluxo presigned") that does not exist anywhere in this codebase yet — confirmed by grep across contracts/services/api/packages/mocks. The closest precedent, Field/Service gallery (AddGalleryAssetRequest, IS-MVP-13.1/13.2), also has no real upload: the client assembles the asset (URL/dimensions) directly and the server stores it as ready immediately. Evidence follows the same simplification — POST /evidence (additive beyond the literal SPEC-API-AUXILIARY-001 endpoint table, same "endpoint added to make a documented request shape reachable" precedent as POST /torcidas/:id/resubmit, EP-MVP-08.1) accepts a client-supplied url/mimeType/sizeBytes and returns a ready EvidenceDto synchronously — no async processing pipeline. Divergence registered in this pack's handoff; a future pack implementing SPEC-API-MANAGEMENT-001's real presign/confirm flow should replace this the same way gallery/ crest/banner uploads are already flagged to (see NEXT_STEPS.md).

Unlike gallery images, evidence is never public: it is never embedded in any public DTO, and no target-facing (denunciado) or moderation/admin endpoint exists in this pack to read it back — only the reporter's own GET /reports/my / GET /support-requests/my echo it, which already satisfies SPEC-DOMAIN-REPORT-001 "Evidências têm acesso restrito" structurally.