/hapo:test and /hapo:code-review#

CafeKit separates execution verification from adversarial review.

/hapo:test#

Use:

/hapo:test --full
/hapo:test <scope>

Typical verdicts:

• PASS
• FAIL
• PARTIAL
• NO_TESTS

What matters:

• tests should not be fabricated
• compile or build failures must not be hidden
• NO_TESTS should not be treated as automatic success

/hapo:code-review#

Use:

/hapo:code-review --pending

This workflow focuses on:

• correctness
• regressions
• security
• contract drift
• missing evidence

Recommended Sequence#

/hapo:develop -> /hapo:test -> /hapo:code-review

When A Task Is Really Done#

A task should only be synchronized as done when:

• implementation exists
• evidence exists
• test verdict is acceptable
• review verdict is acceptable

If any of those are missing, keep the task open.