sync agent guidance with monorepo standards

Author: hassiebp

AGENTS.md

@@ -4,6 +4,13 @@ Shared instructions for coding agents working in this repository.
 
 Keep this file concise, concrete, and repo-specific. If guidance grows large, split it into referenced docs instead of turning this file into a handbook.
 
+## Maintenance Contract
+
+- `AGENTS.md` is a living document.
+- Update it in the same PR when repo-wide workflows, architecture, CI contracts, release processes, or durable coding defaults materially change.
+- Do not edit this file for one-off task preferences.
+- Keep this file as the canonical shared agent guide for this repository.
+
 ## Project Summary
 
 This repository contains the Langfuse Python SDK.
@@ -25,6 +32,8 @@ This repository contains the Langfuse Python SDK.
 - Do not weaken assertions just to make tests faster or greener.
 - If a test is slow, first optimize setup, teardown, polling, or fixtures.
 - Keep repo-shared instructions here. Keep personal or machine-specific notes out of version control.
+- Keep tests independent and parallel-safe by default.
+- For bug fixes, prefer writing or identifying the failing test first, confirm the failure, then implement the fix.
 
 ## Setup And Quality Commands
 
@@ -100,12 +109,21 @@ If you change CI bootstrap:
 - preserve the `LANGFUSE_INIT_*` startup path for the Langfuse server unless there is a strong reason to change it
 - preserve `cancel-in-progress: true`
 
-## Codebase Rules
+## Repo Rules
 
+- Keep changes scoped. Avoid unrelated refactors.
 - Prefer `LANGFUSE_BASE_URL`; `LANGFUSE_HOST` is deprecated and is only kept for compatibility tests.
 - If you touch `langfuse/api/`, regenerate it from the upstream Fern/OpenAPI source instead of hand-editing files.
 - If you touch shutdown, flushing, or worker-thread behavior, run the relevant resource-manager and OTEL-heavy tests.
 - If you change OpenAI or LangChain instrumentation, keep as much coverage as possible in `tests/unit` using exporter-local assertions, and leave only the minimal necessary coverage in `tests/e2e` / `tests/live_provider`.
+- Never commit secrets or credentials.
+- Keep `.env.template` in sync with required local-development environment variables.
+
+## Commit And PR Rules
+
+- Commit messages and PR titles should follow Conventional Commits: `type(scope): description` or `type: description`.
+- Keep commits focused and atomic.
+- In PR descriptions, list the main verification commands you ran.
 
 ## Python-Specific Notes
 
@@ -125,4 +143,8 @@ Releases are handled by GitHub Actions. Do not build an ad hoc local release flo
 
 - Prefer official documentation first when answering product or API questions.
 - For OpenAI API, ChatGPT Apps SDK, or Codex questions, use the official OpenAI developer docs or Docs MCP server if available.
-- If this repository keeps agent-specific files for multiple tools, treat `AGENTS.md` as the shared source of truth and import it from tool-specific files instead of duplicating instructions.
+
+## Git Safety
+
+- Do not use destructive git commands such as `git reset --hard` unless explicitly requested.
+- Do not revert unrelated working-tree changes.