feat(setup): add versioned TUI engine artifacts - #224
Merged
Merged
Conversation
…ntract # Conflicts: # docs/README.md
This was referenced Sep 20, 2026
Deploying src with
|
| Latest commit: |
70944a8
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://c3f1f12e.zi-src.pages.dev |
| Branch Preview URL: | https://feature-222.zi-src.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The guided setup planner currently requires clients to understand human output, internal paths, plan hashes, and partial failure behavior. This adds a versioned machine interface so a future TUI can discover the environment, review an exact plan, and report phase results without duplicating installer logic.
Changes
describe --output DIRdiscovery with atomic directory artifactsapply --result DIRartifacts with stable error codes and exit statuseszunitonly as a compatibility profile for existing installationsmaince74af22db3af827eed9558596275cdf3fb07505Installer contract impact
[installer-impact:cli-profile-behavior] updated here: discovery offers
loaderandannex; detectedzunitremains compatibility-only.[installer-impact:output-status-messages] acknowledged: human-readable output remains available but is outside the machine contract.
[installer-impact:zshrc-setup-entrypoint] acknowledged: the generated entrypoint and managed block remain engine-owned.
[installer-impact:companion-asset-checksum] updated here: the checksum records the changed verified
setup.shasset.[installer-impact:plan-apply-receipts] updated here: plans expose operations and warnings, and apply can publish phase results.
[installer-impact:configuration-targets] acknowledged: target resolution and mutation remain owned by the existing engine.
The Wiki, organization install skill, and Zi README consumers were re-read against the changed surfaces. Their exact reviewed revisions are recorded in the v2 contract manifest. Internal consumers were refreshed in this pull request.
Validation
sh ./tests/installers.shzsh tests/installer-contract-impact.zshzsh scripts/installer-contract-evidence.zshtrunk check public/sh/setup.sh tests/installers.sh public/checksum.txt docs/zi-setup-tui-contract.md docs/README.mdsha256sum -c public/checksum.txtsh -n public/sh/setup.shsh -n tests/installers.shgit diff --checkPart of #222.