feat: CLI quick wins — heph-tui --version, fuzzy --project, heph context, version RPC #6

Merged

eblume merged 6 commits from feature/cli-quick-wins into main

2026-06-04 12:42:20 -07:00

eblume commented

2026-06-04 12:06:47 -07:00

Owner

Summary

A batch of small, independent CLI/daemon quick wins from the Hephaestus project backlog:

heph-tui --version — heph-tui now reports X.Y.Z (sha) like heph/hephd (the missing third binary). Closes the heph-tui half of the cross-binary --version task.
--project is case-insensitive / prefix-fuzzy when unambiguous — a tiered resolver (exact → case-insensitive exact → unambiguous prefix; ambiguous → no match) shared across task/edit/promote/list/parent via a new project.resolve RPC + Store::resolve_project. An exact case-sensitive title always wins outright, so nothing that resolved before changes.
heph context <task-id> — read/--body/--append a task's canonical-context doc body by task id, with no manual canonical_context_id lookup. - reads stdin like node update.
version RPC — returns heph_core::VERSION, so RPC clients (the hephaestus.nvim :Heph version command) can report which hephd they talk to.

Each change ships a changelog fragment.

Already resolved (verified, no code here)

The "--version reports 0.0.0" task was already fixed by the v1.0.1/v1.0.2 release commits — 0.0.0 on dev/branch builds is by design; release-tag installs report the real version.

Testing

cargo test (full workspace) — green; added 3 tests: fuzzy resolver (unit), version + project.resolve over the socket (e2e)
cargo clippy --workspace --all-targets — clean
cargo fmt --all --check — clean
mise run changelog-check — pass
Manual e2e of --project (exact/ci/prefix/ambiguous/unknown) and heph context (read/set/append/stdin/errors) against isolated temp daemons

🤖 Generated with Claude Code

## Summary A batch of small, independent CLI/daemon quick wins from the `Hephaestus` project backlog: - **`heph-tui --version`** — `heph-tui` now reports `X.Y.Z (sha)` like `heph`/`hephd` (the missing third binary). Closes the `heph-tui` half of the cross-binary `--version` task. - **`--project` is case-insensitive / prefix-fuzzy when unambiguous** — a tiered resolver (exact → case-insensitive exact → unambiguous prefix; ambiguous → no match) shared across `task`/`edit`/`promote`/`list`/parent via a new `project.resolve` RPC + `Store::resolve_project`. An exact case-sensitive title always wins outright, so nothing that resolved before changes. - **`heph context <task-id>`** — read/`--body`/`--append` a task's canonical-context doc body *by task id*, with no manual `canonical_context_id` lookup. `-` reads stdin like `node update`. - **`version` RPC** — returns `heph_core::VERSION`, so RPC clients (the `hephaestus.nvim` `:Heph version` command) can report which `hephd` they talk to. Each change ships a changelog fragment. ## Already resolved (verified, no code here) The "`--version` reports 0.0.0" task was already fixed by the v1.0.1/v1.0.2 release commits — `0.0.0` on dev/branch builds is by design; release-tag installs report the real version. ## Testing - [x] `cargo test` (full workspace) — green; added 3 tests: fuzzy resolver (unit), `version` + `project.resolve` over the socket (e2e) - [x] `cargo clippy --workspace --all-targets` — clean - [x] `cargo fmt --all --check` — clean - [x] `mise run changelog-check` — pass - [x] Manual e2e of `--project` (exact/ci/prefix/ambiguous/unknown) and `heph context` (read/set/append/stdin/errors) against isolated temp daemons 🤖 Generated with [Claude Code](https://claude.com/claude-code)

eblume added 4 commits

2026-06-04 12:06:47 -07:00

feat: heph-tui --version reports version + build SHA 58a5544d44

heph-tui was the one daily-driver binary that did not answer --version.
Add the same clap `version = heph_core::VERSION` attribute that heph and
hephd already carry, so all three report `X.Y.Z (sha)` consistently.

Addresses the heph-tui half of the cross-binary --version task.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

feat: --project arg is case-insensitive / prefix-fuzzy when unambiguous fc25f6ac51

The `--project <name>` argument matched titles case-sensitively and
exactly, so `--project hephaestus` or `--project heph` failed against a
`Hephaestus` project. Make project-name resolution forgiving but
deterministic, via a tiered match in `resolve_project_id`:

  1. exact (case-sensitive) — the historical behavior; always wins
  2. case-insensitive exact — only when unambiguous
  3. case-insensitive prefix — only when unambiguous

Ambiguous fuzzy matches resolve to None (callers report "no project
named X") rather than silently picking one. This single resolver already
backed `heph list --project` (via project_scope); route the CLI's
task/edit/promote/parent path through it too with a new `project.resolve`
RPC + `Store::resolve_project`, so every `--project` surface behaves the
same.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

feat: heph context <task-id> reads/edits a task's context doc by id babdb21c0a

Editing a task's canonical-context doc body previously meant looking up
its `canonical_context_id` (e.g. via `heph list --json`) and then
`heph node update <doc-id> --body`. Add a `heph context <task-id>`
command that resolves the canonical-context doc from the task's outgoing
links and:

  * prints the body with no flag,
  * `--body <text>` replaces it (`-` reads stdin, matching `node update`),
  * `--append <text>` adds a blank-line-separated paragraph.

Errors clearly when the id has no canonical-context doc (e.g. a plain
doc node rather than a task). Purely a client-side CLI convenience — no
new RPC.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

feat: add a version RPC returning the daemon build version

Build / validate (pull_request) Failing after 15s

Details

7914232ec4

RPC clients (the hephaestus.nvim plugin, for its `:Heph version`
command) had no way to learn which hephd they are talking to — `health`
returns counts, not a version. Add a tiny `version` method returning
`{ version: heph_core::VERSION }`, the same `X.Y.Z (sha)` string the
binaries print for --version. No store access needed.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

eblume added 1 commit

2026-06-04 12:31:07 -07:00

style: rustfmt the new rpc_socket tests

Build / validate (pull_request) Has been cancelled

Details

8d80208726

The project.resolve socket test had a node.create call over rustfmt's
line limit; CI's `cargo fmt --all --check` flagged it. Wrap it.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

eblume added 1 commit

2026-06-04 12:36:35 -07:00

infra: add cargo-fmt-check pre-push prek hook (mirror CI)

Build / validate (pull_request) Successful in 5m25s

Details

7f48a2a1c5

The cargo-fmt failure on this PR slipped to CI because the pre-commit
prek hooks were never installed in the working clone. The existing
cargo-fmt hook reformats in place but only when it runs. Add a
pre-push cargo-fmt-check hook (`cargo fmt --all --check`) that mirrors
CI's Dagger `check` step exactly, so an unformatted commit is blocked
locally before it can reach the runner — even if the pre-commit hook was
skipped or not installed. Filtered to .rs pushes so Rust-free pushes pay
nothing.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>