repo-dispatch: drop the docs/repo-dispatch markdown artifact, put context in the tracking issue #28
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally filed by @coilysiren on 2026-05-19T08:10:24Z - https://github.com/coilysiren/repo-recall/issues/200
Proposal. Stop writing the per-dispatch markdown artifact at
docs/repo-dispatch/<slug>.md. Put all the frontmatter + prompt body directly into the tracking GitHub issue. One substrate, not two.Why this fits the existing model. The substrate-hygiene rule in
recall-dispatchSKILL.md already says: "No new state in repo-recall's local DB. Dispatch outcomes get derived from closed issues plus their commits." The markdown file is the one piece of dispatch state that isn't in GitHub. It already has a 1:1 tracking issue. Moving the prompt body into the issue body makes the substrate uniform and lets every consumer (planner, pickup, ingest, metrics) read one surface.What changes:
recall-dispatch). Stop writingdocs/repo-dispatch/<slug>.md. Create the tracking issue withlabel: repo-dispatch, title = the dispatch slug (or its description), body = the existing markdown (frontmatter as a fenced YAML block at the top, prompt verbatim below). Skip the file system entirely.tooling-autonomous-pickup). Instead of scanning~/.repo-recall/dispatch/<repo>/*.mdand writing.handledsidecars, scangh issue list --label repo-dispatch --state open --search "no:assignee"(or similar "not yet picked up" predicate). Parse the YAML frontmatter out of the issue body. The "handled" marker becomes an issue-side state change (assigning to a bot user, adding adispatched:picked-uplabel, or just relying on the existence of a comment).src/ingest/docs/repo_dispatch.rs). This module either deletes entirely or simplifies to a thin reader overlabeled_issues_by_state("repo-dispatch", ...)(a surface that already exists for the autonomy metrics rollup). Health check moves from "doesdocs/repo-dispatch/exist and parse" to "are there open repo-dispatch issues that look malformed."recall_dispatch_metricsalready derives from closed labeled issues. Mostly unchanged.Tradeoffs:
grep -r docs/repo-dispatch/(filesystem); that's probably a net win for cross-repo planning.docs/repo-dispatch/*.mdfiles keep ingesting until they're cleared by their corresponding closed tracking issues, then the ingest module retires. Or do a one-shot conversion that walks existing files, posts their bodies as comments on the matching tracking issues, and deletes the files. Either is fine; the latter is cleaner.Out of scope. The
tooling-autonomous-pickupDesktop "Start locally" card mechanism stays; only its source changes from on-disk queue to issue-list query.Origin. Surfaced from a LUCA design conversation about how
luca.askshould persist its Q&A. LUCA decided to skip the substrate-persisted shape entirely (everything LUCA writes will be skill-file changes, not markdown answer artifacts), but the same insight points at repo-dispatch's redundant artifact path.