Update CLAUDE.md: fix CI section, test flags, add memory file note

[PeterRounce]

Summary

• Fix CI section to match actual workflow (race detection, govulncheck, Docker builds)
• Add -race -count=1 flags and HOST_DOMAIN requirement to testing section
• Add Memory File section for cross-session context persistence

Test plan

• Verify CLAUDE.md accurately reflects .github/workflows/ci.yml
• Verify test commands work as documented

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Updates the repository’s Claude Code guidance to better reflect the current CI workflow and local testing requirements, and adds a note about cross-session context persistence.

Changes:

• Update the recommended go test invocation to include -race -count=1.
• Expand the CI section to include govulncheck and Docker image builds (card + webproxy).
• Add a “Memory File” section describing where to persist session learnings.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The CI workflow doesn’t run govulncheck ./... directly; it runs it via go run golang.org/x/vuln/cmd/govulncheck@latest ./... (so it works without a preinstalled binary). To keep this section accurate and copy/pasteable, update the documented command or explicitly note that govulncheck must be installed if using the shorter form.

Suggested change

	- `govulncheck ./...`
	- `go run golang.org/x/vuln/cmd/govulncheck@latest ./...`

[Copilot]

This hard-coded ~/.claude/projects/.../MEMORY.md path is machine/user specific and won’t exist for most contributors or CI. Consider documenting the concept generically (or using a repo-relative path) so the guidance remains applicable across environments.

Suggested change

	After completing a set of changes, update the persistent memory file at `~/.claude/projects/-home-user-boltcard-hub/memory/MEMORY.md` with any new patterns, conventions, or project facts discovered during the session. Keep it concise and organized by topic. This helps maintain context across conversations.
	After completing a set of changes, update the persistent memory file associated with this repository (for example, a `MEMORY.md` file under `.claude/memory/` in the repo root) with any new patterns, conventions, or project facts discovered during the session. Keep it concise and organized by topic. This helps maintain context across conversations.