Add AGENTS.md for AI agent guidance

Add AGENTS.md containing project-specific guidance for AI coding agents,
with quick reference commands for testing/linting and architecture overview.
CLAUDE.md symlinks to AGENTS.md for compatibility.

Also add .agentready to .gitignore.

Assisted-by: Claude Sonnet 4.5 <noreply@anthropic.com>
Signed-off-by: Ralph Bean <rbean@redhat.com>

Author: ralphbean

.gitignore

@@ -22,3 +22,4 @@ fedmsg.d/sync2jira.py
 __pycache__
 .vscode/settings.json
 .worktrees/
+.agentready

AGENTS.md

@@ -0,0 +1,102 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Build, Test, and Lint Commands
+
+### Testing
+```bash
+# Run all tests with coverage (default, excludes integration tests)
+tox
+
+# Run tests for specific Python version
+tox -e py312
+tox -e py313
+
+# Run with HTML coverage report (add this arg locally)
+tox -- --cov-report html:htmlcov-py313
+
+# Run tests directly with pytest
+coverage run -m pytest --ignore=tests/integration_tests
+coverage report
+coverage html  # Generate HTML coverage report
+```
+
+### Linting and Formatting
+```bash
+# Check linting (flake8)
+tox -e lint
+
+# Check code formatting (black)
+tox -e black
+
+# Check import sorting (isort)
+tox -e isort
+
+# Auto-format code
+tox -e black-format
+tox -e isort-format
+```
+
+### Running the Service
+```bash
+# Install in development mode
+pip install -e .
+
+# Run the main sync service
+sync2jira
+
+# Run with initialization (sync all existing issues)
+INITIALIZE=1 sync2jira
+
+# Run the sync-page web UI
+cd sync-page
+python event-handler.py
+```
+
+## Architecture
+
+Sync2Jira is a fedmsg-based service that synchronizes GitHub issues and pull requests to JIRA in real-time.
+
+### Data Flow
+GitHub Event → Fedora Message Bus → sync2jira → Upstream Handler → Intermediary Object → Downstream Handler → JIRA
+
+### Core Components
+
+**sync2jira/main.py**: Entry point and event loop
+- Loads configuration from `fedmsg.d/sync2jira.py`
+- Sets up message handlers for GitHub events
+- Routes messages to appropriate handlers (issues vs PRs)
+- Handles initialization mode for bulk syncing
+
+**sync2jira/intermediary.py**: Platform-agnostic data models
+- `Issue` and `PR` classes represent upstream items in a normalized way
+- `matcher()` function determines if an item should be synced based on filters
+- Converts between GitHub format and internal representation
+
+**sync2jira/upstream_*.py**: GitHub event processors
+- `upstream_issue.py`: Processes GitHub issue events, converts to intermediary objects
+- `upstream_pr.py`: Processes GitHub PR events
+- Handles API calls to fetch full issue/PR data when needed
+- Manages rate limiting
+
+**sync2jira/downstream_*.py**: JIRA interaction layer
+- `downstream_issue.py`: Creates/updates JIRA issues from intermediary objects
+- `downstream_pr.py`: Creates/updates JIRA issues for PRs
+- Handles JIRA-specific logic: custom fields, transitions, components
+- Manages issue linking and remote links back to GitHub
+
+**sync-page/**: Flask web UI for manual sync
+- `event-handler.py`: Flask app that allows triggering syncs for individual repositories
+- Useful for testing or one-off syncs without waiting for fedmsg events
+
+## Configuration
+
+See README.md "Configuration" section and the example in `fedmsg.d/sync2jira.py`.
+
+## Development Guidelines
+
+See CONTRIBUTING.md for:
+- Testing requirements and coverage expectations
+- PR etiquette (history management, comment resolution)
+- Code standards (black, isort, flake8)

CLAUDE.md

@@ -0,0 +1 @@
+AGENTS.md