docs: add agent guidance entrypoint

[ProfRandom92]

Adds root AGENTS.md pointing agents to repo-local skill docs and preserving deterministic CompTextv7 safety rules.

Scope

Docs/config only. No code, tests, packages, artifacts, or benchmark semantics changed.

[gemini-code-assist]

Code Review

This pull request updates AGENTS.md by adding sections for repo-local skill documentation and default safety rules for agents. The review feedback suggests standardizing documentation filenames to use snake_case for consistency and incorporating an explicit safety rule for GDPR/DSGVO privacy compliance to align with the repository's architectural pillars.

[gemini-code-assist]

The documentation filenames in these links use kebab-case (e.g., mcp-context-layer.md), which is inconsistent with the snake_case convention used for existing documentation files in the repository (e.g., research_positioning.md, failure_taxonomy.md, multi_family_admissibility_benchmark.md). For better maintainability and consistency, these should follow the established snake_case pattern.

Suggested change

	- Use `docs/codex_skills/mcp-context-layer.md` for MCP context layer, CLI, prompt rendering, validation, and adapter work.
	- Use `docs/codex_skills/artifact-validation.md` for deterministic artifacts and regeneration checks.
	- Use `docs/codex_skills/git-pr-workflow.md` for branch sync, commits, pushes, and PR preparation.
	- Use `docs/codex_skills/docs-positioning.md` for README/docs positioning and scope boundaries.
	- Use `docs/codex_skills/mcp_context_layer.md` for MCP context layer, CLI, prompt rendering, validation, and adapter work.
	- Use `docs/codex_skills/artifact_validation.md` for deterministic artifacts and regeneration checks.
	- Use `docs/codex_skills/git_pr_workflow.md` for branch sync, commits, pushes, and PR preparation.
	- Use `docs/codex_skills/docs_positioning.md` for README/docs positioning and scope boundaries.

[gemini-code-assist]

The Repository Style Guide (line 10) identifies "Privacy by design aligned with GDPR / DSGVO Art. 25" as an architectural pillar. Adding an explicit safety rule for agents to maintain these privacy and local sanitization boundaries is crucial to prevent accidental data exposure or policy violations during automated edits.

Suggested change

	- Do not commit, push, create PRs, or merge unless explicitly requested.
	- Do not commit, push, create PRs, or merge unless explicitly requested.
	- Maintain local sanitization and privacy boundaries (GDPR/DSGVO Art. 25) at all times.

References

1. Privacy by design aligned with GDPR / DSGVO Art. 25, including local sanitization before downstream model or copilot access. ^(link)