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
- 6
- requests
- 4
- upvotes
- 520
- planned
- 5,600
- shipped
- (motir-core) Adding a Motir-hosted repository REPLACES the project's repo list instead of extending it — the first set row switches the domain off the repos the project already has
- (motir-core) `design/ai-planning` — the plan-review DETAIL surfaces: the out-of-plan PARENT signal and a proposal READ view
- (motir-core) The plan review rail's status tag collides with the plan title — the `<h2>` has no `min-w-0`, so a long unbreakable title overflows under the shrink-0 "Approved" pill
- Sweep the other `Promise.all` fan-outs whose arms OPEN transactions — a rejecting sibling abandons them mid-flight
- (motir-core) `rateLimit/guard.test.ts` takes the DEFAULT 250 ms store deadline, so a loaded runner fails it OPEN — the store-timeout arm MOTIR-2658 fixed in one file and left in the class
- A generation job that DIES leaves its plan `generating` forever — and that empty orphan still pauses the project's auto-plan cadence
- CI Vitest flake — two workers in shard 1 deadlock (`40P01`) on `truncateAuthTables`, killing a test whose body never ran
- The design tree's OTHER 277 failing ink/surface pairs — decide whether a mock's board CHROME owes AA, then sweep or codify
- Planning bug: a card written to remove an unverified mechanism claim carried two of its own — a false clause in its remediation, and a sweep scoped by a grep pattern rather than by the claim
- Planning bug: a guard's declined boundary was warranted by an unmeasured claim about its population's COMPOSITION — only the count had been measured, and the named fixture was 5 of 277
- A CLI token can open a plan it can never fill — and one empty `generating` plan pauses that project's auto-plan cadence forever
- An approved plan's blocked cards land as `todo` — materialize never derives a status from the edges it wires
- A null `base_ref` holds an item FOREVER — the repo-set gate fails closed on pre-existing PR rows, and only a new merge can re-evaluate it
- Planning bug: an acceptance criterion keyed on a COUNT that the code's own idempotency argument forbids — the falsifying comment sat one file from the card's own context refs
- The repository-set design assets specify a FAILING ink/surface pair — muted on `--el-surface-soft` (4.34:1), which the ink lint forbids in code but does not scan for in `design/**`
- `statusDerivation.ts` records the REFUTED debounce mechanism as the warrant for its not-debounced decision — three comment blocks survived MOTIR-2994's measurement
- The Development section shows "No pull request yet" for a repository whose pull request is listed directly above it
- (motir-core) `rateLimit/guard.test.ts` never aligns its window — the LAST unswept member of the epoch-boundary class, and the alignment guard is structurally blind to it
- Planning bug: MOTIR-2757 sat `todo`/`high`/ready for two days after MOTIR-2796's sweep shipped its entire deliverable — every readiness signal read green
- (motir-ai) Mirror the ALREADY-LINKED-KEY clause into `SHARED_PLANNING_RULES` — an existing edge to a key is not evidence its status was resolved