Repository navigation
Open native terminal profiles and map all foundation installation layers - #34
Merged
Merged
Conversation
9 of 22 tasks
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
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 selected foundation had no matching Codex Windows Terminal profile, and its layer overview did not provide a direct installation/E2E map. The host now has both named native profiles; upstream Windows Terminal launch commands returned exit 0, and independent process inspection confirmed separate interactive Claude and Codex clients in the intended project. Previous terminal settings remain intact.
The Foundation guide now links all 16 layers to their selected implementations and existing upstream installation and scoped E2E recipes. A new Setup button opens that map directly. This reuses accepted source-pinned evidence without reinstalling working tools or activating overlapping optional frameworks.
Validation: 50 focused catalog/HTML/lifecycle checks pass, publication integrity and deterministic HTML checks pass, all 60 local Markdown links/anchors resolve, and an independent audit confirms exact retained process-output bytes, live process identity and settings preservation. Existing Qdrant and embedding services returned active.
Scope: opening profiles and observing processes does not qualify native sign-in, interactive context/usage/compaction, HUD, a new model task or complete service E2E. The receipt distinguishes directly transcribed launch returns from retained process output. No new dependency, model trial, provider savings claim or foundation acceptance upgrade is introduced.