docs(docs): add README and MIT license

Why:
- document project usage and layout
- provide a GitHub-recognized license
- clarify commit message bullet formatting

Impact:
- adds README and MIT LICENSE for repository
- enforces no blank lines between bullets in AGENTS
- Tests: just check

Author: icepuma

AGENTS.md

@@ -49,6 +49,7 @@ Rules (strict):
 - Body is required for every commit and must include **Why** and **Impact**
   sections exactly as shown.
 - Use bullet points under **Why** and **Impact** (at least one each).
+- Do not insert blank lines between bullet points.
 - Use **Breaking** only when relevant.
 - Wrap body lines at ~72 chars.
 - If multiple areas change, pick the dominant scope and mention the others in

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Stefan Ruzitschka
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

README.md

@@ -0,0 +1,54 @@
+# intar
+
+QEMU-based DevOps lab environment that runs HCL scenarios in local VMs,
+evaluates probes, and presents progress in a TUI.
+
+## Quick start
+Requirements:
+- Rust toolchain
+- QEMU (`qemu-system-*`, `qemu-img`) in PATH
+
+```sh
+cargo run --bin intar -- start scenarios/broken-nginx.hcl
+```
+
+## Usage
+```sh
+intar start <scenario.hcl>
+intar list --dir <path>
+intar ssh <vm-name> [--run <run>] [--command <cmd>]
+intar logs [--run <run>] [--vm <vm>] [--log-type console|ssh|system]
+```
+
+## Scenario format (HCL)
+```hcl
+scenario "broken-nginx" {
+  description = "Fix a misconfigured nginx server"
+  image "ubuntu-24.04" { ... }
+  probe "nginx-running" { type = "service" ... }
+  vm "webserver" { ... probes = ["nginx-running"] }
+}
+```
+
+See `scenarios/` for full examples.
+
+## Project layout
+- `crates/intar-cli` - CLI entrypoint + agent embedding
+- `crates/intar-vm` - VM orchestration + cloud-init
+- `crates/intar-agent` - guest-side probe runner
+- `crates/intar-probes` - probe specs + validation
+- `crates/intar-ui` - TUI
+
+## Development
+- Run checks: `just check`
+- Rebuild embedded agent (after agent/probe changes):
+  - `cargo zigbuild --release --target x86_64-unknown-linux-musl -p intar-agent`
+  - `cargo zigbuild --release --target aarch64-unknown-linux-musl -p intar-agent`
+  - `cargo build --release -p intar-cli`
+
+## Contributing
+Discussions and PRs welcome. Include the scenario file and `intar logs` output
+when reporting a problem.
+
+## License
+MIT