docs: add build, architecture, and convention sections to AGENTS.md

Add sections that were already present in CLAUDE.md but missing from
AGENTS.md, bringing the two files into sync:

- Build & Test: all npm scripts agents need to run
- Architecture: component map of src/ layers
- Import Conventions: ESM, .ts extensions, no barrel imports
- Test Conventions: Vitest patterns, colocated tests, smoke tests
- Tool Development: manifest-driven tool registration pattern

Also clean up stray trailing hyphens on blank lines.

Author: dpearson2699

AGENTS.md

@@ -1,5 +1,32 @@
 # Development Rules
 
+## Build & Test
+- `npm run build` - Build (tsup, ESM)
+- `npm run test` - Unit/integration tests (Vitest)
+- `npm run test:smoke` - Smoke tests (builds first, serial execution)
+- `npm run lint` / `npm run lint:fix` - ESLint
+- `npm run format` - Prettier
+- `npm run typecheck` - TypeScript type checking (`tsc --noEmit`)
+- `npm run docs:update` - Regenerate `docs/TOOLS.md` from manifests
+- `npm run docs:check` - Validate docs match CLI surface
+
+## Architecture
+ESM TypeScript project (`type: module`). Key layers:
+
+- `src/cli/` - CLI entrypoint, yargs wiring, daemon routing
+- `src/server/` - MCP stdio server, lifecycle, workflow/resource registration
+- `src/runtime/` - Config bootstrap, session state, tool catalog assembly
+- `src/core/manifest/` - YAML manifest loading, validation, tool module imports
+- `src/mcp/tools/` - Tool implementations grouped by workflow (mirrors `manifests/workflows/`)
+- `src/mcp/resources/` - MCP resource implementations
+- `src/integrations/` - External integrations (Xcode mcpbridge proxy)
+- `src/utils/` - Shared helpers (execution, logging, validation, responses)
+- `src/visibility/` - Tool/workflow exposure predicates
+- `src/daemon/` - Background daemon for persistent sessions
+- `src/types/` - Shared type definitions
+
+See `docs/` for detailed documentation (architecture, configuration, tools, troubleshooting).
+
 ## Code Quality
 - No `any` types unless absolutely necessary
 - Check node_modules for external API type definitions instead of guessing
@@ -8,19 +35,36 @@
 - Always ask before removing functionality or code that appears to be intentional
 - Follow TypeScript best practices
 
+## Import Conventions
+- ESM with explicit `.ts` extensions in `src/` (tsup rewrites to `.js` at build)
+- No `.js` imports in `src/` (enforced by ESLint)
+- No barrel imports from `utils/index` - import from specific submodules (e.g., `src/utils/execution/index.ts`, `src/utils/logging/index.ts`)
+
+## Test Conventions
+- Vitest with colocated `__tests__/` directories using `*.test.ts`
+- Smoke tests in `src/smoke-tests/__tests__/` (separate Vitest config, serial execution)
+- Use `vi.mock`/`vi.hoisted` for isolation; inject executors and mock file systems
+- MCP integration tests use `McpServer`, `InMemoryTransport`, and `Client`
+
+## Tool Development
+- Tool manifests in `manifests/tools/*.yaml` define `id`, `module`, `names.mcp` (snake_case), optional `names.cli` (kebab-case), predicates, and annotations
+- Workflow manifests in `manifests/workflows/*.yaml` group tools and define exposure rules
+- Tool modules export a Zod schema, a pure `*Logic` function, and a `handler` via `createTypedTool` or `createSessionAwareTool`
+- Resources export `{ uri, name, description, mimeType, handler }`
+
 ## Commands
 - NEVER commit unless user asks
 
 ## GitHub
 When reading issues:
 - Always read all comments on the issue
--
+
 ## Tools
 - GitHub CLI for issues/PRs
 - CLI design note: do not rely on CLI session-default writes. CLI is intentionally deterministic for CI/scripting and should use explicit command arguments as the primary input surface.
 - When working on skill sources in `skills/`, use the `skill-creator` skill workflow.
 - After modifying any skill source, run `npx skill-check <skill-directory>` and address all errors/warnings before handoff.
--
+
 ## Style
 - Keep answers short and concise
 - No emojis in commits, issues, PR comments, or code
@@ -29,7 +73,7 @@ When reading issues:
 
 ## Docs
 - If modifying or adding/removing tools run `npm run docs:update` to update the TOOLS.md file, never edit this file directly.
--
+
 ### Changelog
 Location: `CHANGELOG.md`
 
@@ -39,14 +83,14 @@ Use these sections under `## [Unreleased]`:
 - `### Changed` - Changes to existing functionality
 - `### Fixed` - Bug fixes
 - `### Removed` - Removed features
--
+
 #### Rules
 - Before adding entries, read the full `[Unreleased]` section to see which subsections already exist
 - New entries ALWAYS go under `## [Unreleased]` section
 - Append to existing subsections (e.g., `### Fixed`), do not create duplicates
 - NEVER modify already-released version sections (e.g., `## [0.12.2]`)
 - Each version section is immutable once released
--
+
 #### Attribution
 - **Internal changes (from issues)**: `Fixed foo bar ([#123](https://github.com/cameroncook/XcodeBuildMCP/issues/123))`
 - **External contributions**: `Added feature X ([#456](https://github.com/cameroncook/XcodeBuildMCP/pull/456) by [@username](https://github.com/username))`