meta-retrospective: no source-access resolution order — first run bulk-delegated to a busy peer session #32

New issue

Closed

opened 2026-08-13 11:55:55 +00:00 by jbr870 · 1 comment

jbr870 commented

2026-08-13 11:55:55 +00:00

Owner

Observation

The first /meta-retrospective run (2026-08-13) requested bulk data gathering (a forge-wide learning scan + run reconstruction) from a live peer session that was mid-/develop on its own feature — before checking whether this box could do the work itself. It could: an authenticated glab made the whole drain ~6 read-only API calls locally. The peer rightly deferred, but absent a withdrawal it would have spent its release-session context later on work that was already done. The only irreplaceable thing the peer contributed was its first-hand observation of a same-day friction — which cost it one message.

Operator feedback (2026-08-13): don't let another session spend its context on work this session can do.

Recurrence

Mechanical-adjacent: first run of the skill, direct operator correction. The skill text currently says to drain each source project "from inside that project's checkout" and is silent on how to resolve access when there is no local checkout — which is exactly where the misjudgment happened.

Hypothesis

Add a source-access resolution order to meta-retrospective's Inputs section: local checkout → local authenticated read-only forge CLI (meta-lane exemption, reads only — mutations still require the helpers) → a fresh dedicated agent on the remote box → a live working session LAST, and then only for what only it has (first-hand observations), never bulk gathering. Withdraw standing requests once satisfied.

Suggested lane

meta-amend (one subsection in meta-retrospective/SKILL.md).

## Observation The first /meta-retrospective run (2026-08-13) requested bulk data gathering (a forge-wide learning scan + run reconstruction) from a live peer session that was mid-`/develop` on its own feature — before checking whether this box could do the work itself. It could: an authenticated glab made the whole drain ~6 read-only API calls locally. The peer rightly deferred, but absent a withdrawal it would have spent its release-session context later on work that was already done. The only irreplaceable thing the peer contributed was its first-hand observation of a same-day friction — which cost it one message. Operator feedback (2026-08-13): don't let another session spend its context on work this session can do. ## Recurrence Mechanical-adjacent: first run of the skill, direct operator correction. The skill text currently says to drain each source project "from inside that project's checkout" and is silent on how to resolve access when there is no local checkout — which is exactly where the misjudgment happened. ## Hypothesis Add a source-access resolution order to meta-retrospective's Inputs section: local checkout → local authenticated read-only forge CLI (meta-lane exemption, reads only — mutations still require the helpers) → a fresh dedicated agent on the remote box → a live working session LAST, and then only for what only it has (first-hand observations), never bulk gathering. Withdraw standing requests once satisfied. ## Suggested lane meta-amend (one subsection in meta-retrospective/SKILL.md).

jbr870 added the

component:shared

type:bug

labels

2026-08-13 11:55:55 +00:00

jbr870 commented

2026-08-13 11:56:34 +00:00

Author

Owner

Outcome — amended (commit `96f957a`)

Added a "Source-access resolution order" subsection to meta-retrospective/SKILL.md Inputs: local checkout → local authenticated read-only forge CLI (checked before asking anyone; reads sanctioned as meta-lane exemption, mutations still helper-only) → fresh dedicated agent on the remote box → live working session last, restricted to first-hand observations, with explicit withdrawal once satisfied.

Gate: lint-conventions clean. Desk-check against the originating scenario: with this text, the first run would have checked glab auth status at step 2 and never messaged the release session for the drain; the one legitimate ask (the session's own same-day observation) still lands on rung 4. The standing request to verity-release was withdrawn today before it spent context on it.

Validates next real retrospective run.

## Outcome — amended (commit 96f957a) Added a "Source-access resolution order" subsection to meta-retrospective/SKILL.md Inputs: local checkout → local authenticated read-only forge CLI (checked *before* asking anyone; reads sanctioned as meta-lane exemption, mutations still helper-only) → fresh dedicated agent on the remote box → live working session last, restricted to first-hand observations, with explicit withdrawal once satisfied. Gate: lint-conventions clean. Desk-check against the originating scenario: with this text, the first run would have checked `glab auth status` at step 2 and never messaged the release session for the drain; the one legitimate ask (the session's own same-day observation) still lands on rung 4. The standing request to verity-release was withdrawn today before it spent context on it. Validates next real retrospective run.

jbr870 closed this issue

2026-08-13 11:56:35 +00:00

jbr870 referenced this issue from a commit

2026-08-13 12:06:38 +00:00

meta-retrospective: add the source-access resolution order (#32)

jbr870 referenced this issue

2026-08-15 13:01:46 +00:00

Ship the suite as a Claude Code marketplace plugin (repo move, plugin root, CLAUDE_PLUGIN_ROOT paths, namespacing) #50