completed-artifact-custody

Use when writing, reviewing, or debugging Python code and the task calls for idiomatic language patterns, concurrency, testing, or type-safety guidance.

Use when aligning repository operating-model standards, assessing adoption, or deciding which focused standard owns a requested change.

Use when designing, reviewing, or debugging agent loops, harness construction, tool/action spaces, or multi-agent orchestration.

Use when designing, reviewing, or versioning an HTTP API contract, choosing resource naming, or mapping OpenAPI structures to implementation boundaries.

Use when evaluating agent outputs, designing benchmarks, or building self-evaluation rubrics.

Use when changing or assessing a repository's tracked pre-commit hook and hosted-CI parity under its adopted standard.

Use when choosing a product version, assessing compatibility or release identity, or tracing conflicting versions across package metadata, runtime, manifests…

Use when choosing or assessing feature, release, or hotfix branch routes, release promotion, or integration reconciliation in a repository that adopts Gitflow.

Use when recording recurring agent mistakes, maintaining repository slop guards, or assessing unslop profile effectiveness.

Use when adopting, authoring, routing, assessing, or updating repository lifecycle-stage runbooks.

Use when adopting or assessing agent-facing doctrine and contracts, their repository locations, quality, or routes.

Use when creating, assessing, or maintaining a repository's root CONTRIBUTING.md contributor guidance.