Contributing

Before editing

Read applicable AGENTS.md, current source, tests, accepted decisions, and relevant contracts. A historical backlog status is not a substitute for checking the composition root. Search for an existing owner before adding a new abstraction or process.

Use English for source, tests, documentation, and necessary comments. Keep comments focused on non-obvious constraints rather than narrating syntax. Avoid unrelated refactors in independently released repositories.

A reviewable change

Explain the concrete problem and resulting behavior. For asynchronous work, identify the durable effect, commit point, retry, crash, replay, and rebalance semantics. For security work, name the authority and residual risk. Include the checks actually run and their result; do not claim tests passed because code inspection looked convincing.

Keep protocol changes in the contracts repository and update consumers explicitly. Do not commit secrets, generated local caches, go.work, or dependency overrides as hidden workspace coupling.

Security-sensitive reports

The inspected repositories do not establish a dedicated published vulnerability disclosure address or policy in this documentation baseline. Do not invent one. Use an existing private maintainer channel available to you for sensitive details rather than placing credentials or exploitable deployment information in a public documentation issue.

Source evidence

Reviewed against the source baseline. Seagull-backend-v2/tests/architecture/dependencies_test.go · Seagull-agent-v2/AGENTS.md (local planning evidence) · Seagull-contracts/README.md.