Add LongHorizon-Harness tool example - #506
Closed
Upper9527 wants to merge 1 commit into
Closed
Conversation
Contributor
|
Thanks @Upper9527 for contributing a tool example — visible, reviewable PRs like this grow the reference for everyone. What happens next
More ways to help — loop-engineering maintainers |
Author
|
Closing this draft PR because I am switching to an issue-first discussion. I will open a concise issue with the project context so maintainers can decide whether this tool mapping fits before any documentation change. Thanks. |
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.
What changed
examples/.Why
The new page maps the repository's six loop primitives to LongHorizon-Harness's Manager / Executor / Auditor lifecycle and durable verified state. It also gives a minimal CLI run, explains where external scheduling and worktree isolation are still needed, and links back to this repository's safety gates.
This is a tool example rather than a new pattern: it does not change the registry or claim pattern coverage that has not been implemented.
Validation
git diff --check; this is the content-only contribution path described inCONTRIBUTING.md.