docs(README): enter maintenance mode

Amolith created 2 days ago

Crush got native todo support, so this project is now maintenance-only.
Removed event rendering section since it won't be implemented. Added
Liberapay badge.

Assisted-by: Claude Opus 4.5 via Crush

Change summary

README.md | 17 +++++------------
1 file changed, 5 insertions(+), 12 deletions(-)

Detailed changes

README.md

@@ -8,9 +8,14 @@ SPDX-License-Identifier: CC0-1.0
 
 [![REUSE status](https://api.reuse.software/badge/git.secluded.site/np)](https://api.reuse.software/info/git.secluded.site/np)
 [![Go Report Card](https://goreportcard.com/badge/git.secluded.site/np)](https://goreportcard.com/report/git.secluded.site/np)
+[![Liberapay donation status](https://img.shields.io/liberapay/receives/Amolith.svg?logo=liberapay)](https://liberapay.com/Amolith/)
 
 _Upgrade your coding tool's todo system_
 
+**Note:** since my preferred agentic coding tool, Crush, got todo
+support, this project is in maintenance mode. Happy to fix issues, but
+there won't be any big new features.
+
 ## Usage
 
 This section is first to entice you with _nasin pali_'s simplicity;
@@ -179,18 +184,6 @@ anything to modify either created tasks or set goals require a reason ("operator
 said so" is insufficiently detailed, but otherwise acceptable) to go with those
 events.
 
-### Event rendering
-
-The interactive, human-focused sub-commands (for now, just `m` for `m`onitor),
-will be for watching the events and the resulting list as they change in
-real-time-ish. The goal and description and tasks and their descriptions will be
-rendered at the top of the UI and updated based on database events using some
-Charm libraries. Change events are underneath the rendered state, sorted most
-recent (top) to least recent (bottom).
-
-This will probably be implemented later, once the LLM-oriented planning commands
-are solid and I see regular success with them.
-
 ### The format the model sees
 
 It uses individual unicode symbols to represent task statuses. This costs one