Clawpito v6 and the Hygiene-First Agentic OS

What changed

Clawpito v6 turns coding into a governed workflow inside Clawpy: review, plan, apply scoped fixes, validate, report readiness, and preserve a useful audit trail for the human operator.

1. Release readiness is now a first-class signal

The coding lane can surface readiness reports, confidence signals, unresolved blockers, hygiene findings, and policy concerns before a human decides whether to push, stage, or continue.

review -> plan -> fix -> test -> score -> report -> human decision

2. Hygiene is part of the product contract

Clawpito checks module budgets, broad exception policy, duplicate mechanics, architecture layering, and failure-path testing. The aim is simple: powerful automation should not create the next monolith.

• Small service boundaries
• Visible failures instead of silent swallows
• Human-readable release and audit summaries