控制审核、风险、财务、提现和审计链路。

OAuth state protects provider redirects from forged callbacks.

Email login codes are HMAC-hashed and cannot verify without a stable secret.

Email signup and login require persisted short-lived verification challenges.

Production must not expose login codes in API responses; the gateway suppresses previews even if this flag is misconfigured.

Webhook outbox delivery needs processing state, last-attempt timestamps, and due-event indexes.

The operating product depends on database-backed accounts, skills, ledger, reviews, and notifications.

Production updates should run the migration runner before rebuilding API and web containers.

Publisher/developer/admin dashboards require operational tables beyond the public registry.

Automated review checks need structured repair metadata so publishers and reviewers can see blockers, target fields, and next actions.

Buyer request submissions need an exact delivered skill version, delivery note, evidence URL, submitted time, and buyer decision record.

Publisher responses turn moderated buyer feedback into a public maintenance and trust loop.

External delivery queues need attempt, retry, provider, and error fields.

Templates make operational communication editable without code deploys; launch needs the required account, review, runtime, billing, payout, buyer-request, feedback, trust, curation, and delivery-operation rows.

Runtime API key hashing needs a stable salt for production verification.

Public launch needs enough verified supply that buyers are not evaluating an empty marketplace.

Supplier diversity keeps SkillHub from looking like a single-team catalog.

Developer-side project state proves listings become governed agent workspace state.

Successful invocations prove the runtime gateway, policy checks, logging, and metering path work.

Published feedback gives buyers public trust evidence and gives publishers a reason to return.

Publishers need payout-account submission sessions and payout-request state before paid marketplace launch.

P0 paid marketplace payout setup uses publisher-submitted PayPal or Alipay receiving details for finance to transfer manually.

Blocked or failed payouts need durable retry conditions and next-action state.

Paid publishing needs a durable record of the accepted operating terms version and accepting user.

OAuth returns, docs links, and product navigation need the public app URL.

Production operations should not silently show bundled demo data when APIs fail.

Direct public token signup should stay disabled after email-code signup exists.

The service token remains a controlled recovery path for initial operators.

Connected login identity storage supports Google, GitHub, email, and account center security.