Skip to content

AGENTS.md

Latest commit

 

History

History
42 lines (33 loc) · 1.87 KB

AGENTS.md

File metadata and controls

42 lines (33 loc) · 1.87 KB
Raw

Repository guidance

Monorepo context

This repository owns the complete public SN118 system: miner and validator code at the root, Platform and Backroom under apps/, services and workers under services/ and workers/, shared contracts under packages/, benchmark research under research/, and cloud state under infra/.

Start substantial work with:

python3 .agents/skills/ditto-subnet-context/scripts/lookup-context.py "<task>"

Use .agents/skills/ditto-subnet-worktree for isolation. Do not use multi-repository temp clones or cross-repository synchronization for components already present in this tree. Read the nearest nested AGENTS.md or CLAUDE.md before editing a component.

Semantic-release commit types

  • Do not use test: as a commit or pull-request title prefix; it is not a valid semantic-release type in this repository.
  • Test-only changes must use the chore(tests): scope, for example chore(tests): pin legacy confirmation regression.

Git-backed Docker build contexts

  • Never pin a Git build context with the legacy URL-fragment form https://github.com/OWNER/REPO.git#<commit-sha>. A clean Docker builder may fail because the commit SHA is not an advertised branch or tag.
  • For a commit on main, use BuildKit's structured query syntax with both an advertised ref and the full 40-character checksum: https://github.com/OWNER/REPO.git?ref=refs/heads/main&checksum=<commit-sha>. The ref makes the repository fetchable, and the checksum makes the build fail closed if the ref does not resolve to the expected commit.
  • Apply the same rule to other branches or tags: use their fully qualified ref plus a full checksum. Do not replace an immutable checksum with a floating ref alone.
  • Verify every changed remote Git context with a fresh or empty BuildKit builder. A successful build against a warm local cache is not sufficient.