Motir

← Back to the top level

• MOTIR-3187Planning bug: the two-homes obligation is stated only in `CORPUS-MAINTENANCE.md`, which no planning pass loads — six occurrences, five sibling cards, no gatedone
• MOTIR-3190Planning bug: a design card specified a CONSTRUCTION (a true normal-offset band) without checking it was geometrically possible at the mark's own proportionsdone
• MOTIR-3210Planning bug: `run.md` never says the at-scale lane is LABEL-gated, so a run labels the PR AFTER creating it — a second trigger at the same sha whose cancelled run poisons the card's CI verdictdone
• MOTIR-3211Planning bug: "the ONLY viewport-sized declaration outside the shell" was a grep for the CSS token — Tailwind's `min-h-screen` compiles to the same `100vh` and five more surfaces carried itdone
• MOTIR-3212Planning bug: MOTIR-3193's AC 4 asks the generated OpenAPI document to reflect an MCP tool ARGUMENT shape it has never containeddone
• MOTIR-3216Planning bug: a contrast ratio was measured in ONE theme context and generalised to "light" — `data-palette` makes it twenty, and four of them faileddone
• MOTIR-3220Planning bug: a card's own detection query prescribed `gh pr view --json files`, which caps at 100 — and the cap became a finding in the card's evidence tabledone
• MOTIR-3228Planning bug: a grep-shaped acceptance criterion whose PATTERN also appears in the comments FORBIDDING it is unfalsifiable — MOTIR-3226's AC 7 returned 3 hits on `origin/main` at authoring timedone
• MOTIR-3230Planning bug: the `subsumption` advisory only sees MERGED pull requests — a defect filed 48 min into the OPEN window of the PR fixing it is invisible to every checkdone
• MOTIR-3258Planning bug: MOTIR-3224 defers the cross-machine wake to MOTIR-2783, which was already `done` when the card was written — so the gap it names has no ownerdone
• MOTIR-3265Planning bug: run.md's branch-prefix rule still cites the `startsWith(head_ref, …)` CI gate that MOTIR-3148 replaced with a diff-based predicate — and understates which prefixes skip the Vercel previewdone
• MOTIR-3266Planning bug: an acceptance criterion named TWO triggers for one event-driven seam, and one of them is a non-terminating loop — the card's own explanation names only the otherdone
• MOTIR-3267Planning bug: MOTIR-3229 names THREE homes and assigns home 2 to MOTIR-3203, which closed without it — `run.md`'s parent-run still stops only on a `design`/`manual` stopperdone
• MOTIR-3269Planning bug: two MOTIR-3249 children were pinned to ONE repo while their criteria need the otherdone
• MOTIR-3270Planning bug: MOTIR-3249 gates four children behind a POST-DEPLOY measurement, so the story cannot be run as a parentdone
• MOTIR-3273Planning bug: a STACKED design PR merged into its already-merged base branch, so its deliverable never reached main while the card read donedone
• MOTIR-3275Planning bug: MOTIR-2853 read `ready: true` with two unexecutable preconditions — an external credential and a post-deployment soak window, neither expressible as an edgedone
• MOTIR-3283A story whose deliverable was a PAGE planned no instrument that OPENS it until its last card — a client-boundary 500 lived through five green subtask PRsdone
• MOTIR-3287Planning bug: `notes.html` entries #68 and #203 still PRESCRIBE the dead branch-prefix CI-skip mechanism — the MOTIR-819 retrieval hands it to future runs as advicedone
• MOTIR-3312Planning bug: `_shared.md` says "Epic is not an offered kind" — the MCP has offered it all along, so every pass routes around a tool that worksdone
• MOTIR-3318Planning bug: guard #4 says an advisory's reference is "a `blocked_by` to WIRE" — followed literally on a CROSS-STORY reference it produces a cross-parent edge, which gate 7 forbidsdone
• MOTIR-3319Planning bug: a story planned building a column that already shipped, and a `manual` card the pipeline can do — the lesson forbidding the second was IN the store, where the runbook planner cannot read itdone
• MOTIR-3341Planning rule: NEVER reopen a `done` work item — plan forward, and log a bug or a new story insteaddone
• MOTIR-3355Planning bug: a test card's fixture table encoded axis semantics that contradict the three-axes-are-independent rule its own parent story states in prosedone
• MOTIR-3356Planning bug: a card forbade the only layer at which its own acceptance criterion was implementable — a prescribed layer is a CLAIM about that layer, and it owes the ADR checkdone
• MOTIR-3363Planning bug: a story scoped its population from where a corpus "STOPS" — but the coverage was a SET, not a prefix, so 44 entries below the boundary were invisible to every checkdone
• MOTIR-3369Planning bug: MOTIR-3324 ships a consumer whose motir-core PRODUCER half owns no card — a conditional in a card body defers a decision the run cannot act ondone
• MOTIR-3377Planning bug: the corpus's conservation check cannot express a RESTATEMENT, and its historical baseline cannot conserve post-baseline text — MOTIR-3293 leaves conserve.py permanently red on thirteen packsdone
• MOTIR-3378Planning bug: an acceptance criterion demanded evidence from a substrate on the OTHER side of a service boundary — "asserted against a real database" for an HTTP seamdone
• MOTIR-3397Planning bug: the MID-SENTENCE WIDENING sweep is owed AGAIN — three packs red for the third time, so MOTIR-2966's remedy collects the debt without stopping it accruingdone
• MOTIR-3399Planning bug: MOTIR-3371 turned "toHaveLength(1) passed, SO a second window opened" into an acceptance criterion — a second mechanism produces that presentation and reproduces 2 in 10done
• MOTIR-3401Planning bug: MOTIR-3274 closed `done` on criteria written over ONE project while its own Context refs named a SECOND consumer — the credential meant to unblock MOTIR-3264 cannot reach the gatewaydone
• MOTIR-3402Planning bug: a card with NO acceptance criteria passes every gate vacuously — and the one mechanised sizing check needs the very field an under-authored card is missingdone
• MOTIR-3403Planning bug: a bug card's MECHANISM was taken from an untested code comment, and three candidate fixes were planned off itdone
• MOTIR-3410Planning bug: MOTIR-3264 imported a suspend delay measured on OTHER endpoints and stated it as its own subject's property — in the title, while its body correctly forbade exactly thatdone
• MOTIR-3412Planning bug: run.md says a card at `todo` is structurally safe from a PR naming it — the sync WALKS the hops, and a one-criterion PR closed a four-criterion carddone
• MOTIR-3428Planning bug: MOTIR-3414/3422 assert "84 step.run call sites across 37 files, incl. services outside lib/jobs/" — measured 58 across 26, ALL inside lib/jobs/done
• MOTIR-3429Planning bug: MOTIR-3414 cannot close — its `manual` post-deploy child needs the merge the story needs the child for, and the E2E is edged to it while forbidding the worker it needsdone
• MOTIR-3476Planning bug: two of MOTIR-3451's acceptance criteria were never RUN before they were written — one quotes markup the file has never carried, the other asserts an output that was already falsedone
• MOTIR-3494Planning bug: a falsified-premise card named TWO of the ten cards its finding invalidated — the referrer sweep was done by memory, not by grepdone
• MOTIR-3496Planning bug: the design gate makes the design card a CHILD of the card it gates — a prerequisite must be a SIBLING wired `blocked_by`, never a childdone
• MOTIR-3499Planning bug: a defect was verified against `origin/main` and filed 47 minutes after the card fixing it went `implemented` — the pre-flight never searched the PLANdone
• MOTIR-3503Planning bug: MOTIR-3455's evidence grep was never RUN — it reports 3 files where its own named ref returns 19done
• MOTIR-3504Planning bug: MOTIR-3462 asks an E2E to assert same-key idempotency on a journey that mints a FRESH key each time — the criterion cannot be run at alldone
• MOTIR-3506Planning bug: a card specified a write + its guarding read inside an existing transaction without checking that the transaction's SECURITY BINDING admits eitherdone
• MOTIR-3509Planning bug: a card RELOCATED a surface without checking that its destination is reachable by everyone the source wasdone
• MOTIR-3511Planning bug: a card was sealed carrying a heading that said "split it", and criteria duplicating a still-open operator card's DNS records — where the duplicate would have BROKEN the card that owns themdone
• MOTIR-3520Planning bug: MOTIR-3440 NAMED `PageSkeleton` as unowned and created no card, so MOTIR-3443 shipped `ready` with an acceptance criterion nothing could satisfydone
• MOTIR-3521Planning bug: a design entry cited an existing component as a surface's pending stand-in without measuring it — 9 tracks against 4, 40px rows against 48done
• MOTIR-3544Planning bug: a mechanism-withdrawal amendment swept four of five dependents — the one it missed was the one whose SCOPE had not moveddone

Showing 150 of 255

Load more at this level