Store overview

Store is the public catalogue of SteamHarness project versions. You can browse entries, inspect technical information, download archives, and publish versions of your own projects.

Store never executes project code and does not replace Server project permissions.

Browse and download

The catalogue filters by project type (Workflow, Conversation, Kanban), System AI usage, and name or recent update. The public list only contains approved and listed entries:

• Search covers title, summary, and description.
• Technical information (dependencies, version, archive metadata) requires a signed-in user.
• Downloads require sign-in and deliver the .tar.gz archive frozen at submission time.
• Anonymous visitors can see public entries and media for approved entries; pending media is visible only to its owner or an admin.

An approved entry is downloadable by any valid signed-in account. Store does not reuse the original project's membership or source permissions; approving a release authorizes distribution to signed-in users.

Publishing surfaces

Surface	Location	What it does
Store console	The Store site's publish and submission pages	Fill in entry details, upload screenshots, save drafts, submit for review, withdraw, unlist
Server Web project console	Server Web's Store and project details	Manage drafts, versions, and listing state for your own projects
Management console	Store review in the management console	Review queue, approve, reject, unlist

Server Web cannot review Store submissions, even for a system administrator; review happens only in the management console. See Publishing to Store for the full workflow.

Account and sign-in

Store uses your SteamHarness account:

• Protected pages redirect to login and return to the original page; a pending download resumes.
• Every request uses the same signed-in session; no extra token is needed.
• Mutations check the request origin, and responses are not cached by the browser.

States and versions

Versions use x.y.z. A submission moves through:

draft → pending → approved / rejected
                  pending → withdrawn
approved → unlisted（hidden, can be listed again）

• An approved version is immutable: the same version cannot be re-approved with a different archive.
• While a new version is pending, the previous approved version remains current and downloadable.
• Rejections must include a reason, which is shown to the publisher.
• Unlisting hides the entry and withdraws any pending revision.

Limits

• Uploading a local project package is not supported; only versions already published on the Server can be listed.
• Archive limits: 100 MiB compressed, 512 MiB expanded, 100,000 entries.
• Archives reject symlinks, unsafe paths, runtime directories, key files, and likely credentials.
• Up to 6 screenshots, 5 MiB each, in PNG / JPEG / WebP.