SDK Portfolio - decide which language SDKs your API ships

Decide a public API's language-SDK portfolio - which languages get official SDKs, built how, tiered how, versioned how and retired on what evidence - then write the portfolio strategy and the end-of-life cases. Free in your browser: every language's traffic share and named deal requests against a self-set add-threshold, read through the integrating vertical's language map and the team's fluency, giving each language one action (add, keep, promote, community, self-service, retire, or gather evidence first); the build model ranked by the spec's state, procurement, self-hosting and the flagship case; the three versioning policies kept apart; an exclusive-usage evidence gate before any end-of-life - a portfolio table and a languages CSV. A metered run writes the portfolio strategy, or the end-of-life cases. Built on the SkillSafe skill @samber/sdk-portfolio-strategy, from samber/developer-platform-skills (MIT), by Samuel Berthe.