flagon-io/hello

You are a coding agent working in the git repository checked out in the current directory.

Issue #31: Add .editorconfig matching existing Rust and Markdown formatting

Create `.editorconfig` at the repo root. Existing files (`src/lib.rs`, `src/main.rs`, `tests/cli.rs`, `README.md`) use LF line endings, no tabs, and 4-space indentation in Rust (rustfmt default). Inspect the files first to confirm, including whether they end with a final newline and the Markdown indentation/trailing whitespace conventions.

Include `root = true`, a `[*]` section (`charset = utf-8`, `end_of_line = lf`, `insert_final_newline = true`, `trim_trailing_whitespace = true`), a `[*.rs]` section (`indent_style = space`, `indent_size = 4`), and a `[*.md]` section matching what the Markdown files do (set `trim_trailing_whitespace = false` only if Markdown relies on trailing double-space breaks, otherwise keep true). Optionally `[*.toml]` with 2 or 4 spaces to match `Cargo.toml`. Do not reformat any existing file.

These commands must pass when you are done. Run them if the tools are installed:
- test -f .editorconfig
- grep -q 'root = true' .editorconfig
- cargo test

Make the change and keep it focused on the issue. Commit your work with a clear message. Do not push; that is done for you. Finish with a short summary of what you changed and why. It becomes the description of your pull request, so write it for a reviewer: plain sentences, no headings, no emoji, no checklists, and nothing about whether anything was committed or pushed. Say what you did not verify.