flagon-io/hello

You are a coding agent working in the git repository checked out in the current directory, on pull request #79 of this repository.

Issue #78: Add CI: formatting, lints and tests on every pull request

Add continuous integration as a GitHub Actions workflow at `.g1t/workflows/ci.yml` (g1t runs GitHub Actions workflows from `.g1t/workflows`), with exactly this content:

```yaml
name: CI
on:
  push:
    branches: [main]
  pull_request:
  merge_group:
jobs:
  check:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7
      - uses: dtolnay/rust-toolchain@stable
        with:
          components: rustfmt, clippy
      - uses: actions/cache@v6
        with:
          path: |
            ~/.cargo/registry
            ~/.cargo/git
            target
          key: cargo-${{ runner.os }}-${{ hashFiles('Cargo.lock') }}
          restore-keys: cargo-${{ runner.os }}-
      - name: Formatting
        run: cargo fmt --check
      - name: Lints
        run: cargo clippy --all-targets -- -D warnings
      - name: Tests
        run: cargo test
```

The code is not formatted with `cargo fmt` today, so the Formatting step would fail: run `cargo fmt` in the same change. Add a line to the README saying that every pull request runs formatting, lints and tests.

Other agents and people are working in this repository at the same time. These pull requests are in progress, and any of them may merge before yours:

- #8 Greet in Spanish and French (for issue #2), by g1t-agent: changes Cargo.lock, src/lib.rs, src/main.rs
- #7 Greet in Spanish and French (for issue #2), by g1t-agent: changes README.md, src/lib.rs, src/main.rs

Keep your change to what your task needs. Where you have to change the same files as one of these, keep your edits small and local so both can merge cleanly: do not reformat, reorder or move code you do not need to change, and do not do work that belongs to one of them.

You have g1t's own tools (mcp__g1t__…) for this repository. Use them to work with the other agents and people here rather than around them: if you find something that needs doing outside your task, open an issue for it with create_issue, saying what and why and naming the pull request you are working on, instead of widening your change; to tell another pull request's author something, such as a conflict you can see coming, comment on it with add_comment; to ask the agent working on another pull request something, or hand it work that belongs there, use message_agent with kind question or handoff and your own pull request as from_number, and keep working: the answer reaches you at a later step. Answer what other agents send you with answer_message. If the work mentions a ticket or alert from another system, such as a Jira key like TECH-1234 or a Sentry link, get_context fetches it as it is now. get_pull_request shows another pull request's change and the files it shares with others. The repository's GitHub Actions workflows run on every commit you push: list_workflow_runs with your pull request's number shows how they went, and get_workflow_run and get_job_logs show why one failed. Mention anything you opened, asked or answered in your summary.

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.