Motir

← Back to the top level

• MOTIR-671bug-e2e-suite-flaky-specs E2E suite has flaky specs that intermittently red CI on unrelated PRs (drag-reorder reload, at-scale cursor paging, inline-edit reload, watch-popover hydration)done
• MOTIR-672bug-e2e-custom-fields-empty-state-hydration-flake Custom-fields E2E spec flakes on the Fields-admin empty state — finding-#89 hydration churn recurs on a surface bug-e2e-suite-flaky-specs did not coverdone
• MOTIR-13128.15 Switching org leaves stale old-org content in the page body (switchers refresh in place; no navigation)done
• MOTIR-13138.16 Create-work-item modal renders "Explanation" twice (disclosure header + editor label)done
• MOTIR-13148.17 /dashboard (DashboardsHome) list card has no data-surface — Neumorphism (and glass/aurora) material never reaches itdone
• MOTIR-13158.18 Hand-Drawn style stops short of the app shell — rail/top-bar frame borders aren't rougheneddone
• ▸MOTIR-1465Captured planning-mistake bugstodo
• MOTIR-1565E2E flake: a bulk shard's whole shell-flows suite reds when the Playwright webServer / inngest dev server fails to come up (sign-up 404 + inngest 404)done
• MOTIR-1679Playwright E2E bulk shards flake: webServer OOM → ERR_CONNECTION_RESET / page.goto timeoutsdone
• MOTIR-1699E2E flake (recurring, 4 PRs): project-isolation.spec.ts:203 — captureSetActiveProjectAction waitForResponse 10s timeout on bulk-4 under loaddone
• MOTIR-1734Acceptance-video uploader publishes only ONE clip per lane run — every extra chaptered acceptance spec is silently droppeddone
• MOTIR-1736Vitest flake (recurring, 2 PRs): ProjectRoadmapCanvas.test.tsx:128 — the auto-reset assertion races the auto-layout effect instead of awaiting itdone
• MOTIR-1737Two more component tests carry the MOTIR-1736 effect-ordering race (OnboardingCanvasRoadmap, TierDocModal) — found by a scheduler-ordering audit worth keepingdone
• MOTIR-1738Evaluate the ROOT fix for the component-test effect-ordering class: IS_REACT_ACT_ENVIRONMENT = true (a ~30-file act() migration)done
• MOTIR-1742CI infra flake (3 PRs in a row): E2E legs die at `Initialize containers` when `docker pull postgres:16-alpine` can't reach Docker Hub — pre-pull/mirror the service image instead of re-runningdone
• MOTIR-2039Work-item description: a Markdown TABLE overflows the description card and paints across the right rail — `.motir-prose` has no `table` rules at all (no scroll container, no borders)done
• MOTIR-2043Bare-key normalization is Markdown-structure-blind: it rewrites work-item keys inside inline code spans, fenced code blocks and link destinations — and PERSISTS the corruption into the stored bodydone
• MOTIR-2050An ARCHIVED work item still shows the green "Ready to start" banner on the detail page and in the quick-view peek — and the peek shows no archived state at all (neither surface gates on `archivedAt`)done
• MOTIR-2074(motir-core) The GitLab concurrent-redelivery test asserts an outcome its OWN comment says is timing-dependent — `is idempotent under concurrent redelivery` flakes red on a loaded CI runnerdone
• MOTIR-2083PLANNING RULES (motir-meta) — two standing per-card gates: an AC must be satisfiable inside the card's own scope boundary, and a bug found mid-story is parented BY that storydone
• MOTIR-2084The Plan / Re-plan entrance still renders on a DONE / CANCELLED work item — the detail page and the quick-view peek gate on canEdit + archived but never on the terminal status categorydone
• MOTIR-2089(motir-ai) MIRROR the two new planning rules into `SHARED_PLANNING_RULES` — the shipped planner learns them too, not just the manual onedone
• MOTIR-2095PLANNING BUG — MOTIR-2082's ACs cited an RLS system-admin branch that does not exist; a card asserting a CODE FACT must have grepped it on origin/maindone
• MOTIR-2097The Plan / Re-plan RULE is not applied everywhere — the /items row ⋯ menu has no terminal gate and offers Re-plan on a childless epic, and no surface picks the leaf face from the descriptiondone
• MOTIR-2098Carry hasDescription on the work-item LIST row, so the /items row ⋯ menu can pick a leaf's Plan / Re-plan face by rule 2done
• MOTIR-2099(motir-ai) MIRROR the design-allocation-emits-consumer-edges corollary into `SHARED_PLANNING_RULES` — the shipped planner must wire the edges a shared design impliesdone
• MOTIR-2100PLANNING RULE (motir-meta) — a design that allocates ONE surface across N consuming cards emits N−1 edges BETWEEN them; the design's own `blocks` fan-out is not those edgesdone
• MOTIR-2108The ARCHIVED list read never projects `type`, yet its row type declares it — every archived row carries `type: undefined`done
• MOTIR-2109(motir-ai) MIRROR the both-content-axes rule into `SHARED_PLANNING_RULES` — the WHY belongs in `explanationMd`, never as a "## Why this card exists" heading in the descriptiondone
• MOTIR-2110BUG (motir-core) — the re-plan job envelope omits `generateExplanations`, so the project's "AI-drafted explanations" setting silently does nothing on re-plandone
• MOTIR-2111(motir-ai) The re-plan handler must READ `context.generateExplanations` and pass it to `runGenerationPass` — the consumer halfdone
• MOTIR-2115WATCH — DeepSeek V4-Pro official release: re-verify the planner's DEFAULT model (pricing, id, the tool_calls workaround, Responses support) when it shipstodo
• MOTIR-2128BUG (motir-ai) — the `augment` and `expand_item` handlers ALSO ignore `context.generateExplanations`, so two of the three plan-edit paths still drop explanationsdone
• MOTIR-2142(motir-ai) MIRROR the claim-vs-pointer gate into `SHARED_PLANNING_RULES` — a code fact a card asserts must have been grepped on origin/maindone
• MOTIR-2488Create API token modal: the Create/Cancel footer is clipped OUTSIDE the dialog — the form bypasses `Modal.Body`, so on a tall variant there is no submit button and no scrollbardone
• MOTIR-2491Sweep the `Modal.Body`-bypass class app-wide — measure every `<Modal>` call site that owns no scroll container, fix the ones that clip, and add a guard so there is no fourth instancetodo
• MOTIR-2608The sandbox guide's dev-container step is unfollowable from a cold start — a command palette it never says how to open, a file a GUI file manager refuses to create, and a command that only exists once the folder is already opendone
• MOTIR-2611The sandbox guide never tells the reader to `docker pull` — `docker run` reuses a stale `:claude`, so anyone who followed it before 2026-08-05 is still on a CLI with no `motir login` while step 4 tells them to run itdone
• MOTIR-2612A credential-free post-publish job must assert the PUBLISHED image's CLI carries every command the shipped docs name — today `sandbox-published` logs in and reads only `--version`done
• MOTIR-2613Cut `cli-v0.2.1` — `package.json` has said 0.2.1 since MOTIR-2537 and four CLI commits sit unreleased, including a user-visible `motir link` error fix and the ACME copy rename the docs already showcancelled
• MOTIR-2614PLANNING BUG — MOTIR-2611 measured only `main`, inferred the TAG's tree from that, and shipped the inference as a fact: every row of its evidence table was about the branch the defect could not be indone
• MOTIR-2615Mirror the two new gates into `SHARED_PLANNING_RULES` — the released-ref absence check and reproduce-before-you-call-it-broken, worded GENERICALLY because the shipped planner plans other people's productsdone
• MOTIR-2616The docs renderer prints backticks literally when `code` sits inside **bold** — `renderInline` is a flat split, so the bold arm emits its own contents as raw textdone
• MOTIR-2617(motir-core) E2E flake, 3rd occurrence — `project-square-flow.spec.ts`'s `rank=popular` navigation stalls the full 180s on bulk-4, on the attempt AND the retry, because the retry re-uses the same degraded webServerdone
• MOTIR-2620MOTIR-2611 broke `acceptance-api-docs.spec.ts` and its own PR could not see it — the sandbox guide's step 2 now has TWO Copy buttons, and the acceptance lane only triggers on `acceptance*.spec.ts` pathsdone
• MOTIR-2630(motir-meta) Write the missing per-type authoring bars — `chore`, plus one per newly-admitted typedone
• MOTIR-2642(motir-meta) Decide whether the planning corpus is COMPRESSED — partitioning is now measured to cap the hardest pass at a 29% reductiondone
• MOTIR-2644(motir-meta) Narrow the motir-meta PR-id rule — carry `MOTIR-<n>` when `targetRepo` IS motir-meta, so a card whose deliverable is a prompts change closes on its own mergedone
• MOTIR-2645(motir-core) E2E flake, 3rd occurrence — `signIn()` returns while the post-auth redirect is still in flight, so the caller's next `page.goto` is aborted by a navigation to /dashboarddone
• MOTIR-2647(motir-core) `rate-limit-gate.test.ts` pins the BUDGET but not the WINDOW, so two calls straddling a minute boundary read as under-budget and the assertion gets PROJECT_NOT_FOUNDdone

Showing 50 of 127

Load more at this level