Motir

← Back to the top level

• MOTIR-1652Planning gap: status-derivation story was scoped upward-only (missed the symmetric downward cascade)done
• MOTIR-1801Planning bug: `AgentRun` named TWO tables across the open-core boundary — 9.1.7/9.1.8 read motir-ai's metering store as the execution record, so the execution record was never owneddone
• MOTIR-2201(motir-core) The `@planner-bug-home` marker resolves through a mutable child row, so a single re-parent silently stops it resolvingdone
• MOTIR-2203(motir-ai) Re-point `MOTIR_META_BUG_PARENT_KEY` to the `@planner-bug-home` marker — MOTIR-1466's unfinished consumer halfdone
• MOTIR-2517PLANNING BUG — a card read a migration's stated INTENT as the database's enforced STATE, so "nothing needs to be created, only adopted" survived every gatedone
• MOTIR-2538PLANNING BUG — a container whose child's job is to FILE CARDS can never finish its own PR, and its title promised what the merge cannot deliverdone
• MOTIR-2587PLANNING BUG — a re-measurement named the card it invalidated, by key, and amended the doc instead of the carddone
• MOTIR-2590PLANNING BUG — one prompt asked a QUESTION and gave an INSTRUCTION about the same page; only the question got a decision gate, so the instruction reached three commits before anyone asked whether the product wanted itdone
• MOTIR-2683Planning bug: a comment listing what an API does NOT publish was read as the publication — a whole decision question was built on itdone
• MOTIR-2686Planning bug: an acceptance criterion was written in a metric the card's own scope forbids it from moving — and the metric was mis-attributed at sourcedone
• MOTIR-2687Planning bug: MOTIR-2659's AC 5 set a line target from a corpus-wide warrant share, and the region's own measurement puts the floor at 204done
• MOTIR-2702Planning bug: the third denominator swap, and `COMPRESSION.measure.py`'s `TAG_LINES = 1` contradicts § Decision 1's two-line tag — so § Decision 4's 1 600-line target is unreachable toodone
• MOTIR-2707Planning bug: a card's acceptance number was inherited from an automated projection whose detector counts the rule's own heading as removable evidencedone
• MOTIR-2722Planning bug: the story pinned a write path to motir-core without verifying motir-core can produce a vector — it holds no embedding credential at alldone
• MOTIR-2723Planning bug: the FOURTH line-target miss, and the re-shape — `--check` compares against a hand-typed constant instead of deriving the floor from the corpusdone
• MOTIR-2733Planning bug: the repository pin was planned as a SINGULAR — the cardinality rule's own standing instance, missed on the one card that was entirely about that field; and the story shipped no E2Edone
• MOTIR-2756Planning bug: a correct mechanism produced a wrong outcome and I concluded the INPUT was illegitimate — three cards filed to prohibit a shape the product needed to supportdone
• MOTIR-2759Planning bug: an AC that reads as a totality claim on two axes — every item, every project, exactly once — left the LIFECYCLE axis unbounded, and the surface's own copy was already asserting itdone
• MOTIR-2762Planning bug: a new surface's SCOPE was settled from competitor precedent without reading the shell tier it was being placed in — and the card had to invent a duplicate nav row to make the mismatch fitdone
• MOTIR-2773`COMPRESSION.conserve.py` cannot express a rule ADDITION — its per-pack baseline is a fixed historical commit, so any pack that gains a rule after its first compression goes red foreverdone
• MOTIR-2779Planning bug: a card headed "One PR" carried an acceptance criterion naming a file in the OTHER repodone
• MOTIR-2791Planning bug: the app-layer cards were declared independent of the fixture batches, but their verification RUNS ON them — the dependency arrow points the wrong waydone
• MOTIR-2798PLANNING BUG — a story titled "the tenant reads" decomposed into fixtures only, and its adjudication card was given an AC that required it to fix the class it was scoped to merely CATALOGUEdone
• MOTIR-2831Planning bug: MOTIR-2797 declared a sibling's 423-file substrate "landed" when it sits on an unmerged branch with no PR — and MOTIR-2734's placement makes the two stories deadlockdone
• MOTIR-2844Planning bug: eleven cards were cut on a measurement the SAME pass created a card to replace — and one target survived only in a titledone
• MOTIR-2847Planning bug: MOTIR-2796 was partitioned from a scanner that reads only lib/repositories, so a whole second population had no card — and the guard that would have found it was scheduled LASTdone
• MOTIR-2848Planning bug: a cross-parent dependency was recorded in PROSE because the planner believed a different parent means no `blocked_by` edge is available (MOTIR-2768 → MOTIR-2764)done
• MOTIR-2850Planning bug: a card asserted two Playwright lanes were interchangeable by RENAME, having compared their globs and never their webServer envdone
• MOTIR-2858Planning bug: read a card's own `pg_policies` fact as reassurance when it named the table breaking four of its eight readsdone
• MOTIR-2859Planning bug: an acceptance criterion quoted an inventory's COUNT, on the card guaranteed to run after 400+ files of its own predecessors' work landeddone
• MOTIR-2863Planning bug: a document said "a separate surface with no card in this story" and no card was filed anywhere — while a downstream criterion read "the full suite passes"done
• MOTIR-2873Planning bug: a card's method clause was written in the semantics of an UNMERGED branch, and its criterion named a card archived 13 minutes after authoringdone
• MOTIR-2875Planning bug: a partition hedged the axis it had an instrument for and ASSERTED the one it did not — "issued by application code, not a test fixture" was wrong for 50 of 174 rowsdone
• MOTIR-2877Planning bug: MOTIR-2872's real blocker was wired `relates_to`, and its advisory landed in the tier guard #4 tells you to skipdone
• MOTIR-2883Planning bug: a mirrored constant MOVED and nothing swept the referrers — and the stale pointer RESOLVES, so it manufactures a false absencedone
• MOTIR-2885DECIDED — status derivation becomes a recompute (no exemption for the planner-bug home): a parent returns to To Do when a new open child is addeddone
• MOTIR-2897Planning bug: a dedup card offered two owners for one write and neither option carried the ADR that one of them was gated by — and its criteria named one of the two collisionsdone
• MOTIR-2898`core.md`'s 620-line cap has no room for the cross-reference index the split made necessary — and the pays-for-itself mechanism is unavailable to any card forbidden from editing `fixtures/`done
• MOTIR-2899Planning bug: the `validate_work_item` post-condition is bound to a PLAN PASS, so no card created mid-run is ever checked by the mechanism built to catch exactly this — MOTIR-2011's family, ×7done
• MOTIR-2900Planning bug: a test card's worked EXAMPLE contradicted the rung table its own story had just writtendone
• MOTIR-2903Planning bug: MOTIR-2757 sat `todo`/`high`/ready for two days after MOTIR-2796's sweep shipped its entire deliverable — every readiness signal read greendone
• MOTIR-2905Planning bug: a card that NAMED its own blocker in prose and NAMED its own open decisions still shipped with no `blocked_by` edge and an acceptance criterion nobody could evaluate — the diagnosis was right and none of it was wireddone
• MOTIR-2907Planning bug: a card's FIX DIRECTION carries the authority of its root-cause evidence without the method — MOTIR-2763 mis-counted its referrer set (2 of 4) and named a test lane that cannot mount the element under testdone
• MOTIR-2916Planning bug: an incident card was authored from a single reconciliation read, and its own two printed timestamps disproved it — the remediation steps would have deleted a live customer's billing entitydone
• MOTIR-2917Planning bug: a TERMINAL card's blocked_by set is written once and never re-derived, so every sibling filed after it leaves the card reading `ready: true` while definitionally un-runnabledone
• MOTIR-2922Capture a merged PR's changed file paths and its merge instant — the substrate a subsumption check needs, and the one `github_pull_request` does not carrydone
• MOTIR-2923Planning bug: MOTIR-2903 specified its mechanism against a "PR set" that carries no diff — the precondition was asserted as already-shipped ("this is the same read"), in a clause whose job was to price the carddone
• MOTIR-2925Planning bug: MOTIR-2919 called MOTIR-2911's conversions "landed" two minutes before their PR existed, and wired the edge `relates_to` — its "0 failures" criterion is unreachable from `origin/main`done
• MOTIR-2926Planning bug: a dedup wrote its blocker's new position in PROSE and left the card parented in a LATER epic — a permanent deadlock that `validate_work_item` reported and nothing readdone
• MOTIR-2928Planning bug: a bug card's COVERAGE NEGATIVE ("no board spec rides that lane") went unchecked and is false — and its 500 does not reproduce at the reporter's own base commitdone

Showing 50 of 255

Load more at this level