Clun v0.3.0

Clun 0.3.0

Phase 26: Final hardening, docs, and release.

• SemVer impact: minor within the selected 0.3.0 prerelease train.
• Compatibility snapshot: 30 Yes / 0 Partial / 0 No across 30 generated rows.
• Public baseline: Bun 1.3.14; engineering baseline: Bun c1076ce95e.
• Target release platforms: Linux and macOS, x64 and arm64.
• License: GPL-3.0-or-later.

The canonical evidence and current limitations are in compat/; make compat-validate and make docs-check reject claim drift.

What's Changed

• docs(release): reconcile v0.2.2 publication surfaces by @theesfeld in #335
• chore: exclude fixture JS/Zig/Rust from GitHub Linguist stats by @theesfeld in #337
• feat: shared-memory MT + eliminate hollow node stubs by @theesfeld in #340
• feat: close zero-stubs inventory (#339) by @theesfeld in #341
• fix(release): bind 0.3.0 candidate to Phase 26 #58 for Pages by @theesfeld in #342
• chore(release): prepare v0.3.0 tag surface and exact-master gates by @theesfeld in #343

Full Changelog: v0.2.2...v0.3.0

Clun v0.2.2

Clun 0.2.2

Phase 26: Final hardening, docs, and release.

• SemVer impact: patch within the selected 0.2.2 prerelease train.
• Compatibility snapshot: 30 Yes / 0 Partial / 0 No across 30 generated rows.
• Public baseline: Bun 1.3.14; engineering baseline: Bun c1076ce95e.
• Target release platforms: Linux and macOS, x64 and arm64.
• License: GPL-3.0-or-later.

The canonical evidence and current limitations are in compat/; make compat-validate and make docs-check reject claim drift.

Highlights

• Immutable v0.2.0-dev.1 peels to exact master commit
  184dfa13577ae6f24a7e6dde785a824ef46aa373. Its release run passed Linux x64/arm64 and macOS
  arm64, but macOS x64 exposed an order-dependent fresh-hoist materialization race. Publication was
  skipped, so that tag has no GitHub Release or assets.
• Issue #219 fixes Darwin workspace links across the /tmp to /private/tmp alias,
  makes HTTPS completion frame-aware without weakening truncation checks, keeps
  CookieMap resource evidence strict and deterministic, and removes the runner
  image's unrelated untrusted aws/tap before Homebrew dependency resolution.
• Issue #221 replaces unsafe single-binary updater activation with checksum-verified full-bundle
  installation and an atomic stable-launcher switch.
• Issue #233 restores real public-registry package use in current source: clun add <pkg> and
  Bun-compatible clun install <pkg> now pass live metadata, transitive tarball, SRI, execution, and
  frozen transport-denied reinstall checks. Three v0.2.0-dev.1 release targets reproduced that
  evidence; the published v0.1.0-dev.21 binary still predates the repair.
• Issues #234 and #235 implement the bounded WebPKI profile plus one-shot fatal-alert and reciprocal
  close_notify behavior. CI, Compatibility, and Release exercise them through the complete
  make test-tls chain.
• Issue #241 keeps package downloads concurrent while committing ready packages in deterministic
  ancestor-before-descendant order independent of lockfile member order. Completed bodies wait in
  the verified cache or a cleaned lazy disk spool. Its forced timing regression reverses the
  lockfile package entries and compares identities parsed from the complete fresh and cache-only
  replay layouts before 0.2.0-dev.2 can replace the failed tag-only attempt.
• The default install destination becomes ~/.local/bin; the complete release bundle is retained
  under the XDG data root, and any failed install or update preserves the prior launcher and bundle.
• Tag publication requires successful push-event CI, Documentation, Compatibility, and Pages runs on
  the exact tagged master SHA. Initial publication and immutable reruns redownload exactly four native
  archives plus checksums.txt, require one checksum record per archive, and run strict SHA-256
  verification.
• The train is breaking in intent; Clun records major while publishing the recovery as the
  conventional pre-1.0 minor-core candidate 0.2.0-dev.2.

What's Changed

• docs(release): reconcile v0.2.1 publication surfaces by @theesfeld in #330
• fix(cli): install man page on clun --update by @theesfeld in #332
• fix(release): bind 0.2.2 candidate to Phase 26 issue #58 by @theesfeld in #333
• chore(release): fire Docs+Compat on exact-master for v0.2.2 by @theesfeld in #334

Full Changelog: v0.2.1...v0.2.2

Clun v0.2.1

Clun 0.2.1

Phase 26: Final hardening, docs, and release.

• SemVer impact: patch within the selected 0.2.1 prerelease train.
• Compatibility snapshot: 30 Yes / 0 Partial / 0 No across 30 generated rows.
• Public baseline: Bun 1.3.14; engineering baseline: Bun c1076ce95e.
• Target release platforms: Linux and macOS, x64 and arm64.
• License: GPL-3.0-or-later.

The canonical evidence and current limitations are in compat/; make compat-validate and make docs-check reject claim drift.

Highlights

• Immutable v0.2.0-dev.1 peels to exact master commit
  184dfa13577ae6f24a7e6dde785a824ef46aa373. Its release run passed Linux x64/arm64 and macOS
  arm64, but macOS x64 exposed an order-dependent fresh-hoist materialization race. Publication was
  skipped, so that tag has no GitHub Release or assets.
• Issue #219 fixes Darwin workspace links across the /tmp to /private/tmp alias,
  makes HTTPS completion frame-aware without weakening truncation checks, keeps
  CookieMap resource evidence strict and deterministic, and removes the runner
  image's unrelated untrusted aws/tap before Homebrew dependency resolution.
• Issue #221 replaces unsafe single-binary updater activation with checksum-verified full-bundle
  installation and an atomic stable-launcher switch.
• Issue #233 restores real public-registry package use in current source: clun add <pkg> and
  Bun-compatible clun install <pkg> now pass live metadata, transitive tarball, SRI, execution, and
  frozen transport-denied reinstall checks. Three v0.2.0-dev.1 release targets reproduced that
  evidence; the published v0.1.0-dev.21 binary still predates the repair.
• Issues #234 and #235 implement the bounded WebPKI profile plus one-shot fatal-alert and reciprocal
  close_notify behavior. CI, Compatibility, and Release exercise them through the complete
  make test-tls chain.
• Issue #241 keeps package downloads concurrent while committing ready packages in deterministic
  ancestor-before-descendant order independent of lockfile member order. Completed bodies wait in
  the verified cache or a cleaned lazy disk spool. Its forced timing regression reverses the
  lockfile package entries and compares identities parsed from the complete fresh and cache-only
  replay layouts before 0.2.0-dev.2 can replace the failed tag-only attempt.
• The default install destination becomes ~/.local/bin; the complete release bundle is retained
  under the XDG data root, and any failed install or update preserves the prior launcher and bundle.
• Tag publication requires successful push-event CI, Documentation, Compatibility, and Pages runs on
  the exact tagged master SHA. Initial publication and immutable reruns redownload exactly four native
  archives plus checksums.txt, require one checksum record per archive, and run strict SHA-256
  verification.
• The train is breaking in intent; Clun records major while publishing the recovery as the
  conventional pre-1.0 minor-core candidate 0.2.0-dev.2.

What's Changed

• docs(release): reconcile v0.2.0 publication surfaces by @theesfeld in #312
• fix(roadmap): allow Phase 26 closed after published stable by @theesfeld in #313
• docs(site): un-slop presentation — product copy, less flash by @theesfeld in #315
• docs(site): product narrative — CL-first, Bun-shaped, hero logo right by @theesfeld in #317
• chore(docs): published-complete status narrative (ElonOptimizer P0) by @theesfeld in #319
• feat(cli): man page always matches live CLI (hard rule) by @theesfeld in #321
• chore(elon): complete P1–P3 optimizer bands by @theesfeld in #322
• docs(public): STE100-style accurate README, site, and man page by @theesfeld in #324
• release: bind 0.2.1 candidate to Phase 26 for publish by @theesfeld in #325
• fix(site): wrap matrix columns — no horizontal scroll by @theesfeld in #328
• ci: trigger Compatibility for v0.2.1 exact-SHA gate by @theesfeld in #326
• chore(release): exact-master Docs+Compat for v0.2.1 tag by @theesfeld in #329

Full Changelog: v0.2.0...v0.2.1

Clun v0.2.0

Clun 0.2.0

Phase 26: Final hardening, docs, and release.

• SemVer impact: minor within the selected 0.2.0 prerelease train.
• Compatibility snapshot: 30 Yes / 0 Partial / 0 No across 30 generated rows.
• Public baseline: Bun 1.3.14; engineering baseline: Bun c1076ce95e.
• Target release platforms: Linux and macOS, x64 and arm64.
• License: GPL-3.0-or-later.

The canonical evidence and current limitations are in compat/; make compat-validate and make docs-check reject claim drift.

Highlights

• Immutable v0.2.0-dev.1 peels to exact master commit
  184dfa13577ae6f24a7e6dde785a824ef46aa373. Its release run passed Linux x64/arm64 and macOS
  arm64, but macOS x64 exposed an order-dependent fresh-hoist materialization race. Publication was
  skipped, so that tag has no GitHub Release or assets.
• Issue #219 fixes Darwin workspace links across the /tmp to /private/tmp alias,
  makes HTTPS completion frame-aware without weakening truncation checks, keeps
  CookieMap resource evidence strict and deterministic, and removes the runner
  image's unrelated untrusted aws/tap before Homebrew dependency resolution.
• Issue #221 replaces unsafe single-binary updater activation with checksum-verified full-bundle
  installation and an atomic stable-launcher switch.
• Issue #233 restores real public-registry package use in current source: clun add <pkg> and
  Bun-compatible clun install <pkg> now pass live metadata, transitive tarball, SRI, execution, and
  frozen transport-denied reinstall checks. Three v0.2.0-dev.1 release targets reproduced that
  evidence; the published v0.1.0-dev.21 binary still predates the repair.
• Issues #234 and #235 implement the bounded WebPKI profile plus one-shot fatal-alert and reciprocal
  close_notify behavior. CI, Compatibility, and Release exercise them through the complete
  make test-tls chain.
• Issue #241 keeps package downloads concurrent while committing ready packages in deterministic
  ancestor-before-descendant order independent of lockfile member order. Completed bodies wait in
  the verified cache or a cleaned lazy disk spool. Its forced timing regression reverses the
  lockfile package entries and compares identities parsed from the complete fresh and cache-only
  replay layouts before 0.2.0-dev.2 can replace the failed tag-only attempt.
• The default install destination becomes ~/.local/bin; the complete release bundle is retained
  under the XDG data root, and any failed install or update preserves the prior launcher and bundle.
• Tag publication requires successful push-event CI, Documentation, Compatibility, and Pages runs on
  the exact tagged master SHA. Initial publication and immutable reruns redownload exactly four native
  archives plus checksums.txt, require one checksum record per archive, and run strict SHA-256
  verification.
• The train is breaking in intent; Clun records major while publishing the recovery as the
  conventional pre-1.0 minor-core candidate 0.2.0-dev.2.

What's Changed

• docs(release): reconcile v0.2.0-beta.2 publication surfaces by @theesfeld in #310
• release: stage first stable 0.2.0 — finish Phase 26 by @theesfeld in #311

Full Changelog: v0.2.0-beta.2...v0.2.0

Clun v0.2.0-beta.2

Clun 0.2.0-beta.2

Phase 26: Final hardening, docs, and release.

• SemVer impact: patch within the selected 0.2.0 prerelease train.
• Compatibility snapshot: 30 Yes / 0 Partial / 0 No across 30 generated rows.
• Public baseline: Bun 1.3.14; engineering baseline: Bun c1076ce95e.
• Target release platforms: Linux and macOS, x64 and arm64.
• License: GPL-3.0-or-later.

The canonical evidence and current limitations are in compat/; make compat-validate and make docs-check reject claim drift.

Highlights

• Immutable v0.2.0-dev.1 peels to exact master commit
  184dfa13577ae6f24a7e6dde785a824ef46aa373. Its release run passed Linux x64/arm64 and macOS
  arm64, but macOS x64 exposed an order-dependent fresh-hoist materialization race. Publication was
  skipped, so that tag has no GitHub Release or assets.
• Issue #219 fixes Darwin workspace links across the /tmp to /private/tmp alias,
  makes HTTPS completion frame-aware without weakening truncation checks, keeps
  CookieMap resource evidence strict and deterministic, and removes the runner
  image's unrelated untrusted aws/tap before Homebrew dependency resolution.
• Issue #221 replaces unsafe single-binary updater activation with checksum-verified full-bundle
  installation and an atomic stable-launcher switch.
• Issue #233 restores real public-registry package use in current source: clun add <pkg> and
  Bun-compatible clun install <pkg> now pass live metadata, transitive tarball, SRI, execution, and
  frozen transport-denied reinstall checks. Three v0.2.0-dev.1 release targets reproduced that
  evidence; the published v0.1.0-dev.21 binary still predates the repair.
• Issues #234 and #235 implement the bounded WebPKI profile plus one-shot fatal-alert and reciprocal
  close_notify behavior. CI, Compatibility, and Release exercise them through the complete
  make test-tls chain.
• Issue #241 keeps package downloads concurrent while committing ready packages in deterministic
  ancestor-before-descendant order independent of lockfile member order. Completed bodies wait in
  the verified cache or a cleaned lazy disk spool. Its forced timing regression reverses the
  lockfile package entries and compares identities parsed from the complete fresh and cache-only
  replay layouts before 0.2.0-dev.2 can replace the failed tag-only attempt.
• The default install destination becomes ~/.local/bin; the complete release bundle is retained
  under the XDG data root, and any failed install or update preserves the prior launcher and bundle.
• Tag publication requires successful push-event CI, Documentation, Compatibility, and Pages runs on
  the exact tagged master SHA. Initial publication and immutable reruns redownload exactly four native
  archives plus checksums.txt, require one checksum record per archive, and run strict SHA-256
  verification.
• The train is breaking in intent; Clun records major while publishing the recovery as the
  conventional pre-1.0 minor-core candidate 0.2.0-dev.2.

What's Changed

• docs(release): reconcile v0.2.0-beta.1 publication by @theesfeld in #303
• fix(cli): updater maturity rank, TLS recovery, TTY update notice by @theesfeld in #305
• docs(site): cinematic fluid scroll motion by @theesfeld in #307
• chore(release): bind beta.2 candidate to Phase 26 #58 by @theesfeld in #308
• chore(release): retrigger Compatibility for beta.2 exact-master tag by @theesfeld in #309

Full Changelog: v0.2.0-beta.1...v0.2.0-beta.2

Clun v0.2.0-dev.8

Clun 0.2.0-dev.8

Phase 82: Purity-compatible Bun-surface final audit and release.

• SemVer impact: minor within the selected 0.2.0 prerelease train.
• Compatibility snapshot: 30 Yes / 0 Partial / 0 No across 30 generated rows.
• Public baseline: Bun 1.3.14; engineering baseline: Bun c1076ce95e.
• Target release platforms: Linux and macOS, x64 and arm64.
• License: GPL-3.0-or-later.

The canonical evidence and current limitations are in compat/; make compat-validate and make docs-check reject claim drift.

Highlights

• Immutable v0.2.0-dev.1 peels to exact master commit
  184dfa13577ae6f24a7e6dde785a824ef46aa373. Its release run passed Linux x64/arm64 and macOS
  arm64, but macOS x64 exposed an order-dependent fresh-hoist materialization race. Publication was
  skipped, so that tag has no GitHub Release or assets.
• Issue #219 fixes Darwin workspace links across the /tmp to /private/tmp alias,
  makes HTTPS completion frame-aware without weakening truncation checks, keeps
  CookieMap resource evidence strict and deterministic, and removes the runner
  image's unrelated untrusted aws/tap before Homebrew dependency resolution.
• Issue #221 replaces unsafe single-binary updater activation with checksum-verified full-bundle
  installation and an atomic stable-launcher switch.
• Issue #233 restores real public-registry package use in current source: clun add <pkg> and
  Bun-compatible clun install <pkg> now pass live metadata, transitive tarball, SRI, execution, and
  frozen transport-denied reinstall checks. Three v0.2.0-dev.1 release targets reproduced that
  evidence; the published v0.1.0-dev.21 binary still predates the repair.
• Issues #234 and #235 implement the bounded WebPKI profile plus one-shot fatal-alert and reciprocal
  close_notify behavior. CI, Compatibility, and Release exercise them through the complete
  make test-tls chain.
• Issue #241 keeps package downloads concurrent while committing ready packages in deterministic
  ancestor-before-descendant order independent of lockfile member order. Completed bodies wait in
  the verified cache or a cleaned lazy disk spool. Its forced timing regression reverses the
  lockfile package entries and compares identities parsed from the complete fresh and cache-only
  replay layouts before 0.2.0-dev.2 can replace the failed tag-only attempt.
• The default install destination becomes ~/.local/bin; the complete release bundle is retained
  under the XDG data root, and any failed install or update preserves the prior launcher and bundle.
• Tag publication requires successful push-event CI, Documentation, Compatibility, and Pages runs on
  the exact tagged master SHA. Initial publication and immutable reruns redownload exactly four native
  archives plus checksums.txt, require one checksum record per archive, and run strict SHA-256
  verification.
• The train is breaking in intent; Clun records major while publishing the recovery as the
  conventional pre-1.0 minor-core candidate 0.2.0-dev.2.

What's Changed

• docs(release): reconcile v0.2.0-dev.7 publication surfaces by @theesfeld in #268
• feat: clun publish — npm Yes (0.2.0-dev.8) by @theesfeld in #269

Full Changelog: v0.2.0-dev.7...v0.2.0-dev.8

Clun v0.2.0-dev.7

Clun 0.2.0-dev.7

Phase 82: Purity-compatible Bun-surface final audit and release.

• SemVer impact: major within the selected 0.2.0 prerelease train.
• Compatibility snapshot: 29 Yes / 1 Partial / 0 No across 30 generated rows.
• Public baseline: Bun 1.3.14; engineering baseline: Bun c1076ce95e.
• Target release platforms: Linux and macOS, x64 and arm64.
• License: GPL-3.0-or-later.

The canonical evidence and current limitations are in compat/; make compat-validate and make docs-check reject claim drift.

Highlights

• Immutable v0.2.0-dev.1 peels to exact master commit
  184dfa13577ae6f24a7e6dde785a824ef46aa373. Its release run passed Linux x64/arm64 and macOS
  arm64, but macOS x64 exposed an order-dependent fresh-hoist materialization race. Publication was
  skipped, so that tag has no GitHub Release or assets.
• Issue #219 fixes Darwin workspace links across the /tmp to /private/tmp alias,
  makes HTTPS completion frame-aware without weakening truncation checks, keeps
  CookieMap resource evidence strict and deterministic, and removes the runner
  image's unrelated untrusted aws/tap before Homebrew dependency resolution.
• Issue #221 replaces unsafe single-binary updater activation with checksum-verified full-bundle
  installation and an atomic stable-launcher switch.
• Issue #233 restores real public-registry package use in current source: clun add <pkg> and
  Bun-compatible clun install <pkg> now pass live metadata, transitive tarball, SRI, execution, and
  frozen transport-denied reinstall checks. Three v0.2.0-dev.1 release targets reproduced that
  evidence; the published v0.1.0-dev.21 binary still predates the repair.
• Issues #234 and #235 implement the bounded WebPKI profile plus one-shot fatal-alert and reciprocal
  close_notify behavior. CI, Compatibility, and Release exercise them through the complete
  make test-tls chain.
• Issue #241 keeps package downloads concurrent while committing ready packages in deterministic
  ancestor-before-descendant order independent of lockfile member order. Completed bodies wait in
  the verified cache or a cleaned lazy disk spool. Its forced timing regression reverses the
  lockfile package entries and compares identities parsed from the complete fresh and cache-only
  replay layouts before 0.2.0-dev.2 can replace the failed tag-only attempt.
• The default install destination becomes ~/.local/bin; the complete release bundle is retained
  under the XDG data root, and any failed install or update preserves the prior launcher and bundle.
• Tag publication requires successful push-event CI, Documentation, Compatibility, and Pages runs on
  the exact tagged master SHA. Initial publication and immutable reruns redownload exactly four native
  archives plus checksums.txt, require one checksum record per archive, and run strict SHA-256
  verification.
• The train is breaking in intent; Clun records major while publishing the recovery as the
  conventional pre-1.0 minor-core candidate 0.2.0-dev.2.

What's Changed

• docs(release): reconcile v0.2.0-dev.6 publication surfaces by @theesfeld in #260
• feat: secrets Yes (pure-CL vault) + colored CLI (0.2.0-dev.7) by @theesfeld in #264
• feat: native-addons Yes — machine load/hook (0.2.0-dev.7) by @theesfeld in #266

Full Changelog: v0.2.0-dev.6...v0.2.0-dev.7

Clun v0.2.0-dev.6

Clun 0.2.0-dev.6

Phase 82: Purity-compatible Bun-surface final audit and release.

• SemVer impact: major within the selected 0.2.0 prerelease train.
• Compatibility snapshot: 27 Yes / 3 Partial / 0 No across 30 generated rows.
• Public baseline: Bun 1.3.14; engineering baseline: Bun c1076ce95e.
• Target release platforms: Linux and macOS, x64 and arm64.
• License: GPL-3.0-or-later.

The canonical evidence and current limitations are in compat/; make compat-validate and make docs-check reject claim drift.

Highlights

• Immutable v0.2.0-dev.1 peels to exact master commit
  184dfa13577ae6f24a7e6dde785a824ef46aa373. Its release run passed Linux x64/arm64 and macOS
  arm64, but macOS x64 exposed an order-dependent fresh-hoist materialization race. Publication was
  skipped, so that tag has no GitHub Release or assets.
• Issue #219 fixes Darwin workspace links across the /tmp to /private/tmp alias,
  makes HTTPS completion frame-aware without weakening truncation checks, keeps
  CookieMap resource evidence strict and deterministic, and removes the runner
  image's unrelated untrusted aws/tap before Homebrew dependency resolution.
• Issue #221 replaces unsafe single-binary updater activation with checksum-verified full-bundle
  installation and an atomic stable-launcher switch.
• Issue #233 restores real public-registry package use in current source: clun add <pkg> and
  Bun-compatible clun install <pkg> now pass live metadata, transitive tarball, SRI, execution, and
  frozen transport-denied reinstall checks. Three v0.2.0-dev.1 release targets reproduced that
  evidence; the published v0.1.0-dev.21 binary still predates the repair.
• Issues #234 and #235 implement the bounded WebPKI profile plus one-shot fatal-alert and reciprocal
  close_notify behavior. CI, Compatibility, and Release exercise them through the complete
  make test-tls chain.
• Issue #241 keeps package downloads concurrent while committing ready packages in deterministic
  ancestor-before-descendant order independent of lockfile member order. Completed bodies wait in
  the verified cache or a cleaned lazy disk spool. Its forced timing regression reverses the
  lockfile package entries and compares identities parsed from the complete fresh and cache-only
  replay layouts before 0.2.0-dev.2 can replace the failed tag-only attempt.
• The default install destination becomes ~/.local/bin; the complete release bundle is retained
  under the XDG data root, and any failed install or update preserves the prior launcher and bundle.
• Tag publication requires successful push-event CI, Documentation, Compatibility, and Pages runs on
  the exact tagged master SHA. Initial publication and immutable reruns redownload exactly four native
  archives plus checksums.txt, require one checksum record per archive, and run strict SHA-256
  verification.
• The train is breaking in intent; Clun records major while publishing the recovery as the
  conventional pre-1.0 minor-core candidate 0.2.0-dev.2.

What's Changed

• docs(release): reconcile v0.2.0-dev.5 publication surfaces by @theesfeld in #254
• docs(site): kill bar chart; green Yes cells; elevate npm + secrets by @theesfeld in #256
• fix(tls): silence system CA parse warnings (0.2.0-dev.6) by @theesfeld in #258

Full Changelog: v0.2.0-dev.5...v0.2.0-dev.6

Clun v0.2.0-dev.5

Clun 0.2.0-dev.5

Phase 82: Purity-compatible Bun-surface final audit and release.

• SemVer impact: major within the selected 0.2.0 prerelease train.
• Compatibility snapshot: 27 Yes / 3 Partial / 0 No across 30 generated rows.
• Public baseline: Bun 1.3.14; engineering baseline: Bun c1076ce95e.
• Target release platforms: Linux and macOS, x64 and arm64.
• License: GPL-3.0-or-later.

The canonical evidence and current limitations are in compat/; make compat-validate and make docs-check reject claim drift.

Highlights

• Immutable v0.2.0-dev.1 peels to exact master commit
  184dfa13577ae6f24a7e6dde785a824ef46aa373. Its release run passed Linux x64/arm64 and macOS
  arm64, but macOS x64 exposed an order-dependent fresh-hoist materialization race. Publication was
  skipped, so that tag has no GitHub Release or assets.
• Issue #219 fixes Darwin workspace links across the /tmp to /private/tmp alias,
  makes HTTPS completion frame-aware without weakening truncation checks, keeps
  CookieMap resource evidence strict and deterministic, and removes the runner
  image's unrelated untrusted aws/tap before Homebrew dependency resolution.
• Issue #221 replaces unsafe single-binary updater activation with checksum-verified full-bundle
  installation and an atomic stable-launcher switch.
• Issue #233 restores real public-registry package use in current source: clun add <pkg> and
  Bun-compatible clun install <pkg> now pass live metadata, transitive tarball, SRI, execution, and
  frozen transport-denied reinstall checks. Three v0.2.0-dev.1 release targets reproduced that
  evidence; the published v0.1.0-dev.21 binary still predates the repair.
• Issues #234 and #235 implement the bounded WebPKI profile plus one-shot fatal-alert and reciprocal
  close_notify behavior. CI, Compatibility, and Release exercise them through the complete
  make test-tls chain.
• Issue #241 keeps package downloads concurrent while committing ready packages in deterministic
  ancestor-before-descendant order independent of lockfile member order. Completed bodies wait in
  the verified cache or a cleaned lazy disk spool. Its forced timing regression reverses the
  lockfile package entries and compares identities parsed from the complete fresh and cache-only
  replay layouts before 0.2.0-dev.2 can replace the failed tag-only attempt.
• The default install destination becomes ~/.local/bin; the complete release bundle is retained
  under the XDG data root, and any failed install or update preserves the prior launcher and bundle.
• Tag publication requires successful push-event CI, Documentation, Compatibility, and Pages runs on
  the exact tagged master SHA. Initial publication and immutable reruns redownload exactly four native
  archives plus checksums.txt, require one checksum record per archive, and run strict SHA-256
  verification.
• The train is breaking in intent; Clun records major while publishing the recovery as the
  conventional pre-1.0 minor-core candidate 0.2.0-dev.2.

What's Changed

• feat(node): Phase 47 residual — node:url legacy module by @theesfeld in #100
• feat(transpiler): ambient declare enum strip (language.typescript Partial) by @theesfeld in #101
• feat(runtime): Phase 38 Partial — Response/Request.body ReadableStream by @theesfeld in #105
• feat(test-runner): pure-CL bun:test module resolve (Partial) by @theesfeld in #103
• test(shell): close chmod-000 ls permission residual (#39) by @theesfeld in #102
• feat(server): Phase 51 WebSocket constitutional checkpoint by @theesfeld in #107
• feat(transport): Phase 28 foundation + real compat gate IDs by @theesfeld in #95
• docs(release): reconcile v0.1.0-dev.21 publication boundary by @theesfeld in #119
• fix(compat): stabilize password-hashing async-hash tick race by @theesfeld in #117
• feat(engine): Phase 37 m3 Set methods (Refs #11) by @theesfeld in #109
• feat(secrets): Phase 58 OS secrets constitutional checkpoint by @theesfeld in #106
• fix(shell): inventory burn-down + unmatched-glob fail (Partial) by @theesfeld in #111
• feat(shell): parser lex/parse corpus burn-down (101/102) by @theesfeld in #122
• feat(test): cooperative test.concurrent / describe.concurrent (#40) by @theesfeld in #110
• feat(node): pure-CL path.win32 residual (#108) by @theesfeld in #114
• feat(runtime): spawn residual — object form, AbortSignal, timeout, ref/unref by @theesfeld in #112
• feat(server): Phase 49 lifecycle Partial (idleTimeout / body limit / stop force) by @theesfeld in #113
• test(shell): credit lifecycle+pipeline residual corpus sites by @theesfeld in #123
• feat(websocket): Phase 51 M1 handshake + framing (Partial) by @theesfeld in #124
• feat(shell): language residual export isolation + 118 corpus closes (Partial) by @theesfeld in #125
• feat(shell): tooling.shell Partial→Yes — zero pending corpus by @theesfeld in #126
• fix(docs): bind Phase 65 active release to issue #39 by @theesfeld in #141
• feat(node): pure-CL node:fs residual gaps (#132) by @theesfeld in #144
• feat(cron): pure-CL Clun.cron parse + in-process jobs (Phase 76) by @theesfeld in #146
• feat(archive): pure-CL gzip/deflate/zip + Clun.Archive (Phase 74) by @theesfeld in #157
• fix(docs): bind Phase 74 active release to issue #48 by @theesfeld in #166
• feat(test): tooling.test-runner Partial→Yes by @theesfeld in #152
• feat(runtime): pure-CL WritableStream + TransformStream by @theesfeld in #156
• feat(websocket): server.websocket Partial→Yes (#129) by @theesfeld in #163
• feat(webstd): runtime.web-standard-apis Partial→Yes by @theesfeld in #159
• feat(runtime): pure-CL Clun.markdown + HTMLRewriter (Phase 75) by @theesfeld in #164
• feat(typescript): language.typescript Partial→Yes (#133) by @theesfeld in #154
• feat(server): server.http Partial→Yes at 0.1.0-dev.43 (#128) by @theesfeld in #170
• feat(npm): package-manager.npm Partial→Yes at 0.1.0-dev.44 (#131) by @theesfeld in #140
• feat(node): runtime.node-compatibility Partial→Yes (#132) by @theesfeld in #176
• docs(full-port): permanent law + honesty scrub — qualified Yes is No (#177) by @theesfeld in #193
• feat(jsx): language.jsx full port → Yes at 0.1.0-dev.46 (#186) by @theesfeld in #195
• feat(pm): package-manager.monorepo No→Yes — workspaces + filters (#182) by @theesfeld in #196
• feat(secrets): security.encrypted-secrets Yes — pure-CL vault exceeding Bun.secrets by @theesfeld in #194
• feat(plugins): runtime.loader-plugins Yes — pure-CL Bun.plugin host (#187) by @theesfeld in #197
• feat(redis): database.redis full port → Yes at 0.1.0-dev.50 by @theesfeld in #198
• feat(hot-reload): tooling.hot-reload → Yes — pure-CL --hot full port (#188) by @theesfeld in #200
• feat(s3): cloud.s3 No→Yes — pure-CL SigV4 client exceeding Bun.s3 by @theesfeld in #199
• feat(sql): database.sql-drivers No→Yes — pure-CL PG/MySQL/SQLite (#183) by @theesfeld in #201
• feat(bundler): tooling.bundler No→Yes — pure-CL Clun.build full port (#180) by @theesfeld in #202
• feat(frontend-dev): tooling.frontend-dev-server → Yes — pure-CL HTML entry + HMR (#189) by @theesfeld in #204
• chore(docs): drop multi-agent train staffing rules from AGENTS.md by @theesfeld in #206
• chore(docs): bind active release to Phase 68 issue #42 by @theesfeld in #208
• feat(sfe): tooling.single-file-executables full port → Yes at 0.1.0-dev.57 by @theesfeld in #203
• feat(typescript): language.typescript full port → Yes at 0.1.0-dev.59 (#192) by @theesfeld in #211
• feat(engine): Phase 37 m4 keyed Promise combinators (Refs #11) by @theesfeld in #158
• feat(webstd): runtime.web-standard-apis Partial→Yes at 0.1.0-dev.64 by @theesfeld in #210
• feat(fmt-lint): tooling.formatter-linter full port → Yes at 0.1.0-dev.65 by @theesfeld in #212
• feat(ffi): runtime.native-addons full port → Yes at 0.1.0-dev.66 by @theesfeld in #213
• feat(node): runtime.node-comp...

Clun v0.2.0-dev.11

Clun 0.2.0-dev.11

Phase 82: Purity-compatible Bun-surface final audit and release.

• SemVer impact: patch within the selected 0.2.0 prerelease train.
• Compatibility snapshot: 30 Yes / 0 Partial / 0 No across 30 generated rows.
• Public baseline: Bun 1.3.14; engineering baseline: Bun c1076ce95e.
• Target release platforms: Linux and macOS, x64 and arm64.
• License: GPL-3.0-or-later.

The canonical evidence and current limitations are in compat/; make compat-validate and make docs-check reject claim drift.

Highlights

• Immutable v0.2.0-dev.1 peels to exact master commit
  184dfa13577ae6f24a7e6dde785a824ef46aa373. Its release run passed Linux x64/arm64 and macOS
  arm64, but macOS x64 exposed an order-dependent fresh-hoist materialization race. Publication was
  skipped, so that tag has no GitHub Release or assets.
• Issue #219 fixes Darwin workspace links across the /tmp to /private/tmp alias,
  makes HTTPS completion frame-aware without weakening truncation checks, keeps
  CookieMap resource evidence strict and deterministic, and removes the runner
  image's unrelated untrusted aws/tap before Homebrew dependency resolution.
• Issue #221 replaces unsafe single-binary updater activation with checksum-verified full-bundle
  installation and an atomic stable-launcher switch.
• Issue #233 restores real public-registry package use in current source: clun add <pkg> and
  Bun-compatible clun install <pkg> now pass live metadata, transitive tarball, SRI, execution, and
  frozen transport-denied reinstall checks. Three v0.2.0-dev.1 release targets reproduced that
  evidence; the published v0.1.0-dev.21 binary still predates the repair.
• Issues #234 and #235 implement the bounded WebPKI profile plus one-shot fatal-alert and reciprocal
  close_notify behavior. CI, Compatibility, and Release exercise them through the complete
  make test-tls chain.
• Issue #241 keeps package downloads concurrent while committing ready packages in deterministic
  ancestor-before-descendant order independent of lockfile member order. Completed bodies wait in
  the verified cache or a cleaned lazy disk spool. Its forced timing regression reverses the
  lockfile package entries and compares identities parsed from the complete fresh and cache-only
  replay layouts before 0.2.0-dev.2 can replace the failed tag-only attempt.
• The default install destination becomes ~/.local/bin; the complete release bundle is retained
  under the XDG data root, and any failed install or update preserves the prior launcher and bundle.
• Tag publication requires successful push-event CI, Documentation, Compatibility, and Pages runs on
  the exact tagged master SHA. Initial publication and immutable reruns redownload exactly four native
  archives plus checksums.txt, require one checksum record per archive, and run strict SHA-256
  verification.
• The train is breaking in intent; Clun records major while publishing the recovery as the
  conventional pre-1.0 minor-core candidate 0.2.0-dev.2.

What's Changed

• docs(release): reconcile v0.2.0-dev.10 publication surfaces by @theesfeld in #279
• fix(cli): human errors + animated install + spawn ownership by @theesfeld in #281

Full Changelog: v0.2.0-dev.10...v0.2.0-dev.11