[alex-clickhouse]

A proposed plan was easy to miss: plan_propose sent no notification, agents sent a
free-text notify with no link, and task notes named plans as plain text.

What changes:

• New statuses. Migration v059 adds backlog ("Backlog") and plan_review ("Plan in
  review", protected). backlog goes before pending, plan_review after it; other
  statuses keep their order. No built-in job selects backlog.
• Plan review status. plan_propose and plan_update move a pending, backlog or
  in_progress task to plan_review. A task in a custom status keeps it. Approve moves
  the task to in_progress, a revision request keeps plan_review, decline closes it.
• One notification per plan. The plan tools send "Plan ready for review: " with
  plan_id and task_id in the metadata. A new version replaces the older card, approve
  and decline dismiss it, and it makes no sound during quiet hours. The notifications page and the toast show
  "Open plan" and "Open task". Telegram shows an "Open plan" button that opens the plan
  card of /plans. Prompts, templates and guides no longer ask the agent to notify
  after plan_propose, and the tool result tells it not to.
• Links in notes and bodies. Task notes from the plan tools link to /plans/<id> and
  /chat/<session>. Notification bodies render as markdown. App links open in place.
• New Task dialog. A status picker, default backlog, with a hint that the agent can
  pick up pending tasks. The agent's task_create default stays pending.
• Docs. docs/tasks.md, docs/plans.md and the worker guide describe the statuses
  and the flow.

Verification: full backend suite (6687 collected, all pass; the plan and notification
tests again after the review fixes), npm run build, npm test (1002 pass), migration
number check. Screenshots of the toast, the notifications page,
task notes and the dialog in light and dark.

Known gaps: an install from before keeps its old task-planner prompt in system.yaml
until the Automation step writes the file again, so its planner can still plan a
backlog task and still asks the agent to notify (the tool result tells it not to).
Slack has no link to the plan (no web UI address is configured).

🤖 Generated with Claude Code

[nerveai]

Nerve PR review · ✅ Ready to merge

This closes a real gap in the plan loop. Proposing a plan now moves the task to a protected plan_review status and sends one notification with links: "Open plan"/"Open task" on the web, and a Telegram button into the existing /plans card. It goes out silent in quiet hours, and approve or decline dismisses it. The logic sits in the shared plan handlers and plan_service, so all three tool paths and both backends get it, and every ctx factory passes notification_service. Because a planned task leaves pending, the task-planner gate also stops firing for tasks that already have a plan.

Completeness: 15 flow tests cover the revision-checked move, keeping a custom status, dismissal on a decision, a silenced row and the Telegram button. Migration v059 is unique among open PRs (#545 and the stacked #547 use v060). Docs, both template sets and the goldens are updated, and the system.yaml upgrade gap is disclosed.

Worth considering:

• nerve/agent/plan_service.py:418: the dismissal runs unguarded between the committed implementing claim and the dispatch at :439. If that write raises, the plan stays implementing with nothing running and cannot be approved again. Wrap it as _notify_plan_ready does (handlers/plans.py:76-87), or move it after the dispatch.

_{Checked: full backend suite in an offline sandbox at 314751e, in 3 chunks without test_slack_integration.py: 6638 passed, 38 skipped. Read plan_service, the plan handlers, the notification service and store, v059, the Telegram plan callbacks and the web diff. Frontend not run locally (CI frontend build green). Merges cleanly with current main and with #490 · automated review by nerveai — mention @nerveai to ask a follow-up.}