You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pharn update already recorded an abandoned layout in either direction, but only warned for flat→pharn/. A project recorded at pharn/ meeting a flat clone was migrated in silence, leaving the whole pharn/ tree (contracts, floor scripts, trusted docs, and every capability) unmanaged.
The report now prints a matching warning for the reverse direction, naming what was left and that it must be deleted by hand. The flat→pharn/ message is unchanged, and update still never deletes in either direction.
Docs and changelog cover the reverse case; a test pins the renderer branch and that the other direction's message does not fire.
Test plan
npm test -- tests/update.test.ts — the new warns that the abandoned pharn/ tree is no longer managed pin, plus the existing flat→pharn/ pin, both green
npm run check — format, lint, typecheck, and full test suite
Confirm a pharn→flat fixture run prints the pharn/ tree warning and does not print moved to the pharn/ layout
Confirm the abandoned pharn/ files are still on disk after the update (update never deletes)
Reviews should be triggered manually for repositories with fewer than 10 stars. Select Trigger review above or comment @coderabbitai review to review the latest changes. For a full review, comment @coderabbitai full review.
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 1c787f19-a231-42eb-9190-56075ea97d7d
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
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
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
pharn updatealready recorded an abandoned layout in either direction, but only warned for flat→pharn/. A project recorded atpharn/meeting a flat clone was migrated in silence, leaving the wholepharn/tree (contracts, floor scripts, trusted docs, and every capability) unmanaged.pharn/message is unchanged, andupdatestill never deletes in either direction.Test plan
npm test -- tests/update.test.ts— the newwarns that the abandoned pharn/ tree is no longer managedpin, plus the existing flat→pharn/pin, both greennpm run check— format, lint, typecheck, and full test suitepharn/ treewarning and does not printmoved to the pharn/ layoutpharn/files are still on disk after the update (update never deletes)Made with Cursor