1.4 KiB
Definition of Done
A task is done only when scope is implemented, architecture invariants hold, format/lint/typecheck pass, relevant tests pass, migrations/contracts/docs are updated as needed, no secrets are committed, retrieval changes include RAG regression results, and known limitations are documented.
For asynchronous ingestion or retry tasks, relevant tests must also prove durable Job/Attempt state, bounded retry classification, idempotent duplicate delivery, cleanup-before-retry, preservation of the immutable source, and terminal behavior when cleanup fails. Batch ingestion must cover per-file partial failure and configured limits.
For MCP tasks, contract tests must cover tool discovery, identity propagation, authorization/error boundaries, REST/application-service parity, infrastructure redaction, and the explicitly targeted MCP client compatibility check.
For cluster delivery tasks, completion also requires reproducible production images, Secret-only sensitive configuration, serialized migration, readiness/liveness probes, resource and pod-security defaults, idempotent Helm install/upgrade, rolling-restart verification, durable worker recovery, stable HTTPS Admin/MCP endpoints, and remote WorkBuddy acceptance. Manifests, rendered output, logs and images must be checked for credential leakage. Public-knowledge delivery does not complete or waive V1 user/ACL tasks.