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
- 賛成票
- 465
- 計画済み
- 4,364
- リリース済み
- (motir-core) `main` is RED — MOTIR-3086 widened the repo-pin domain after MOTIR-3078's migration test asserted the old rejection, and neither PR could see the other
- The design-result publisher red-lights every PARENT-RUN pull request that touches `design/**` — a container-addressed publish fails instead of no-opping
- (motir-core) Read a proposal with the SHIPPED quick view (editing disabled), REMOVE the proposal edit modal, and hold `PlanReviewItemDto` against `PlanItemProposedFields`
- (motir-core) The plan canvas renders the parent's ROADMAP LEVEL — breadcrumb + real siblings, with proposals overlaid in `add` style
- The plan review surface is NARROWER than the proposal it reviews — an out-of-plan parent renders as a root, and there is no read view for a proposed card
- Seven design mocks have never had a `.png` export — the three-file rule is stated in `CLAUDE.md` and enforced by nothing
- (motir-core) The deploy is STARVED, not lost — `ci.yml`'s workflow-level `cancel-in-progress` lets each merge kill the run in flight, so no run on `main` ever survives to reach Fly
- (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