fix: unify Harness compatibility and release validation - #135
Merged
Conversation
Preserve member delivery, model fallback and recovery across exact Alpha.2, Alpha.5 and rc.1 hosts. Pin the dependency cohort, add installation diagnostics, and verify the same package across the supported host matrix before release. Integrate community maintenance skills and record the issue and PR audit.
This was referenced Sep 5, 2026
Closed
Open
This was referenced Sep 5, 2026
This was referenced Sep 5, 2026
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.
Summary
Harness Alpha.5 and rc.1 removed the setup and delivery APIs used by AgentTeams 0.1.15. This change restores complete member execution through one audited compatibility boundary, preserving FIFO delivery, model/reasoning selection, fallback, failure handling and cold recovery on exact Alpha.2, Alpha.5 and rc.1 hosts.
Real-host tests also exposed and fixed lost fallback settings, a retry using the failed model snapshot, and an installed doctor bin that silently skipped execution through npm symlinks. Captain claims now require safe member reassignment, and both mutation routes enforce bounded JSON bodies behind the existing authentication gate.
The repository now includes the pinned community maintenance skills, a single compatibility policy, frozen host dependencies, an installation doctor, contribution/issue procedures and a publish gate that verifies and publishes the same package artifact. Prereleases use
next;latestrequires the recommended host and complete supported matrix.Migration analysis and reproductions from #119, #124 and #130 are credited in the release notes. Nine independent contributions were already merged with their original authors. The dated maintenance report records the review of all 25 PRs and 41 issues, including remaining feature requests and incomplete reports.
Validation
deepseek-official/deepseek-v4-flashcompleted the team workflow on all three hosts from/tmp(12 / 15 / 14 requests), including worker claims/updates, message delivery, captain wakeup and the independently verified result. An additional rc.1 Web run completed the same real-model workflow through browser input in the existing/tmpworkspace. No credentials are included in evidence.Candidate version:
0.1.16-rc.1, intended fornext. This PR does not claim an npm release has occurred. Evidence and remaining limits are indocs/maintenance-2026-09-06/.