Motir

← Back to the top level

• MOTIR-3548Planning bug: the COLLAPSED supervisors run on Inngest between MOTIR-3417's merge and MOTIR-3489's flip, holding one invocation for the container's whole lifedone
• MOTIR-3549Planning bug: MOTIR-3547 was sealed UN-SIZED at ~5h across three repos, and asserted a code fact read from ONE of a tool's TWO return channelsdone
• MOTIR-3561Planning bug: MOTIR-3487 claims an E2E lane 'already has every piece' from a sibling spec's SUBJECT — the spec seeds the ledger and its own header says the writer path has no seamdone
• MOTIR-3562Planning bug: MOTIR-3557's AC 3 forbade a behaviour a shipped test deliberately guarantees — a criterion phrased as a NEGATIVE about rendered output carries an ungrepped code claimdone
• MOTIR-3566Planning bug: MOTIR-3560 was sealed at 5 pts / 60 min carrying its OWN six enumerated deliverables — the sizing advisory is blind to a card whose numbers are present and wrongdone
• MOTIR-3571Record the never-fires lesson — an acceptance criterion that asks to OBSERVE something in production is unsatisfiable when the trigger has never fired (5 of MOTIR-3463's 20 ids, all_time=0)done
• MOTIR-3572Planning bug: two bugs were filed mid-run WITHOUT the bug-filing protocol — one proposed a rule the corpus already carries in both homes, and the rule forbidding exactly that was routed to the pass that skipped itdone
• MOTIR-3582Planning bug: MOTIR-3573's criteria asserted a violation the API cannot express — the input type was never read before two ACs were written about itdone
• MOTIR-3605Planning bug: MOTIR-3595 plans a cross-repo READ seam no card creates — "read the plan's proposals through core" has no producerdone
• MOTIR-3607Planning bug: MOTIR-2508 asserts "ONE PR, one file" in two criteria and then requires a second file in a thirddone
• MOTIR-3618Planning bug: three 8.4 legal cards were typed `coding_agent` while their acceptance required counsel review — and the human-sized estimate was the tell nobody readdone
• MOTIR-3630Planning bug: `motir run <id>` step 0a CLAIMED an archived card — `transition_status` does not reject one, and no gate before the worktree reads `archivedAt` or `readiness.ready`done
• MOTIR-3632Planning bug: MOTIR-3626 recorded the over-gate advisory as "REAL" and declined it IN WRITING — an advisory ACKNOWLEDGED is not an advisory DISCHARGED, and the acknowledgement makes the card read as carefuldone
• MOTIR-3641Planning bug: the ADR allocated the account-SUSPEND action to a card while the suspension MECHANISM — a schema column, session revocation and a sign-in refusal — was owned by nobody and priced into nothingdone
• MOTIR-3654A plan proposal's `type` is a bare `z.string()` while every enum beside it is a `z.enum` — an out-of-enum value is stored, passes validate, and 500s at approvedone
• MOTIR-3689Planning bug: a card ABOUT a stale population count carried a stale population count — MOTIR-3682 says "exactly one thing" remains on Inngest, and three diddone
• MOTIR-3690Planning bug: a diagnosed defect was recorded ONLY inside another card's body — "this paragraph is currently the only record" — and then ran unnoticed for 23 daysdone
• MOTIR-3696Planning bug: a design that merges AFTER the card it gates re-opens that card's SIZING, and MOTIR-1136 reached dispatch at 5 pts / 65 min for a ten-card featuredone
• MOTIR-3714Planning bug: MOTIR-3693 enumerated its population by hand-reading ONE folder — the guard it was filed about counts 18 assets across 9 areas, not 6done
• MOTIR-3718Planning bug: MOTIR-3230 deferred its filing-time limb with NO card — the prerequisite has since landed, and the duplicate that limb exists to prevent was filed two hours laterdone
• MOTIR-3720Planning bug: a card's central premise was a config COMMENT quoted as fact — six counter-examples sat nine lines below it, and two "options" were both already shippeddone
• MOTIR-3723Planning bug: two stories in different epics planned the SAME deliverable (`@motir/design-system`) two days apart, with no edge — MOTIR-1524 shipped it and MOTIR-1456 stayed claimable for eight weeksdone
• MOTIR-3729Planning bug: MOTIR-3721's dependency on a sibling's OPEN pull request was written as prose, not a `blocked_by` — and two cards in the same story shipped with a null `explanationMd`done
• MOTIR-3733Planning bug: MOTIR-3721 inherited its reader inventory from the ADR that authorised the retirement, so the readers the replacement CANNOT serve were never counteddone
• MOTIR-3740Planning bug: MOTIR-3739 called a neighbouring line "protected" without reading its call chain, and named ONE instance of a copy-pasted pattern as the populationdone
• MOTIR-3741Planning bug: a card's second half was inferred from a MODULE PATH — `lib/ai/codeContext` was read as "calls motir-ai" while its whole import closure is Prismadone
• MOTIR-3746Planning bug: the IMPORT door's `?intent=import` has no reader and no owning card — its tracker twin got MOTIR-3639 and the import half was never carveddone
• MOTIR-3748Planning bug: a bug card's root cause was derived from a STALE COMMENT and from a call path a memo makes unreachable — two mechanisms, both falsified at the first grepdone
• MOTIR-3749Planning bug: MOTIR-3634's own TEST asserts a property of sibling MOTIR-3635's output, and the split left the two edge-freedone
• MOTIR-3753Planning bug: the CORRECTION to MOTIR-3721's inventory was itself scoped by a one-file grep, so nine is short by seven in the same shape as five was short by fourdone
• MOTIR-3771Planning bug: a card proposed 'restore the yield, not the stepping' — the two are not separable, and the record it cited already said sodone
• MOTIR-3775Planning bug: MOTIR-3750's measurement block secured the SET and left the CAUSAL sentence beside it unmeasured — the file it blames the classifier for was last touched two days BEFORE the classifier existed (and the count was one high)done
• MOTIR-3779Planning bug: a card that ENUMERATES the homes of a symbol quotes a grep it did not run — MOTIR-3777 named seven of tendone
• MOTIR-3792Planning bug: the corpus CONTRADICTS ITSELF on what approve does to a proposal's status — `_shared.md` and `run.md` say it derives nothing and cite the code, `plan-procedure.md` says it derives from the edges, and the shipped `materialize` agrees with `plan-procedure.md`done
• MOTIR-3793Planning bug: a card's post-merge PUBLISH obligation was recorded as a comment and offered as a question ("say so and I will propose one") instead of filed as a card — MOTIR-1456 went `done` with `@motir/brand` unpublished, and MOTIR-1152 hit it eight hours laterdone
• MOTIR-3794Planning bug: a story was authored with a DEPLOYED-tenant verification card inside it, gating three siblings that ship at merge — so the story's own pull request could never opendone
• MOTIR-3801Planning bug: the delivery-reader inventory's own re-measurement was short by two — its grep cannot match `?.workItemId`done
• MOTIR-3804(motir-core) A `modify` proposal's body cannot carry an intra-plan CHIP — materialize rewrites `motir-ref:planItem:` on `add`s only, so an amendment naming a card the same plan proposes ships an inert linkdone
• MOTIR-3805Planning bug: a card whose precondition is a DEPLOY was gated by a `blocked_by` edge, which discharges at MERGE — the RULE half (the lesson shipped)done
• MOTIR-3807Planning bug: MOTIR-3735 deliverable 2 asserted `schema.prisma`'s `sessionBranch` "carries no comment" — it carries a 12-line one at the cited refdone
• MOTIR-3820Planning bug: a card's rung-2 evidence asserted an absent workflow edge that ships — the decision survived, the argument's KIND did notdone
• MOTIR-3821Planning bug: a card generalised the side-effects-outside-the-transaction rule onto the AUDIT ROW, which is the one write that must be inside itdone
• MOTIR-3822Planning bug: an acceptance criterion's own COMMAND enumerated a strict superset of its claim, so the criterion was unpassable and its literal reading was destructivedone
• MOTIR-3849Planning bug: a `blocked_by` wired to an ARCHIVED predecessor gates nothing — the card sealed `ready: true` against a retirement that has not shipped, and the advisory that named it was never readtodo
• MOTIR-3854Planning bug: an acceptance criterion quoted durations from a run where the jobs were SKIPPED — a skipped job reports zero, not an absence, and the ceiling it implied would have failed a green runtodo
• MOTIR-3855Planning bug: the 8.3 re-plan moved the public marketing surface to motir.co and never swept MOTIR-1043, whose whole premise was that surface — it kept `(motir-core)` in its title, and had no design blocker, for two monthstodo
• MOTIR-3857Planning bug: a `coding_agent` card carried a criterion only a BROWSER SESSION can discharge — minting a `CLI_TOKEN_GRANT` token is cookie-session-only by design, and no gate noticedtodo
• MOTIR-3858Planning bug: a bug card filed mid-run asserted an ORM reader nobody grepped, and promoted that mechanism into two acceptance criteria that cannot be satisfiedtodo
• MOTIR-3871Planning bug: a copy card scripted a PUBLIC marketing claim about an unshipped capability — no gate checks a customer-facing sentence against the product, because the precondition rule only asks whether the card can be BUILTtodo
• MOTIR-3873Planning bug: MOTIR-3868's AC 1 required a diff against `work_item.targetRepoRole`, a column retired 11 days earlier — the enumeration was verified, the column behind it was nottodo

Showing 200 of 258

Load more at this level