chore(release): promote next to main

[ss-o]

Promotion readiness record

This is the reviewed same-repository next to main promotion. It updates the Git-consumed main branch but does not create a tag or GitHub release.

Candidate identity

• Prior main SHA: 68038088a2d92b65f9a86fd74bc8fe85a0c40150
• Candidate next SHA: 5878fcc1d6d1fd85682c30618ecf353e08f1b2db
• Complete compare: 68038088...5878fcc

The PR head SHA must still equal the recorded candidate SHA before merge.

Required validation

The Promotion gate check is required by the active main ruleset alongside Guard main branch source. It fails if any constituent below fails, is cancelled, or is skipped.

Validation	Stable job name	Result
Zsh syntax and compile	Zsh syntax and compile	Success
ZD ZUnit integration, including compatibility suite	ZD integration	Success
Trunk	Trunk	Success
CodeQL	CodeQL	Success
Exact-candidate clean install and startup	Clean install and startup	Success
Aggregate	Promotion gate	Success

• z-shell/zd#95 merged immutable Zi-SHA support.
• z-shell/zd#96 merged focused compatibility tests.
• z-shell/zd#107 scoped those tests explicitly to next promotions.
• The candidate SHA is unchanged after all required checks complete.
• Reconciliation PR chore: reconcile promotion bootstrap into next #400 made main an ancestor of next.
• PRs fix(ci): align commit lint with org policy #401 through test(version): cover reporting across checkout states #404 produced the current candidate, and every required check above completed successfully on its exact head SHA.

Readiness review

Unresolved issues and dispositions

• Define semantic-tag publication flow for zi #346: semantic-tag publication remains separate and is explicitly out of scope; this PR creates no tag or release.
• Completion refresh misses newly generated completions #349: completion refresh remains an open, independently tracked runtime bug; this promotion does not claim to resolve it.
• chore(deps): align dependency automation config #352: the blocked Renovate rollout is excluded. Dependabot remains active until hosted Renovate processing is separately verified.
• build(deps): bump trunk-io/trunk-action from 1.2.4 to 2.0.0 #395: the stale Dependabot PR targeting main is excluded; the candidate's Dependabot configuration routes future GitHub Actions updates to next.
• No security issue or failed required validation is being waived by this record.

User-facing and migration notes

• adds zi version, zi --version, and zi -V; they report the exact Git tag, the abbreviated commit for an untagged checkout, or unknown when Git metadata is unavailable;
• restores documented compatibility helpers, aliases, timing flags, and deterministic self-update behavior discovered during promotion review;
• adds CMake-aware module builds, prebuilt module retrieval, and release-candidate asset discovery with legacy fallback behavior;
• removes the unallocated X from PMSPEC; organization-wide consumer inspection found no reader of that capability;
• modernizes repository CI, branch governance, contribution guidance, and public-contract impact reporting;
• removes stale repository automation and metadata that no longer matched organization policy.

No migration is required for supported usage: the version command is additive, the runtime changes restore or preserve documented contracts, module changes retain fallback paths, and the removed PMSPEC letter was unallocated and had no identified consumer.

Public-contract follow-ups

• ci: generate a public-contract impact report for behavioral changes #376 / ci(contract): add public impact gate #383 add a deterministic public-contract impact gate and SHA-pinned consumer evidence covering wiki, docs, src, zd, annexes, and compatibility consumers.
• The contract manifest is introduced by this promotion, so the main...next report identifies monitored-surface additions but cannot enumerate changes that predate the baseline. The user-facing notes above include the resulting manual historical inventory item for the version command.
• The PMSPEC documentation follow-up remains linked from PMSPEC advertises an unallocated X capability letter #393 to z-shell/wiki#859.
• No automatic cross-repository edit or publication is included in this promotion.

Rollback readiness

• Rollback owner: @ss-o
• Observable rollback criteria:
  • required validation later proves nondeterministic or materially incomplete;
  • a clean install or shell startup fails at the promoted main head;
  • the ZD compatibility suite identifies a promoted contract regression;
  • a user-blocking regression is reproduced and cannot be safely corrected with a narrower hotfix.
• Prior main SHA recorded above.
• Rollback path is a same-repository hotfix-* PR reverting the promotion commit through protected main.
• The revert PR will run Guard main branch source and Promotion gate.
• No force-push rollback will be used.

After any revert, clean install and startup must be confirmed at the new main head.

Publication boundary

Merging this PR changes main only. A semantic tag and GitHub release remain separately approved publication actions under #346, with independent release notes and green validation.

Closes #376
Closes #377