feat: establish architecture security foundation - #1
Merged
Conversation
YishenTu
marked this pull request as ready for review
July 31, 2026 08:21
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
Establishes the architecture and safety foundation for DarthScriptum by making Markdown source authority, document synchronization, recovery, local rendering, and editor resize behavior explicit and testable.
This is a foundation-scale change that reorganizes production code and tests around clear
app,core,document,editor,workspace, andresourcesownership boundaries.What changed
Architecture and ownership
Source, synchronization, and recovery
MarkdownSourceBufferthe sole in-memory Markdown mutator with revision-checked edits, bounded undo/redo history, document metrics, and scalable line indexingEditor and local rendering
0.10.1to0.11.0and add focused compatibility coverageVerification and CI
Verification performed
./scripts/verify.shtests/architecture/run-tests.shgit diff --check origin/main...HEADverifyGitHub Actions checkReview follow-ups addressed
Package.resolvedin CI with Xcode resolved-file-only package flags instead of allowing automatic re-resolutiontests/architecture/run-tests.shfrom bothscripts/verify.shand hosted CI so guard regressions fail automated verificationNon-goals