Restore tracked source and establish deterministic CI - #1
Merged
Conversation
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.
Summary
src/andpublic/trees as normal tracked fileschatData.tsmodule and referenced logo verbatim from repository historyCodebase.zipand ZIP-dependent setup instructionsvalidatejob for frozen install, lint, tests, and production buildRoot cause
mainhad no workflow and no trackedsrc/tree. A clean build failed at/src/main.tsx; after restoring the current archive, the build then proved thatsrc/data/chatData.tsandsrc/assets/ecxo-logo.pngwere also omitted from that archive. Both omitted files were recovered from the repository's earlier source ZIP commit.Validation
bun install --frozen-lockfilebun run lint— 0 errors, 7 non-blocking Fast Refresh warningsbun run test— 1 passed, 0 failedbun run buildThe source scan found no
.env*files, credentials, API keys, tokens, private keys, connection strings, real phone numbers, or non-example email addresses. The chatbot and administration surfaces remain local UI simulations; CI makes no live LLM/API calls.