Motir

The acceptance walk, and the one place the setting is proved to do something rather than merely persist.

1. Sign in as an admin, open project settings, reach AI planning.
2. The group is there, on by default, with its explanation visible.
3. Switch it off; reload and confirm it stayed off.
4. Run a planning pass that would capture a lesson, and confirm none was recorded for the project.
5. Switch it back on; the same pass records one.

Step 4 is the story. Steps 1–3 prove a boolean round-trips through a form, which is true of any setting and worth almost nothing on its own. The claim this feature makes is that the switch stops something happening in another service, and only a walk that provokes the capture and then looks at the store can show it.

Also assert what OFF leaves alone, because a user who switches it off should not lose things they did not ask to lose: with capture off, an existing lesson is still listed and still applies.

A non-admin cannot change the setting.

Acceptance criteria

• The walk passes, navigating from settings rather than a deep link.
• The group renders ON by default for a project that has never touched it.
• Step 4 asserts against the lesson store — no new row for that project — not against a UI state.
• Step 5 shows the same pass recording one when the setting is back on.
• An existing lesson is unaffected by the setting being off, asserted.
• A non-admin cannot change the setting.
• Seeded through the service; selectors follow the repo's convention; runs in the E2E lane.

Context refs

• motir-core tests/e2e/ — the lane, fixtures, sign-in helpers, selector conventions.
• MOTIR-3352 — the group and copy under test.
• MOTIR-3351 — the gate whose effect step 4 observes.
• MOTIR-3340 — the sibling walk; share fixtures rather than building a second harness.