Motir

← Back to the top level

• MOTIR-2292The permission guards are RED on `main` — an inline object type in a parameter hides the gate, and one route is missing from the inventorydone
• MOTIR-2293`assertPermission` — one gate per catalog key, its typed refusal, and the twelve administrative keys entering the built-in role setsdone
• MOTIR-2294Retire `repository:connect` — the provider connection binds an installation to a WORKSPACE, so no project permission can govern itdone
• MOTIR-2295`member:manage` + `project:manage_access` — and the second admin check `projectMembersService` re-implements privatelydone
• MOTIR-2296`board:configure` — the boards, their columns, swimlanes and WIP limits (and NOT the card drag, which stays `work_item:edit`)done
• MOTIR-2297`workflow:manage` + `automation:manage` — the statuses a column projects, the automation rules, and the status-derivation switchesdone
• MOTIR-2298`field:manage` + `component:manage` + `label:manage` + `estimation:manage` — the four project vocabularies, with their READS left where they aredone
• MOTIR-2299`repository:manage` + `repository:manage_access` — the project's repository SET, and who may clone it (self-connect stays open)done
• MOTIR-2300`ai:configure` — the project's AI-planning cadence and planner model (the settings write only, not the planner itself)done
• MOTIR-2302Story test gate (Vitest) — the coverage floor, the route→service→gate seams, and the guards that stop a second policy implementationdone
• MOTIR-2303Story E2E (Playwright) — every settings page as an admin, then as a member: nothing an admin could do broke, nothing a member could do was takendone
• MOTIR-2304The guard's gate pattern is a NAME WHITELIST — three privately-named gates are invisible, and three domain cards are sized against the opposite of the truthdone
• MOTIR-2305PLANNING BUG — three domain cards were sized on "ungated", and the gates were there and TIGHTER; the guard's name whitelist produced the inversiondone

Showing 13 of 13