Use English across the Demo and align AlvenX branding - #4
Merged
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.
The Demo now uses English consistently across its interface, accessible labels, execution states, error messages, documentation references, and README screenshot. Stored execution results remain explicitly labeled as saved evidence; this language update does not imply a new experiment or a product-stage promotion.
This PR also preserves the separately authorized AlvenX brand handoff in two commits: the shared README descriptor contract and the canonical centered wordmark with matching provenance. The English UI implementation and acceptance receipt follow in separate commits.
Validation completed locally:
pnpm check: 80 unit/process tests and 4 browser tests passed, with formatting, lint, type, brand, and evidence checks.pnpm package:smoke: passed.0e02daca5b4aab4c6a5b02e876aa10480f243849: frozen pnpm installation, brand verification, and 4 browser tests passed.The product gate remains
SPIKE_CONDITIONAL, with product value still unproven. PR CI passed on 52c1819: https://github.com/AlbertXXuu/ReproLock/actions/runs/33890143146. Merged as 5b16d22; main CI passed: https://github.com/AlbertXXuu/ReproLock/actions/runs/33890395310. Both runs passed Node 22.23.2 and 24.20.0. The fixed D-drive checkout is clean on main and matches origin/main and the tested PR tree. The local integration receipt and CI job details are preserved in the AlvenX workspace audit for this follow-up.