Fetch origin Once Before decision-triage's History Check

.agents/skills/decision-triage/SKILL.md

@@ -94,10 +94,15 @@ of its own.
    carrying `handoff`, `canonical-sweep`, or `deferred`, and keep the `deferred` count for the
    report. Mark the open `decision` issues as questions already queued.
 2. **Classify the rest** in batches, one `standard` classifier per batch, at most four running at
-   once. Each applies "Needs the Maintainer" above, which its brief quotes whole. Before that, it
-   checks whether a later change has already overtaken the issue, which is a cheap history check
-   rather than research. The check reads `git log origin/main` on the files the issue names, the
-   state of any child issues it tracks, and any later comment recording a decision. A fix merged
+   once. Before dispatching, the triaging session runs `git fetch origin main develop` once, and
+   stops and reports if it fails. A stale `main` reads an overtaken issue as `HELD`. A stale
+   `develop` reads a `HELD` one as open work. The subagents read the refs this fetch updated and
+   fetch nothing.
+   Each classifier applies "Needs the Maintainer" above, which its brief quotes whole. Before
+   that, it checks whether a later change has already overtaken the issue, which is a cheap
+   history check rather than research. The check reads `git log refs/remotes/origin/main` and
+   `git log refs/remotes/origin/develop` on the files the issue names. It also reads the state of
+   any child issues the issue tracks, and any later comment recording a decision. A fix merged
    into `develop` and not yet promoted makes the issue `HELD` awaiting promotion rather than
    `OVERTAKEN`. The queued `decision` issues get the same check and no classification beyond it.
    The classifier returns one line per issue in the form "Return Lines" below.
@@ -111,7 +116,8 @@ of its own.
    code. It returns in the form "Return Lines" below, and writes only to the scratch directory
    its brief names. A queued question a later change has already answered or overtaken comes
    back as `OVERTAKEN` rather than as options. A fix counts as that change only once it is on
-   `origin/main`.
+   `refs/remotes/origin/main`. The triaging session repeats step 2's fetch before dispatching,
+   under the same stop.
 4. **Record each question** before asking it, so the question survives an interrupted session.
    - For an `ASK`, comment the researched question on the issue and add the `decision` label.
    - For a `SPLIT`, file a new issue holding only the undecided item, carrying `decision`.

.claude-plugin/fleet-skills/.source-digests/decision-triage

@@ -1 +1 @@
-f5a2fe8201774e01
+442bfb38707552cd

.claude-plugin/fleet-skills/skills/decision-triage/SKILL.md

@@ -94,10 +94,15 @@ of its own.
    carrying `handoff`, `canonical-sweep`, or `deferred`, and keep the `deferred` count for the
    report. Mark the open `decision` issues as questions already queued.
 2. **Classify the rest** in batches, one `standard` classifier per batch, at most four running at
-   once. Each applies "Needs the Maintainer" above, which its brief quotes whole. Before that, it
-   checks whether a later change has already overtaken the issue, which is a cheap history check
-   rather than research. The check reads `git log origin/main` on the files the issue names, the
-   state of any child issues it tracks, and any later comment recording a decision. A fix merged
+   once. Before dispatching, the triaging session runs `git fetch origin main develop` once, and
+   stops and reports if it fails. A stale `main` reads an overtaken issue as `HELD`. A stale
+   `develop` reads a `HELD` one as open work. The subagents read the refs this fetch updated and
+   fetch nothing.
+   Each classifier applies "Needs the Maintainer" above, which its brief quotes whole. Before
+   that, it checks whether a later change has already overtaken the issue, which is a cheap
+   history check rather than research. The check reads `git log refs/remotes/origin/main` and
+   `git log refs/remotes/origin/develop` on the files the issue names. It also reads the state of
+   any child issues the issue tracks, and any later comment recording a decision. A fix merged
    into `develop` and not yet promoted makes the issue `HELD` awaiting promotion rather than
    `OVERTAKEN`. The queued `decision` issues get the same check and no classification beyond it.
    The classifier returns one line per issue in the form "Return Lines" below.
@@ -111,7 +116,8 @@ of its own.
    code. It returns in the form "Return Lines" below, and writes only to the scratch directory
    its brief names. A queued question a later change has already answered or overtaken comes
    back as `OVERTAKEN` rather than as options. A fix counts as that change only once it is on
-   `origin/main`.
+   `refs/remotes/origin/main`. The triaging session repeats step 2's fetch before dispatching,
+   under the same stop.
 4. **Record each question** before asking it, so the question survives an interrupted session.
    - For an `ASK`, comment the researched question on the issue and add the `decision` label.
    - For a `SPLIT`, file a new issue holding only the undecided item, carrying `decision`.

.github/skills/decision-triage/SKILL.md

@@ -94,10 +94,15 @@ of its own.
    carrying `handoff`, `canonical-sweep`, or `deferred`, and keep the `deferred` count for the
    report. Mark the open `decision` issues as questions already queued.
 2. **Classify the rest** in batches, one `standard` classifier per batch, at most four running at
-   once. Each applies "Needs the Maintainer" above, which its brief quotes whole. Before that, it
-   checks whether a later change has already overtaken the issue, which is a cheap history check
-   rather than research. The check reads `git log origin/main` on the files the issue names, the
-   state of any child issues it tracks, and any later comment recording a decision. A fix merged
+   once. Before dispatching, the triaging session runs `git fetch origin main develop` once, and
+   stops and reports if it fails. A stale `main` reads an overtaken issue as `HELD`. A stale
+   `develop` reads a `HELD` one as open work. The subagents read the refs this fetch updated and
+   fetch nothing.
+   Each classifier applies "Needs the Maintainer" above, which its brief quotes whole. Before
+   that, it checks whether a later change has already overtaken the issue, which is a cheap
+   history check rather than research. The check reads `git log refs/remotes/origin/main` and
+   `git log refs/remotes/origin/develop` on the files the issue names. It also reads the state of
+   any child issues the issue tracks, and any later comment recording a decision. A fix merged
    into `develop` and not yet promoted makes the issue `HELD` awaiting promotion rather than
    `OVERTAKEN`. The queued `decision` issues get the same check and no classification beyond it.
    The classifier returns one line per issue in the form "Return Lines" below.
@@ -111,7 +116,8 @@ of its own.
    code. It returns in the form "Return Lines" below, and writes only to the scratch directory
    its brief names. A queued question a later change has already answered or overtaken comes
    back as `OVERTAKEN` rather than as options. A fix counts as that change only once it is on
-   `origin/main`.
+   `refs/remotes/origin/main`. The triaging session repeats step 2's fetch before dispatching,
+   under the same stop.
 4. **Record each question** before asking it, so the question survives an interrupted session.
    - For an `ASK`, comment the researched question on the issue and add the `decision` label.
    - For a `SPLIT`, file a new issue holding only the undecided item, carrying `decision`.