[CHORE] Prepare v1.0.0 release with enhanced documentation

[vereis]

Prepares EctoLiteFS for v1.0.0 release and publishing to hex.pm.

[Copilot]

Pull request overview

This PR prepares EctoLiteFS for its 1.0.0 release on hex.pm by significantly enhancing documentation and bumping the version from 0.1.0 to 1.0.0. The changes are entirely documentation-focused with no functional code modifications.

Key changes include:

• Comprehensive module documentation with quick-start guides, architecture explanations, and API references
• Enhanced README with feature lists, architecture diagrams, and telemetry monitoring examples
• Version increment to 1.0.0 signaling production-readiness

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
mix.exs	Bumps version from 0.1.0 to 1.0.0 for initial stable release
lib/ecto_litefs/rpc.ex	Adds @SPEC type annotation for better documentation and dialyzer support
lib/ecto_litefs.ex	Adds extensive moduledoc including quick examples, setup instructions, telemetry documentation, error handling guide, and public API reference
README.md	Enhances user-facing documentation with features list, quick start guide, architecture diagram, configuration examples, and telemetry monitoring patterns

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The telemetry events documentation is incomplete. It should specify:

1. What measurements each event provides (e.g., :stop and :exception include duration, :start includes system_time)
2. That the :exception event includes reason in its metadata in addition to the common fields

Consider adding a section that documents the full signature of each event with both measurements and metadata.

Suggested change

	All events include metadata: `%{repo: repo, action: action, primary_node: node}`
	Each event emits measurements and metadata:
	- `[:ecto_litefs, :forward, :start]`
	- **Measurements:** `%{system_time: integer}` (monotonic system time in native units)
	- **Metadata:** `%{repo: repo, action: action, primary_node: node}`
	- `[:ecto_litefs, :forward, :stop]`
	- **Measurements:** `%{duration: non_neg_integer}` (forwarding duration in native time units)
	- **Metadata:** `%{repo: repo, action: action, primary_node: node}`
	- `[:ecto_litefs, :forward, :exception]`
	- **Measurements:** `%{duration: non_neg_integer}` (time from start until exception)
	- **Metadata:** `%{repo: repo, action: action, primary_node: node, reason: reason}`
	The `repo`, `action`, and `primary_node` fields are common to all events; `reason` is only present
	on `:exception` events and contains the failure reason.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The documentation references :erpc.call/4, but the actual implementation uses :erpc.call/3 (which takes node, function, and timeout as parameters). Update the documentation to reference :erpc.call/3 for accuracy.

Suggested change

	to the primary node via `:erpc.call/4`.
	to the primary node via `:erpc.call/3`.

[Copilot]

The string interpolation is escaped and will not work correctly. The backslash before the hash symbol causes the interpolation to be printed literally as #{action} and #{duration} instead of evaluating the variables. Remove the backslashes to fix the interpolation.

Suggested change

	Logger.info("Forwarded \#{action} to primary in \#{duration}ns")
	Logger.info("Forwarded #{action} to primary in #{duration}ns")

[Copilot]

The documentation references :erpc.call/4, but the actual implementation uses :erpc.call/3 (which takes node, function, and timeout as parameters). Update the documentation to reference :erpc.call/3 for accuracy.

[Copilot]

The documentation references :erpc.call/4, but the actual implementation uses :erpc.call/3 (which takes node, function, and timeout as parameters). Update the documentation to reference :erpc.call/3 for accuracy.