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
- solicitações
- 4
- votos
- 414
- planejadas
- 4.220
- entregues
- Planning bug: MOTIR-4375's children asserted THREE fields that do not exist — a 12-property body that has 14, a catalogue `examples` field, and a 4-key grant that has 6
- Planning bug: a bug card asserted a check "does not have one" three days after the check merged — the negative was never grepped, and the card cites the shipping story's own sibling
- Planning bug: MOTIR-5295 told the run to gate a new MCP tool on one key and "let the service's role check decide" — which would have handed a narrowed token its owner's moderation reach
- Planning bug: a pass that LAYS SEVERAL cards searched the lesson store ONCE, so the rarest risk in the set — a destructive migration with a recorded three-phase protocol — was never ranked for
- Planning bug: a card BLOCKED BY a design pre-specified that design's OUTPUT as its own acceptance criteria — so the design's arrival read as a wording nit, and the card sat at exactly the over-sizing threshold
- Planning bug: an acceptance criterion asked a run to open author sessions "only for the proposals the request touches" — nothing on the seed can carry that, because the sessions open before the model says what it is touching
- Planning bug: the dispatched agent's re-plan door was planned as a CLI shell-out, while every other instruction in the SAME protocol is an MCP tool call
- (motir-ai) Retire the limb from the PACK and the SEEDED LESSON — one repo, two channels, and the lesson needs a migration
- (motir-core · test) `acceptance-approvals-tab.spec.ts` ejects merge-queue entries — its page-rooted `getByText('Nothing is waiting on your approval')` matches a HIDDEN second copy of the empty state (7th strict-locator incident)
- (motir-core · design) `design/agent-sandbox/` still ARGUES for the container MOTIR-4972 threw away — the asset says "there is no `--rm`, and the container is named", and calls that departure deliberate
- (motir-core) The tests type-check project sits at 89% of the heap on main — a story adding ~40 test files crosses the 90% tripwire; split tests/components into its own projectApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The work item page renders TWO `main` landmarks — the shell's and the page's own `<main>`
- (motir-core) The GitLab connect screen says connecting "adds a webhook for merge-request and pipeline events" — no code registers any GitLab webhook
- (motir-core) THE LANDING CASCADE — `/workbench` reads the counts it already fetches and forwards to To approve, else In progress, else To doApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) Playwright acceptance E2E + VIDEO — sign in three times and be landed on To approve, then In progress, then To do, and ask for an empty tab by address (en + zh)Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The story's VITEST GATE — the coverage floor over the changed surface, the axis → strip → page seam, and the guards a percentage cannot see (one canonical URL per tab, totality over the five)Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) EVERY TAB BECOMES ADDRESSABLE — `?tab=` for all five including To approve, `/workbench` stops being a tab address, and every helper and spec that assumed the bare path is sweptApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The strip ORDER — To approve · In progress · To do · Recently finished · Watching, in `WORKBENCH_TABS` and the rendered nav, with the default left exactly where it isApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- You land on what is WAITING ON YOU — the Workbench leads with To approve, and the landing CASCADES to the first tab that has something in itApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- 8.95 (motir-core) FOUR more callers resolve a repository BY WORKSPACE — `link_pull_request` raises `GithubRepoNotFoundError`, and the file-read and code-scanning seams degrade SILENTLY, in any workspace but the one the App was installed from