feat: add time entry CRUD tools (closes #7, revisits #8 and #12)

[madisonrickert]

Adds full time entry CRUD per #7, reimplemented from current main per the maintainer's "fresh PR from current main with tests against the post-1.1.0 handler structure" note when closing #12 (and equivalent guidance closing #8).

Note

Tracking #36, depends on #37. Same coordination story as #37 (tag CRUD): authored against current main. The request 200/empty-body fix is cherry-picked from #37 because tag DELETE and time entry DELETE share the same Toggl response shape — patch-id collision will let the duplicate commit drop cleanly when either PR rebases. Happy to rebase against post-#36/#37 main and add handler tests using the new tests/mcp-server.test.ts pattern, or merge in any order — your call.

What's added

Three MCP tools that complete the time entry CRUD surface, plus a small extension to toggl_start_timer:

• toggl_create_time_entry — POST /workspaces/{wid}/time_entries. Required: start. Optional: stop, duration, description, project_id, task_id, tags, tag_ids, billable. Fills the create gap for retroactively logging past work — toggl_start_timer only creates running timers.
• toggl_update_time_entry — PUT /workspaces/{wid}/time_entries/{tid}. All fields optional except entry_id; only fields the caller passed are sent, so { project_id: 50 } doesn't clobber description.
• toggl_delete_time_entry — DELETE /workspaces/{wid}/time_entries/{tid}.
• toggl_start_timer — gains optional billable parameter for parity.

All three new tools resolve workspace via resolveWorkspaceForTool, return via jsonResponse, and hydrate response entries via cache.hydrateTimeEntries. Errors flow through the central catch with errorPayload(error). No new cache invalidation — time entries aren't cached as a collection.

Includes a small request() fix (cherry-picked from #37)

toggl_delete_time_entry hits the same Toggl 200/content-length: 0 shape as tag DELETE. The existing request() short-circuited only on 204 and called response.json() on the empty body, throwing and triggering a misleading retry that surfaced as a bogus 404. The cherry-picked fix from #37 treats 200/empty-body the same as 204. Behavior unchanged for non-empty success responses.

Resolves prior closed work

• Feature Request: toggl_update_time_entry tool for editing existing time entries #7 (open, @YoungR25): explicit feature request for toggl_update_time_entry with project/task/description/tags/billable. Implemented.
• feat: add billable support to start_timer and new update_entry tool #8 (closed, @rocketworm): billable on start_timer + update_entry tool. Maintainer's closing note: "rewrite from current main if billable/update-entry support is still wanted." Reimplemented from current main; original author credited via Co-Authored-By.
• feat: add create_time_entry and delete_time_entry tools #12 (closed, @arndjan): create + delete time entry tools. Maintainer's closing note: "fresh PR from current main with tests against the post-1.1.0 handler structure." Reimplemented from current main; original author credited via Co-Authored-By.

Both contributors' branches were too far behind to cherry-pick cleanly (pre-1.1.0). Their work informed the design but the implementation here is fresh against current main patterns: WorkspaceResolutionError, jsonResponse, errorPayload, resolveWorkspaceForTool, cache.hydrateTimeEntries.

Plan-tier billable note

A small UX hint: the billable parameter description on all three tools that accept it now mentions that some Toggl plans (Free) silently set entry-level billable to false even when the project itself is billable. Agents can check the response to detect the discrepancy rather than assuming the flag applied. Verified live during smoke testing — the Toggl API accepts the flag and returns 200, but the response shows billable: false on Free workspaces.

Commits

Three commits:

1. fix(api): handle Toggl 200/empty-body responses — cherry-picked from feat: add tag CRUD tools (revisits #9) #37
2. feat: add time entry CRUD tools and billable on start_timer — Co-Authored-By: Andreas Wurm, Arnd Jan Gulmans
3. docs: note plan-tier billable behavior in tool schemas

Verification

• npm test — 36/36 passing (5 new API-level tests: POST/PUT/DELETE shape, billable-passthrough, 4xx no-retry)
• npm run build — clean
• npm run lint — no new warnings
• Smoke-tested end-to-end against a real Toggl workspace: create with billable → list (verify visible) → update (assign project, hydrate via cache) → delete → verify cleanup. The empty-body fix is verified live; delete returns clean success: true, no false 404.

Coverage with #36's proposed thresholds

Same approach as #37 — every metric improves over main; further gain available via handler tests once createTogglServer lands.

Scope

Time entry CRUD only. No project/client write tools, no SDK upgrade.

[jack-arturo]

I opened a maintainer refresh branch as #58: #58

This keeps the time-entry CRUD work moving without force-pushing to the contributor fork, and stacks the implementation on the refreshed self-host HTTP foundation from #36. The refresh preserves the CRUD intent here, adds the missing read-only toggl_list_tasks lookup requested in #7, adds MCP handler coverage, disables retries for ambiguous write failures, handles Toggl 200/empty-body write responses, and validates write-tool arguments before calling Toggl. Original contributor attribution is included in the commit and PR body.

Local verification on #58:

• npm run build
• npm test
• npm run test:coverage
• npm run lint
• npm audit --audit-level=high