release: promote Swagger Petstore examples

[sjungwon03]

Summary

Closes #19.

Promote the reviewed Swagger Petstore examples from dev to release-only main.

• Exact source: bc99aceff608af7e66de6ca3f1bcf3a9e4e7823b
• Main is a verified ancestor of current dev after reconciliation PR chore(release): reconcile main history into dev #18.
• Feature work was independently approved in PR feat: add read-only Swagger Petstore agent examples #16 at its exact head; reconciliation PR chore(release): reconcile main history into dev #18 was separately approved as a zero-content-delta, two-parent merge.

Included product behavior

• Fixed-host, GET-only Swagger Petstore v2 client with timeout and response validation.
• TypeMCP wrapper exposing exactly search_available_pets, get_pet, and get_petstore_inventory.
• Deterministic TypeChain workflow using createTypeMcpLangChainTools() to invoke the adapted read-only MCP tool.
• Offline fixture tests, manual live smoke examples, and documentation of public demo volatility plus no-LLM/no-MCP-transport boundaries.

Required promotion evidence

• Current source is dev as enforced by .github/workflows/release-promotion.yml.
• verify and release-promotion must both pass on this PR's exact source head.
• Fresh independent review must approve that exact source head.
• Review threads must be resolved before squash merge, per the main-release ruleset.

[sjungwon03-ai]

Formal independent review at exact HEAD bc99ace.

(1) Head matches current dev; main (3d07fa8) is a verified ancestor (behind_by 0).
(2) Diff is scoped to the reviewed Swagger Petstore feature: 10 added example/test/doc files, README doc update, and 4 package.json scripts. No dependency, lockfile, override, or .github/workflow changes.
(3) Client fixes https://petstore.swagger.io/v2, issues only GET, validates responses with Zod, applies AbortSignal timeout, and exposes no credential, configurable host, or write path.
(4) TypeMCP server declares exactly search_available_pets, get_pet, and get_petstore_inventory with Zod input schemas.
(5) TypeChain workflow uses createTypeMcpLangChainTools (in-process adapter) with an explicit resolver; no model provider, MCP client, or transport is created — documented honestly in-code and in README.
(6) Tests inject fixture fetch; CI runs no live Petstore requests; README and planning doc accurately disclose public-demo volatility and the no-LLM/no-transport boundary.
(7) verify and release-promotion are SUCCESS at this exact HEAD; main-release ruleset is active; zero unresolved threads.

APPROVE.