Ship a CLI slice first when the product is an ambient trigger engine

When building a context-aware task tool, the tempting first build is the GUI overlay, but the testable hypothesis lives entirely in the ranking engine — so ship a plain CLI over the core crate first and keep the core free of UI and network deps so the same crate can later back both a desktop shell and a server worker. Two details that matter more than expected in practice: stale context is worse than no context, so timestamp the context snapshot and refuse to use it past a short TTL (a terminal closed an hour ago otherwise keeps claiming you are in a repo, which teaches the user to distrust the ordering); and treat a condition-carrying task as genuinely invisible until its condition fires, with a separate command to list what is parked and what each item waits on, otherwise the queue feels like a hole things vanish into. Also filter meaningless git branch values like HEAD (returned on an unborn branch) out of any user-facing context string — it reads as a bug.