From fef4e67ce2f30514a5195a446a39954b99231060 Mon Sep 17 00:00:00 2001 From: Jarek Potiuk Date: Sun, 31 May 2026 20:15:22 +0200 Subject: [PATCH] =?UTF-8?q?feat(github-rollup):=20append=20helper=20for=20?= =?UTF-8?q?status-rollup=20comments=20=E2=80=94=20read/PATCH=20out=20of=20?= =?UTF-8?q?context?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Every status-update-emitting skill (sync, import, allocate, dedupe, fix) folds its update into one rollup comment per tracker via the recipe in `tools/github/status-rollup.md`. The recipe currently walks the agent through: fetch the comment body, concatenate `` + ruler + new entry, PATCH the comment. That loops the full rollup body — which grows monotonically on long-running trackers — through agent context on every sync pass. `tools/github-rollup/` is the same shape as PR #412's `github-body-field`: a stdlib + `gh` subprocess wrapper that keeps the body out of agent context. CLI: github-rollup append --action "