0.2.1 - #41
Merged
Merged
Conversation
added 30 commits
November 23, 2018 16:09
added 13 commits
December 5, 2018 17:59
Try this again... ?
Codecov Report
@@ Coverage Diff @@
## master #41 +/- ##
=======================================
Coverage 58.01% 58.01%
=======================================
Files 41 41
Lines 4475 4475
=======================================
Hits 2596 2596
Misses 1879 1879
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #41 +/- ##
=======================================
Coverage 58.01% 58.01%
=======================================
Files 41 41
Lines 4475 4475
=======================================
Hits 2596 2596
Misses 1879 1879
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #41 +/- ##
=======================================
Coverage 58.01% 58.01%
=======================================
Files 41 41
Lines 4475 4475
=======================================
Hits 2596 2596
Misses 1879 1879
Continue to review full report at Codecov.
|
ms609
pushed a commit
that referenced
this pull request
Aug 5, 2026
…age diff run Rotation (11 mod 13)+1 = 12, sonnet (last visit yielded). Filed #41 (routing state is tier-only) and #42 (scope rows never diffed against the file tree). The scope-coverage diff flagged on 2026-07-03 and never run is now run: two subsystems, 5553 + 2183 loc, in no area at all. 17 files added to rows 1/2/4/5/6 inline, area 7 extended to the Shiny app tests, area 8 broadened from test-ts-*.R to tests/testthat/*.R (it excluded ~44 of ~110 files). Every addition annotated UNMEASURED, per this area's own lesson that a grown scope row inherits no dry verdict. Also corrected: README severity breakdown had drifted within the round it was written (6/5/13 vs a true 6/4/14) — replaced with a query; the undocumented area:N label dependency; a missing migration-map-todo.tsv row; and the "NEVER REVIEWED" rationales on areas 12 and 13, both stale. src/rearrange.cpp: header claimed "DEAD CODE ... Safe to remove" and was false. The Rcpp::export tags are commented out but RcppExports.cpp and TreeSearch-init.c were never regenerated, so nni/spr/spr_moves stay registered, bound at R/RcppExports.R:60-68 and exercised by three test files. Acting on the header breaks them. Comment corrected; no code change. Reverted a finder action: needs-escalation had been applied to #18/#19 for a backlog row whose ask is sequencing, not tier. Area 13 is already opus, and a label hit makes step 3 skip reading the row that holds the ask. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ms609
added a commit
that referenced
this pull request
Aug 5, 2026
… routing and scope gaps The user-level `/red-team` skill carried dual-mode machinery for a `findings.md` store this project deleted at the 2026-08-04 migration. Retired to `~/.claude/skills-retired/red-team/` — the only surviving record of file mode, which is still correct for a project with no GitHub remote — and replaced with a project-local skill that assumes issues throughout, alongside `/next-issue`. The one-off process for standing up a repo under `agent-issues` (fork, default branch, push block, labels, Actions, secrets, findings migration) moves to a subsidiary `github-repo-setup.md` that a normal round never opens. Fixes #41 — the rotation's routing state was tier-only: - a work-shape gate between brief assembly and dispatch, so a recorded "the next visit should NOT be a finder" verdict stops the round and reports instead of auto-dispatching. Areas 10 and 13 both carry one, and area 13 is next. - `needs-escalation` is documented as a tier flag and nothing else; sequencing and cross-area residuals stay prose, and step 3 now reads `escalation-backlog.md` whether or not the label query hit — a hit used to suppress the row holding the actual ask. - the finder brief carries the area's open issues, so a finder cannot spend its budget re-investigating a mechanism already filed. - `area:N` semantics stated: it marks which area owns the code, not which round found it, and the compound label query ANDs correctly. Addresses #42 — scope coverage: - the `tidy` pass now leads with a scope-coverage diff (glob `R/*.[Rr]`; the lowercase `pp_info_extra_step.r` is invisible to a case-sensitive pattern). - area 14 (statistics & support metrics, 14 files) and area 15 (legacy pure-R search API, 9 files) added, both `sonnet` / UNMEASURED. #42 recommended `opus` for 14 and review-once-then-park for 15; the maintainer chose measured maturity for both. N is now 15. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ms609
added a commit
that referenced
this pull request
Aug 5, 2026
…ion state only The previous commit put the skill and its repo-setup guide inside this repo. Both were wrong. The skill is shared across projects, so burying it here takes /red-team away from every other project; and `github-repo-setup.md` documents standing a repo UP under agent-issues, which is precisely the thing already done here and never needed again — it belongs where a not-yet-configured project reads it, next to the skill. Both now live at `~/.claude/skills/red-team/`, with the #41 routing fixes applied there. This branch keeps only what is genuinely project state: areas 14 and 15, N = 15, and the README/AGENTS label range. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
TreeSearch 0.2.1
New features
CollapseNodesandCollapseEdgesallow the creation of polytomiesTree2Splitslists the bipartition splits implied by a tree topologyEnhancements
SplitFrequencynow supports larger treesReadTntTree, to avoid reliance ongenerative file
Bug fixes