[yw0nam]

Summary

AGENTS.md states each rule as the target behavior, drops sentences that repeat another rule, and points at the two dev tools agents reach for.

 Development work
-  Worktree → PR: guard denies commit/push on main — the agent cannot … must request the user
+  Worktree → PR: worktree from `scripts/worktree.sh <branch>`; the user runs commit/push on main
-  Verify: … attach proof
+  Verify: … attach proof; `uv run python -m memory_base.eval.sandbox` serves the real REST API for it
-  Comments: minimal … no breadcrumbs. And Should use only English …
+  Comments: one line, present tense, English; history, spec, issue number go in the commit and PR
 Tracker & commit conventions
-  fill the PR template
+  fill the PR template, one `Closes #N` line per resolved issue
-  No AI attribution: Never append … trailer
+  No AI attribution: write the message as the change itself (trailer examples kept as the guardrail)

Prohibition-led sentences in Working principles (simplest implementation, layers, libraries, long-term decisions) are rewritten as the positive target. "grounded in web research" is dropped; "Look at established products first" holds that rule. The PR template's Related-issues hint reads One line per resolved issue: Closes #N.

Related issues

None.

Runtime evidence (required for ingest / retrieval / serving behavior)

N/A — no runtime behavior change (docs only).

• Before: —
  After: cat AGENTS.md .github/PULL_REQUEST_TEMPLATE.md | bash scripts/ci/docs-guard.sh → exit 0

Merge Danger

Door: two-way

Blast Radius: steering

Every agent session in this repo loads AGENTS.md; a revert restores the previous wording.

Verification

• uv run pytest passes — N/A, docs only
• uv run ruff format --check . and uv run ruff check . pass — N/A, docs only
• docker compose build mcp passes — N/A
• Runtime evidence attached above, or N/A justified

Checklist (core principles)

• Selective storage — notes stay distilled; verbatim text lives only in doc_rows and the turns lane
• Source-specific logic stays out of the source-agnostic core (ingest pipeline, retrieval, serving)
• No hardcoded endpoints/models — configuration lives in .env
• New/changed behavior ships a test in this PR (or skip-tests label justified) — no behavior change