mirror of
https://github.com/alkimake/paperclip.git
synced 2026-06-15 18:30:39 +09:00
## Thinking Path > - Paperclip orchestrates AI agents for zero-human companies > - Reliable execution depends on heartbeat routing, issue lifecycle semantics, telemetry, and a fast enough local verification loop to keep regressions visible > - The remaining commits on this branch were mostly server/runtime correctness fixes plus test and documentation follow-ups in that area > - Those changes are logically separate from the UI-focused issue-detail and workspace/navigation branches even when they touch overlapping issue APIs > - This pull request groups the execution reliability, heartbeat, telemetry, and tooling changes into one standalone branch > - The benefit is a focused review of the control-plane correctness work, including the follow-up fix that restored the implicit comment-reopen helpers after branch splitting ## What Changed - Hardened issue/heartbeat execution behavior, including self-review stage skipping, deferred mention wakes during active execution, stranded execution recovery, active-run scoping, assignee resolution, and blocked-to-todo wake resumption - Reduced noisy polling/logging overhead by trimming issue run payloads, compacting persisted run logs, silencing high-volume request logs, and capping heartbeat-run queries in dashboard/inbox surfaces - Expanded telemetry and status semantics with adapter/model fields on task completion plus clearer status guidance in docs/onboarding material - Updated test infrastructure and verification defaults with faster route-test module isolation, cheaper default `pnpm test`, e2e isolation from local state, and repo verification follow-ups - Included docs/release housekeeping from the branch and added a small follow-up commit restoring the implicit comment-reopen helpers that were dropped during branch reconstruction ## Verification - `pnpm vitest run server/src/__tests__/issue-comment-reopen-routes.test.ts server/src/__tests__/issue-telemetry-routes.test.ts` - `pnpm vitest run server/src/__tests__/http-log-policy.test.ts server/src/__tests__/heartbeat-run-log.test.ts server/src/__tests__/health.test.ts` - `server/src/__tests__/activity-service.test.ts`, `server/src/__tests__/heartbeat-comment-wake-batching.test.ts`, and `server/src/__tests__/heartbeat-process-recovery.test.ts` were attempted on this host but the embedded Postgres harness reported init-script/data-dir problems and skipped or failed to start, so they are noted as environment-limited ## Risks - Medium: this branch changes core issue/heartbeat routing and reopen/wakeup behavior, so regressions would affect agent execution flow rather than isolated UI polish - Because it also updates verification infrastructure, reviewers should pay attention to whether the new tests are asserting the right failure modes and not just reshaping harness behavior ## Model Used - OpenAI Codex coding agent (GPT-5-class runtime in Codex CLI; exact deployed model ID is not exposed in this environment), reasoning enabled, tool use and local code execution enabled ## Checklist - [x] I have included a thinking path that traces from project context to this change - [x] I have specified the model used (with version and capability details) - [ ] I have run tests locally and they pass - [x] I have added or updated tests where applicable - [ ] If this change affects the UI, I have included before/after screenshots - [x] I have updated relevant documentation to reflect my changes - [x] I have considered and documented any risks above - [x] I will address all Greptile and reviewer comments before requesting merge --------- Co-authored-by: Paperclip <noreply@paperclip.ing>
61 lines
2.1 KiB
TypeScript
61 lines
2.1 KiB
TypeScript
import express from "express";
|
|
import request from "supertest";
|
|
import { describe, expect, it, vi } from "vitest";
|
|
|
|
/**
|
|
* Regression test for https://github.com/paperclipai/paperclip/issues/2898
|
|
*
|
|
* Express 5 (path-to-regexp v8+) dropped support for the `*paramName`
|
|
* wildcard syntax used in Express 4. Routes declared with the old syntax
|
|
* silently fail to match, causing every `/api/auth/*` request to fall
|
|
* through and return 404.
|
|
*
|
|
* The correct Express 5 syntax for a named catch-all is `{*paramName}`.
|
|
* These tests verify that the better-auth handler is invoked for both
|
|
* shallow and deep auth sub-paths.
|
|
*/
|
|
describe("Express 5 /api/auth wildcard route", () => {
|
|
function buildApp() {
|
|
const app = express();
|
|
let callCount = 0;
|
|
const handler = (_req: express.Request, res: express.Response) => {
|
|
callCount += 1;
|
|
res.status(200).json({ ok: true });
|
|
};
|
|
app.all("/api/auth/{*authPath}", handler);
|
|
return {
|
|
app,
|
|
getCallCount: () => callCount,
|
|
};
|
|
}
|
|
|
|
it("matches a shallow auth sub-path (sign-in/email)", async () => {
|
|
const { app } = buildApp();
|
|
const res = await request(app).post("/api/auth/sign-in/email");
|
|
expect(res.status).toBe(200);
|
|
});
|
|
|
|
it("matches a deep auth sub-path (callback/credentials/sign-in)", async () => {
|
|
const { app } = buildApp();
|
|
const res = await request(app).get(
|
|
"/api/auth/callback/credentials/sign-in"
|
|
);
|
|
expect(res.status).toBe(200);
|
|
});
|
|
|
|
it("does not match unrelated paths outside /api/auth", async () => {
|
|
// Confirm the route is not over-broad — requests to other API paths
|
|
// must fall through to 404 and not reach the better-auth handler.
|
|
const { app, getCallCount } = buildApp();
|
|
const res = await request(app).get("/api/other/endpoint");
|
|
expect(res.status).toBe(404);
|
|
expect(getCallCount()).toBe(0);
|
|
});
|
|
|
|
it("invokes the handler for every matched sub-path", async () => {
|
|
const { app, getCallCount } = buildApp();
|
|
await request(app).post("/api/auth/sign-out");
|
|
await request(app).get("/api/auth/session");
|
|
expect(getCallCount()).toBe(2);
|
|
});
|
|
});
|