release: promote accepted Temporal 0.1.1 stable

[bobisme]

Stable package promotion

Prepare Temporal 0.1.1 from the accepted 0.1.1-rc.1 component and unchanged
project-side Lua companion. This does not publish a Rust crate: the
publish = false runtime crate remains at its accepted 0.1.1-rc.1 identity,
with Cargo.lock, runtime, helper, WIT, dependencies and release controls unchanged.
The package/crate split follows the earlier 0.1.0 promotion.

The stable package manifest changes to 0.1.1. Tests explicitly pin the frozen
runtime crate and retain the closed version-family, host and capability checks.
Docs record RC acceptance, correct the 65-second Start typo (only close-event
History permits 65 seconds), and use conditional 0.1.1 install examples.

Evidence and gates

• CAPI accepted the exact RC and companion: five profiles, 10 scenarios,
  319 unchanged assertions and both expected-RED fingerprints. The addendum
  closes human-output and explicit server-not-found evidence. CAPI's reviewed
  caller intentionally awaits a stable pin; no RC merge is required.
• Full pinned-public-host just check passed; 12 actual component calls passed.
  Three legacy source-host packaging integrations explicitly skipped; all
  public release-host integrations ran.
• Rebuilt component is byte-identical to the accepted RC:
  b427ab70cb4643c771996a3610456872e4ed50e49f24fe8859186a654833a7b8.
• Independent clean reproduction agrees. Repeated local packages, public
  canonical-writer parity and destination-reuse rejection passed.
• Exact-range security review: Seal cr-2u4rcc,
  base 103aed1 through
  2f5b83ff774a3a1881a4222fb03a6153a79b13fa. The lead verifies the actual vote
  before opening this PR.

Publication remains a separate first-attempt candidate build, independent
approval of the final source and three downloaded asset hashes, fresh immutable
control readback, and a one-shot provenance publisher. No stable-artifact CAPI
run or publication is claimed by this PR.