Repository navigation
Standardize merged freview operations schema, docs and defaults - #21
Merged
Merged
Conversation
…ain documentation
… separate policy contracts
…only audit separation
…only audit separation
…only audit separation
raiseCatError
marked this pull request as ready for review
October 17, 2026 09:03
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.
Post-merge standardization on main
All five feature PRs (#16–#20) were merged in stack order into
mainusing merge commits to retain test-first history. The integrated main commit410dffb5130678fd7dc526837a5086cacb68dff1passed Ubuntu and macOS CI (run 39019289770).This small, separate follow-up aligns source tree conventions without enabling new executable behavior:
schemas/freview-ops.schema.json(JSON Schema Draft 2020-12), mirrored atskills/freview/assets/schemas/freview-ops.schema.json.ops.pyremains the execution and permission authority; schema validation by itself never grants execution.tests/test_ops_schema_contract.pyguards schema strictness, fields, runtime enum/option parity, safe example defaults, exact distribution copy, and README status..freview.json(read-only audit preferences) vs.freview-ops.json(separate opt-in operations) in docs.Verification gates
mainUbuntu/macOS CI green at410dffb5mainpush CI and diff/schema presenceFuture work: physical Mac and trusted external SSD acceptance, real mutmut/Stryker runs and independent live agent CLI testing; not claimed complete here.