feat(registration): centralize decorated plugin surfaces

[offendingcommit]

Summary

Runtime-gated Hermes plugins can now keep every active surface inside the kit’s decorator contract instead of maintaining a second registration framework. register_plugin accepts an already-filtered declaration set while retaining duplicate rejection, deterministic ordering, optional-skill handling, exact summaries, and one lifecycle receipt.

Existing plugins can adopt decorators without changing their public schemas or handler-owned error envelopes: @tool(schema=..., validate_required=False) deep-copies and validates the original Hermes schema while preserving its required fields for the model.

Validation

• make test (77 passed)
• make build
• persona-voice consumer contract (29 passed against this checkout)
• memory-sync focused and full consumer suites passed against this checkout
• git diff --check

Post-Deploy Monitoring & Validation

• Search gateway logs for registered plugin= after each migrated consumer reload.
• Healthy: one receipt per plugin, exact active names, no schema or import failures.
• Failure: missing receipt, duplicate declaration error, schema rejection, or changed handler envelope. Roll back consumer pins before reloading gateways.
• Window/owner: first reload of each migrated plugin and the following 15 minutes, Jonathan.

---