Update repository project name from 'lunatask-mcp-server' to
'llm-projects' in the `pr.pico.sh` examples and links.

Removed alternative contribution methods (SourceHut, Radicle) to
simplify the collaboration guidelines, focusing solely on using
`pr.pico.sh` for patch requests.

Added a comprehensive list of all available tools with their parameters
and descriptions to the README.md file.

- Documented get_timestamp tool
- Documented list_areas_and_goals tool
- Documented create_task tool with all parameters
- Documented update_task tool with all parameters
- Documented delete_task tool
- Documented list_habits_and_activities tool
- Documented track_habit_activity tool

This makes it easier for users to understand what tools are available
and how to use them.

Co-Authored-By: Crush <crush@charm.land>

Co-Authored-By: Crush <crush@charm.land>

Add support for Eisenhower Matrix quadrant classification in both
create_task and update_task operations. The field accepts human-readable
values that are translated to API integers:
- uncategorised (0) - clears the field
- both urgent and important (1)
- urgent, but not important (2)
- important, but not urgent (3)
- neither urgent nor important (4)

Includes proper validation and helpful error messages following the
existing priority field pattern.

- Standardize estimate max value to 720 minutes (12 hours) across both tools
- Fix incorrect tool name references from get_task_timestamp to get_timestamp

- Add detailed workflow instructions for all tools with proper sequencing
- Document enum constraints and parameter limits in natural language
- Include system prompt requirements for task creation workflow
- Clarify when to include optional parameters vs when to omit them
- Add speech-to-text interpretation guidance for better user experience

Change gofumpt command in justfile to use '.' instead of './...' to format the
root directory and not only children directories.

The TOML configuration keys `goals` and `areas` were incorrectly pluralized.
This commit renames them to the singular `goal` and `area` respectively to align
with the TOML parser's expectation for arrays of a single type.

Updates the task priority argument to accept string values ("lowest", "low",
"neutral", "high", "highest") instead of a number range (-2 to 2). This improves
clarity and user experience. The internal representation remains an integer.

Improve the explanation of the patch request workflow and add a link to the
pico.sh patch request homepage for further details.

Update the 'priority' field in the MCP schema from a number between -2 and 2 to
a string enum with values like 'lowest', 'low', and 'highest'. This provides a
more descriptive way to specify task priority.

Translate the string input to the corresponding integer value before processing
the task creation.

The new `.rules` file outlines a standardized process for LLMs to follow after
completing requests. This includes checking project diagnostics and running
automated checks to ensure code quality and consistency.

Explicitly set the `PerformedOn` field's datetime validation format
in `TrackHabitActivityRequest` to `2006-01-02T15:04:05Z07:00` (RFC3339).

This change replaces the generic `datetime` validator tag to improve
code clarity and ensure the expected input format is self-documenting.
It assumes the previous default validation behavior was already RFC3339,
so no functional change to validation logic is intended.

Introduces a more robust mechanism for tracking habits and activities.
This change renames the configuration key for habits and updates the
LLM tools for better interaction and functionality.

The `Config.Habits` field in `config.toml` has been renamed to
`Config.Habit` for consistency and to support these enhancements.

The `list_habits` tool has been removed. It is replaced by the new
`list_habits_and_activities` tool. This tool lists habits and their
IDs, enabling the LLM to better identify entries for tracking or
marking completion via the `track_habit_activity` tool. The description
for `track_habit_activity` has also been updated.

The prompt guidance in `README.md` is updated to leverage these changes,
instructing the LLM to use `list_habits_and_activities` to find
relevant habits when a user indicates completion of a task without
other context.

BREAKING CHANGE:
- The configuration field `Habits` in `config.toml` has been renamed
  to `Habit`. Users must update their configuration files:
  e.g., `Habits = [...]` should become `Habit = [...]`.
- The LLM tool `list_habits` has been removed and is superseded by
  `list_habits_and_activities`. LLM prompts or integrations relying
  on the `list_habits` tool must be updated.

This commit introduces functionality to track and list habits
via the Lunatask API and new MCP tools.

Key changes include:
- `lunatask.TrackHabitActivity`: New client method and associated types
  for tracking habit completions. Includes request validation.
- `list_habits` MCP tool: Lists configured habits and their IDs.
- `track_habit_activity` MCP tool: Allows tracking of habit activity
  using a habit ID and a timestamp (obtained via `get_timestamp`).
- Configuration: Added `Habits` section to `config.toml` for defining
  habits.

Tooling improvements:
- Renamed `get_task_timestamp` MCP tool to `get_timestamp`.
- Clarified descriptions for parameters in `create_task` and
  `update_task` MCP tools.

BREAKING CHANGE: The MCP tool `get_task_timestamp` has been renamed to
`get_timestamp`. Clients using the old tool name need to reload their
integration.

This commit introduces the functionality to delete tasks.

It adds a `DeleteTask` method to the Lunatask client, along with
a `DeleteTaskResponse` struct, enabling interaction with the
Lunatask API's task deletion endpoint.

Additionally, a new `delete_task` tool and its corresponding
`handleDeleteTask` handler are integrated into the MCP server,
exposing this new capability.

Introduces `Task` and `Source` data transfer objects (DTOs) for
representing task-related data, primarily for API responses.

Validation for `CreateTaskRequest` has been updated:
- `AreaID` validation now enforces `uuid4` format if the field is present.
- `GoalID` validation now enforces `uuid4` format if the field is present.

BREAKING CHANGE: The `AreaID` and `GoalID` fields in the `CreateTaskRequest`
must now be valid UUIDv4 strings if provided. Previously, these fields
might have accepted non-UUID strings or had less strict validation.
Clients sending requests to create tasks must ensure these IDs conform to
the UUIDv4 format to avoid validation errors.

- Don't correct yourself with confirmation
- Mention priority options (it was thinking "top" = 10 even though tool desc
  says -2 - 2).
- Explicitly tell it to intuit intent a bit
- Add user_provided_content block