04 — Migrate human approval and smart-mode activity

[XMethues]

Parent

#1

What to build

Migrate approval hooks to the normalized activity intake and distinguish real human waiting from smart-mode inference. Human approval must surface as 候旨; automatic smart approval must surface as 推演.

Acceptance criteria

• Documented pre-approval-request and post-approval-response hooks are registered and tolerate additional Hermes keyword arguments.
• A request that actually waits for a human surfaces as 候旨.
• Smart-mode approval checks surface as 推演 and never as 候旨.
• Approval resolution closes the matching in-flight approval state without closing unrelated parallel activity.
• Denial and timeout are neutral: they apply neither a reward nor a penalty.
• A tool blocked by denial or timeout is not subsequently misreported as a failed tool action.
• An approved tool proceeds through ordinary tool outcome classification.
• Human approval has priority over direct tool activity; direct tool activity has priority over smart-mode inference.
• Real-HTTP integration tests cover human approval, smart-mode approval, approval, denial, timeout, and concurrent activity.

Blocked by

#4.