Publish an Olares app to the public Market

Shared front door: load ../olares-shared/SKILL.md for suite routing and platform entry points. Publishing itself does not require an Olares login; apply the shared auth gate only when returning to local upload/install validation.

This skill is the public-distribution step, not the authoring step. Turning a repo / compose / Helm chart into an Olares app, refining it, and proving it installs and reaches running on your own Olares all live in ../olares-chart/SKILL.md. Come here after the app already runs locally and you want it in the public Olares Market.

Use olares-cli chart lint --help and olares-chart for chart syntax and authoring.

When to use

• Publish / publicly list / submit / distribute / 上架 an app to the public Olares Market
• Open or fix a PR to beclab/apps
• Sell an app (pay-to-download / paid listing)
• Produce the listing assets themselves — app icon, Market screenshots / 宣传图
• Write, revise, translate, or review the public Market copy in OlaresManifest.yaml and localized manifests
• Keywords: publish to Market, submit to beclab/apps, app store listing, app description, fullDescription, upgradeDescription, i18n, locale, app icon, metadata.icon, featuredImage / promoteImage, spec.supportArch, multi-arch, GitBot, owners file, price.yaml, paid app

Prerequisite — the app must already run on your Olares. Public submission without a working local install wastes GitBot cycles and reviewer time. Do the deploy loop in the olares-chart skill (its Deploy step) first.