feat: add Origin field parser and warnings for repository migration #10
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
Add support for the
Originfield in REPOSITORIES.md to enable future repository migration automation from "powered by worlddriven" to "worlddriven project" status.This PR implements the parser foundation and appropriate warnings while the transfer automation logic is still in development.
Changes
Parser Support
originfield parsing inscripts/parse-repositories.jsorigin?: stringDrift Detection
pendingTransfercategory to drift detectionSync Automation
Documentation
Originfield in REPOSITORIES.md properties sectionTesting
npm testAll tests pass, including new tests for origin field parsing.
Why This PR
This establishes the foundation for repository migration automation while being explicit that the feature is not yet complete. Users who add an
Originfield will receive clear warnings that:Next Steps
See issue #9 for remaining implementation work:
Related
Closes: N/A (foundational work)
Related: #9