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
- suggestions
- 4
- votes
- 419
- planifiés
- 4 271
- livrés
- (motir-core) Settings → Organisation → Git offers `Connect GitHub` to an organisation that IS connected — the connection card asks a WORKSPACE question, and `github_installation` has no org read arm
- (motir-core) Correct the RECORD that made the three call sites look right — `20260906000000`'s first-arm guarantee is false, and the correction goes where a reader meets it
- (motir-core) The unlinked-PR check calls a SIBLING-workspace repository "not planned" — bind the org on `pullRequestLinkCheckService`'s `project_repository` read
- (motir-core) Attribute a SIBLING-workspace repository — bind the org AND take `organizationId` off the repo row, in the CI meter and the runner provisioner
- (motir-core) A repository linked from a SIBLING workspace is invisible to every SERVICE-context read of `project_repository` — CI minutes go unattributed, runner provisioning is refused, and the link check reports `not planned`
- (motir-core · test) Playwright's retry is INERT for three cloud specs — the seed creates a FIXED-email user, so attempt 2 dies in setup with `DuplicateEmailError` and REPLACES attempt 1's real failure in the report
- (motir-core) A repository nobody has pushed since MOTIR-4724 shipped reads `Current` FOREVER — the label claims currency the state cannot support
- (motir-core · test) `cloud-agent-runs`'s unscoped `getByText('Nothing has run yet')` hits strict mode in the MERGE QUEUE — green twice, red once, on app code that never changed
- (motir-core) `translateLinkViolation`'s P2002 fallback is UNCONDITIONALLY the name error — a lost repo-claim race is reported as "that name is taken", and it evicts merge-queue entries
- (motir-core) `Used by N projects` now OVER-reports — every set-less project is named against every connected repository, on the dialogue a disconnect leans on
- (motir-core) `Used by N projects` counts the repository SET only, so every connected repository reads “used by no project yet”
- (motir-core) `Code access` reads the repository SET only, so a project with connected repositories shows none — and nothing says how it differs from `Repositories`
- (motir-core) The project Repositories page names the ACTOR’s first organisation, not the project’s
- (motir-core) The shell brand mark links to `/dashboard`, not the landing — the product question MOTIR-3173 deliberately left, now answered; and the rail demotes `Dashboard` below `Backlog`
- 25 (motir-core) `publish_design_result` is unreachable for a real design asset — the door takes bytes INLINE, and the agent it is written for cannot emit them
- 24 (motir-core) The "Plan with AI" hero and the M orb render byte-identically in all 11 styles — the design's `[data-surface='ai-cta']` hook is emitted nowhere, and the fill is painted INLINE where no style rule can reach it
- 8.76 (motir-core) Sweep the E2E suite for the unguarded mutation→assert SHAPE — MOTIR-3694 swept one file, this card proposed to sweep the next one, and 770 candidate sites across 122 specs say the bound was never the file
- (motir-meta) MOTIR-4723 split the journey unit's APPLY STEPS in two and recorded only the half that MOVED — assertion 3 is RED on `origin/main`, one unrecorded divergence, for the clause that STAYED in `kind-container.md`
- (motir-meta) The SKILL doors cite nine pack paths that no guard checks — `MIRROR.check.py` assertion 7 sweeps `prompts/*.md` non-recursively, so the corpus's new front entrance can point at a retired pack under a green gate
- (motir-core) The ONBOARDING fact never crosses the wire — a `plan` submit carries no `context.onboarding`, so motir-ai guesses it from an EMPTY TREE and a migrate onboarding over an imported backlog is planned as continued work