Repository navigation
curate: decline 4 (each checked against HEAD and filed) (2026-09-30 pass) - #1799
Merged
Merged
Conversation
Every fragment waiting in trap.d/ described a live design question or a still-true code gap, not an agent-facing lesson a jit-context rule could carry -- so all four are declined with a citation rather than promoted or merged, per commands/run/curate.md own routing for a code-claim fragment. - 1770.doctor-enabled-github-security-settings-unasked -> #1795: a policy gap in agents/doctor.md own disposition list for outward GitHub security-setting PATCHes. - 1777.select-issues-first-time-contributor-tension -> #1796: confirmed unchanged at HEAD; select_issues.py and inbound_triage.py still disagree on FIRST_TIME_CONTRIBUTOR/FIRST_TIMER. - 1788.default-plugins-root-more-sites -> #1797: confirmed still true at three sites (statusline.py, bin/oss-workspace, doctor.py). - 1789.curate-pr-stranded-no-tick-reviews-it -> #1798: confirmed the tick cadence still has no step that reviews a pull request it did not itself dispatch. Co-Authored-By: Claude Sonnet 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
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.
Curate pass, 2026-09-30
4 fragments were waiting in
trap.d/. Read all four before deciding any of them; none share amerge-worthy dimension with each other, and none is an agent-facing lesson a jit-context rule can
express -- each is a live design question or a still-true code gap that needs a maintainer's
decision or a real code fix. Outcome: 0 promote, 0 merge, 4 decline (each filed), 0 defer.
Every decline was checked against the tree at HEAD before being declined, per
commands/run/curate.md's "a decline of a live code defect must never be the only record of it"rule -- none was "already fixed", all four are "still true", so all four were filed rather than
silently declined.
1770.doctor-enabled-github-security-settings-unasked-> Part of doctor: outward GitHub security-setting PATCHes need a needs-maintainer disposition #1795.oss:doctorapplied four outward GitHub repository security settings via
gh api -X PATCH/PUT, unasked.agents/doctor.mdnames no disposition distinguishing this from an ordinary in-repo filerepair. Policy decision, not a rule.
1777.select-issues-first-time-contributor-tension-> Part of select_issues.py and inbound_triage.py disagree on FIRST_TIME_CONTRIBUTOR/FIRST_TIMER classification #1796.select_issues.pyand
inbound_triage.pytake opposite deliberate positions on the sameFIRST_TIME_CONTRIBUTOR/FIRST_TIMERGitHub values. Confirmed unchanged at HEAD. Needs amaintainer's call on whether the two contexts genuinely differ.
1788.default-plugins-root-more-sites-> Part of plugin_update.py's CLAUDE_CONFIG_DIR-aware default not yet applied to statusline.py, bin/oss-workspace, doctor.py #1797. The$CLAUDE_CONFIG_DIR-awareplugin-root default landed in
scripts/plugin_update.py(plugin_update.py's enablement() conflates a $CLAUDE_CONFIG_DIR install with not-installed #1788) but not inscripts/statusline.py,bin/oss-workspace, orscripts/doctor.py-- confirmed stillhardcoded in all three at HEAD. Cross-import design question, not a rule.
1789.curate-pr-stranded-no-tick-reviews-it-> Part of No tick step reviews or merges a pull request the tick did not itself dispatch (e.g. a curate PR) #1798. A curate pull request satunmerged across three consecutive ticks because no step in the tick cadence reviews a pull
request the tick did not itself dispatch. Confirmed the gap is still current in both
commands/run.mdandagents/sub-manager.md. Real cadence fix, not a rule.Each decline's trace is recorded in
.claude/jit-context/paths/00-manual/00-README.mdunder "Filed, as defect reports rather thanrules."
no_close = true; this pass consumed each fragment into a filed issue rather than doing that
issue's own work, so nothing here closes any of the four.
[AI-generated]