06 — Contract legacy activity delivery

[XMethues]

Parent

#1

What to build

Complete the contract phase after every Hermes activity category has migrated: remove the file-backed and legacy HTTP delivery paths so the versioned direct POST seam is the only activity intake.

Acceptance criteria

• Runtime activity no longer depends on pet_state.json or its read, age, or freshness semantics.
• Every supported Hermes hook category sends only the normalized, versioned direct POST envelope.
• The /hook/event alias is removed.
• Old unversioned payload shapes are rejected.
• The /state endpoint reports the new aggregate activity model.
• Restarting the plugin-owned server begins with idle activity and does not replay transient activity from disk.
• Failed activity delivery is logged and dropped; there is no retry, queue, or replay path.
• No event is rejected merely because its timestamp is older than another accepted event.
• Full real-HTTP and hook-adapter regression tests prove the old and new paths cannot both apply one Hermes action.
• Existing tests remain green after obsolete compatibility coverage is removed.

Blocked by

#5 and #6.