Support TNT source file in NEXUS format - #38
Merged
Merged
Conversation
ms609
pushed a commit
that referenced
this pull request
Aug 5, 2026
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>
ms609
added a commit
that referenced
this pull request
Aug 5, 2026
T-300's SPR half landed long ago (f531bbc EW, 014ccde NA); what issue #38 still describes as "full_rescore after every accepted move" is now only the residue: accepts that rerooted the clipped fragment, which still fell through to full_rescore. apply_tbr_move reverses the parent/child links along clip_node..reroot_parent, so every node on that path gains new children — and after the reversal that path IS clip_node's rootward chain. One extra dirty seed at clip_node therefore covers the rerooting case exactly, with no new machinery: the NA kernel already took a third seed for precisely this region (it backs exact_verify_sweep), so this only adds the same parameter to the EW/IW kernel and drops the is_spr gate at the accept site. Measured, and the honest answer is that the lever is spent. Post-T-300 the whole accept branch is 0.18-0.51% of tbr_search wall (in-DLL na_t_accept_ms, Vinther2008/Agnarsson2004/Zanol2014 x EW,IW, 15 paired cells). This cuts that slice to x0.901 median (12/15 cells) => ~0.03% end-to-end, i.e. undetectable. Rerooting accepts are ~18% of accepts, so that is a real ceiling, not thin coverage. The case for merging is codepath unification, not speed; area 4 is recorded AT-LIMIT so it is not profiled again. Correctness, given an earlier incremental attempt shipped a systematic delta=-3 (b7303ee): - TS_TBR_ACCEPTCHK, a new env-gated in-flight oracle, cross-checks every incremental accept against full_rescore and aborts on drift. Clean over the 70-cell battery (1322 accepts) and over 624 assertions spanning the constrained, pool, IW, XPIWE, sector and drift paths. - Scores and accept counts are byte-identical to the pre-patch library across all 15 A/B cells and the 70-cell battery, so trajectories are unchanged. - n_reroot_accepts (src/ts_data.h) makes the new regression test non-vacuous: the four pre-existing tests assert score identity but cannot tell whether the rerooting arm was ever entered, so the new one asserts coverage as well as correctness. 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.
No description provided.