Add OpsHistory local-first contract hardening#88
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
1 participant
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
Adds the first branch-based hardening pass for the OpsHistory / BearHistory / local-first service contract family.
This PR builds on the initial OpsHistory contract seed by adding:
docs/contract-additions/ops-history-catalog.mdsemantic/ops-history-vocabulary.jsonld.github/workflows/validate-ops-history.ymlThe existing contract seed already includes:
schemas/OpsHistoryEvent.jsonschemas/OpsHistorySyncPolicy.jsonschemas/LocalFirstServiceManifest.jsonschemas/BearHistoryEvent.jsonschemas/BearHistorySyncPolicy.jsonschemas/ShellReceiptEvent.jsonschemas/OpsHistoryContextPackRef.jsonschemas/RedactionTombstone.jsontools/validate_ops_history_examples.pyasyncapi.ops-history.patch.yamldocs/contract-additions/ops-history.mdWhy
OpsHistory is the shared local-first operational event fabric for governed multi-chat human/agent operations. The contract family captures:
Validation
Expected validation command:
This PR also adds a dedicated GitHub Actions workflow for OpsHistory validation.
Notes
The changelog still needs a small entry. A full-file changelog update was blocked by the tool filter during automation, so I am leaving that as follow-up rather than risking a bad large replacement.
Non-goals
This is contract hardening only.