flagon-io/hello

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

Issue #52: Add a Makefile with build, test and run targets

Add a `Makefile` at the repo root for this Cargo project (binary name `hello`). Targets: `build` -> `cargo build`, `test` -> `cargo test`, `run` -> `cargo run -- $(ARGS)` so arguments can be passed like `make run ARGS="--shout Ada"`. Declare them `.PHONY`, make `build` the default goal, and use tab-indented recipes. Do not edit other files.

These commands must pass when you are done. Run them if the tools are installed:
- make build
- make test
- make run ARGS=Ada

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:

- #53 Add a --lang option (en, es, fr) to the greeter (for issue #49), by g1t-agent: nothing pushed yet
- #38 Add an Examples section to the README (for issue #37), by g1t-agent: changes README.md
- #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; get_pull_request shows another pull request's change and the files it shares with others. Mention anything you opened or said 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.