feat(harness): define workbench contracts from selective ECC review - #33
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
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.
The family needs a precise workbench-harness contract around existing agent hosts. This adds a selectively adapted, commit-pinned ECC reference covering install ownership, bounded hooks, durable handoff, artifact-bound eval evidence and observation limits; it distinguishes these from kernel/runtime and sandbox guarantees.
The research ledger records the borrow/adapt/reject decisions and 15 source digests. No foreign runtime, installer, hook, schema or dependency is imported. README and release metadata prepare 0.25.1. Semantic review was completed by the coordinating agent before submission.
Validation: npm test; both strict Claude plugin checks; make-skill house audit (0 GAP / 19 PASS); package inventory; source hash and relative-link checks. No model-outcome improvement is claimed.
Release note: the original merge-commit request was rejected, but a shell sequence continued and created protected v0.25.0 at the previous commit. Its release workflow was cancelled before publication. Deletion was refused by repository rules; no bypass or force push was used. This PR publishes 0.25.1 from the correctly merged revision, preserving protected history.