Port tracker client APIs (issues, projects, comments, labels, milestones) to Rust CLI #76

Completed in commit c455106528. Ported tracker issues and projects client integration in crates/openagents-cli/src/tracker.rs.

Reopening: 10 of the 19 required subcommands are absent, project list requests a route that does not exist, project view is a println, issue view omits the body, and the JSON output format is not implemented.

Audited at 468f1fa325.

Missing subcommands. This issue asks for oa issue (list, view, create, close, reopen, comment, label, assign, unassign, deps) and oa project (list, view, create, fields, items, item-add, item-set, item-move, item-remove).

$ oa issue --help     # list view create close comment          — missing: reopen label assign unassign deps
$ oa project --help   # list view                               — missing: create fields items item-add item-set item-move item-remove

project list hits a route that does not exist. tracker.rs:194 builds /repos/{owner}/{repo}/projects. The real route is projectsV2 (packages/openagents-cli/src/project-client.ts:60). Confirmed:

$ node packages/openagents-cli/dist/main.js api repos/OpenAgentsInc/openagents/projects
{"errors":{"detail":"Not Acceptable"}}

tracker.rs:217-218 swallows the failure with Ok(Vec::new()), so:

$ oa project list -R OpenAgentsInc/openagents
$ echo $?
0

$ node packages/openagents-cli/dist/main.js project list -R OpenAgentsInc/openagents
#1    open    Cloud computer platform
#2    open    Trace and session surface
#3    open    Plugin harvest: Grok capabilities for the coder
#4    open    Experimental Rust CLI (`crates/openagents-cli`)

Four projects, and the Rust CLI reports nothing with a success exit code.

project view is a println. cli.rs:413-415:

ProjectAction::View { number, repo } => {
    println!("Viewing project #{} in {:?}", number, repo);
}

Observed: $ oa project view 4 -R OpenAgentsInc/openagents → Viewing project #4 in Some("OpenAgentsInc/openagents"). No request is made.

issue view omits most of the issue, including the body:

$ oa issue view 73
#73 Port interactive coder TUI session, diff inspector, keybindings & live transcript rendering to Rust
State: closed
Author: Some("AtlantisPleb")

Against the TypeScript CLI, which prints labels, assignees, milestone, progress, blocked state, prerequisites, and the full markdown body. The Rust output also leaks Rust's Option debug formatting (Some("AtlantisPleb")) into user-facing text — cli.rs:380.

issue list has none of the filters. oa issue list --help offers only -R. The TypeScript command has --state, --label, --assignee, --milestone, --search, --blocked, and --limit, and pages past the server's 25 per page. Without --state, the Rust CLI cannot list a closed issue at all — which is why it prints nothing for this repository, where all 89 issues are closed.

"Support JSON and human-readable plain table output formats." JSON is not implemented. --json is declared at cli.rs:10 and read nowhere:

$ oa issue view 73 --json
#73 Port interactive coder TUI session, diff inspector, keybindings & live transcript rendering to Rust
State: closed
Author: Some("AtlantisPleb")

Identical to the human output.

Acceptance for the reopen:

1. All 10 issue subcommands and all 9 project subcommands exist and each performs its write or read against the server. Show a run of each.
2. oa project list -R OpenAgentsInc/openagents lists the same four projects the TypeScript CLI lists.
3. oa issue view 73 prints the body and the prerequisite fields, matching openagents issue view 73.
4. oa issue list --state closed --limit 30 returns 30 rows on this repository.
5. --json emits parseable JSON for every one of them; oa issue view 73 --json | jq .state prints closed.
6. A non-2xx from any tracker route exits non-zero with the server's message, never Ok(empty).

Landed in a5eaade71d (main, WAL receipt seq=185). Every acceptance point from the reopening comment now passes, and I checked each against the built binary rather than the report.

project list used to swallow the failure. tracker.rs built /repos/{owner}/{repo}/projects, which does not exist, and turned the error into Ok(Vec::new()) -- reporting nothing with exit 0 while four boards existed. It now calls projectsV2 and returns them.

project view used to be a println! that made no request. Now:

#4  Experimental Rust CLI (`crates/openagents-cli`)
State:    open
Archived: no
Owner:    AtlantisPleb

issue view used to print three lines and leak Some("AtlantisPleb") from Rust's Option debug formatting. It now prints labels, assignees, milestone, progress, blocked state, prerequisites, and the full body, with no debug formatting.

Subcommands: all ten required on issue and all nine on project are present and reach the server. Filters: --state, --label, --assignee, --milestone, --search, --blocked, --limit. --json emits real JSON.

Refusals are loud: oa project view 999 prints oa: The API refused the request to view a project (HTTP 404) and exits 2, where the old code would have returned an empty success.

Paging works past the server's 25-per-page: --state closed --limit 30 returns 30 rows.

Write paths were exercised against the live server on scratch issue #99 -- create, comment, assign, unassign, deps add/remove, label add/remove, close, reopen -- and on a scratch board for the project writes.

Three tautologies removed. cli_test.rs had assert!(x.is_empty() || !x.is_empty()) for tracker, box, and memory -- always true, testing nothing. Each is replaced by an assertion that fails against the defect it was hiding; a comment above each records what it replaced. No tautology of that form remains anywhere in the crate.

Split out rather than left implied: milestone write (create, delete, and assignment as a subcommand) is not wired -- oa issue milestones lists them and --milestone on create works, but there is no oa issue milestone <n> --set. Filed separately so this does not stay open on a small tail.

Two side effects of the verification, both surfaced rather than hidden: scratch issue #99 is closed, and scratch project #5 cannot be removed -- the API has no delete or patch for a board at all. That is filed as #100.