chore(ts-sdk): bump publish version to 0.1.1

[Lythaeon]

Description

Bump the TypeScript SDK release surface from 0.1.0 to 0.1.1 so npm publish can proceed after 0.1.0 became unreusable. This keeps the SDK and all six native runtime packages on a single consistent release version and updates the checked-in release examples to match.

Changes

• sdks/typescript/package.json: bump main SDK version to 0.1.1
• sdks/typescript/native/*/package.json: bump all six native runtime packages to 0.1.1
• sdks/typescript/src/app.ts: update exported typeScriptSdkVersion constant to 0.1.1
• sdks/typescript/src/runtime/runtime-extension.test.ts: update fixed SDK version expectations
• sdks/typescript/src/runtime/runtime-extension-stdio.test.ts: update fixed SDK version expectations
• sdks/typescript/RELEASING.md: update release tag example to ts-sdk-v0.1.1
• Architecture/runtime impact: none beyond publish/version metadata; no API or behavior change

For slice-related changes, include:

• Affected slices: TypeScript SDK packaging/release surface only
• Cross-slice communication changes (if any) and why: none
• Migration requirements (if any): npm release should use ts-sdk-v0.1.1 instead of ts-sdk-v0.1.0

Motivation

Business motivation:

The previous 0.1.0 publish attempt made that exact npm version unavailable for reuse, so a new publishable SDK version is required.

Technical motivation:

All publishable packages and internal SDK version markers need to remain aligned or the release workflow will reject the tag and metadata checks will fail.

Alternative approaches considered:

• Reusing 0.1.0: not viable because npm does not allow reusing a previously published package version

Scope and impact

• Affected slices: sdks/typescript and native runtime package manifests
• Data/API changes: none
• Backward compatibility: fully backward compatible; version metadata only
• Performance impact: none
• Security impact: none

Testing

• Unit tests
• Integration tests
• Manual verification
• Performance checks (if applicable)
• Security checks (if applicable)

Commands/results:

pnpm --dir sdks/typescript run check
act workflow_dispatch -W .github/workflows/release-typescript-sdk.yml -e /tmp/release-sdk-event-011.json -j verify --container-architecture linux/amd64

Results:

• pnpm --dir sdks/typescript run check: passed
• Release workflow verify job under act/Docker: passed with SDK version 0.1.1

Related issues and documentation

• Fixes: npm republish blockage for 0.1.0
• Related: upcoming ts-sdk-v0.1.1 release tag on main
• Architecture docs: docs/architecture/README.md
• Relevant ARD/ADR:
• Operations/runbook updates: sdks/typescript/RELEASING.md updated for the new example tag

Reviewer checklist

• Code follows project standards and architecture constraints
• Slice boundaries are respected (docs/architecture/ard/0003-slice-dependency-contracts.md)
• Tests added/updated and passing
• Documentation updated (README/docs/operations as needed)
• No undocumented breaking change
• Performance trade-offs documented where relevant
• Security considerations addressed where relevant

Additional notes

This PR intentionally does not move any release tags. After merge, the publish flow should tag main with ts-sdk-v0.1.1 only.