Remove markdown-emit endpoints (dispatch / structural-asks / agents-drift) #37

New issue

Closed

opened 2026-05-23 20:55:25 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-05-23 20:55:25 +00:00

Owner

Originally filed by @coilysiren on 2026-05-14T22:48:41Z - https://github.com/coilysiren/repo-recall/issues/150

Make repo-recall fully read-only. Today three endpoints write markdown into discovered repos:

POST /api/repos/{id}/dispatches + mcp::recall_record_dispatch -> <repo>/docs/repo-dispatch/<slug>.md plus mirror at ~/.repo-recall/dispatch/<repo>/<slug>.md
structural-asks emitter -> <repo>/docs/structural-asks/<slug>.md plus mirror
agents-drift emitter -> <repo>/docs/agents-drift/<slug>.md plus mirror

Reasoning: the autonomous engineering flow that motivated these emitters belongs to the agent driving the MCP session, not to repo-recall. repo-recall reads. The agent writes through whatever its own tooling already supports (gh issues, direct git, etc.). Removing the writes simplifies the security model (cache-only writes), tightens the IO surface, and removes a feature that no consumer outside the autonomous loop calls.

Scope:

Remove POST /api/repos/{id}/dispatches and recall_record_dispatch MCP tool
Remove src/display/dispatch_artifacts.rs (write-once emitter)
Remove the structural-asks emit code in src/process/structural_asks.rs (keep the read path that ingests existing files)
Remove the agents-drift emit code in src/process/agents_drift.rs (keep the read path)
Update SECURITY.md write list (when #147 v2 lands) and AGENTS.md
Drop REPO_RECALL_DISPATCH_ROOT, REPO_RECALL_STRUCTURAL_ASKS_ROOT, REPO_RECALL_AGENTS_DRIFT_ROOT from config schema

Out of scope:

Reading existing dispatch / structural-ask / agents-drift markdown files in discovered repos. The ingest stays; only the emit goes.

Designed in chat 2026-05-14.

_Originally filed by @coilysiren on 2026-05-14T22:48:41Z - [https://github.com/coilysiren/repo-recall/issues/150](https://github.com/coilysiren/repo-recall/issues/150)_ Make repo-recall fully read-only. Today three endpoints write markdown into discovered repos: - `POST /api/repos/{id}/dispatches` + `mcp::recall_record_dispatch` -> `<repo>/docs/repo-dispatch/<slug>.md` plus mirror at `~/.repo-recall/dispatch/<repo>/<slug>.md` - structural-asks emitter -> `<repo>/docs/structural-asks/<slug>.md` plus mirror - agents-drift emitter -> `<repo>/docs/agents-drift/<slug>.md` plus mirror Reasoning: the autonomous engineering flow that motivated these emitters belongs to the agent driving the MCP session, not to repo-recall. repo-recall reads. The agent writes through whatever its own tooling already supports (gh issues, direct git, etc.). Removing the writes simplifies the security model (cache-only writes), tightens the IO surface, and removes a feature that no consumer outside the autonomous loop calls. Scope: - Remove `POST /api/repos/{id}/dispatches` and `recall_record_dispatch` MCP tool - Remove `src/display/dispatch_artifacts.rs` (write-once emitter) - Remove the structural-asks emit code in `src/process/structural_asks.rs` (keep the read path that ingests existing files) - Remove the agents-drift emit code in `src/process/agents_drift.rs` (keep the read path) - Update SECURITY.md write list (when #147 v2 lands) and AGENTS.md - Drop `REPO_RECALL_DISPATCH_ROOT`, `REPO_RECALL_STRUCTURAL_ASKS_ROOT`, `REPO_RECALL_AGENTS_DRIFT_ROOT` from config schema Out of scope: - Reading existing dispatch / structural-ask / agents-drift markdown files in discovered repos. The ingest stays; only the emit goes. Designed in chat 2026-05-14.

coilysiren added the

label

2026-05-31 01:55:03 +00:00

coilysiren commented

2026-06-17 08:24:30 +00:00

Author

Owner

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.

coilysiren

2026-06-17 08:24:30 +00:00