Repository navigation
Fix formatting in project structure section - #7
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.
What does this PR do?
A clear, specific description. Not "fixes bug" — what was broken, what changed, why this approach.
Related issue
Closes #
Component(s) touched
protocol/— Signal Protocol implementation (X3DH, Double Ratchet)backend/— server, auth, databasefrontend/— UIsimulator/— protocol explainertests/README.md,specification_docs/, etc.)Is this security-relevant?
If yes: does this address a known threat from
datathreat.md? Which one (e.g.T-07)? If it's a new issue not yet documented there, say so explicitly — don't let a security-relevant change land without the threat model catching up.How was this tested?
npm testpasses locallynpm run test:x25519passes locallyDescribe manual testing if applicable:
Checklist
.dbfiles, or key material committed (checkgit statusagainst.gitignore)README.mdif an endpoint or message type changedtype(scope): descriptionconventionAnything else reviewers should know?
Tradeoffs made, things you're unsure about, follow-up work you're deliberately leaving out of scope.