Motir

← Back to the top level

• MOTIR-220911.5.1 Decision — the CLI's v1 client contract: the type generator, where runtime validation happens, how the generated artifact stays fresh, the skew comparison, and the adapter boundarydone
• MOTIR-221011.5.2 The generated v1 client types + their freshness guards — one command, a committed artifact, and a CI diff that cannot be argued withdone
• MOTIR-221111.5.3 The HTTP transport core — `fetch` + bearer + the boundary parse, the status→typed-error map, and the version-skew gatedone
• MOTIR-221211.5.4 The adapter module + the IDENTITY reads (`whoami`, `listProjects`) — and the test harness learns `/api/v1`done
• MOTIR-221311.5.5 The DISPATCH + SESSION methods over `/api/v1` — transitions, the prompt read, integration and session close-outdone
• MOTIR-221411.5.6 Drop `@modelcontextprotocol/sdk` — delete the MCP transport, re-point the `auth login` probe at `GET /api/v1/me`, and prove nothing imports itdone
• MOTIR-221511.5.7 Story vitest gate — the `packages/cli` coverage floor, the transport↔adapter↔renderer seams, and the architecture guards the migration owesdone
• MOTIR-221611.5.8 Story end-to-end — teach the socket harness to serve `/api/v1`'s DYNAMIC routes, then drive the BUILT binary through the whole loop against themdone
• MOTIR-221711.5.9 Docs — re-describe `@motir/cli` as a client of the public REST API, and tell a user what to do when their server is olderdone
• MOTIR-221811.5.10 Release PREP — bump `@motir/cli` to 0.2.0 and write the changelog entry for the transport migrationdone
• MOTIR-221911.5.11 CUT `cli-v0.2.0` — push the tag on the merge commit, watch both lanes, and install the published package as an anonymous userdone
• MOTIR-222011.5.12 RECORD the `cli-v0.2.0` release — transcribe the published version and the sandbox image digests into the repositorydone
• MOTIR-227911.5.13 Decision, then implement — does a `/api/v1` collection row embed a minimal ACTOR object? (the ready row's assignee, `targetRepo`, and `excludeIds` without an internal id)done
• MOTIR-2280PLANNING BUG — MOTIR-2279 was filed twice wrong: a deliberate omission called an oversight, and a cross-story dependency hung off the epic instead of a story-level edgedone
• MOTIR-228311.5.14 Apply Amendment 9 Q1 to the COMMENT author — the one activity shape that kept the overturned rationaledone
• MOTIR-231711.5.15 The ready set's REPEATABLE `kind` / `priority` are declared as arrays — the document catches up to the routedone
• MOTIR-231811.5.16 A v1 client cannot COUNT a filtered set — the work-item collection reports no totaldone
• MOTIR-231911.5.17 `searchWorkItems` onto the v1 collection, and the four `total` readers onto `countWorkItems`done
• MOTIR-232011.5.18 The activity `all` page reports ONE total where the stream has two — `totalComments` / `totalChanges`done
• MOTIR-233811.5.19 The exclusion list is keyed by KEY, not the internal row iddone
• MOTIR-2339PLANNING BUG — 11.5 was decomposed by METHOD GROUP behind a "no command file" boundary, which cannot hold for a client portdone
• MOTIR-234111.5.20 The PLANNING-CONVERSATION methods over `/api/v1` — the session thread, the submit, and the two plan readsdone
• MOTIR-234411.5.21 The COLLECTION reads over `/api/v1` — `listReady` and `listSprints`done
• MOTIR-234511.5.22 The DETAIL reads over `/api/v1` — `getWorkItem`, the activity stream, and what `--json` emitsdone
• MOTIR-2379BUG — the repo-level CLI story suites never mounted `/api/v1`, so 43 of their tests went red the moment the reads moveddone
• MOTIR-239811.5.23 `nextReady` off MCP — pick from the RANKED ready set, and route from the dispatch promptdone
• MOTIR-2399PLANNING BUG — a ROUND-TRIP eviction: 11.5.5 and 11.5.19 handed `next_ready` to each other 22 minutes apart, so no card's criteria owned the port and it reached the deletion carddone
• MOTIR-240011.5.24 Decision, then implement — the v1 ready row says READY but not "ready relative to WHAT": the inherited session branchdone
• MOTIR-2405BUG — the `…/work-items/count` endpoint left two structural guards red: unprobed in the MCP drift guard, uncovered in the conformance walkdone
• MOTIR-240611.5.25 The dispatch prompt tells an agent to SIGNAL — set the card in review when done; record the finding and submit a plan when the card is wrongdone
• MOTIR-240711.5.26 `motir auto` reads the agent's SIGNAL — in review to continue, a finding to submit the re-plan and stop; the PR is always lastdone
• MOTIR-241111.5.27 The run's PR body is written by the AGENTS — assemble it from the commits, not from card titlesdone
• MOTIR-2419BUG — `implementationHarness` records the LAUNCHER, not the agent: every BYOK card claims it was built by `motir-cli`, and the model is never recorded at alldone
• MOTIR-2421BUG — `motir batch` records NO implementation provenance: there is no way to stamp source/harness/model without a session branchdone
• MOTIR-2422The run's PR TITLE names what it delivers, not the run id — the shared parent when there is onedone
• MOTIR-2423A close-out agent SYNTHESISES the run — one paragraph above the commits saying what they deliver togetherdone
• MOTIR-2425A `Planning` status in the IN PROGRESS category — a card being re-planned is not blocked, and must leave the pickable setdone
• MOTIR-2427A run CLAIMS its card — assign to the token owner, and pick up only the TO DO category — because Motir is used by teamsdone
• MOTIR-2436BUG — the sandbox smoke's stub server still speaks MCP only, so every image smoke test 405s the moment the CLI moved to `/api/v1`done
• MOTIR-2445`DispatchPromptDto` carries `parentKey` — promote the parent the prompt already renders as prose into a structural fielddone
• MOTIR-2446PLANNING BUG — a request-count criterion named no operation, and the bug filed about it asserted an absence it never enumerated: the bulk read existed, on a component its own evidence list nameddone
• MOTIR-2447BUG — `motir done --session` CLOBBERS the provenance the run recorded: the close-out stamps `motir-cli/<version>` over the agent's name and nulls its modeldone
• MOTIR-2448Mirror the request-COUNT precondition limb into `SHARED_PLANNING_RULES` — the shipped planner must refuse an uncited request budget toodone

Showing 43 of 43