AGENTS.md for /tickets/ folder

HTML

# AGENTS for Tickets (PM+AI)

## Goal
Create high quality tickets that are implementable without back and forth, tuned to this repo's expectations.

## Ticket identity
- File name: T-###-short_title.md
- Inside the file: include Ticket ID, Date, Owner, Status, Estimate

## Prior work and references
Tickets do not exist in a vacuum. Before writing a ticket, check what has already been built and reference it concretely.

- **Check completed tickets:** Read prior tickets in this folder to understand what modules, functions, and data shapes already exist. Do not re-specify something that is already built — reference it by file path and function name.
- **Check existing source code:** If earlier phases produced working modules (e.g., `src/core/data_store.php`), open those files and reference the actual function signatures, return types, and patterns — not what the plan originally said they would be. Implementation often diverges from the plan.
- **Reference by path and function name:** Instead of "use the data store module", write `ds_write_json()` from `src/core/data_store.php`. Instead of "call the Kalshi client", write `hypo_kalshi_get_market()` from `src/core/kalshi_client.php`.
- **Note what changed:** If prior work revealed something unexpected (a Kalshi API field name differs from what was planned, a function signature was simplified, etc.), call it out in Context so the implementer has accurate information.
- **Planning docs:** Reference `docs/planning/planClaude.md` for architectural decisions and resolved design questions. Don't repeat the full rationale — link to the relevant section.

## Required sections
1) Title
2) Decision Snapshot
3) Context
4) Goal
5) Non goals
6) Requirements
7) Acceptance Criteria
8) Dependencies
9) Risks and Edge Cases
10) Implementation Notes
11) Test Plan
12) Observability
13) Rollback Plan

## Decision Snapshot format
A short, high signal summary answering:
- What is being built
- Why now
-...