clawmax AGENTS.md

Repository Instructions

Commit Messages

• Every commit subject must start with a lowercase Conventional Commit-style prefix followed by a colon and a space.
• Use the narrowest applicable prefix: feat:, fix:, docs:, test:, refactor:, build:, ci:, chore:, release:, or merge:.
• Keep the subject concise and describe the user-visible or engineering outcome.
• Do not publish an unprefixed commit subject. Check the proposed subject before committing, especially for release-candidate work pushed directly to main.
• Keep commits focused by concern: separate dependency/security remediation, product behavior, tests, documentation, and release metadata when they can be reviewed or reverted independently. Push each focused commit so CI identifies the exact change that introduced or fixed a failure.
• Commit and push as soon as one coherent, directly tested concern is complete. Do not accumulate multiple independently reviewable concerns in the working tree, and do not start the full suite, an image build, or release CI with completed implementation work still uncommitted. If later validation finds a defect, fix it in a new focused commit and push that checkpoint separately.

Repository Ownership

• Keep public host contracts, generic dashboard components, public plugins, and public scoring logic in this repository.
• Keep first-party proprietary plugin manifests, suggested items, implementation details, and plugin-specific tests in the private clawmax-plugins monorepo. Partner-owned or customer-specific plugins may remain separate when they require different access controls. Never copy private source into this repository or the public image.
• Lifecycle and Review are the public product plugins in the current 2.0 phase. Evals, Guardrails, and Optimize are private enterprise plugins. Treat PLUGINS/test/plugin-* as synthetic contract fixtures only; they must not contain or become copies of private product implementations.
• Keep every other plugin private unless its ownership is explicitly changed.
• Plugin enablement must be manageable from the PLUGINS sidebar as well as deployment configuration. Persist an explicit instance selection, including the valid empty selection, and never expose synthetic contract fixtures in the manager. Public documentation may describe the generic host boundary, but must not enumerate private plugin items, rules, prompts, schemas, or implementation details.
• A plugin can represent any ClawMax extension domain. Do not design generic plugin APIs or UI around assumptions that all plugins are guardrails or evals.