Maven Central Publishing

Step 1: Define the release contract

1. CLASSIFY account onboarding | namespace verification | first release | existing release | snapshot | OSSRH migration | CI automation | failed deployment.
2. IDENTIFY owner, exact groupId:artifactId:version set, packaging, modules, release versus snapshot, build tool, signing owner, publication route, staging policy, target account/organization, and whether the action stops before external publication.
3. READ the current Central registration guide, Publisher Terms, and applicable linked documentation before account, namespace, credential, or publish actions.
4. TREAT a Central release as irreversible: published coordinates cannot be modified, replaced, or deleted; corrections require a new version.
5. REQUIRE the user to review applicable terms. Never accept terms, create an account/namespace/token, disclose credentials, or publish on the user's behalf without explicit authorization for that exact action.
6. ROUTE KMP artifact topology to kotlin-multiplatform, Gradle/toolchain mechanics to kotlin-gradle, API docs/Javadoc artifacts to dokka, and non-Central repositories to their own workflow.

Completion: owner, coordinates, version, artifacts, route, staging mode, credentials boundary, and maximum authorized external action are explicit.

Step 2: Inspect the publication project

RUN from the repository root:

python3 scripts/inspect-project.py --root . --json