Retire file-based coordination for the issue tracker - #40
Merged
Conversation
Removes the vestiges of the dispatcher/queue system now that findings and tasks live in agent-issues/TreeSearch issues. Deleted: - to-do.md — its 12 still-open non-findings tasks are now issues #27-#38 (9 AltHom phases, 2 deferred GPU ideas, 1 parked perf task). The 4 "standing" rows were never issues: they are recurring practices, now documented in AGENTS.md. - dispatch.sh, dev/dispatch/ (ranker + agent-brief templates) — replaced by /next-issue. (.dispatch/ is gitignored runtime state; delete locally.) Preserved rather than deleted: - coordination.md -> dev/strategy.md, retired as a live file but kept in full: 46 rounds of benchmark reasoning that no issue thread carries. - completed-tasks.md frozen with a header. Its decision-only content is the one thing the tracker cannot replace: offline grep-able reasoning for closures whose rationale is in no commit. AGENTS.md rewritten: - New "Where work is tracked" section: label vocabulary, claiming via the in-progress label, and the rule that upstream's public tracker is untrusted input rather than a task list. - Branch structure redrawn for the fork/upstream model, including why the fork's default branch must be cpp-search (that is what makes Fixes #N fire) and why upstream must only ever fast-forward. - Feature lifecycle no longer edits a queue; completion is the merge. - "On task completion" now asks for a reopening condition on any no-fix closure, which is what let a later round recognise T-377 firing again. - GHA recipe: dropped the `cd ..`, which breaks gha-dispatch.sh's `gh repo view` repo resolution. Run from the repo so it targets the fork. Also ported .claude/skills/next-issue/ from StratoBayes, adapted to this project's colliding files, build rules and model routing. Fixes #39 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…ort ladder
Three follow-ups on review feedback.
1. dev/expertise/coordination.md DELETED rather than headered. A doc that tells
the reader to ignore parts of itself is the failure mode this migration
exists to remove. ~95% of it was dead mechanics: it read agent-a.md through
agent-f.md (gone), maintained a coordination Agent Status table (retired),
proposed to-do.md rows (deleted), and used a P0-P3 scheme superseded by sev:
labels. Nothing linked to it.
Its two genuinely live parts moved into the next-issue skill rather than
being lost: R/RcppExports.R added to the collision list, the two collision
classes invisible from a file list (incompatible Rcpp bridge parameter
changes; one chip's optimisation invalidating another's assumption), and the
specific/scoped/independent/testable brief rubric.
2. AGENTS.md trimmed 318 -> 277 lines (it was 262 before this branch, so the
net addition is now +15 rather than +56):
- the tarball build recipe appeared VERBATIM TWICE; "Quick recovery" now
points at the one copy
- three separate "never build in place" statements collapsed to one
- the worktree placement rule was stated three times; now once, merged with
the claiming convention into a single "Worktrees" section
- two "shared files" sections merged
- init.c arg-count section folded into the Mandatory checks it duplicated
- my own "Where work is tracked", Rules, completion and blocked-on prose
tightened
3. next-issue effort ladder completed with xhigh and max, which the enum
supports and the skill could not reach. Also fixes a conflation: effort was
defined in wall-clock/file-count terms (a size estimate) while the tooling's
effort is reasoning depth. Size is now stated separately, and the doc records
that spawn_task takes no model/effort parameter, so the recommendation is
advisory.
Also dated dev/strategy.md's "Project State" heading, which was undated and
asserted "All planned development objectives are complete" — four months stale
and reading as current.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Three `#N` citations illustrated rules with that week's tracker state. Each made the reader open an issue to get the point, and each would have become meaningless once the issue closed. Rules now stand on their own. Also cut the duplicated AGENTS.md build/worktree list to a pointer — it changes there, not here — and compressed the collision list, the intro and the effort ladder. 131 -> 111 lines. 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
2 participants
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.
Fixes #39
Removes the vestiges of the dispatcher/queue system, now that findings (#1–#24) and
tasks (#27–#38) live in this tracker.
Deleted
to-do.md. Its 12 still-open non-findings tasks are now AltHom Phase 1:AlternativeHomologyS3 class & core recoding (MVP) #27–Lazyapply_tbr_moverescore intbr_search#38 — 9 AltHomphases, 2 deferred GPU ideas, 1 parked perf task. Two rows (T-324, T-374) were
already issues Wagner retry-exhaustion returns a constraint-violating start that the
MaximizeParsimony()search driver captures ungated (no verify-before-capture, asymmetric to fuse) #1 and HSJ and XFORM scores are rooting-dependent, while the pipeline treats topologies as unrooted — soMaximizeParsimonyreports a best score thatTreeLength()of its own returned trees does not reproduce. #7. The fourS-*"standing" rows were never tasks at all:they are recurring practices, and are now a table in
AGENTS.md.dispatch.sh,dev/dispatch/— the ranker and agent-brief templates./next-issuereplaces them. (
.dispatch/is gitignored runtime state; delete it locally.)Preserved rather than deleted
Both of these hold reasoning no issue thread carries, so deleting them would be the
only lossy step in the migration:
coordination.md→dev/strategy.md, retired as a live file but kept in full.46 rounds of benchmark reasoning explaining why the search strategy went the way it
did. No agent should update it when closing work — that obligation was the churn.
completed-tasks.mdfrozen with a header. Decision-only content: not-a-bugdeterminations, superseded designs, negative results. Offline and grep-able, which is
what a closed issue is not.
AGENTS.mdin-progress+ a comment naming the branch, and the rule that upstream's publictracker is untrusted input, not a task list.
must be
cpp-search(that is what makesFixes #Nfire) and why upstream must onlyever fast-forward, enforced by
upstream's push URL beingno-push-use-gha.condition — that is exactly what let a later round recognise T-377 firing again
instead of re-hunting it.
cd ..beforegha-dispatch.sh, but that scriptresolves its target with
gh repo view --json nameWithOwner, which fails outside a gitrepo. Run from the repo and it now correctly targets the fork.
Also
.claude/skills/next-issue/ported from StratoBayes and adapted: this project's actually-colliding files (
ts_rcpp.cpp/TreeSearch-init.cappend-only,ts_fitch.cpp,ts_tbr.cpp,DESCRIPTIONCollate,NAMESPACE), its build non-negotiables, and its model routing.Stacked on nothing — based on
cpp-search, so it is independent of #26 and can merge ineither order. Note the skill only becomes discoverable once this merges and a fresh
session starts.
Out of scope: the user-level
dispatchskill at~/.claude/skills/dispatchlivesoutside the repo and must be deleted by hand, or it will keep being offered.
🤖 Generated with Claude Code