Motir

← Back to the top level

• MOTIR-3890Planning bug: the `AgentRun` collision was RECORDED and not removed — the name shipped into the plan anyway, and a year's drift made it three-waytodo
• MOTIR-3903Planning bug: MOTIR-3892 "measured" a closed PR from its CARD — #332 never split the constant, changed no test, and turned no guard redtodo
• MOTIR-3904Planning bug: a story was authored with three children whose acceptance criteria can only be met after the story's own merge and deploy — the container had no exit, and every gating signal read greentodo
• MOTIR-3906Planning bug: a story ACCEPTANCE CRITERION had no child that owns it — MOTIR-3870 pre-dates MOTIR-3891 and was scoped against a different parenttodo
• MOTIR-3914Planning bug: a card planned a live-run indicator on the READY list, whose membership predicate excludes every item that has a run — and removing it exposed that a run had no general door at alltodo
• MOTIR-3926Planning bug: a region measured by SEARCHING for its boundary — `SHARED PLANNING RULES` occurs inside the framing it was cuttingtodo
• MOTIR-3930Planning bug: a reversed direction was recorded as a COMMENT on the decision card it governed, leaving four of its seven criteria demanding the rejected shapetodo
• MOTIR-3935Planning bug: MOTIR-3933 was sized for the defect its author had REPRODUCED and carried a second one it had only described — 3 points for a one-attribute fix plus a 69-rule isolation problemtodo
• MOTIR-3952Planning bug: a re-plan reason that admitted two OPPOSITE readings was acted on without confirmation — an approved plan archived the wrong surface and wrote a false lesson into the corpustodo
• MOTIR-3964Planning bug: a card asserted the release re-runs the PR's matrix without reading the lanes' own `if:` — the most expensive one had been PR-exempt for nine daystodo
• MOTIR-3987Planning bug: a card can PUBLISH its reproduction command and its ref and still state a number that command does not produce — nobody runs the command they paste, and pasting one makes the figure look MORE verifiedtodo
• MOTIR-3988Planning bug: a bug card asserted a check "does not have one" three days after the check merged — the negative was never grepped, and the card cites the shipping story's own siblingtodo
• MOTIR-3992Planning bug: MOTIR-3965 put a human MERGE between two of its own acceptance criteria — a release authored as one card, sized for the publish alonedone
• MOTIR-3993Planning bug: MOTIR-3947 was carved out of MOTIR-3933 and inherited two unverified claims — a consumer that does not exist in that form, and a figure one tile optimistictodo
• MOTIR-3994Planning bug: a bug card counted "the other three inks clear it" over the set its OWN diagnosis had just shown to be unmeasured — the enumeration inherited the guard's blind spot it was filed abouttodo
• MOTIR-4027Planning bug: a bug card filed FROM a sibling's unmerged branch inherits that branch as its substrate and gets no `blocked_by` — the discovery link is written as `relates_to`todo
• MOTIR-4029Planning bug: MOTIR-4017 asserted two facts about the plan detail that the render falsified — a scroll that does not happen, and an arrival floor this surface cannot reachtodo
• MOTIR-4031Planning bug: a ratchet number was attached to a counter that measures a SUBSET of the population the card's own reason quantifies overtodo
• MOTIR-4040Planning bug: a card asserted the default E2E lane is cloud-on — it is off-cloud, and the whole two-arm plan was built on ittodo
• MOTIR-4044Planning bug: MOTIR-3932's /explore and /docs scope items have no cards after the host-branch cards were archivedtodo
• MOTIR-4048Planning bug: MOTIR-3999 re-combined the publish + the re-pin on one card and omitted the 0.1.3 bump — the exact release-shape MOTIR-3965 was re-scoped out of, one release latertodo
• MOTIR-4049Planning bug: a bug card's error count was measured against a stale generated Prisma client — 175 phantom errors, 1 realtodo
• MOTIR-4070Planning bug: a later merge deleted every test subject while the lane-fix work item stayed readytodo
• ▸MOTIR-4086Planning bug: the no-lift LIMB teaches an edge that makes a plan INVALID — a `blocked_by` is always same-level, and the limb lives in THREE homes including a seeded global lessontodo
• MOTIR-4090Planning bug: `blocks` does not cross the AI boundary either — MOTIR-4055 enumerates THREE missing link kinds and there are FOURtodo
• MOTIR-4091Planning bug: a card's scope-boundary OUT list named the sibling that BUILDS the surface its criteria assert against — and the `blocked_by` edge pointed the other waytodo
• MOTIR-4099Planning bug: an ABSENCE-shaped acceptance criterion left the repo column BLANK — gate 1's sweep cannot run on "there is no read path for this", and the straddle detector has no path to matchtodo
• MOTIR-4100Planning bug: MOTIR-3909 was planned with a post-DEPLOY child inside it — the epic that had already recorded this rule reintroduced it two stories latertodo
• MOTIR-4125Planning bug: an interim UI defect card was ready with four visible dispositions and no design prerequisitetodo
• MOTIR-4127Planning bug: MOTIR-4106 pinned motir-core owed a row in docs/contract.md, which is a motir-ai file — a repo straddle the BARE path hid from the detectortodo
• MOTIR-4128Planning bug: a card specified ONE rule delivered to two packs with identical text — which `INVARIANT B — disjoint cover` forbids, and the 88-char segment id collides ontodo
• MOTIR-4131Planning bug: a card declared the WHAT out of scope on the ladder's HOW argument, and addressed its start-gate to the phase being gatedtodo
• MOTIR-4132Planning bug: MOTIR-4093 was sealed on two unverified preconditions — a credential that is not a configured secret, and a read path (`GET …/acceptance-evidence`) that has never existedtodo
• MOTIR-4135Planning bug: gate 14(c)'s ORDERING signal is an ENUMERATION of four phrases, and "measured after the change" is not one of them — MOTIR-4095 sealed a post-merge criterion with `advisories: []`todo
• MOTIR-4150Planning bug: a card read an element's specified measure off an UNAPPLIED rule in the mock's stylesheet, and called it "the value the asset draws"todo
• MOTIR-4151Planning bug: MOTIR-3942 planned the conversation's whole CONTRACT and no PRODUCER — the pack, the value and the rules all ship, and nothing runs a conversationtodo
• MOTIR-4152Planning bug: the corpus routes 13 live citations to `plan-rules/op-replan.md`, which MOTIR-3869 DELETED — including one that says "stated in full there; do not restate it here"todo
• MOTIR-4155PLANNING BUG — the taxonomy defines `decision` TWICE and the two disagree: §1 says it IS the ADR (an artifact), the executor column and the `legal` boundary say it is the judgement WITH NO artifact. The planner is handed only the first, plus `executor: human`.todo
• MOTIR-4163Planning bug: MOTIR-4130 counted 3 of the 6 rows its claim quantifies over, and denied on the record the one edge it owed — to the OPEN PR that changes the row the card is named aftertodo
• MOTIR-4164Planning bug: an `## Advisory dispositions` section discharged gate 4 by naming the BRANCH the substrate sits on — "committed on parent/… " read as "shipped", and the card sealed ready against a 404todo
• MOTIR-4166Planning bug: the public write surface's session-gate count was measured over /p/* and generalised — "one of ten" is five of thirteen, and the request intake was recorded as anonymous when it has never beentodo
• MOTIR-4168Planning bug: the WHAT's PRODUCER and CONSUMER disagree on its SHAPE — MOTIR-4083 pins it to prose `text`, MOTIR-4082 consumes a validated struct, and nothing converts one to the othertodo
• MOTIR-4170Planning bug: a card told a second repository to MIRROR a mechanism the first repository retired nineteen hours later — "mirror X" is a claim about another repo's current shape, and nothing re-checks ittodo
• MOTIR-4173Planning bug: MOTIR-3975 scoped out ACTING on the completeness report and deferred it to "a later sibling" with no card — two predicates are now computed and neither is acted ontodo
• MOTIR-4189Planning bug: the dispatched agent's re-plan door was planned as a CLI shell-out, while every other instruction in the SAME protocol is an MCP tool calltodo
• MOTIR-4192Planning bug: a card enumerated a tool schema's MISSING fields without the command that produced the list, and named one the schema already hadtodo
• MOTIR-4200Planning bug: MOTIR-4079 asked motir-ai's gate to assert core's READINESS verdict "through the shipped read" — motir-ai's lanes fake core by construction, so the verdict can only be asserted in motir-coretodo
• MOTIR-4203Planning bug: a card put a per-phase asymmetry in the SHARED tier — the clause was true on one phase and forbade the other phase's deliverabletodo
• MOTIR-4235Planning bug: MOTIR-4206's Q7 cited Atlassian's rename cap as 3; the documented figure on the cited page is 15todo
• MOTIR-4236Planning bug: a card filed MID-RUN carried a criterion the FILING run then satisfied itself, and pinned both repositories — the next run claimed half-done work behind a repo set that could never closetodo

Showing 250 of 259

Load more at this level