docs: clarify tox venv usage and commit conventions

Author: TomKaltofen

AGENTS.md

@@ -24,6 +24,14 @@ Use `tox` to run all checks:
 tox
 ```
 
+Run checks from the project virtualenv:
+```bash
+source .venv/bin/activate && tox
+```
+
+`tox` is the required final verification step after code or dependency changes.
+Running only `pytest` is not sufficient for completion.
+
 ### Run individual checks
 
 ```bash
@@ -34,6 +42,14 @@ mypy --strict --ignore-missing-imports .
 bandit -c pyproject.toml -r -q .
 ```
 
+## Commit messages
+
+Use Conventional Commit format for all commits so semantic versioning/release tooling can parse intent.
+
+Examples:
+- `fix: handle empty feature set`
+- `chore(deps): bump mloda to 0.4.6`
+
 ## Claude Code Skills
 
 The mloda-registry provides Claude Code skills that assist with plugin development:

CLAUDE.md

@@ -22,6 +22,14 @@ Use `tox` to run all checks:
 tox
 ```
 
+Run checks from the project virtualenv:
+```bash
+source .venv/bin/activate && tox
+```
+
+`tox` is the required final verification step after code or dependency changes.
+Running only `pytest` is not sufficient for completion.
+
 ### Run individual checks
 
 ```bash
@@ -31,3 +39,11 @@ ruff check .
 mypy --strict --ignore-missing-imports .
 bandit -c pyproject.toml -r -q .
 ```
+
+## Commit messages
+
+Use Conventional Commit format for all commits so semantic versioning/release tooling can parse intent.
+
+Examples:
+- `fix: handle empty feature set`
+- `chore(deps): bump mloda to 0.4.6`