moooon
Motir
Vibe the project. Bring an idea — Motir's three AI layers plan it, track it, and ship it, end to end. You're looking at Motir, built in Motir.
- Vibe Project
- Open Source
- AI Agent
- AI Loop
- 5
- 요청
- 4
- 추천
- 443
- 계획됨
- 4,442
- 출시됨
- `startSprint`'s FOR UPDATE guard cannot lock an EMPTY set — the first activation races, and the index's refusal reaches the caller as a raw Prisma error
- 11.3.11 End-to-end conformance — drive the whole planning cadence as an EXTERNAL HTTP client with a real PATPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.3.10 Story vitest gate — coverage floor, the write→read seams, and the contract guards the planning endpoints owePublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.3.9 `GET /api/v1/projects/{projectKey}/ready` — the ready set in DISPATCH rank, with each row's dependency edgesPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.3.8 The two RANKED work-item collections — `GET /api/v1/projects/{projectKey}/backlog` and `GET /api/v1/sprints/{sprintId}/work-items`, paged in `backlogRank` orderPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.3.7 Sprint MEMBERSHIP in both directions — `POST /api/v1/sprints/{sprintId}/work-items` and `POST /api/v1/projects/{projectKey}/backlog/work-items`, atomic per batchPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.3.6 The sprint LIFECYCLE moves — `POST /api/v1/sprints/{sprintId}/start` and `/complete`, proven under REAL concurrencyPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.3.5 The sprint WRITE pair — `POST /api/v1/projects/{projectKey}/sprints` and `PATCH /api/v1/sprints/{sprintId}`, gated on `sprints:write` AND the sprint-admin rolePublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.3.4 The v1 SPRINT resource — its schema, the missing by-id service read, `GET /api/v1/projects/{projectKey}/sprints` and `GET /api/v1/sprints/{sprintId}`Public REST API — the versioned `/api/v1` integration surface every client shares
- 11.3.3 The v1 PROJECT resource schema + `GET /api/v1/projects` and `GET /api/v1/projects/{projectKey}`Public REST API — the versioned `/api/v1` integration surface every client shares
- 11.3.2 The ORDER-AGNOSTIC v1 page cursor — a signed, collection-scoped envelope around a service-owned positionPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.3.1 Decision — amend the `/api/v1` ADR: cursors over SERVICE-OWNED sort orders, the ranked-collection `totalCount`, the by-id re-presentation carve-out, and the page-projection second readPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.3 Projects, sprints, backlog and the ready set over `/api/v1`Public REST API — the versioned `/api/v1` integration surface every client shares
- Planning gap: status-derivation story was scoped upward-only (missed the symmetric downward cascade)
- (motir-core) `/planning` paints NOTHING until the roadmap read resolves — the workspace should open first and stream the canvas in
- 11.2.12 End-to-end conformance — drive the whole work-item journey as an EXTERNAL HTTP client with a real PATPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.2.11 Story vitest gate — coverage floor, the write→read seams, and the contract guards the work-item endpoints owePublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.2.10 `POST /api/v1/work-items/{key}/archive` and `/restore` — the reversible soft-remove, gated on `work_items:archive`Public REST API — the versioned `/api/v1` integration surface every client shares
- 11.2.9 `GET` + `POST` + `DELETE /api/v1/work-items/{key}/links` — the dependency and relationship edges, `blocked_by` includedPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.2.8 `GET` + `POST /api/v1/work-items/{key}/comments` — the discussion sub-resource, paged in the v1 cursor envelopePublic REST API — the versioned `/api/v1` integration surface every client shares