docs(site): align public docs with gittensor aesthetic - #4
Merged
Conversation
JSONbored
added a commit
that referenced
this pull request
May 29, 2026
* feat(agent): make next-action recommendations repo-specific Weave language fit, label overlap, queue size, and prior outcome counts into per-repo whyThisHelps / nextActions. Add publicNextActions for sanitized GitHub surfaces so counts stay private. Stop priorityFor from penalizing cleanup_first for the open_pr_pressure blocker that triggered the recommendation in the first place. Closes #16. * fix(agent): restore actionKind guards and add split-lane copy recommendationText now distinguishes cleanup_existing_prs, land_existing_prs, file_issue_discovery, and maintainer-lane action kinds again (falling through to per-repo nextActions only as a last resort). whyThisHelpsFor / nextActionsFor / publicNextActionsFor gain a split-lane arm so AC #4 covers all four lanes. Drop dead code in RepoCopyContext and labelFit, unify the defensive ?. on profile.github. * test(agent): tighten and extend decision-pack regression coverage Add split-lane and avoid_for_now fixtures. Add maintainer-vs-outside separation test (same outcome.openPullRequests surfaces in cleanup copy, not maintainer copy). Add end-to-end buildContributorDecisionPack test so a regression in languageSet threading fails. Replace the noop /\b8 open PR/ guard with a structural noStructuralCountLeak check applied across all 5 recommendation tiers. Tighten the orchestrator integration assertion to require per-lane phrasing. Strengthen the determinism test to also assert priorityScore and nextActions equality. * test(agent): cover review-requested branches and tier sanitization Push branches over the 95% gate (94.94 -> 95.03). New cases: - languageMatch true/false and labelFit empty/non-empty paths. - cleanup_first triggered via openPullRequests >= 3 (no open_pr_pressure blocker) still outranks pursue baseline. - scoreBlockersFor with outcome undefined exercises the nullish guards. - whyThisHelpsFor / nextActionsFor cleanup_first + watch (split lane) with outcome undefined. - withSnapshotMetadata falls back to nowIso when both generatedAt fields are absent. - publicNextActions sanitization asserted for every recommendation tier: no decimals, no share/emission/priority words, no field-name leaks. --------- Signed-off-by: ghost <49853598+JSONbored@users.noreply.github.com> Co-authored-by: mkdev11 <MkDev11@users.noreply.github.com> Co-authored-by: ghost <49853598+JSONbored@users.noreply.github.com>
JSONbored
added
the
gittensor:bug
This was referenced Jun 26, 2026
This was referenced Jul 5, 2026
Closed
15 tasks
This was referenced Jul 30, 2026
loopover-orb Bot
pushed a commit
that referenced
this pull request
Jul 30, 2026
…t the PR ahead of it (#9954) The wait comment named the immediate blocker and nothing else: Queued in the merge train behind #4, which touches overlapping work and was opened first. "Behind #4" and "behind #4 and six others" are very different waits, and a queue that will not say which one it is reads as a stall rather than a wait -- which is how it was read in practice. The information was already computed and thrown away: shouldWaitForOlderSiblings builds the full sorted list of viable overlapping older siblings and returned only viable[0]. It now returns the whole list, and the comment reports the position: Queued in the merge train at position 4, behind 3 overlapping PRs opened before this one (#1, #2, #3). The nearest is #1. The single-blocker wording is unchanged -- rendering a one-item queue as "1 PR ahead: #4" is noise. The queue inherits every eviction rule the blocker choice already had, which the tests pin: a draft, a conflicted PR, a manual-review hold and a non-overlapping sibling are all absent from it. A contributor must never be told they are behind PRs that are not actually in front of them. Closes #9952
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.
Summary
What changed
Validation
git diff --checknpm run docs:checknpm run docs:buildNotes