feat: reboot Weft as a Bun AI-native reader#1
Open
dpunj wants to merge 8 commits into
Open
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
Reboots Weft around a Bun + TypeScript document spine and a modern local web reader preview.
This keeps the original Weft spirit — vim-like reading for books — but moves the forward path toward an AI-native reader inspired by
recrsv/RLM-style document exploration.What changed
WeftDocumentSectionBlockSourceSpanbun run read book.epubbun run web book.epubhttp://localhost:4173j/k,h/l,g/G,t)recrsv-style exploration rail:tocsearch_textcontext_getdocs/WEFT_REBOOT.mddocs/shaped/ai-native-reader-reboot.mdHow to try it
Open:
Try the exploration rail with:
Validation
bun run typecheck/api/document/api/page/api/rlm?q=panama%20canalNotes
This does not yet wire in a real LLM tool loop. The exploration rail is deterministic for now, but the UI/server shape is ready for the next slice: streaming model-driven
toc → search_text → context_get → answerevents.Recommended next steps are captured in the shaping doc:
repl_exec