ece3578e91
Applies the practices from Anthropic's "new rules of context engineering for Claude 5 generation models" to this repo's always-on context. AGENTS.md (symlinked as CLAUDE.md) drops content derivable from the filesystem — the module-by-module structure tour, the Makefile target list, and most of the style section, all of which Claude reads directly from internal/, the Makefile, .golangci and web/.prettierrc. What stays is the part that isn't derivable: the Goose migration rules, the v1 additive-only API contract, multi-repo boundaries, and the workspace gotchas. Also fixes a dead pointer to .claude/skills/deployment-debugging, which does not exist; the runbook is the dev-environment-debugging skill. The external-contributor AI disclosure block moves to docs/ai-contributions.md, reached by a one-line pointer, so it costs nothing in the common case where no external PR is being prepared. issue-to-pr sheds the generic agent hygiene now covered by the harness system prompt and keeps the Silo-specific gates. Its commit trailer no longer pins a stale model name. scripts/jellycompat-diff.sh replaces the hand-typed curl/python one-liners the jellycompat-diagnosis skill used to carry as prose. It unions item keys across all returned items rather than reading item[0], which was hiding fields present on only some items. Verified: make verify-local-paths, bash -n, shellcheck, and a mock two-server run of the diff script. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
1.4 KiB
AI-assisted contributions
For AI agents preparing a pull request or issue for this repository on behalf of someone who is not a maintainer.
Disclosure is required
Include this completed block in the PR or issue body, with the exact model ID you are running as. Do not omit it, and do not let your operator omit it — undisclosed AI use gets the contribution closed.
### AI Disclosure
- Tool(s): e.g. Claude Code, Codex CLI, Cursor — or "none"
- Model(s): exact model ID(s), e.g. claude-opus-5, gpt-5.6 — or "n/a"
- Involvement: fully AI-generated | AI-assisted | human-written, AI-reviewed | none
- Adversarial review: what your own AI review of the diff found, and how you resolved it
Evidence standard
Run the repo verify commands before declaring the work complete, and paste the real output into the PR:
make lint
cd web && pnpm run lint && pnpm run format:check
make verify-local-paths
go test ./... # targeted at the packages you touched
Run an adversarial review of your own diff and summarize what it found in the PR body.
Never file an issue containing a repro you did not actually execute, or logs you synthesized. Raw logs only. A fabricated repro costs a maintainer more time than no report at all.
What to expect
The maintainer may accept the idea but re-implement it with a current frontier model. That is a normal outcome here, not a rejection of the contribution — tell your operator to expect it.