Developers
Developers now acts as the Day 6 supply source of truth: supplier identity and provider endpoint access models are fixed before marketplace listings, live installs, and payout flows go live.
Module Entry Map
Developers module entry map
Day 9 leaves the supplier-side subroutes in place now, so identity review, endpoint management, service offerings, and onboarding do not need to appear as late navigation after the first real mutation work starts.
Developers
把 developer identity、endpoint、offering、onboarding 这些二级入口提前固定下来，避免后面接审核或 mutation 时再返工导航。
Identity Review
In Code为个人、企业、域名所有者三类 developer identity 预留独立 verification / operator note 入口。
Endpoint Catalog
In Code为 first-party、remote API、self-hosted、domain-mapped endpoint 预留独立目录入口。
Service Offerings
In Code为 service offering、pricing model、install eligibility 与 commercial scope 预留独立目录入口。
Onboarding Queue
In Code为 supplier onboarding、identity readiness、endpoint readiness、payout readiness 预留统一队列入口。
Developer Supply
Developer identity and endpoint access now share one supply foundation
Module 5 Day 6 now fixes how provider endpoints enter the supply side after identity selection but before live onboarding, verification automation, and marketplace installs. First-party, remote API, self-hosted, and domain-mapped access patterns now resolve through the same shared platform truth.
Service boundary: foundation-control-plane-service · demo:error
Verified identities
--
Healthy endpoints
--
Active offerings
--
Developer supply state
Developer supply data could not be loaded
This error-state demo models the supply foundation failing before developer profiles, endpoints, or offerings can render.
We need this shell now so later onboarding, domain verification, and endpoint health checks can fail without redesigning the console.