v0.2.12

Release-candidate validation:

• The named product candidate validation
  passed private-corpus-001 check exit 0/0
  diagnostics and tests 12,315/12,315 with 0 failed/compile/runtime/unsupported;
  private-corpus-002 check exit 0/0 diagnostics and tests 782/782 with the
  same zero failures.
• The public corpus covered 86 projects with 40 expected/40 observed
  diagnostics, zero missing/unexpected/unclassified, and an exact identity
  multiset match. Public diagnostics are the known baseline, not passes.
• The Salesforce current-release gate recorded 475/475 pass, zero
  fail/inconclusive, and cleanup PASS. This validates the named product
  candidate. Promotion is valid only after these counts are reproduced by fresh
  exact-SHA gates for the tagged candidate; no prior candidate evidence carries
  forward.

Salesforce release upgrades:

• Added moving-correctness support for source API 65.0, 66.0, and 67.0 while
  retaining endpoint API 60.0, 65.0, 66.0, and 67.0. The default remains 65.0;
  malformed or future Apex project versions and unsupported Execute Anonymous,
  LWC, or endpoint versions fail rather than silently falling back.
• Preserved valid historical Apex project versions through project loading,
  per-file analysis, glade check, glade test, and package artifacts without
  adding them to the checked 65.0-67.0 parity window. Historical versions
  receive no parity credit. Execute Anonymous and LWC bundle versions remain
  limited to the checked window.
• Made Apex semantic availability, LWC module availability, REST and Tooling
  routing, anonymous execution, DAP, playground caching, and org bindings keep
  their explicit source or endpoint API version.
• Added generated availability tables from the checked Salesforce release
  contract, including API-versioned Tooling discovery and explicit unsupported
  boundaries for System.IntegrationTest and PlatformEventMigration.
• Added release-bound behavior for API 66 complex LWC expressions, invocable
  parameter constructor visibility, and Automated Process WITH USER_MODE,
  plus API 67 <details name>, elastic async-limit keys, sharing defaults, and
  database user-mode defaults.
• Kept hosted-only Named Credentials identity-provider changes, Invocable Apex
  REST actions, and OpenAPI specification generation as tested, explicit
  non-parity instead of claiming local runtime support.
• Bound each release inventory to an exporter-generated source receipt that
  preserves the exact Atlas family hashes and the latest current-only LWC
  source/filter provenance.
• The Salesforce promotion gate now checks generated drift, installs the real
  LWC compiler, rejects binaries not built from the named clean commits,
  records candidate hashes and the complete Go test event log, and closes exact
  surface, behavior, source, endpoint, org-profile, release-note, and
  no-fallback denominators before promotion.
• Standard SObject instance-field assignments no longer produce a static-field
  diagnostic.
• Project-referenced numeric fields no longer depend on whether an integer or
  decimal literal was observed first.
• Custom platform-event EventUuid and ReplayId fields now resolve for Apex
  access and SOQL queries.

Local checks and releases:

• Local-test progress event rendering is serialized so concurrent workers
  cannot corrupt terminal or NDJSON output.

Distribution and upgrades:

• The release workflow publishes parser-capable macOS and Linux archives for
  AMD64 and ARM64, SHA256SUMS.txt, CycloneDX SBOMs, and provenance
  attestations. Verify the checksum and run glade doctor as described in the
  distribution workflow.
• No migration is required for documented CLI flags, database schemas, or server
  API behavior. The default local API version remains v65.0.
• Known hosted gaps remain explicit in
  KNOWN_GAPS.md.
  Local deterministic mocks and explicit non-parity outcomes are not hosted
  Salesforce support.