refactor: sync runtime core paths#36
Merged
Merged
Conversation
This was referenced Apr 19, 2026
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
server/routes/**path layer with compatibility wrappers over the proven PawWork implementationsWhy
This continues the
#27runtime-core sync work for PR5. The goal is to bring the remaining upstream runtime behavior into PawWork without widening into project, session, app, or desktop lanes, while preserving current PawWork-specific behavior where the surfaces differ.Related Issue
Part of #27
How To Verify
Screenshots or Recordings
N/A, no visible UI changes.
Checklist
devbranch