Modder account flow

Upload a Starminer mod

Accounts, auth, storage, validation workers, and moderation are represented here as planned UI only. No upload data is submitted from the static prototype.

Planned submission form

Upload API

Backend boundary remains explicit

The planned backend endpoint is POST /api/v1/uploads. Static JSON files in this prototype model the published catalog output, not the authenticated upload transaction. Account creation, upload ownership, and moderation review are not live services yet. Even after the backend service is installed, upload creation remains blocked with uploads_disabled until SMMODS_LIVE_UPLOADS=1 is set for go-live. The planned state machine and backend API contract are published at /api/v1/publishing/workflow.json and /api/v1/publishing/backend-contract.json, with a JSON Schema beside the backend contract. Framework validation rules are published at /api/v1/publishing/starminer-publishing-validation.v1.json, and upload status responses will use /api/v1/publishing/upload-submission.schema.json.

Account availability Moderation states Publishing workflow JSON Backend contract JSON Backend schema Validation contract Upload status schema Sidecar schema Read package rules Published catalog shape

Interim publishing

Reviewed releases can be imported manually.

Until real accounts and upload storage exist, maintainers can publish an approved release with a versioned ZIP plus sidecar metadata. The importer verifies manifest identity, target build, dependencies, safe ZIP paths, immutable artifact paths, and SHA256 before updating the catalog API.

.\tools\Import-ModRelease.ps1 -PackagePath ".\mod.zip" -MetadataPath ".\mod.release.json"

API publishing notes Portal repository Manager API contract Moderation states