`GET …/app/pulls` lists an adapter's recorded pull runs, newest first #10112

GET /api/v1/repos/:owner/:name/app/pulls now returns an app's recorded pull runs as { items, next_cursor: null }, newest first. ?limit= takes a whole number from 1 to 100 (default 20); anything else gets a 422. Each item is { id, at, durationMs, state, error, written, skipped, failed, cursor, repeat }. error holds the failure sentence and is null on a good run. cursor is null after a failed run.

What to look at

• Read function: pullRunLines(db, appId, limit) in src/apps/pull.ts reads the rows through the existing listPullRuns and returns plain data, so a page or MCP can reuse it. The work already in flight here (#10037, #10084) is untouched.
• Route: it lives in a new small module, src/http/api/app_pulls.ts, registered next to appRoutes. It uses the same gate as GET …/app: anyone who can read the repository sees the runs, including a guest on a public app. Anyone else, or a repository with no app, gets 404. There is deliberately no token-scope check: one would have turned a guest's 404 into a 401, so a stranger could tell the private app exists.
• OpenAPI: the route is in src/contract/openapi/routes/getApiV1ReposOwnerNameAppPulls.ts, with the limit bound taken from the same constant the handler uses. The index was regenerated with bun scripts/openapi-routes.ts.
• Docs: the Status section of docs/ADAPTERS.md now says the API reads the runs.
• Test: test/adapter-pulls-api.test.ts records a good and a failed run and reads them back newest first. It checks the limit and its 422s, and that the owner can read a private app's runs while another member and a guest get 404, as does a repository that doesn't exist.

Left out

• MCP: no MCP action or page reads the runs yet. The function is ready for one, and test/mcp-size.test.ts passes unchanged.
• Paging: the list doesn't page, because 100 rows is the cap.
• Plan on the issue: I didn't keep one, because the keep_plan tool isn't available in this session.

Checks run: bun scripts/gate.ts, bun x tsc --noEmit, and the covering tests, all passing: the new test, app-pull-now, adapter-card, apps-adapter, contract, openapi* (coverage, limit-bounds, routes, served), route-timing-coverage, unreached and mcp-size. scripts/fast.ts named 1,564 files because src/http/api.ts changed, so the full suite is left to the forge's check.

Try it: curl https://lab--<pull>--forge-trevato-apps.open-platform.sh/api/v1/repos/<owner>/<app>/app/pulls?limit=5

🤖 Generated with Claude Code

Closes #10101

GET /api/v1/repos/:owner/:name/app/pulls now returns an app's recorded pull runs as { items, next_cursor: null }, newest first. ?limit= takes a whole number from 1 to 100 (default 20); anything else gets a 422. Each item is { id, at, durationMs, state, error, written, skipped, failed, cursor, repeat }. error holds the failure sentence and is null on a good run. cursor is null after a failed run.

What to look at

• Read function: pullRunLines(db, appId, limit) in src/apps/pull.ts reads the rows through the existing listPullRuns and returns plain data, so a page or MCP can reuse it. The work already in flight here (#10037, #10084) is untouched.
• Route: it lives in a new small module, src/http/api/app_pulls.ts, registered next to appRoutes. It uses the same gate as GET …/app: anyone who can read the repository sees the runs, including a guest on a public app. Anyone else, or a repository with no app, gets 404. There is deliberately no token-scope check: one would have turned a guest's 404 into a 401, so a stranger could tell the private app exists.
• OpenAPI: the route is in src/contract/openapi/routes/getApiV1ReposOwnerNameAppPulls.ts, with the limit bound taken from the same constant the handler uses. The index was regenerated with bun scripts/openapi-routes.ts.
• Docs: the Status section of docs/ADAPTERS.md now says the API reads the runs.
• Test: test/adapter-pulls-api.test.ts records a good and a failed run and reads them back newest first. It checks the limit and its 422s, and that the owner can read a private app's runs while another member and a guest get 404, as does a repository that doesn't exist.

Left out

• MCP: no MCP action or page reads the runs yet. The function is ready for one, and test/mcp-size.test.ts passes unchanged.
• Paging: the list doesn't page, because 100 rows is the cap.
• Plan on the issue: I didn't keep one, because the keep_plan tool isn't available in this session.

Checks run: bun scripts/gate.ts, bun x tsc --noEmit, and the covering tests, all passing: the new test, app-pull-now, adapter-card, apps-adapter, contract, openapi* (coverage, limit-bounds, routes, served), route-timing-coverage, unreached and mcp-size. scripts/fast.ts named 1,564 files because src/http/api.ts changed, so the full suite is left to the forge's check.

Try it: curl https://lab--<pull>--forge-trevato-apps.open-platform.sh/api/v1/repos/<owner>/<app>/app/pulls?limit=5

🤖 Generated with Claude Code

GET /api/v1/repos/:owner/:name/app/pulls now returns an app's recorded pull runs as { items, next_cursor: null }, newest first. ?limit= takes a whole number from 1 to 100 (default 20); anything else gets a 422. Each item is { id, at, durationMs, state, error, written, skipped, failed, cursor, repeat }. error holds the failure sentence and is null on a good run. cursor is null after a failed run.

What to look at

• Read function: pullRunLines(db, appId, limit) in src/apps/pull.ts reads the rows through the existing listPullRuns and returns plain data, so a page or MCP can reuse it. The work already in flight here (#10037, #10084) is untouched.
• Route: it lives in a new small module, src/http/api/app_pulls.ts, registered next to appRoutes. It uses the same gate as GET …/app: anyone who can read the repository sees the runs, including a guest on a public app. Anyone else, or a repository with no app, gets 404. There is deliberately no token-scope check: one would have turned a guest's 404 into a 401, so a stranger could tell the private app exists.
• OpenAPI: the route is in src/contract/openapi/routes/getApiV1ReposOwnerNameAppPulls.ts, with the limit bound taken from the same constant the handler uses. The index was regenerated with bun scripts/openapi-routes.ts.
• Docs: the Status section of docs/ADAPTERS.md now says the API reads the runs.
• Test: test/adapter-pulls-api.test.ts records a good and a failed run and reads them back newest first. It checks the limit and its 422s, and that the owner can read a private app's runs while another member and a guest get 404, as does a repository that doesn't exist.
• Gate fix: the first push failed the gate because no commit message said why the work goes now or how to try it. An empty follow-up commit adds the Why now: and Try: lines, so no force push was needed.

Left out

• MCP: no MCP action or page reads the runs yet. The function is ready for one, and test/mcp-size.test.ts passes unchanged.
• Paging: the list doesn't page, because 100 rows is the cap.
• Plan on the issue: I didn't keep one, because the keep_plan tool isn't available in this session.

Checks run:

• First push: gate, type check and the covering tests all passed. The tests were the new one, app-pull-now, adapter-card, apps-adapter, contract, openapi* (coverage, limit-bounds, routes, served), route-timing-coverage, unreached and mcp-size.
• After the gate fix: FORGE_CHECK_BASE=0c3a3ea5 bun scripts/gate.ts and bun x tsc --noEmit pass, and so do test/adapter-pulls-api.test.ts and test/openapi-routes.test.ts.
• Full suite: scripts/fast.ts named 1,564 files because src/http/api.ts changed, so the full suite is left to the forge's check.

Try it: curl https://lab--<pull>--forge-trevato-apps.open-platform.sh/api/v1/repos/<owner>/<app>/app/pulls?limit=5

🤖 Generated with Claude Code