Commit Graph
48 Commits
Author SHA1 Message Date
bincxz 21d3487b28 chore(ci): keep Cursor automation on triage only
Pause implement, issue follow-up coding, and the Codex review loop
so Cursor only classifies new issues. Restore with
CURSOR_AUTOMATION_MODE=full and the commented schedule crons.
2026-08-14 15:48:32 +08:00
Cursor Agentand陈大猫 4bcc619de4 fix(ci): stop automation verify gate false positives
Ignore success-case TAP YAML diagnostics and normalize volatile console
noise in baseline comparison so red-but-unchanged candidate runs pass as
baseline_only. Align the session-backed fastPut expectation with live-path
uploads, harden SCP abort teardown races, drop mixed hallucinated research
citations instead of failing classify, and soften verification failure
copy so it no longer claims the patch introduced the failure.

Co-authored-by: 陈大猫 <binaricat@users.noreply.github.com>
2026-08-07 08:49:13 +00:00
陈大猫 ae74f25588 fix(ci): dedupe same-head @codex review requests (#2754)
* fix(ci): dedupe same-head @codex review requests

Plain maintainer/Cursor-bot @codex review comments did not plant the
cursor-external-codex marker, so own_rerequest on synchronize posted a
second request for the same SHA. That concurrent pair produced a clean
issue comment from one job and a findings review from the other.

Skip re-request when any trusted or Cursor-bot author already requested
this head via external marker, cursor-codex-head pin, or a recent plain
@codex review.

* fix(ci): only dedupe plain @codex against the current head push

Plain unpinned requests no longer skip solely by age — that blocked
re-request after a new synchronize when an older plain @codex still
looked "recent". Callers pass the head commit time as notBefore so
only post-push plain requests suppress a duplicate.

* fix(ci): use PR head-change time for plain @codex dedupe

Commit author/committer dates predate cherry-picks and rebases, so a
plain @codex for the previous head could suppress re-request after a
new synchronize. Pass pull_request.updated_at (moves with the push)
as notBefore instead.

* fix(ci): dedupe @codex only via head-pinned markers

Drop plain-unpinned timestamp heuristics — they cannot safely know which
SHA a bare @codex review targeted. Skip re-request when a trusted author
already pinned this head with cursor-codex-head or cursor-external-codex.
2026-08-05 23:40:51 +08:00
陈大猫 07c914a73d fix(ci): let maintainer @bot reclassify auto-closed issues (#2753)
* fix(ci): let maintainer @bot reclassify auto-closed issues

Author reopen disputes still stay on issue_followup when
triage:already-available/unclear remain, but an explicit maintainer
@netcatty-bot mention must re-enter issue_classify so re-triage can
run without an open bot PR.

* fix(ci): prefer maintainer @bot over author follow-up routing

When a trusted maintainer is also the issue author, route explicit
@netcatty-bot mentions as maintainer re-triage so auto-closed
already-available/unclear issues can re-enter classify.
2026-08-05 22:12:22 +08:00
a97002c0a7 fix(ci): stop reopen from replaying issue triage (#2751)
* fix(ci): stop reopen from replaying issue triage

Already-admitted issue reopen events were routed back into full classify,
so follow-up handoffs and maintainer reopens could close again or overwrite
ready-for-human with needs-info. Skip bot reopen, hand auto-closed human
reopens to maintainers, and keep already-available disputes on follow-up.

Co-authored-by: 陈大猫 <binaricat@users.noreply.github.com>

* fix(ci): keep ready-for-human follow-ups off classify

After reopen handoff drops triage:already-available, actionable author
replies could still be refined into classify and auto-close again. Treat
ready-for-human like the dispute signal and keep those comments on
follow-up.

Co-authored-by: 陈大猫 <binaricat@users.noreply.github.com>

* fix(ci): preserve already-available dispute label on handoff

Keep triage:already-available when handing reopened auto-closed issues
to humans, and only use that label (not ready-for-human) to block
reclassify. This stops the close loop without blocking feature_defer or
other ready-for-human follow-ups from re-entering classify.

Co-authored-by: 陈大猫 <binaricat@users.noreply.github.com>

* fix(ci): keep unclear reopen disputes off classify

Match the already-available dispute guard for triage:unclear / unclear so
human reopen handoffs of auto-closed unclear issues cannot re-enter
classify and close again on the next author follow-up.

Co-authored-by: 陈大猫 <binaricat@users.noreply.github.com>

* fix(ci): revalidate auto-close labels before handoff

Queued ready_for_human_handoff must not overwrite a maintainer who already
cleared triage:already-available/unclear and moved the issue (for example
to ready-for-agent). Skip the handoff when those outcome labels are gone.

Co-authored-by: 陈大猫 <binaricat@users.noreply.github.com>

* test(ci): cover skipped reopen handoff without auto-close labels

Co-authored-by: 陈大猫 <binaricat@users.noreply.github.com>

* fix(ci): do not reopen issues already closed before handoff

Queued ready_for_human_handoff must respect a maintainer who re-closed the
issue while the job was waiting. Skip when live state is closed instead of
forcing ensureOpen.

Co-authored-by: 陈大猫 <binaricat@users.noreply.github.com>

* fix(ci): reclassify non-auto-close issue reopens

After a merged automation fix, cleanup leaves triage:bug-ready/admitted on
the source issue. Human reopen of those labels must re-enter classify so a
failed fix can spawn another implementation; only bot reopen stays skipped.

Co-authored-by: 陈大猫 <binaricat@users.noreply.github.com>

---------

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: 陈大猫 <binaricat@users.noreply.github.com>
2026-08-05 20:47:57 +08:00
bincxz 85d9710a8b fix(ci): enforce issue reference boundaries 2026-08-04 17:24:19 +08:00
bincxz 887d228a1b fix(ci): parse multi-issue pull references 2026-08-04 17:21:56 +08:00
bincxz 9af475c16a fix(ci): reclassify related PR follow-ups 2026-08-04 17:11:46 +08:00
bincxz 68269ce2bd fix(ci): preserve trusted maintainer routing 2026-08-04 17:02:21 +08:00
bincxz 0d6df02bf6 fix(ci): close automation review gaps 2026-08-04 16:57:01 +08:00
bincxz 6b1c5632e3 fix(ci): address automation review findings 2026-08-04 16:40:31 +08:00
bincxz a603a0e1f0 fix(ci): harden cursor automation handoffs 2026-08-04 16:27:14 +08:00
bincxz e1998cfcd2 fix: protect existing test sources 2026-07-31 19:34:21 +08:00
bincxz 83f524524f fix: compare runner failures across full output 2026-07-31 19:05:00 +08:00
bincxz 5832b91051 fix: protect automation validation boundaries 2026-07-31 18:57:25 +08:00
bincxz 7e26869a43 fix: close Cursor automation review gaps 2026-07-31 17:45:53 +08:00
bincxz 092b010ec0 fix: harden CI and Cursor automation 2026-07-31 17:34:03 +08:00
陈大猫 e74859f786 fix(ci): proxy GitHub screenshots before research (#2551) 2026-07-27 23:15:25 +08:00
bincxz 93f23b9312 fix(ci): require identical research candidates 2026-07-27 19:39:58 +08:00
bincxz 7c90d40159 fix(ci): validate all research status candidates 2026-07-27 19:37:30 +08:00
bincxz 2d3316093c fix(ci): reject conflicting research statuses 2026-07-27 19:34:32 +08:00
bincxz 0bb06dca72 fix(ci): prefer rebuilt final research fence 2026-07-27 19:31:20 +08:00
bincxz 0d2c435687 fix(ci): parse Cursor partial stream boundaries 2026-07-27 19:28:10 +08:00
bincxz f2c47d2ab7 fix(ci): distinguish Cursor final flushes 2026-07-27 19:23:21 +08:00
bincxz d87029e200 fix(ci): trust valid terminal research result 2026-07-27 19:19:31 +08:00
bincxz 25669b1118 fix(ci): rebuild final research envelope 2026-07-27 19:15:57 +08:00
bincxz c91aa04945 test(ci): handle split research fences 2026-07-27 19:13:17 +08:00
bincxz 6dd3868a90 fix(ci): prefer final Cursor research status 2026-07-27 19:10:01 +08:00
bincxz b1221501c5 fix(ci): trust only final research message 2026-07-27 18:08:43 +08:00
bincxz 28be1d396c fix(ci): accept fenced Cursor research status 2026-07-27 18:06:45 +08:00
bincxz 27517f0d76 fix(ci): restore Cursor issue automation 2026-07-27 11:10:47 +08:00
bincxz 2840463b3d fix(automation): gate ready-state follow-ups and research web denials
Only automation bot PRs re-check source-issue pending comments before
mark-ready, so maintainer Fixes-only PRs are not stuck draft. Write
WebSearch/WebFetch denials after the isolated research pass so classify
and follow-up research can still call those tools.
2026-07-26 21:43:37 +08:00
bincxz 768d5b9f23 merge: resolve main into continuous issue follow-ups
Keep PR follow-up routing (trigger_comment_id, pending issue gates) and
main's head_ref concurrency plus implement issue.json preparation.
2026-07-25 18:55:59 +08:00
陈大猫andnetcatty-bot 5633631840 fix(ci): reduce flaky failures and PR runtime (#2474)
* fix(ci): reduce flaky failures and PR runtime

* fix(ci): avoid label scope failures

* fix(ci): tolerate GitHub download outages

* fix(ci): cover packaged inputs in PR triggers

* fix(ci): keep test-only changes out of package builds

* perf(ci): reuse unchanged ET PR builds

* fix: address Codex review on PR #2474

* fix(ci): harden automation PR handoffs

* fix(ci): preserve reused implementation branches

* fix(ci): deduplicate automation follow-ups

* fix(ci): deduplicate automation follow-ups

* fix(ci): ignore remapped stale Codex findings

* fix(ci): use the established handoff label

* fix(ci): isolate manual package validations

* fix(ci): refresh existing Nix metadata PRs

* fix(ci): hand off divergent implementation branches

* fix(ci): serialize Homebrew tap updates

---------

Co-authored-by: netcatty-bot <308658023+netcatty-bot@users.noreply.github.com>
2026-07-25 15:04:22 +08:00
bincxz f88c66caf9 fix(automation): restore sandboxed Codex follow-ups 2026-07-25 11:56:56 +08:00
bincxz efecf436a7 feat(automation): add isolated web research pass 2026-07-25 00:47:42 +08:00
bincxz a55e9e7e7f feat: continue issue automation after follow-ups 2026-07-25 00:02:49 +08:00
陈大猫 48b2cd1f67 fix(ci): close Cursor automation handoffs and label state machine (#2461)
- Format recovery dispatches triage before clearing invalid-format
- Shared CJK-friendly title rules; codex label terminal state machine
- Research steps in classify; agent TITLE + PR body for bot PRs
- Single @codex review via CODEX_REQUEST_GITHUB_TOKEN (binaricat)
2026-07-24 20:10:28 +08:00
陈大猫 3ff16920fd fix(ci): make triage replies plain and drop Cursor disclaimer (#2447)
Public issue comments no longer show a generated-by line. Grounding stays
in code_findings/reasoning only so reply can use UI language without file
paths, symbols, or dense parentheses. Classify prompt and rewrite templates
match that tone.
2026-07-24 15:08:47 +08:00
陈大猫 27a42e3a76 fix(ci): Cursor triage crash + already_available how-to close (#2439)
* fix(ci): stop Cursor issue triage crashing on Search pagination

Octokit normalizes Search API pages so response.data is already the items
array. Mapping response.data.items returned undefined and then crashed on
candidate.user during daily-limit admission — so every valid new issue
failed before Cursor classify could run.

* fix(ci): classify already-available issues with how-to and auto-close

Add an already_available triage category for requests the product already
ships: after code-grounded inspection, reply with the concrete UI entry
path, then close as completed. Low confidence falls back to other instead
of closing. Keeps the Search pagination fix so new issues can classify.
2026-07-24 14:01:11 +08:00
bincxz 31d4e16055 fix(ci): prefer local UI polish as feature_quick_win
Triage was biased toward feature_defer ("be conservative" + treating existing
UI tests / layout preference as strategic). Prefer quick wins for small,
same-panel UI work; reserve defer for multi-module or true product strategy.
Slightly lower the auto-downgrade floor for feature confidence to 0.7.
2026-07-24 10:12:05 +08:00
bincxz f160e9ad51 fix(ci): require code search and file reads before triage replies
Classification must open real source files first. The prompt mandates
search→read→classify, JSON now requires code_paths/code_findings, and
normalizeClassification rejects ungrounded replies so agents cannot answer
from issue text alone.
2026-07-24 10:04:06 +08:00
bincxz 4d18ea811d fix(ci): harden Cursor automation until Codex CLI review is clean
Address multi-round Codex CLI findings: trusted control markers, reaction-only
clean detection with head pins, draft-until-clean gates, secret leak scans
isolated from agent git hooks, fix eligibility limited to maintainers/actions
bot, P3 handoff, open-PR-only bot PR detection, and related safety fixes.
2026-07-24 04:27:59 +08:00
bincxz 073083c6ee fix(ci): address Codex review findings for automation safety
Isolate publish onto fresh runners, harden Codex loop head scoping,
protect fork bootstrapping, and polish classification replies and
mark-ready error handling after local codex review.
2026-07-24 01:54:30 +08:00
bincxz ba5932e285 fix(ci): raise default Codex fix loop cap to 40 rounds
Allow longer Cursor fix ↔ @codex review cycles on own/bot PRs; still
overridable via CURSOR_CODEX_FIX_MAX_ROUNDS.
2026-07-24 01:10:30 +08:00
bincxz 13d54ee4f4 fix(ci): harden Cursor automation after multi-agent review
Tighten re-triage, Codex single-flight signals, protected-path checks on
commit ranges, trusted helper loading from RUNNER_TEMP, and failure
handling so own/bot loops stay safe and forks only re-@codex.
2026-07-24 00:55:12 +08:00
bincxz 656d2077a5 fix(ci): re-request Codex on external PR pushes only
Drop Cursor CLI review for third-party/fork PRs. Initial Codex review
stays with the existing connector; after contributor synchronize we only
comment @codex review (deduped per head SHA).
2026-07-24 00:35:21 +08:00
bincxz 528489e15c feat(ci): add Cursor CLI issue/PR automation with Codex review loop
Wire GitHub Actions to classify and implement issues via Cursor CLI,
open draft PRs, request @codex review for own/bot PRs, fix findings,
and only post read-only review comments on third-party PRs.
2026-07-24 00:31:57 +08:00