Publish OpenAgent profile specification and discovery - #188
Merged
Merged
Conversation
ThreatCrush Security Scan22 finding(s) HIGH/CRITICAL: 3 | MEDIUM: 10 | LOW: 9
Snippets are redacted; ThreatCrush never prints matched credential material. |
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.
OpenAgent had no standalone specification or public page even though OpenRental already references
openagentmembers. Publish/openagentand/docs/openagentaround the existinglogicsrc.agentschema, with a downloadable validated example, discovery conventions and explicit bindings to OpenFleet, OpenProfile and OpenRental. Register it in the shared spec catalog so navigation, docs, sitemap and LLM feeds discover it.Validation: full
npm run check, schema fixtures, all 20 desktop/mobile Playwright E2E checks, browser checks of the new landing page and discovery surfaces, and example validation through the published@logicsrc/validators@0.3.0CLI passed. Local installation used the repository's pinned npm 11.11.0; browsers used the existing local Chromium library directory.