Plan: Create CLAUDE.md for agent-core-artefacts#

Summary#

Create a CLAUDE.md at the repo root that describes agent-core-artefacts as a document/artefact storage repository (not a service), its directory structure, naming conventions, and branch/PR rules. No build system exists — this must be explicitly stated.

Files#

Steps#

1. Create CLAUDE.md at the repo root with the following sections:
   • What this repo is — document storage for AgentSDE pipeline artefacts (architecture docs, ARDs, RFCs, planning docs, test cases, per-issue task files). Not a service, no runtime.
   • Directory structure — describe docs/ (subdirs: arch/, ard/, rfc/, planning/, test-cases/, testing/) and tasks/ (subdirs: production/AgentSDE/<repo>/gh-<N>/, e2e/AgentSDE/<repo>/gh-<N>/). Each task directory contains plan/, meta/, and optionally input/, changes/ subdirectories.
   • Naming conventions — task dirs follow gh-<issue-number> pattern, grouped by environment (production/e2e) and org/repo.
   • Dev workflow — explicitly state no package.json, no Makefile, no build/test/lint commands.
   • Branch & PR rules — feat/<issue-number>-<slug> or fix/<issue-number>-<slug>, PR body must include Closes #<N>, never commit directly to master.
2. Verify CLAUDE.md contains no stale references to agent-core commands or environment variables that don't apply.

Verification#

• CLAUDE.md exists at repo root and is well-formed Markdown
• All documented directories match actual repo structure
• No references to build/test/lint commands that don't exist

Risks#

• Directory structure may evolve as new artefact types are added — the file should note this is a living document