[EdbertChan]

Summary

This adds one rule to the assistant's standing instructions. It covers questions about who made something you own.

Now the assistant lists your own work first, newest first. It checks that list before it searches by keywords.

The problem: asked which merge request produced a page you own, the assistant searched by keywords. Searches timed out or returned unrelated results, and it said none existed.

The cause: a keyword search finds only the words the author chose. A list of your own work does not depend on what anything is called.

The fix: one rule line.

Review Claim

Approve one added rule that makes the assistant list your own items before it searches by keywords.

Review Lane

behavior

Review Unit

corpus-lesson

Safety Invariant

This slice adds one line of text to the standing instructions and changes no code, hook, or script. It narrows no existing rule. It only adds an order of search: your own items first, then keywords.

Slice Rationale

One rule line, one claim. The two related checks (block a negative answer after a timeout, and stop accepting a timeout as a reason to skip a check) are code and ship separately.

Non-goals

• No hook, script, or test changes.
• No change to any existing rule's wording.
• No rule about retrying after a timeout.

Measured

none: this adds instruction text only, so there is no speed, size, or cost to measure.

Test Plan

Test Plan

• python3 engine/skills/make-pr/scripts/preflight.py --base origin/main --commit-only --dry-run printed unit corpus-lesson: 1 file(s), gates none required for these paths, ok preflight passed (exit 0).
• python3 engine/skills/make-pr/scripts/preflight.py --base origin/main --commit-only --body-file <this body> ran the body validator and the description check. Output:

unit    corpus-lesson: 1 file(s)
declare Review Unit: corpus-lesson
gates   none required for these paths
gate    description_check pr-owner-first.md
        description clean
gate    node engine/skills/draft-pr/scripts/validate-pr-body.mjs --body-file pr-owner-first.md --changed-files-file <1 changed path(s)>
        PR body validation passed.
ok      preflight passed

• Not run: a new session obeying the rule. Blocker: the rule only takes effect when the next session loads the instructions, so it cannot be exercised before merge.

Revert Plan

Revert Plan

• Safe to revert? Yes
• Revert command: git revert <merge commit of this PR>
• Post-revert steps: None
• Data migration? No

🤖 Generated with Claude Code

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: c5634eaa-3d93-47ee-b396-b66e8ab249be)

[mergify]

Queued — the merge queue status continues in this comment ↓.

[EdbertChan]

@Mergifyio queue

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-10-13 10:13 UTC · Rule: admin-bypass · triggered by a @mergifyio queue command
• 🟠 Checks running · on draft merge queue: checking #1378 + #1381 + #1387 together on main (d9d05c4) #1396
• 🚫 Left the queue — 2026-10-13 10:15 UTC · at ade44cb6c7419e60fb3be832cbcca94e1174742d

This pull request spent 1 minute 55 seconds in the queue, with no time running CI.

Reason

Pull request #1387 has been merged manually at 8c43e89

Hint

You were too fast!

Waiting for

• check-success = lint
• check-success = test
• check-success = validate

All conditions

• check-success = lint
• check-success = test
• check-success = validate

Tick the box to put this pull request back in the merge queue (same as @mergifyio queue).

• Requeue this pull request

[mergify]

queue

☑️ The pull request has been merged manually

Details

The pull request has been merged manually at 8c43e89