## Onboarding Analysis

Thoroughly understand this repository and generate two onboarding artifacts. Use your tools (read, bash, write, edit) to inspect the repo, then write the files.

### Quick discovery (pre-scanned)

{{{DISCOVERY_JSON}}}

### Steps

1. Read the README, manifests, and key source files to understand what this project actually does.
2. Identify: project purpose, tech stack, important directories, commands (run/test/lint/build), conventions, entry points.
3. Write `AGENTS.md` in the repo root{{{AGENTS_SAFETY}}}.
{{{HTML_STEP}}}

### AGENTS.md format

Write clean, well-formatted markdown. Lean and practical (50-150 lines). Do NOT include any HTML comments or hidden markers — just plain readable markdown.

```markdown
# AGENTS.md

> Auto-generated by pi-onboard. Review before committing.

## Project purpose
(1-3 sentences on what this project actually does — be specific)

## Tech stack
- TypeScript / Node.js / etc. with versions if known
- Key frameworks and libraries

## Important paths
- `dir/` — what's in it and why it matters

## Commands
- **Run**: `command` — what it does
- **Test**: `command` — what it does
- **Lint**: `command` (label uncertain ones as 'likely')
- **Build**: `command`

## Working conventions
(patterns and gotchas discovered in the code)

## Where to start when making changes
1. Read `file` — why
2. Check `dir/` — why

## Open uncertainties
(things you couldn't determine — be honest)
```

### File safety
{{{FILE_SAFETY}}}
{{{HTML_FORMAT}}}
{{{TEXT_ONLY_NOTE}}}
After writing the files, print a brief summary of what you generated.