Conversation
The updater compares manifest versions; PR #10 changed skill content without bumping, so installed copies would stay at the 6.1.1 tree. 6.1.2 is a fork-local version ahead of upstream's 6.1.1 by design — it re-converges at the next upstream release sync. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SYxaVSy1xS1PFzAAesybUJ
Release v6.1.2: 2026-07-06 evaluation fixes to main
- working-from-issues: repositories may define an issue claiming protocol in agent instruction files (claim marker, claim comment, release rules, collision check). The protocol pre-authorizes exactly its claim and release mutations; everything else stays two-step gated. The shared standing pre-authorization block is untouched (byte-identical guard). - triaging-issues: Triage Result gains an advisory Complexity field (low/standard/high/unknown) as a routing hint the dispatcher may override; repository policy decides any label mapping. - pressure scenarios and structural tests cover collision stop, claim/release lifecycle, and complexity semantics. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016xnwbnRb3AVN2XoTfjr3ms
…issue Review fixes: claim/release mutations are now a closed set (status label, self-assignment, comment on the target issue only); close/reopen/transfer/ milestone/delete, cross-issue mutations, and extra comment content are excluded even if a protocol labels them claiming. Adds a smuggling red flag, pressure scenario 15, structural assertions pinning the boundary, spec-draft Complexity drift fix, and a dispatch-hint note in Route by Actionability. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016xnwbnRb3AVN2XoTfjr3ms
Add repository claiming protocol and triage complexity routing hint
Minor bump: working-from-issues gains the repository claiming protocol and triaging-issues gains the advisory Complexity field (PR #12). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016xnwbnRb3AVN2XoTfjr3ms
Release v6.2.0: repository claiming protocol + triage complexity hint
5 tasks
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.
Why
devhad fallen 7 commits behindmain, frozen at PR #10 (v6.1.1). Releases #11–#13 were merged directly intomainand never back-merged intodev, sodevmissed both the 6.2.0 content and the version bumps — the same root cause as the plugin-manifest version drift.Under the new branch-protection ruleset ("Protect main and dev"), all changes now flow through PRs — including this back-merge.
What
Brings
devup tomain(v6.2.0) with the 7 missing commits:After merge,
devcontent equalsmain(v6.2.0).devwill then sit one merge-commit ahead ofmain— the normal dev-first state.Merge method
Use Create a merge commit to preserve #11–#13 history (do not squash/rebase).