Motir

• 2026年8月8日Four coverage thresholds are INERT — a `app/(authed)/…` literal path matches no file, so the route-group components have never been gated
• 2026年8月8日PLANNING BUG — a design landed after the cards that build to it, named them, replaced their structure and their premise, and amended none of themPermissions — a permission catalog, custom project roles, and permission-gated UI
• 2026年8月8日The Linear import connection dies after 24 hours — Linear moved every OAuth app to refresh tokens on 2026-04-01 and our connector has no refresh path
• 2026年8月8日The root layout puts the Prisma client in EVERY function bundle — a 404 and the token specimen ship a database client
• 2026年8月8日BUG — `motir done --session` CLOBBERS the provenance the run recorded: the close-out stamps `motir-cli/<version>` over the agent's name and nulls its model
• 2026年8月8日PLANNING 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 namedPublic REST API — the versioned `/api/v1` integration surface every client shares
• 2026年8月8日`DispatchPromptDto` carries `parentKey` — promote the parent the prompt already renders as prose into a structural fieldPublic REST API — the versioned `/api/v1` integration surface every client shares
• 2026年8月8日BUG — the sandbox smoke's stub server still speaks MCP only, so every image smoke test 405s the moment the CLI moved to `/api/v1`
• 2026年8月8日A run CLAIMS its card — assign to the token owner, and pick up only the TO DO category — because Motir is used by teamsPublic REST API — the versioned `/api/v1` integration surface every client shares
• 2026年8月8日A `Planning` status in the IN PROGRESS category — a card being re-planned is not blocked, and must leave the pickable setPublic REST API — the versioned `/api/v1` integration surface every client shares
• 2026年8月8日A close-out agent SYNTHESISES the run — one paragraph above the commits saying what they deliver togetherPublic REST API — the versioned `/api/v1` integration surface every client shares
• 2026年8月8日The run's PR TITLE names what it delivers, not the run id — the shared parent when there is onePublic REST API — the versioned `/api/v1` integration surface every client shares
• 2026年8月8日BUG — `motir batch` records NO implementation provenance: there is no way to stamp source/harness/model without a session branch
• 2026年8月8日BUG — `implementationHarness` records the LAUNCHER, not the agent: every BYOK card claims it was built by `motir-cli`, and the model is never recorded at all
• 2026年8月8日11.5.27 The run's PR body is written by the AGENTS — assemble it from the commits, not from card titlesPublic REST API — the versioned `/api/v1` integration surface every client shares
• 2026年8月8日11.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 lastPublic REST API — the versioned `/api/v1` integration surface every client shares
• 2026年8月8日11.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 wrongPublic REST API — the versioned `/api/v1` integration surface every client shares
• 2026年8月8日BUG — the `…/work-items/count` endpoint left two structural guards red: unprobed in the MCP drift guard, uncovered in the conformance walk
• 2026年8月8日11.5.24 Decision, then implement — the v1 ready row says READY but not "ready relative to WHAT": the inherited session branchPublic REST API — the versioned `/api/v1` integration surface every client shares
• 2026年8月8日PLANNING 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 cardPublic REST API — the versioned `/api/v1` integration surface every client shares

以前の記録

Atom で購読