TonioandPaperclip d8052a1742 docs(server): pin the no-first-task contract on the cloud seed path ...

PAP-67 r17.4. #11101 added a server-owned onboarding first-task path
(`POST /issues` with `onboardingFirstTask: true`, board actor + zero
issues) that stamps `ONBOARDING_FIRST_TASK_ORIGIN_KIND` and races safely
on the partial unique index `issues_onboarding_first_task_uq`. The seed
receiver creates an unstamped issue, so if it ever created the first task
on the cloud walk the company would get a *second*, greeting-less task
rendered as a user bubble — silently, because the uq index only guards
origin-stamped rows.

The seed Cloud sends is mission-only (`agent`/`firstTask` are never
populated by the signup wizard; a paperclip-cloud `node:test` pins it),
so `firstTaskTitle` is null on the cloud path and this branch stays
inert. Document that contract at the branch it protects; the branch is
retained for the endpoint's documented body.

Co-Authored-By: Paperclip <noreply@paperclip.ing>

2026-08-13 18:21:44 -07:00

..

scripts

fix(server): use stable tsx/cli entry point in dev-watch

2026-03-28 06:42:03 +07:00

src

docs(server): pin the no-first-task contract on the cloud seed path

2026-08-13 18:21:44 -07:00

CHANGELOG.md

chore: release v0.3.1

2026-03-12 13:09:22 -05:00

package.json

fix(server): export manual OpenTelemetry spans (#10565)

2026-07-31 12:47:57 -07:00

tsconfig.json

Fix root TypeScript solution config

2026-03-09 14:09:30 -05:00

vitest.config.ts

fix(test): stop flaky server-suite afterAll hook timeouts (#10024)

2026-07-22 11:51:30 -07:00