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
- 추천
- 442
- 계획됨
- 4,442
- 출시됨
- PLANNING BUG — 11.6's family cards froze their MCP suites "unmodified" while the story's own core change makes one of them false: `key` means the numeric key on MCP work-item rows and the identifier on `/api/v1`Public REST API — the versioned `/api/v1` integration surface every client shares
- 11.7.9 End-to-end conformance — walk the whole work loop as an EXTERNAL HTTP client with a real PATPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.7.8 Story vitest gate — coverage floor, the service→schema→response seams, and the contract guards this surface owesPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.7.7 The ACTIVITY read over `/api/v1` — the change trail beside the comments, and its opaque composite cursorPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.7.6 The planning CONVERSATION over `/api/v1` — open/resume by scope, append one turn, submit the accumulated threadPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.7.5 Expansion + the two PLAN reads over `/api/v1` — submit a job, read its outcome, read the plan with its proposalsPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.7.4 Session close-out over `/api/v1` — record one item as integrated, and bulk-close a merged branch with per-item outcomesPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.7.3 The work-loop RESOURCE SCHEMA module + `GET …/dispatch-prompt` — the representation every other endpoint in this story returns intoPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.7.2 The three FIELD PROJECTIONS on the shipped work-item schemas — per-child edges, per-row edges, and the blocked ancestor's titlePublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.7.1 Decision — amend the ADR for the work-loop resources: paths and verbs, scope MIRRORING, the job-handle response shape, and the three projections as §8 additionsPublic REST API — the versioned `/api/v1` integration surface every client shares
- 11.7 The WORK-LOOP operations over `/api/v1` — dispatch, session close-out, expansion, the planning conversation, the activity read, and the three edge projections the shipped reads omitPublic REST API — the versioned `/api/v1` integration surface every client shares
- Flaky: `story-gate.test.ts > a VALID token refused for SCOPE (403) DOES spend budget` — the same epoch-aligned-window race MOTIR-2101 fixed, left unswept in a sibling file
- (motir-core) Cancelling a human/manual work item stamps `implementationSource: 'manual'` — the live transition lane counts `cancelled` as implemented, and the backfill's own doc says it doesn't
- 11.1.7 `/api/v1/me` and `/api/v1/workspaces` MAP through `lib/api/v1/identity/schema.ts` — the shape becomes the value the routes emit, not a description beside themPublic REST API — the versioned `/api/v1` integration surface every client shares
- (motir-ai) Re-point `MOTIR_META_BUG_PARENT_KEY` to the `@planner-bug-home` marker — MOTIR-1466's unfinished consumer half
- (motir-core) The `@planner-bug-home` marker resolves through a mutable child row, so a single re-parent silently stops it resolving
- (planning) ADR Amendment 2's schema-ownership split silently OMITS Story 11.1's own two endpoints — `/api/v1/me` and `/api/v1/workspaces` had no owner, so 11.4.5 had to author their shapesPublic REST API — the versioned `/api/v1` integration surface every client shares
- (motir-core) `board-at-scale` test 4 fails on EVERY first attempt — test 3 persists `groupBy=Assignee` on the shared board and CI's `retries: 1` re-runs `beforeAll`, hiding it
- (motir-core) Three MORE seeders write a `position` the product cannot mint — `scripts/seed-large.ts` pads to 8, and the two board E2E specs write `p0000001` (invalid LENGTH, not head)
- 11.4.10 Story E2E + acceptance video — a developer finds the reference, reads an operation, follows getting-started, and reaches it from both doorsPublic REST API — the versioned `/api/v1` integration surface every client shares