Claim, publish, and follow review

Claim the manifest publisher

fabled module publisher status
fabled module publisher claim .

status reports whether the current account owns a publisher namespace and shows its state without exposing the owner identity. claim reads publisher.id and publisher.name from the project manifest. Publisher ids are 2–39 lowercase letters, digits, and hyphens and become the first segment of every package id.

Submit one release channel

Choose one command for the release you intend to submit. Use prerelease while iterating with reviewers:

fabled module publish . --channel prerelease

Use stable only when the validated archive is the release candidate you want reviewed for the stable channel:

fabled module publish dist/release.zip --channel stable

publish accepts a project directory or validated archive, uploads it as review-quarantined data, and checks that Fabled's receipt matches the package id, version, channel, SHA-256, and byte length. Uploading does not make package code executable or put the release in the player catalog.

List and wait for review

fabled module submissions --status pending
fabled module submissions --package my-studio.my-dice --page 0 --size 25
export FABLED_SUBMISSION_ID="replace-with-the-submission-id"
fabled module status "$FABLED_SUBMISSION_ID"
fabled module status "$FABLED_SUBMISSION_ID" --wait

A submission moves through PENDING, CHANGES_REQUESTED, REJECTED, APPROVED, or WITHDRAWN. Human and JSON output include bounded reviewer notes, automated findings, and warnings. --wait stops at a decision, polling every 5 seconds for up to 600 seconds by default; --interval accepts 1–30 seconds and --timeout accepts 1–1800 seconds.

After approval

Approval is one gate, not automatic activation. A release must also be promoted into an available catalog channel. A member then acquires its entitlement, explicitly installs the exact release while accepting its terms, and activates it in an eligible scope. Fabled resolves compatible dependencies and delivers only a signed runtime projection trusted by the browser host. Campaign activation follows the owner and entitlement checks in the installation guide; community support requires the matching source-candidate deployment.