You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The repository lacks a dedicated AGENTS.md that defines clear execution rules for automation agents. We currently have contributor and CI guidance, but no single agent-focused policy document.
This leads to inconsistent agent behavior, especially around post-change Rust checks and documentation updates.
Design
Add an AGENTS.md with a minimal, explicit rule set.
Problem
The repository lacks a dedicated
AGENTS.mdthat defines clear execution rules for automation agents. We currently have contributor and CI guidance, but no single agent-focused policy document.This leads to inconsistent agent behavior, especially around post-change Rust checks and documentation updates.
Design
Add an
AGENTS.mdwith a minimal, explicit rule set.For Rust code changes, require exactly:
cargo fmtcargo clippy --all-targets --no-deps --features telemetry-otel -- -W clippy::pedanticFor behavior/usage changes, require documentation sync in the same PR:
README.mddocs/content (including issue [Feature] Set up public documentation site with Read the Docs, MkDocs, and versioned docs #49 related updates)template/skills/99problems/SKILL.mdwhen usage/workflow changesScope
AGENTS.mdin ./agentsBoundary
Acceptance Criteria
AGENTS.mdexists in .agents/README.md,docs/, skill file when relevant).Context
This is a lightweight process hardening change to make agent contributions more predictable and easier to review.