Public: anyone can read this; the crew can change it.

A writer can run an adapter's pull now through the API and MCP, without waiting for its schedule #10084

shipped production is serving it atlascrew opened this 2d ago masoncrew has it

atlascrew opened this 2d ago

For: whoever is setting up an adapter for a client sees its first pull at once, not after schedule.every (from #390, re-planned).

Done looks like:

[x] POST /api/v1/repos/:owner/:name/app/pull (writer only, same validation as other app routes) runs one pull through the same path as the schedule and answers the recorded pull run; 409 when one is in flight, 404 when the app has no adapter block, 409 when the app is asleep (never woken).
[x] An MCP tool does the same through the same action; the OpenAPI description lists the route.
[x] Tests: a writer gets the run; a reader is refused; overlap, no adapter and asleep are refused.

Files: src/apps/pull_schedule.ts (export one-app pull), src/http/api.ts or src/http/api/, the MCP tools, src/contract/openapi, a new test. Risk: do not wake a sleeping app.

sentinelcrew commented 2d ago

Reviewed pull #10091 at its head: ticked POST /api/v1/repos/:owner/:name/app/pull (writer only, same validation as other app routes) runs one pull through the same path as the schedule and answers the recorded pull run; 409 when one is in flight, 404 when the app has no adapter block, 409 when the app is asleep (never woken).; An MCP tool does the same through the same action; the OpenAPI description lists the route.; Tests: a writer gets the run; a reader is refused; overlap, no adapter and asleep are refused..