kami a33ad82178 Let the /routines page accept a proposal, gated at step-up (#46) ...

Accepting a routine gives the trigger loop a new standing reason to speak to
the human, so it is the same authority tier as enabling a tool and shares the
stepUpOK gate; dismiss only ever makes maven quieter, so it is ungated.
Look at handleRoutines and acceptRoutine in cmd/mavweb/main.go: accept creates
the recurring reminder, then links it via the new ipc AcceptProposedRoutine.
The page now says what maven noticed in her own words (pattern.PhraseRoutine).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CGeSZxh1DCtRxmFVSYVGvJ

2026-07-31 02:23:28 +04:00

..

auth_test.go

Let the /routines page accept a proposal, gated at step-up (#46)

2026-07-31 02:23:28 +04:00

enrollment.go

initial commit

2026-07-03 00:32:48 +02:00

gate.go

initial commit

2026-07-03 00:32:48 +02:00

policy.go

mavweb: handler tests + gate DisableTool at step-up

2026-07-03 21:22:10 +04:00

scope.go

initial commit

2026-07-03 00:32:48 +02:00

tier.go

Fold SPEC/maven/ROADMAP into DESIGN.md and drop the stale session logs

2026-07-30 23:39:56 +04:00