drive-planlisted

# drive-plan — execute to acceptance, not endless polish Read `delivery-methodology`, the repo's `AGENTS.md`/`CLAUDE.md`, and linked delivery/testing docs before implementation. Preserve a supplied Project Root. Use the supplied Plan comm/file; create a separate Plan via `worklog` only when the initiative's complexity benefits from one. ## Source of truth Keep scope, acceptance, delivery slices, topology, decisions, material status, receipts, and remaining risks current in the Plan/worklog body. Put review batch summaries, steering exchanges, and escalations in comments. Local-file mode keeps both current state and a concise evidence log in the file. Keep the working Comment.io route/identity. Invoke `comment-identity` only immediately before an uncredentialed direct-REST write; never switch to an ambient registered or Botlets identity. ## Operating rules - Make reasonable implementation decisions and record only material ones. - Work one bounded delta at a time with an explicit base and intended head. - Optimize for the simplest user-useful implementation; do not add speculative enterprise hardening, abstraction, or hypothetical edge-case machinery. - Run the narrowest useful checks while editing. - A phase is not automatically a review, staging, steering, or artifact gate. - Review at a delivery-slice boundary, when a sensitive invariant changes, or when uncertainty makes review useful. - Update the worklog at material milestones, not every command or minor edit.