fix(policy): materialize fleet rules under .revealui first - #153
Merged
Merged
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
2 participants
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.
Fleet rules were owned only under
profiles/revealfleet/claude, so a project such as RevDev could materialize tracked policy only into.claude. Move the 14 byte-identical rules toprofiles/revealfleet/revealui/rulesand extend the maintained RevCon linker to materialize them first at.revealui/content/rules, with a source-hashed native manifest. A plain link now selects RevealUI only. Claude and other vendors require an explicit editor selection; the Claude adapter projects native rule bodies while retaining unique Claude-only content.The existing status, unlink, and copy-lockstep tools recognize the native tree. Native selection fails before writing when its profile has no native content, which prevents a silent success for the legacy
revealuiproduct profile; that profile's generated product content remains owned by@revealui/harnesses manager materialize.Validation: 27 shell scenarios and 10 workflow fixtures passed; rule and skill lockstep checks passed; shell syntax and diff checks passed. Native copy produced exactly 14
content/rulesentries witheditor: revealuiand canonical profile source paths, and emitted no Claude tree. The original policy bytes and prior worktrees were preserved.RevDev's companion migration is in a separate branch: its native manifest and 14 rules are produced by this maintained linker, and its CI gate checks that content instead of tracked Claude copies. The old
revealfleet/claudesource path is removed; any external references to it must move to the new canonical profile path.